-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow setting machineNetwork CIDR in hcp CLI #3758
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
In Baremetal (agent based) installs, it is necessary to define a machine network CIDR in addition to the clusterNetwork and serviceNetwork CIDRs. The HostedCluster CR supports this under spec.networking.machineNetwork but this is not an option for
hcp create cluster agent
Currently, --cluster-cidr and --service-cidr exist as options, this issue proposes adding --machine-cidr for ipv4 and ipv6 CIDR entries.
The text was updated successfully, but these errors were encountered: