Changed
- Upgraded chart dependency to kube-prometheus-stack-61.0.0
- Replace
in-addr.arparecords inzonelabel forcoredns_cache_.*metrics due to large cardinality.
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
in-addr.arpa records in zone label for coredns_cache_.* metrics due to large cardinality.in-addr.arpa records in zone label for coredns_cache_.* metrics due to large cardinality.in-addr.arpa records in zone label for coredns_cache_.* metrics due to large cardinality.in-addr.arpa records in zone label for coredns_cache_.* metrics due to large cardinality.We are happy to announce the first release for Azure that uses the new release framework.
In order to consume the new flow, the following two fields need to be manually adapted:
<cluster name>-userconfig set .Values.global.release.version to the release version, e.g. 25.0.0.<cluster name> remove the spec.version field. In case of GitOps, Flux might complain that the app manifest is invalid as the spec.version field is mandatory. In that case, edit the live App CR and set spec.version to an empty string. That will unblock Flux and allow it reconcile successfully.And if you want to use kubectl-gs to create a cluster, you’d need to now specify the release version, e.g.:
kubectl-gs template cluster --provider capz --organization my-org --name cluster_name --region westeurope --azure-subscription-id AZURE_ID --release 25.0.0
--enable-long-name flag (affected commands: kubectl gs template cluster/nodepool/networkpool/catalog)kubectl gs template cluster command, now we set the workload cluster release version via the --release flag (like for vintage AWS), instead setting cluster-aws version via --cluster-version.azurefile-csi-driver-app to 1.30.2-gs1