title: Exposure of Eclipse-Che
body: <p>We want to expose a test eclipse-che deployment on a corpo VM, so it can be accessed from our browsers through our corpo network. It's being deployed via <code>minikube</code> and <code>chectl</code>.</p>
  <p>Steps to recreate:</p>
  <ul>
  <li>Minikube version: v1.25.2</li>
  <li>Kubectl version: v1.23.4</li>
  <li>Chectl vesrion: 0.0.20220216</li>
  </ul>
  <p>References: <a href="https://www.eclipse.org/che/docs/che-7/installation-guide/installing-che-on-minikube/" rel="nofollow noreferrer">https://www.eclipse.org/che/docs/che-7/installation-guide/installing-che-on-minikube/</a></p>
  <p><code>minikube start --addons=ingress --memory=8192</code> (Uses Docker)</p>
  <p><code>chectl server:deploy --platform minikube</code></p>
  <p>Here's the Output we get:</p>
  <pre><code> ✔ Eclipse Che 'next' has been successfully deployed.
      ✔ Documentation             : https://www.eclipse.org/che/docs/
      ✔ --------------------------------------------------------------------------
      ✔ Users Dashboard           : https://192.168.49.2.nip.io/dashboard/
      ✔ --------------------------------------------------------------------------
      ✔ Plug-in Registry          : https://192.168.49.2.nip.io/plugin-registry/v3/
      ✔ Devfile Registry          : https://192.168.49.2.nip.io/devfile-registry/
      ✔ --------------------------------------------------------------------------
      ✔ Dex user credentials      : che@eclipse.org:admin
      ✔ Dex user credentials      : user1@che:password
      ✔ Dex user credentials      : user2@che:password
      ✔ Dex user credentials      : user3@che:password
      ✔ Dex user credentials      : user4@che:password
      ✔ Dex user credentials      : user5@che:password
      ✔ --------------------------------------------------------------------------
  Command server:deploy has completed successfully in 09:11.
  </code></pre>
  <p>Apparently <em>Users Dashboard</em> is available at: <a href="https://192.168.49.2.nip.io/dashboard/" rel="nofollow noreferrer">https://192.168.49.2.nip.io/dashboard/</a></p>
  <p>Here's what we get from <code>minikube service list</code>:</p>
  <pre><code>|-------------------------|-----------------------------------------|--------------|---------------------------|
  |        NAMESPACE        |                  NAME                   | TARGET PORT  |            URL            |
  |-------------------------|-----------------------------------------|--------------|---------------------------|
  | cert-manager            | cert-manager                            | No node port |
  | cert-manager            | cert-manager-webhook                    | No node port |
  | default                 | kubernetes                              | No node port |
  | devworkspace-controller | devworkspace-controller-manager-service | No node port |
  | devworkspace-controller | devworkspace-controller-metrics         | No node port |
  | devworkspace-controller | devworkspace-webhookserver              | No node port |
  | dex                     | dex                                     | No node port |
  | eclipse-che             | che-dashboard                           | No node port |
  | eclipse-che             | che-gateway                             | No node port |
  | eclipse-che             | che-host                                | No node port |
  | eclipse-che             | devfile-registry                        | No node port |
  | eclipse-che             | plugin-registry                         | No node port |
  | eclipse-che             | postgres                                | No node port |
  | ingress-nginx           | ingress-nginx-controller                | http/80      | http://192.168.49.2:30743 |
  |                         |                                         | https/443    | http://192.168.49.2:32641 |
  | ingress-nginx           | ingress-nginx-controller-admission      | No node port |
  | kube-system             | kube-dns                                | No node port |
  |-------------------------|-----------------------------------------|--------------|---------------------------|
  </code></pre>
  <p>And finally <code>kubectl get ingress -n eclipse-che</code>:</p>
  <pre><code>NAME      CLASS     HOSTS                 ADDRESS        PORTS     AGE
  che       &lt;none&gt;    192.168.49.2.nip.io   192.168.49.2   80, 443   26m
  </code></pre>
  <p>What shall be done after this point?</p>
  <p>Things I've tried, testing with various ports:</p>
  <p><code>kubectl expose deployment che --type=NodePort -n eclipse-che --port PORT</code></p>
  <p><code>kubectl port-forward -n che svc/che PORT:PORT</code></p>
  <p>or</p>
  <p><code>ssh -i ~/.minikube/machines/minikube/id_rsa docker@$(minikube ip) -NL \{MACHINE_IP}:PORT:0.0.0.0:PORT</code></p>
  <p>With the last command and 30743/32641 as PORTS, at least I can get a <code>NGINX 404</code>on my browser when accessing {MACHINE_IP}:30743 or {MACHINE_IP}:32641 but nothing on <code>/dashboard</code> URI.</p>
  <p>Similar question that didn't help:
  <a href="https://stackoverflow.com/questions/64925345/access-k8s-service-hosted-by-minikube-from-another-machine">access k8s service hosted by minikube from another machine</a></p>
  <p>Well, I'm a little bit clueless, any help appreciated.</p>
  <p>Thanks for reading.</p>