Changed
- Changed ownership to Team Shield
- Prepare for Backstage service
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
List of allowed origins was extended by @ljakimczuk in https://github.com/giantswarm/happa/pull/4635
Full Changelog: https://github.com/giantswarm/happa/compare/v1.69.0...v1.70.0
Mimir / Continuous test
dashboard.This release fixes a bug when Grafana links for component deployments had incorrect namespace variable. See ./docs/releases/v0.41.3-changelog.md for more information.
See ./docs/releases/v0.41.2-changelog.md for more information.
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
controller.admissionWebhooks.service.servicePort
.PodDisruptionBudget
.matchLabelKeys
in Topology Spread Constraints.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.