Added
- Improves container security by setting
runAsGroup
andrunAsUser
greater than zero for all deployments.
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
runAsGroup
and runAsUser
greater than zero for all deployments.runAsGroup
and runAsUser
greater than zero for all deployments.kube-prometheus-stack
to 11.0.0 and prometheus-operator-crd
to 11.0.0. This upgrade mainly consists in:grafana-agent
from 0.4.3 to 0.4.4CiliumNetworkPolicy
egress and ingress sections.plugin-scaffolder-backend-module-gs
backend module with custom parseClusterRef
filter for scaffolder plugin.in-addr.arpa
records in zone
label for coredns_cache_.*
metrics due to large cardinality.in-addr.arpa
records in zone
label for coredns_cache_.*
metrics due to large cardinality.in-addr.arpa
records in zone
label for coredns_cache_.*
metrics due to large cardinality.in-addr.arpa
records in zone
label for coredns_cache_.*
metrics due to large cardinality.We are happy to announce the first release for Azure 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. 25.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 capz --organization my-org --name cluster_name --region westeurope --azure-subscription-id AZURE_ID --release 25.0.0