Changed
- Workflows update with
devctl - Implemented fixes on
organization/namespacedeletion
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
devctlorganization/namespace deletionFalco chart version from 3.8.1 to 4.6.1.Falco-exporter chart version from 0.9.9 to 0.11.0Falcosidekick chart version from 0.7.5 to 0.8.2Falco to upstream version 0.38.1.Falco chart version from 3.8.1 to 4.6.1.Falco-exporter chart version from 0.9.9 to 0.11.0Falcosidekick chart version from 0.7.5 to 0.8.2Falco to upstream version 0.38.1.cluster to v1.1.0. (#325)observability-policies.runAsGroup and runAsUser greater than zero for all deployments.cainjector’s Vertical Pod AutoscalersecurityContext.readOnlyRootFilesystem helm value (default true).NET_ADMIN and drop ALL capabilities.NET_BIND_SERVICE capability.require-non-root-groups/autogen-check-runasgroup.node and app labels in ServiceMonitor.alloy v0.3.0 as alloy-logsalloy-logs app to camel case alloyLogs.grafana-agent to 0.4.5.alloy to 0.3.1.promtail to 1.5.4.prometheus-operator-crd to 11.0.1.application.giantswarm.io/prometheus-rule-kind: lokikube-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.observability-policies app to deploy Kyverno Observability Policies into clusters.kyverno-crds app to handle Kyverno CRD install.kyverno (app) to v0.17.15. This version disables the CRD install job in favor of kyverno-crds App.podAntiAffinity so teleport-kube-agent pods run on different control-plane nodes also increased the number of replicas to 3 to maintain better high availability.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.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 vsphere --organization my_org --name cluster_name -vsphere-network-name network_name --release 27.0.0
get cluster command.