I walk you through how to create your VPC manually to install OCPv4 on AWS dashboard.
"install-config.yaml" should include 3 private and 3 subnet IDs as follows. And you should select machineCIDR in your VPC CIDR.
networking:
clusterNetwork:
- cidr: 10.128.0.0/14
hostPrefix: 23
machineCIDR: 10.0.0.0/16
networkType: OVNKubernetes
serviceNetwork:
- 172.30.0.0/16
platform:
aws:
region: ap-northeast-1
userTags:
user: test
subnets:
- subnet-08b0dcab7875eaa71
- subnet-0371bc505996d580f
- subnet-09e967834e7e18a87
- subnet-0f4220dc1dfb8b467
- subnet-0c86ef8e6ed2e68a5
- subnet-04fc969510e8b7d1f
Type | Subnet Name | CIDR |
---|---|---|
Private | a-northeast-1a-private-subnet | 10.0.0.0/20 |
Private | a-northeast-1c-private-subnet | 10.0.16.0/20 |
Private | a-northeast-1d-private-subnet | 10.0.32.0/20 |
Public | a-northeast-1a-public-subnet | 10.0.128.0/20 |
Public | a-northeast-1c-public-subnet | 10.0.144.0/20 |
Public | a-northeast-1d-public-subnet | 10.0.160.0/20 |
I will create VPC CIDR with "10.0.0.0/16" which is matched with "machineCIDR" in install-config.yaml
Enable enableDnsHostnames as follows. enableDnsSupport is enabled by default.
Creating 3 private subnets as repeating the following operation.
Creating 3 public subnets as repeating the following operation.
In this case, the public subnet routing table is used with the VPC default routing tables by default. You can custom your public subnet routing table according to your use cases. Such as creating each routing table for each public subnet. Anyway we need to create another routing table for each private tables as reating the following operations.
Change current routing table association to new each one as follows. We need to configure each NAT Gateway to each routing table on each private subnet. This is more stable than sharing one NAT Gateway with all private subnet.
Attach the IGW to your VPC.
Add routing rule for IGW to public subnet routing tables.
Add routing rule for NAT Gateway to each routing table on each private subnet.
Done.