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
Match public IP address SKU to load balancer SKU for Azure #10678
Match public IP address SKU to load balancer SKU for Azure #10678
Conversation
Skipping CI for Draft Pull Request. |
/test pre-kubermatic-e2e-azure-ubuntu-1.24 |
@embik can we move forward with this one? :D |
There's still no MC release that includes the necessary fields ... |
6a8f9bf
to
241c7f1
Compare
…B clusters Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
241c7f1
to
d1f48e6
Compare
/test pre-kubermatic-e2e-azure-ubuntu-1.24 |
/retest |
1 similar comment
/retest |
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
LGTM label has been added. Git tree hash: aeb226e50002d5b9411aa99c8aad73c62d9c80ee
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, embik 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 |
What does this PR do / Why do we need it:
This PR fixes an issue with the
standard
load balancer SKU that apparently went unnoticed since #7208: When running with that LB SKU and using public IPs on your nodes, the public IP address SKU not matching the LB SKU will fail load balancer reconciliation.Through a new field in Azure's cloud spec in MC, the IP address SKU can now be set (previously, it was defaulted to basic unless dualstack was used). This PR defaults the IP address SKU on any MachineDeployment to
standard
to match the LB.This needs a new MC release, so the PR is a draft and there's an override for a fresh MC commit.
I also took the liberty to upgrade our conformance test scenarios to the
standard
LB. It's the SKU recommended by Azure anyway.Does this PR close any issues?:
Fixes #10673
Special notes for your reviewer:
Documentation:
Does this PR introduce a user-facing change?: