Accessing a Service from outside the cluster about dcos-kubernetes-quickstart HOT 5 CLOSED

Hi @vishal-biyani,

For your nginx container, can you share details on the Kubernetes manifests, and image you used? It looks like kube-proxy is routing the traffic, but perhaps your nginx container is listening on a different port than what you have specified.

For your LoadBalancer question, we have not enabled the cloud-provider flags on Kubernetes yet (this is coming shortly), so an external load balancer will not be configured.

At this time, the best way to expose a Kubernetes application is to use the NodePort. We have an example here: https://github.com/mesosphere/dcos-kubernetes-quickstart/blob/master/examples/os-detector/os-detector.md

from dcos-kubernetes-quickstart.

hey @vishal-biyani I have made a demo hoe to expose your web apps externally https://github.com/rimusz/dcos-k8s-beer-demo
Check from https://github.com/rimusz/dcos-k8s-beer-demo#helm-setup part

from dcos-kubernetes-quickstart.

@smugcloud can you please add documentation to our public docs about how a user can access a Service from outside of the cluster? Ping me and let's sync because while I have all the possible solutions on my mind, time is really short for me.

from dcos-kubernetes-quickstart.

Hi @vishal-biyani, we have updated documentation that walks through exposing services. Currently, we support the AWS cloud-provider (configuration flag at Kubernetes package installation), or an Ingress resource.

Let me know if you run into any issues.

from dcos-kubernetes-quickstart.

Is it possible to expose nodeport service via marathon-lb ? If yes , can you please provide a link which can help me understand, how a nodeport service can be exposed via marathon-lb ?

from dcos-kubernetes-quickstart.