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
Add ipFamily option to clusterNetwork API #9652
Add ipFamily option to clusterNetwork API #9652
Conversation
Signed-off-by: Rastislav Szabo <rastislav@kubermatic.com>
Signed-off-by: Rastislav Szabo <rastislav@kubermatic.com>
Signed-off-by: Rastislav Szabo <rastislav@kubermatic.com>
Signed-off-by: Rastislav Szabo <rastislav@kubermatic.com>
Signed-off-by: Rastislav Szabo <rastislav@kubermatic.com>
Signed-off-by: Rastislav Szabo <rastislav@kubermatic.com>
/retest |
LGTM label has been added. Git tree hash: 2538d2356137aa37e2763cae70d08fd2550db6e7
|
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: imharshita, lsviben, rastislavs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Review the full test history Silence the bot with an |
/retest |
1 similar comment
/retest |
What does this PR do / Why do we need it:
Adds optional
ipFamily
option to theclusterNetwork
API, so that dual-stack clusters can be created without specifying pods and services CIDRs (which can now be defaulted for dual-stack clusters as well).Does this PR close any issues?:
Fixes #9616
Special notes for your reviewer:
Documentation:
Does this PR introduce a user-facing change?: