-
Notifications
You must be signed in to change notification settings - Fork 132
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
Dualstack support with AWS CCM #1466
Conversation
0f30758
to
f9a7f4d
Compare
/retest |
9d8ca61
to
359414b
Compare
Signed-off-by: Sachin Tiptur <[email protected]>
/retest |
/lgtm |
LGTM label has been added. Git tree hash: 22fc5bbfacd271fc06fc0f6fc0bd8e2bf86ba984
|
/assign @ahmedwaleedmalik |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
Please propagate this change to OSM as well
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, sachintiptur 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 |
OSM does not need these changes as Kubermatic imports only the structure from MC and does configure the cloud-config for control plane node. |
Signed-off-by: Sachin Tiptur <[email protected]> Signed-off-by: Sachin Tiptur <[email protected]>
Signed-off-by: Sachin Tiptur <[email protected]> Signed-off-by: Sachin Tiptur <[email protected]>
Signed-off-by: Sachin Tiptur [email protected]
What this PR does / why we need it:
This PR adds NodeIPFamilies to GlobalOpts struct. This is required in Kubermatic repo for adding dual stack support with AWS CCM which is enabled with control plane version 1.24 onwards.
Which issue(s) this PR fixes:
Fixes #
What type of PR is this?
/kind feature
Special notes for your reviewer:
This is only a struct change, the actual logic will be added in Kubermatic repo.
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: