Get a LoadBalancer for your private Kubernetes cluster

Click for: original source

In this tutorial, author will walk through how you can expose a Service of type LoadBalancer in Kubernetes, and then get a public, routeable IP for any service on your local or dev cluster through the new inlets-operator. By Alex Ellis.

The inlets-operator is a Kubernetes controller that automates a network tunnelling tool I released at the beginning of the year named inlets. Inlets can create a tunnel from a computer behind NAT/firewall/private networks to one on another network such as the internet. Think of it like “Ngrok, but Open Source and without limits”.

Alex Ellis

First we’ll create a local cluster using K3d or KinD, then create a Deployment for Nginx, expose it as a LoadBalancer, and then access it from the Internet.

The article walks you through:

  • Prerequisites
  • Option A – Install your local cluster with k3d
  • Option B – Install your local cluster with KinD
  • Create a Cloud Access Token
  • Deploy the inlets-operator into your cluster
  • Create a test deployment
  • Expose Nginx as a LoadBalancer
  • Access your local cluster service from the Internet
  • Management and the CRD

… and more. Plenty of screen shots and good explanation of all the commands you will use to run your cluster. There is also link to video demo. By using inlets and the new inlets-operator, we can now get a public IP for Kubernetes services behind NAT, firewalls, and private networks. Exciting!

[Read More]

Tags devops kubernetes containers microservices