...
A quick-start guide can be found here: httphttps://kubernetes.io/docs/gettingsetup/pick-startedright-guides/dockersolution/
This will set up a Kubernetes cluster running locally on your VM.
...
The alternative to NodePort is using a LoadBalancer , which is not yet supported on OpenStack.(see below).
Ingress Loadbalancer
If you're running on GCE, you will need to run a GLBC to handle routing your ingress traffic.
For all other platforms, an nginx instance running within your cluster can serve as the Ingress Loadbalancer
In addition to routing traffic to your running services, these loadbalancers can also handle things like TLS-termination, authentication via basic-auth (working) or OAuth2 (still in ongoing development), and providing unified custom error messages for all services.
Caveats:
- The pod must run on a node with a Public IP
- Your server must have a real DNS OR you must run your own bind DNS server within the cluster
Labels and Selectors
You can choose which pods a service affects by applying labels to the Pod(s) in question.
...
Namespaces are synonymous with "users" in NDS Labs, and allow you to encapsulate services from one another even further - Services cannot communicate between namespaces.