CAPA Releases

  • This release introduces several changes that are required for Vintage to CAPA migration use-cases.

    Most notable change is that now auditd is disabled by default. If you actively use this feature, please add the following field global.components.auditd.enabled set to true in the Cluster App user values before the upgrade.

    Changes compared to v25.1.0

    Components

    • cluster-aws from v1.1.0 to v1.1.2

    cluster-aws v1.1.0…v1.1.2

    Added

    • Chart: Add global.connectivity.network.pods.nodeCidrMaskSize to schema.
    • Chart: Allow to enable auditd through global.components.auditd.enabled.
    • Chart: Support multiple service account issuers.

    Changed

    • Chart: Update cluster to v0.35.2.
      • Allow to enable auditd service through global.components.auditd.enabled.
      • Support multiple service account issuers.
      • Allow configuring kube-controller-manager --node-cidr-mask-size flag.
  • This release introduces several changes that are required for Vintage to CAPA migration use-cases.

    Most notable change is that now auditd is disabled by default. If you actively use this feature, please add the following field global.components.auditd.enabled set to true in the Cluster App user values before the upgrade.

    Changes compared to v25.2.0

    Components

    • cluster-aws from v1.3.0 to v1.3.2

    cluster-aws v1.3.0…v1.3.2

    Added

    • Chart: Add global.connectivity.network.pods.nodeCidrMaskSize to schema.
    • Chart: Allow to enable auditd through global.components.auditd.enabled.
    • Chart: Support multiple service account issuers.

    Changed

    • Chart: Update cluster to v1.0.1.
      • Allow to enable auditd service through global.components.auditd.enabled.
      • Support multiple service account issuers.
      • Allow configuring kube-controller-manager --node-cidr-mask-size flag.
  • This release introduces several changes that are required for Vintage to CAPA migration use-cases.

    Most notable change is that now auditd is disabled by default. If you actively use this feature, please add the following field global.components.auditd.enabled set to true in the Cluster App user values before the upgrade.

    Changes compared to v26.1.0

    Components

    • cluster-aws from v1.3.0 to v1.3.2

    cluster-aws v1.3.0…v1.3.2

    Added

    • Chart: Add global.connectivity.network.pods.nodeCidrMaskSize to schema.
    • Chart: Allow to enable auditd through global.components.auditd.enabled.
    • Chart: Support multiple service account issuers.

    Changed

    • Chart: Update cluster to v1.0.1.
      • Allow to enable auditd service through global.components.auditd.enabled.
      • Support multiple service account issuers.
      • Allow configuring kube-controller-manager --node-cidr-mask-size flag.
  • This release introduces several changes that are required for Vintage to CAPA migration use-cases.

    Most notable change is that now auditd is disabled by default. If you actively use this feature, please add the following field global.components.auditd.enabled set to true in the Cluster App user values before the upgrade.

    Changes compared to v27.1.0

    Components

    • cluster-aws from v1.3.0 to v1.3.2

    cluster-aws v1.3.0…v1.3.2

    Added

    • Chart: Add global.connectivity.network.pods.nodeCidrMaskSize to schema.
    • Chart: Allow to enable auditd through global.components.auditd.enabled.
    • Chart: Support multiple service account issuers.

    Changed

    • Chart: Update cluster to v1.0.1.
      • Allow to enable auditd service through global.components.auditd.enabled.
      • Support multiple service account issuers.
      • Allow configuring kube-controller-manager --node-cidr-mask-size flag.
  • This release introduces several changes that are required for Vintage to CAPA migration use-cases.

    Most notable change is that now auditd is disabled by default. If you actively use this feature, please add the following field global.components.auditd.enabled set to true in the Cluster App user values before the upgrade.

    Changes compared to v28.1.1

    Components

    • cluster-aws from v1.3.0 to v1.3.2

    cluster-aws v1.3.0…v1.3.2

    Added

    • Chart: Add global.connectivity.network.pods.nodeCidrMaskSize to schema.
    • Chart: Allow to enable auditd through global.components.auditd.enabled.
    • Chart: Support multiple service account issuers.

    Changed

    • Chart: Update cluster to v1.0.1.
      • Allow to enable auditd service through global.components.auditd.enabled.
      • Support multiple service account issuers.
      • Allow configuring kube-controller-manager --node-cidr-mask-size flag.
  • This release fixes an issue where certain apps installed during or before v25 will break due to API removals when upgrading to v29.

    Changes compared to v28.1.0

    Apps

    • security-bundle from v1.7.0 to v1.7.2

    security-bundle v1.7.0…v1.7.2

    Changed

    • Update trivy-operator (app) to v0.9.1.
    • Update kyverno (app) to v0.17.14.
    • Update starboard-exporter (app) to v0.7.11.
  • Changes compared to v29.0.0

    Components

    Apps

    • cert-exporter from v2.9.1 to v2.9.2
    • node-exporter from v1.19.0 to v1.20.0
    • observability-bundle from v1.5.2 to v1.6.1
    • security-bundle from v1.8.0 to v1.8.1

    cert-exporter v2.9.1…v2.9.2

    Added

    • Chart: Add VPA and resources configuration for deployment and daemonset. (#382)

    node-exporter v1.19.0…v1.20.0

    Changed

    • Synced with upstream chart v4.38.0 (node-exporter 1.8.2).

    observability-bundle v1.5.2…v1.6.1

    Added

    • Add alloy v0.4.0 as alloyMetrics.

    Changed

    • Disable usage reporting to GrafanaLabs by:
      • Bumping alloyLogs and alloyMetrics to v0.4.1.
      • Bumping grafanaAgent to v0.4.6.
    • Bump alloyLogs to v0.4.0.
    • Rename alloy-logs app to camel case alloyLogs.

    security-bundle v1.8.0…v1.8.1

    Changed

    • Update trivy-operator (app) to v0.9.1.
  • This release updates the apps and components, keeping them up to date with the latest v25 and v26 releases. It also brings improvements for the container registry usage.

    Change details compared to CAPA 27.0.0

    cluster-aws 1.3.0

    Changed

    • All workload clusters will by default use Zot registry as a pull-through cache of Azure Container Registry.

    cert-manager 3.7.9

    Fix

    • Remove quotes from acme-http01-solver-image argument. The quotes are used when looking up the image which causes an error.

    Update

    • Improves container security by setting runAsGroup and runAsUser greater than zero for all deployments.

    containerlinux 3815.2.5

    Changes since Stable 3815.2.4

    Security fixes:

    Updates:

    cilium 0.25.1

    Changed

    • Fix regression setting Policy BPF Max map policyMapMax back to 65536 from 16384.
    • Upgrade cilium to v1.15.6.
  • This release updates cluster-aws Helm chart, which brings improvements for container registry usage.

    Change details compared to CAPA 25.1.0

    cluster-aws 1.3.0

    Changed

    • All workload clusters will by default use Zot registry as a pull-through cache of Azure Container Registry.
  • This release updates the apps and components, keeping them up to date with the latest v25 release. It also brings improvements for the container registry usage.

    Change details compared to CAPA 26.0.0

    cluster-aws 1.3.0

    Changed

    • All workload clusters will by default use Zot registry as a pull-through cache of Azure Container Registry.

    cert-manager 3.7.9

    Fix

    • Remove quotes from acme-http01-solver-image argument. The quotes are used when looking up the image which causes an error.

    Update

    • Improves container security by setting runAsGroup and runAsUser greater than zero for all deployments.

    containerlinux 3815.2.5

    Changes since Stable 3815.2.4

    Security fixes:

    Updates:

    cilium 0.25.1

    Changed

    • Fix regression setting Policy BPF Max map policyMapMax back to 65536 from 16384.
    • Upgrade cilium to v1.15.6.

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.