-
Notifications
You must be signed in to change notification settings - Fork 190
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
network: fix generation of VIPs for single- and dual-stack setups #1628
base: master
Are you sure you want to change the base?
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cc @cybertron |
/lgtm Seems fine. I assume this is related to deploying single stack clusters on dual stack envs? |
/hold Yes, the issue with current state is that we do not generate a valid install-config yaml for a single-stack cluster with dual-stack hosts. For such a scenario (allowed by syntax of config.sh) we put dual-stack VIPs in install-config.yaml but only single cluster network. This is illegal and does not pass the basic validations. With this fix I want to be explicit as the VIP configuration goes. I am still not allowing to have single VIP setup with dual-stack cluster but extending feature set is not my goal, all I want first is to remove a scenario that prevents installation when in general it should work |
@mkowalski: The following tests failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
No description provided.