Private Kubernetes clusters now available

Starting today, Kubernetes clusters you create with Container Engine for Kubernetes using the Console are VCN-native by default. VCN-native clusters are completely integrated with your Virtual Cloud Network (VCN) and you can make them private or public. Your cluster worker nodes and load balancers are already part of the VCN; you can now add the Kubernetes API endpoint to the VCN too.

Regular VCN routing and firewall rules control access to the Kubernetes API endpoint and make it accessible from a corporate network only, or via a bastion host, or by specific SaaS services.

For more information, see Container Engine and Kubernetes Concepts.