Upstream update to v1.4.5 #77
Conversation
| description: Type is the type of Azure Identity used. ServicePrincipal, ServicePrincipalCertificate, UserAssignedMSI or ManualServicePrincipal. | ||
| enum: | ||
| - ServicePrincipal | ||
| - UserAssignedMSI |
There was a problem hiding this comment.
This reverts theoretical breaking change from previous minor version.
| properties: | ||
| dnsName: | ||
| type: string | ||
| ipTags: |
There was a problem hiding this comment.
IP tags are optional, so vintage workload clusters are not affected.
| image: | ||
| description: Image is used to provide details of an image to use during VM creation. If image details are omitted the image will default the Azure Marketplace "capi" offer, which is based on Ubuntu. | ||
| properties: | ||
| computeGallery: |
There was a problem hiding this comment.
This replaces now deprecated SharedGallery. Giant Swarm vintage workload clusters are not using these fields, so they are not affected with this change.
| acceleratedNetworking: | ||
| description: AcceleratedNetworking enables or disables Azure accelerated networking. If omitted, it will be set based on whether the requested VMSize supports accelerated networking. If AcceleratedNetworking is set to true with a VMSize that does not support it, Azure will return an error. | ||
| type: boolean | ||
| additionalCapabilities: |
There was a problem hiding this comment.
New optional property. Giant Swarm vintage Azure clusters are using AzureMachine only as a very basic control plane CR, so they are not affected by this change.
| acceleratedNetworking: | ||
| description: AcceleratedNetworking enables or disables Azure accelerated networking. If omitted, it will be set based on whether the requested VMSize supports accelerated networking. If AcceleratedNetworking is set to true with a VMSize that does not support it, Azure will return an error. | ||
| type: boolean | ||
| additionalCapabilities: |
There was a problem hiding this comment.
New optional property. Giant Swarm vintage Azure clusters are not using AzureMachineTemplate CRs, so they are not affected by this change.
| readOnly: true | ||
| serviceAccountName: capz-manager | ||
| terminationGracePeriodSeconds: 10 | ||
| tolerations: |
There was a problem hiding this comment.
These tolerations should be fine.
|
|
||
| images: | ||
| - name: us.gcr.io/k8s-artifacts-prod/cluster-api-azure/cluster-api-azure-controller | ||
| - name: registry.k8s.io/cluster-api-azure/cluster-api-azure-controller |
There was a problem hiding this comment.
New container image registry used by upstream projects.
nprokopic
force-pushed
the
upstream-update-v1.4.5
branch
from
6bc8c21 to
d9e2df4
Compare
Towards https://github.com/giantswarm/giantswarm/issues/24551
This PR is currently on top of
upstream-update-v1.3.2branch.TODO:
mainafter merging Upstream update to v1.3.2 #76Changes
Highlighted upstream changes that can be relevant for vintage workload clusters
Highlighted upstream changes
(with specified upstream cluster-api-provider-azure versions)
v1.4.0Add support for Ultra Disks as Persistent Volumesv1.4.0Add support for user-assigned identity as AzureClusterIdentityv1.4.0Add ComputeGallery field and add community galleries supportv1.4.3Addnode-role.kubernetes.io/control-planetoleration to CAPZ manager deployment implemented in this PRUpstream release notes