1. Docs
  2. Changes and releases
  3. Fleet Management

Fleet Management

  • Fleet Management kubectl-gs v2.34.1

    Fixed

    • kubectl gs template cluster now by default creates a node pool with the name nodepool0, instead of machine-pool0, as the latter is no longer valid according to the cluster-aws schema as of v0.24.0.
  • Fleet Management vertical-pod-autoscaler-app v3.3.1

    Added

    • Added the use of the runtime default seccomp profile.
  • Fleet Management kubectl-gs v2.34.0

    Added

    • cluster template supports a generic way to template CAPI based clusters where all the input parameters are given as values.yaml from the corresponding cluster and default-apps chart.
    • CAPZ: removed unmaintained CAPZ implementation and switched to the generic templating implementation.

    Changed

    • kubectl gs template cluster for Cluster API provider AWS has been adapted to work with the values schema of cluster-aws v0.28.0.
  • Fleet Management vertical-pod-autoscaler-app v3.3.0

    Changed

    • Sync with upstream update concerning image.registry
  • Fleet Management vertical-pod-autoscaler-app v3.2.0

    Added

    • Add VPA CR to VPA.
  • Fleet Management vertical-pod-autoscaler-app v3.1.0

    Changed

    • Upgrade to AppVersion 0.13.0
  • Fleet Management kubectl-gs v2.33.0

    Added

    • Add workload cluster login support for CAPZ based clusters
    • CAPA: Add hidden flags --aws-prefix-list-id and --aws-transit-gateway-id for private clusters

    Changed

    • CAPA: Renamed hidden parameter --role to --aws-cluster-role-identity-name and adapted manifest output to the new name awsClusterRoleIdentityName (see cluster-aws change)
  • Fleet Management vertical-pod-autoscaler-app v3.0.0

    Added

    • Add cilium network policy so that the crd-install job can reach the k8s api to install the CRDs.
    • README: doc improvements

    Changed

    • Remove push-to-app-collection jobs for onprem providers since this app became a part of default apps bundle.
    • Moved to chart dependency
    • ⚠ Major upgrade, breaking changes
      • values structure changes. We rely on a subchart, meaning all of previous setup goes to a vertical-pod-autoscaler section
      • the upstream repo has changed and thus as did the helm chart config
      • for more detailed explanations, check the README
  • Fleet Management kubectl-gs v2.32.0

    As part of our automatic upgrades journey, we have learnt that cluster chart should structure in such a way that allows overwriting all sections in different levels Warning: This results in a breaking change in the template output of a capa clusters machine pools.

    Changed

    • Breaking: Update capa machine pools to template usings an object instead of arrays as of cluster-aws v0.24.0
  • Fleet Management kubectl-gs v2.31.2

    Fixed

    • Fixed creating client certificates for workload clusters in capvcd installations.