title: deployment on minikube locally
body: <p>I have deployed and created services for  <code>socketcluster</code>, <code>scc-broker</code> and <code>scc-state</code> on <code>kubernetes</code> locally via <code>minikube</code> directly through using the docker-files (see this <a href="https://github.com/SocketCluster/socketcluster/tree/master/kubernetes" rel="nofollow noreferrer">link</a> for <code>.yaml</code> files). And I have also created a service for <code>ingress</code> within the same cluster with the <code>.yaml</code> file provided in the link that I have mentioned.  As far as I understand by default these services are of <code>ClusterIP</code> type. </p>
  
  <p>Deployment of the services is working properly on the vm (minikube).
  Status is set to running on the Kubernetes dashboard for</p>
  
  <ul>
  <li><p>pods</p></li>
  <li><p>deployment</p></li>
  </ul>
  
  <p>But the issue I am facing is that there is no public endpoints exposed from scc-state, scc-broker, socketcluster server.
  So currently I am not able to understand how do I access the services externally i.e. outside the virtual machine (that is running on minikube).</p>
  
  <p>The images were built from the kubernetes yml files directly, with the ingress TLS security disabled.</p>
  
  <p>Am I missing out on any aspect as to how to access the socketcluster on the host machine? Should I specify the service type to any other type other than <code>ClusterIP</code> as I know that using this type ensures that the service will be exposed within cluster only. But again my doubt is that if I am using <code>ingress</code> , it should help access the services outside the vm. Do I need to have an <code>ingress controller</code> separately such as NGINX ?</p>
  
  <p>Any lead will be appreciate.</p>
  
  <p>Thanks!     </p>
  
  <p>P.S. Following <a href="https://github.com/SocketCluster/socketcluster/blob/master/scc-guide.md" rel="nofollow noreferrer">this</a> guide to for the deployment. </p>