Changed
- Upgrade to AppVersion 0.13.0
CAPZ based clusters--aws-prefix-list-id and --aws-transit-gateway-id for private clusters--role to --aws-cluster-role-identity-name and adapted manifest output to the new name awsClusterRoleIdentityName (see cluster-aws change)push-to-app-collection jobs for onprem providers since this app became a part of default apps bundle.vertical-pod-autoscaler sectionAs 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.
capa machine pools to template usings an object instead of arrays as of cluster-aws v0.24.0capvcd installations.region, vpcId and IAM role annotations automatically from Giant Swarm provided default cluster values.gitops add base from bases/clusters/<PROVIDER> to bases/clusters/<PROVIDER>/templategitops add base generated templates to capa and gcp (CAPG) providers with value: machine-pool0login command to provide an option to choose from multiple connectorscloud-director--connector-id flag in the login command to specify a Dex connector to use and skip the selection step--cluster-type, --https-proxy, --http-proxy, --no-proxy, --api-mode, --dns-mode, --vpc-mode and `–topoltotemplate clusterthat specifycapa` as provider.gitops add base command to generate CAP[A,G,O] bases. The values for --provider flag is compatible with the template cluster command (A: capa, G: gcp, O: openstack).