Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale docker-for-desktop-robot added the lifecycle/stale label Dec 5, 2018.

How to install compiler for c++ on mac. How to get texture packs for minecraft for mac. Please, check. Issues without logs and details cannot be debugged, and will be closed. • I have tried with the latest version of my channel (Stable or Edge) • I have submitted Diagnostics • I have included the Diagnostics ID in this Issue • Windows Version: Win 10 pro • Docker for Windows Version: 18.03.0-ce-win58 (16761) I have installed the nginx-ingress-controller (0.10.2 from Kubernetes github) on my Kubernetes cluster and it seems to work fine.

However, it exposes the node internal IP which is not directly accessible from a browser executing outside the cluster. Expected behavior It would be great to have a forwarding to localhost as it is the case with the LoadBalancer, but I suspect that it means a special ingress controller support inside 'kubernetes for windows' Actual behavior The node internal IP is used as the exposed IP, this IP is unfortunately not accessible directly from the browser running on the main host. Information Steps to reproduce the behavior • Install nginx-ingress-controller as specified here: [(note: I had some pb with more recent versions) • Create an ingress test case • kubectl get ing should show the node internal IP as the ADDRESS field.

I got the ingress to work fine on docker-for-win by following the install instructions for mac located here kubectl apply -f kubectl apply -f That will create the ingress controllers. Then you just need to create an ingress for one of your services Example: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: vote-ingress spec: rules: - host: vote.local.com http: paths: - path: / backend: serviceName: vote servicePort: 5000. I also followed (on Windows) steps and it seems I am hitting the nginx-ingress-controller but getting the default 404. Likewise, the /healthz endpoint returns 200 The only difference in my set up is I need https (TCP 443) to work. Furthermore, in metadata, I added annotations: kubernetes.io/ingress.class: 'nginx' nginx.org/ssl-services: 'my-svc' nginx.ingress.kubernetes.io/ssl-redirect: 'false' and finally applied namespaces 'ingress-nginx' as well. Does someone have experience or can help with this development case?