Oracle Cloud (OCI) — Network Configuration for Kubernetes Cluster
When you are creating a Kubernetes Cluster on OCI, you have the option to use a “Quick Create” workflow to automatically create the Kubernetes cluster/nodes along with the required network resources.
However, in many cases the creator of a Kubernetes cluster does not have the access needed to create the network resources, as the network resources are usually managed by Network Admins. In that case, Kubernetes clusters need to leverage the existing network resources while creating the Kubernetes Cluster, by using the “Custom Create” workflow.
Before starting the creation of Kubernetes cluster, it is very important to ensure that the VCN/Subnet’s Route Tables and Security Lists are accurately configured as required by the Kubernetes Cluster.
The following links give examples of the required network configurations for custom creation of different types of Kubernetes Clusters.
- Cluster with Flannel CNI Plugin, Public Kubernetes API Endpoint, Private Worker Nodes, and Public Load Balancers
- Cluster with Flannel CNI Plugin, Private Kubernetes API Endpoint, Private Worker Nodes, and Public Load Balancers
- Cluster with OCI CNI Plugin, Public Kubernetes API Endpoint, Private Worker Nodes, and Public Load Balancers
- Cluster with OCI CNI Plugin, Private Kubernetes API Endpoint, Private Worker Nodes, and Public Load Balancers
Only after you have accurately configured the network resources, then you can use the “Custom create” workflow to create the Kubernetes cluster (by following the steps detailed in Oracle Docs).
Want to talk about it? Join our public Slack channel to discuss with other Oracle developers!
