Changes and Releases

Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.

  • We are happy to announce the first release for Azure that uses the new release framework.

    Migration to new releases flow

    In order to consume the new flow, the following two fields need to be manually adapted:

    • In ConfigMap <cluster name>-userconfig set .Values.global.release.version to the release version, e.g. 25.0.0.
    • In App <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
    
  • Changes compared to v25.0.0

    • Kubernetes version change from 1.25.16 to 1.26.15
    • azure-cloud-controller-manager from 1.24.18-gs6 to 1.26.22-gs2
    • azure-cloud-node-manager from 1.24.18-gs6 to 1.26.22-gs2
    • cluster-azure from 0.17.0 to 0.18.0
    • azuredisk-csi-driver from 1.26.2-gs6 to 1.30.2-gs2.
  • Removed

    • BREAKING Remove deprecated --enable-long-name flag (affected commands: kubectl gs template cluster/nodepool/networkpool/catalog)

    Changed

    • BREAKING When templating cluster manifests for CAPA clusters with 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.
    • Update module version to v3.
  • Changed

    • Upgraded upstream chart from 6.5.2 to 6.6.4 - see changelog for more information.
  • Changed

    • Upgraded upstream chart from 6.5.2 to 6.6.4 - see changelog for more information.
  • Improves cert-manager CA injector on demanding clusters

    Change details

    cert-manager 3.7.7

    Changed

    • Changed the way the registry is being parsed in helm templates
    • Enable VPA by default for CA injector
  • Changed

    • Update azurefile-csi-driver-app to 1.30.2-gs1
  • Changed

    • Bump cloud-provider-vsphere to 1.7.0 for Kubernetes 1.27 compatibility.
      • Update vSphere CSI to 3.2.0.
      • Update vSphere CPI to 1.27.0.
      • Update kube-vip to 0.8.0.
      • Update kube-vip-cloud-provider to 0.0.5.
  • Changed

    • Chart: Change restartPolicy to OnFailure for the CRD job. (#298)
  • Changed

    • Chart: Change restartPolicy to OnFailure for the CRD job. (#298)

This part of our documentation refers to our vintage product. The content may be not valid anymore for our current product. Please check our new documentation hub for the latest state of our docs.