Get public TCP LoadBalancers for local Kubernetes clusters. When using a managed Kubernetes engine, you can expose a Service as a "LoadBalancer" and your cloud provider will provision a TCP cloud load balancer for you, and start routing traffic to the selected service inside your cluster. In other words, you get ingress to an otherwise internal service. The inlets-operator brings that same experience to your local Kubernetes cluster by provisioning a VM on the public cloud and running an inlets server process there. Within the cluster, it runs the inlets client as a Deployment, and once the two are connected, it updates the original service with the IP, just like a managed Kubernetes engine.
Features
- Plays well with other LoadBalancers
- Use IPVS for your Kubernetes networking
- Run a private-cloud or a homelab
- Self-host applications and APIs
- Test and share work with colleagues or clients
- Integrate with webhooks and third-party APIs