1. Docs
  2. Changes and releases

Changes and Releases

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

  • Managed Apps cert-manager-app v3.7.8

    Added

    • Improves container security by setting runAsGroup and runAsUser greater than zero for all deployments.
  • Workload cluster releases for AWS releases v20.1.3

    This is a security release featuring latest version of Flatcar Container Linux with major CVE fix for OpenSSH CVE-2024-6387. Upgrade to this release will result in nodes rollout.

    Change details

    containerlinux 3815.2.5

    Changes since Stable 3815.2.4

    Security fixes:

    Updates:

  • Workload cluster releases for AWS releases v19.3.5

    This is a security release featuring latest version of Flatcar Container Linux with major CVE fix for OpenSSH CVE-2024-6387. Upgrade to this release will result in nodes rollout.

    Change details

    containerlinux 3815.2.5

    Changes since Stable 3815.2.4

    Security fixes:

    Updates:

  • Web UI backstage v0.26.0

    Added

    • Add plugin-scaffolder-backend-module-gs backend module with custom parseClusterRef filter for scaffolder plugin.
    • GS Auth: add custom sign-in resolver for GitHub auth provider.

    Removed

    • Clean up catalog templates.
  • Dashboards dashboards v3.20.0

    Added

    • Add “BPF map pressure” graph to “Cilium performance” dashboard.
    • Add kube-builder logs in “Kube-Builder Operators” dashboard.

    Changed

    • fluentbit dashboard: cluster selection

    Fixed

    • Mimir Cost Estimation: fix RAM usage

    Removed

    • Removed the dashboard ‘Webhook Health’.
  • Managed Apps kube-prometheus-stack-app v11.0.0

    Changed

    • Upgraded chart dependency to kube-prometheus-stack-61.0.0
      • prometheus-operator from 0.73.2 to 0.75.0 - adding remoteWrite.proxyFromEnvironment support
      • prometheus upgraded from 2.52.0 to 2.53.0
      • grafana from 7.3.12 to 8.2.0
      • thanos ruler upgraded from 0.35.0 to 0.35.1
      • prometheus-node-exporter upgraded from 1.8.0 to 1.8.1
    • Replace in-addr.arpa records in zone label for coredns_cache_.* metrics due to large cardinality.
  • Observability Platform kube-prometheus-stack-app v11.0.0

    Changed

    • Upgraded chart dependency to kube-prometheus-stack-61.0.0
      • prometheus-operator from 0.73.2 to 0.75.0 - adding remoteWrite.proxyFromEnvironment support
      • prometheus upgraded from 2.52.0 to 2.53.0
      • grafana from 7.3.12 to 8.2.0
      • thanos ruler upgraded from 0.35.0 to 0.35.1
      • prometheus-node-exporter upgraded from 1.8.0 to 1.8.1
    • Replace in-addr.arpa records in zone label for coredns_cache_.* metrics due to large cardinality.
  • Managed Apps prometheus-operator-app v11.0.0

    Changed

    • Upgraded chart dependency to kube-prometheus-stack-61.0.0
      • prometheus-operator from 0.73.2 to 0.75.0 - adding remoteWrite.proxyFromEnvironment support
      • prometheus upgraded from 2.52.0 to 2.53.0
      • grafana from 7.3.12 to 8.2.0
      • thanos ruler upgraded from 0.35.0 to 0.35.1
      • prometheus-node-exporter upgraded from 1.8.0 to 1.8.1
    • Replace in-addr.arpa records in zone label for coredns_cache_.* metrics due to large cardinality.
  • Observability Platform prometheus-operator-app v11.0.0

    Changed

    • Upgraded chart dependency to kube-prometheus-stack-61.0.0
      • prometheus-operator from 0.73.2 to 0.75.0 - adding remoteWrite.proxyFromEnvironment support
      • prometheus upgraded from 2.52.0 to 2.53.0
      • grafana from 7.3.12 to 8.2.0
      • thanos ruler upgraded from 0.35.0 to 0.35.1
      • prometheus-node-exporter upgraded from 1.8.0 to 1.8.1
    • Replace in-addr.arpa records in zone label for coredns_cache_.* metrics due to large cardinality.
  • Workload cluster releases for Azure releases azure-25.0.0

    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

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.