Changes compared to v29.3.0
Apps
- cloud-provider-cloud-director from v0.3.1 to v0.4.0
cloud-provider-cloud-director v0.3.1…v0.4.0
Changed
- Update to
1.6.0-gsof CPI. (Upstream1.6.0plus custom patch from previous release.)
1.6.0-gs of CPI. (Upstream 1.6.0 plus custom patch from previous release.)components.containerd to the schema and values.Note: When upgrading to this security-bundle version with Falco enabled, the Falco App will fail to upgrade due to a breaking change in the upstream chart. To finish the upgrade, disable, then re-enable the Falco App by setting apps.falco.enabled=[false|true] in the security-bundle user values Config Map.
trivy-operator (app) to v0.10.3.trivy (app) to v0.13.1.kyverno (app) to v0.18.1.kyverno-crds (app) to v1.12.0.kyverno-policies (app) to v0.21.0.starboard-exporter (app) to v0.8.0.falco (app) to v0.9.1.cluster to v1.7.0.teleport-init systemd unit to handle initial token setup before teleport service startsteleport service reliability by adding proper file and service dependencies and pre-start checksgiantswarm.io/monitoring_basic_sli as this slo generation label is not used anymore.coredns image to 1.11.4.alloy v0.7.0 as alloyEvents.alloy-logs and alloy-metrics to chart 0.7.0.alloy from 1.4.2 to 1.5.0kube-prometheus-stack from 65.1.1 to 66.2.1global.podSecurityStandards.enforced. (#420)prometheus-agent from v0.6.9 to v0.7.0.kube-prometheus-stack from 61.0.0 to 65.1.1alloyLogs to v0.6.1coredns image to 1.11.3.alloy v0.4.0 as alloyMetrics.alloyMetrics catalogalloyLogs and alloyMetrics to v0.4.1.grafanaAgent to v0.4.6.cloudnative-pg (app) to v0.0.6.trivy-operator (app) to v0.10.0.kyverno-policy-operator (app) to v0.0.8.kyverno (app) to v0.17.16.podSecurityContext for seccompProfile.version 16global.imageRegistry. (#315)crds.image.tag. (#316)We are happy to announce the first release for VMware Cloud Director that uses the new release framework.
In order to consume the new flow, the following two fields need to be manually adapted:
<cluster name>-userconfig set .Values.global.release.version to the release version, e.g. 27.0.0.<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 cloud-director --organization my_org --name cluster_name --release 27.0.0