Creating a Control Plane Subnet (VCN-Native Pod)
Create the following resources in the order listed:
-
Control plane security list
-
Control plane subnet
Create a Control Plane Security List
Create a security list. See Creating a Security List. For Terraform input, see Example Terraform Scripts (VCN-Native Pod).
For this example, use the following input for the control plane subnet security list. The kubernetes_api_port
is the port used to access the Kubernetes API: port 6443. See also Workload Cluster Network Ports (VCN-Native Pod).
Console property |
CLI property |
---|---|
|
|
One egress security rule:
|
One egress security rule:
|
Twelve ingress security rules: |
Twelve ingress security rules:
|
Ingress Rule 1
|
Ingress Rule 1
|
Ingress Rule 2
|
Ingress Rule 2
|
Ingress Rule 3
|
Ingress Rule 3
|
Ingress Rule 4
|
Ingress Rule 4
|
Ingress Rule 5
|
Ingress Rule 5
|
Ingress Rule 6
|
Ingress Rule 6
|
Ingress Rule 7
|
Ingress Rule 7
|
Ingress Rule 8
|
Ingress Rule 8
|
Ingress Rule 9
|
Ingress Rule 9
|
Ingress Rule 10
|
Ingress Rule 10
|
Ingress Rule 11
|
Ingress Rule 11
|
Ingress Rule 12
|
Ingress Rule 12
|
Create the Control Plane Subnet
Create a subnet. See Creating a Subnet. For Terraform input, see Example Terraform Scripts (VCN-Native Pod).
Use the following input to create the control plane subnet. Use the OCID of the VCN that was created in Creating a VCN (VCN-Native Pod). Create the control plane subnet in the same compartment where you created the VCN.
Create either a NAT private control plane subnet or a VCN private control plane subnet. Create a NAT private control plane subnet to communicate outside the VCN.
The name of this subnet must be exactly "control-plane".
Console property |
CLI property |
---|---|
|
|
The difference in the following private subnet is the VCN private route table is used instead of the NAT private route table.
Console property |
CLI property |
---|---|
|
|