Changed
- Update
Trivy
to upstream version v0.56.1. - Disable PSPs.
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Trivy
to upstream version v0.56.1.Trivy
to upstream version v0.56.1.We are happy to announce the first release for vSphere 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.1
.<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 vsphere --organization my_org --name cluster_name -vsphere-network-name network_name --release 27.0.1
kube-vip
static pod manifest for Kubernetes 1.29
onwards.coredns
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 16
global.imageRegistry
. (#315)crds.image.tag
. (#316)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.