Guides you through configuring the Hypershield Controller by setting internal network subnets and updating the bootstrap.yaml file to prevent IP address conflicts prior to onboarding and security enablement.
Configure the Hypershield Controller before onboarding and security enablement.
The Hypershield Controller, by default, uses 10.20.0.0/16 and 10.30.0.0/16 IP subnets for setting up internal network connectivity within the Hypershield Controller Kubernetes cluster. If these subnets overlap with any routable networks in your data center environment and you want to avoid routing issues with the controller, update the bootstrap.yaml on the Hypershield Controller. The other option is to deploy the Hypershield Controller with a different set of subnets of /16 size instead of the default. The fields to be updated (with example overrides) in the bootstrap.yaml are:
# Override the bootstrap defaults of 10.20.0.0/16 and 10.30.0.0/16.
# 10.0.0.0/12 is not Cisco-internal routable (e.g. 10.0.0.0/16 through 10.15.0.0/16).
podCIDR: "10.8.0.0/16"
serviceCIDR: "10.9.0.0/16"