Releases: giantswarm/cluster-azure
Releases · giantswarm/cluster-azure
v1.5.0
v1.4.0
Changed
- Make
external-dns-private
app depend on theprometheus-operator-crd
app, because it usesServiceMonitors
.
v1.3.0
v1.2.0
v1.1.0
Changed
- Apps: Use
catalog
from Release CR.
v1.0.0
Important
Releases that include this cluster-azure
version have to define os-tooling
in the their .spec.components
.
See image changes below for more details and Azure (CAPZ) release v27.0.0 for a Release resource example.
Changed
- Chart: Update
cluster
to v1.1.0. (#325)- Machine Template: Adapt new image format.
- Apps: Enable
observability-policies
.
v0.18.0
Changed
- Update cluster chart version to v1.0.0. This update adds MC Zot deployment as a registry mirror for
gsoci.azurecr.io
registry. This is the new default behavior.
v0.17.0
⚠️ Breaking change ⚠️
- Support for Release CR's.
How to migrate to cluster-azure
- In ConfigMap
<cluster name>-userconfig
set.Values.global.release
to the release version, e.g.25.0.0
. - In App
<cluster name>
set theversion
to an empty string.
v0.16.1
Changed
- Respect
global.apps.externalDnsPrivate
to overwrite configuration ofexternal-dns-private
app.
v0.16.0
Breaking change
- Append cluster name to
natgateway
resource to differentiate CR names forazure-service-operator
. - Set
routeTable
for control plane nodes by default.
Commands to run after upgrade
- Login to azure
az login
az account set -s <subscription-of-azurecluster>
- Remove natgateway manually so that CAPZ can recreate it with a unique name
export CLUSTER_NAME=<cluster-name>
az network vnet subnet update --resource-group $CLUSTER_NAME --vnet-name $CLUSTER_NAME-vnet --name node-subnet --remove natGateway.id
az network nat gateway delete --resource-group $CLUSTER_NAME --name node-natgateway
- Add route table to CP nodes
az network vnet subnet update --resource-group $CLUSTER_NAME --vnet-name $CLUSTER_NAME-vnet --name control-plane-subnet --route-table $CLUSTER_NAME-node-routetable