-
Notifications
You must be signed in to change notification settings - Fork 1
Upstream update to v1.3.2 #76
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
Conversation
| - ServicePrincipal | ||
| - ManualServicePrincipal | ||
| - UserAssignedMSI | ||
| - ServicePrincipalCertificate |
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.
This looks like a breaking change in theory, but in practice it is not, as UserAssignedMSI never worked, see this comment for more details.
In any case we should not be affected, because all vintage workload clusters are using ServicePrincipal type.
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.
just for reference i did test it in capz 1.6.x and it worked for me using the UA assigned to the MC node
apparently the actual issue with UA Identity was fixed in CAPZ 1.4 kubernetes-sigs/cluster-api-provider-azure#1104
👍
| type: string | ||
| description: AdditionalTags is an optional set of tags to add to Azure resources managed by the Azure provider, in addition to the ones added by default. | ||
| type: object | ||
| addonProfiles: |
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.
We are still not using CAPZ managed clusters, so not affected by this.
bavarianbidi
left a comment
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.
lgtm for CAPI (Clippy)
primeroz
left a comment
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.
LGTM
Towards https://github.com/giantswarm/giantswarm/issues/24551
Changes
Highlighted upstream changes that can be relevant for vintage workload clusters
(with specified upstream cluster-api-provider-azure versions)
v1.3.0Add support for Service Principal with Certificate auth using AAD pod identity. This looks like a breaking change in theory, sinceAzureClusterIdentityUserAssignedMSItype is removed, but in practice it is not, becauseUserAssignedMSInever worked, see this comment for more details. In any case Giant Swarm workload clusters are not be affected, because all of them are usingServicePrincipaltype (I checked all workload clusters that are deployed at the time of writing on 2022-12-17) and this breaking change is reverted in the next minor release.Upstream cluster-api-provider-azure release notes