We would love to see support for a Kubernetes Private Cluster where the following configurations are applied:

• No Public IPs for Nodes: Ensure that nodes in the cluster don’t receive any public IPs, improving security by keeping the internal infrastructure isolated from external networks.

• Service Exposure via LoadBalancer: Allow services to be exposed securely using a LoadBalancer, providing controlled access without the need for public-facing nodes.

This setup would enable more secure, private clusters while still allowing external traffic to reach specific services via managed, secure entry points (LoadBalancers). It’s the perfect blend of security and usability, ensuring that sensitive infrastructure remains isolated while still making applications accessible as needed.

Would love to see this feature added for better flexibility and security in Kubernetes deployments!