You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Added NetworkSpec option for subnet name
* Added logic to select specific subnet by name
* Updated templates to have configurable IP CIDRs
* Doc updates for new fields and environment variables
Copy file name to clipboardExpand all lines: docs/src/topics/vpc.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,11 @@ spec:
61
61
62
62
Reference to LinodeVPC object is added to LinodeCluster object which then uses the specified VPC to provision resources.
63
63
64
+
### Additional Configuration
65
+
By default, the VPC will use the subnet with the `default` label for deploying clusters. To modify this behavior, set the `SUBNET_NAME` environment variable to match the label of the subnet to be used. Make sure the subnet is set up in the LinodeVPC manifest.
66
+
67
+
Additionally, the `VPC_NETWORK_CIDR` and `K8S_CLUSTER_CIDR` environment variables can be used to change which CIDR blocks are used by the VPC and its clusters. `VPC_NETWORK_CIDR` designates the range used by the VPC, while `K8S_CLUSTER_CIDR` designates the range used by clusters for nodes. The `K8S_CLUSTER_CIDR` should be within the `VPC_NETWORK_CIDR`.
68
+
64
69
## Troubleshooting
65
70
### If pod-to-pod connectivity is failing
66
71
If a pod can't ping pod ips on different node, check and make sure pod CIDRs are added to ip_ranges of VPC interface.
0 commit comments