This patch release fixes an issue with the installation of the Teleport Kube Agent app.
Changes compared to v33.1.0
Apps
- coredns from v1.28.2 to v1.28.3
coredns v1.28.2…v1.28.3
Changed
- Update
corednsimage to 1.13.2.
This patch release fixes an issue with the installation of the Teleport Kube Agent app.
coredns image to 1.13.2.Update Kubernetes to v1.33.6, Flatcar to v4459.2.1 and various component upgrades.
global.baseDomain and global.managementCluster required values. These values will be passed to the chart when deploying it from the cluster-app-installation-values ConfigMap in the default namespace.required keyword and error messages. This is normally done automatically by a Kyverno policy.cluster to v4.4.0.cluster to v4.3.0.kubescape (app) version v0.0.4.kyverno (app) to v0.21.1.kyverno-crds (app) to v1.15.0.kyverno (app) to v0.20.1.kyverno-crds (app) to v1.14.0.kyverno-policies (app) to v0.24.0.reports-server (app) to v0.0.3.ephemeral-storage requests and limits to satisfy Kyverno policy require-emptydir-requests-and-limits.This release updates Flatcar to v4230.2.4 and includes several app updates and improvements.
cainjector-servicecoredns image to 1.13.1.coredns image to 1.13.0.kyverno (app) to v0.20.1.kyverno-crds (app) to v1.14.0.kyverno-policies (app) to v0.24.0.reports-server (app) to v0.0.3.kyverno update (#536, #531, #538).kyverno-policy-operator (app) to v0.1.6.kyverno (app) to v0.20.0.kyverno-crds (app) to v1.14.0.kyverno-policies (app) to v0.24.0.kyverno-policy-operator (app) to v0.1.5.trivy-operator (app) to v0.12.1.trivy (app) to v0.14.1.falco (app) to v0.11.0.kyverno update (#536, #531, #538).kyverno-policy-operator (app) to v0.1.6.kyverno (app) to v0.20.0.kyverno-crds (app) to v1.14.0.kyverno-policies (app) to v0.24.0.kyverno-policy-operator (app) to v0.1.5.trivy-operator (app) to v0.12.1.trivy (app) to v0.14.1.falco (app) to v0.11.0.WARNING: This release enables the
OwnerReferencesPermissionEnforcementadmission controller by default. This means that only users with delete permission to an object can change itsmetadata.ownerReferences, and only users with update permission to the finalizers subresource of the referenced owner can changemetadata.ownerReferences[x].blockOwnerDeletion. If you have workloads that need to modify these fields, please ensure that the necessary RBAC permissions are in place before upgrading to this release.
Example:
- apiGroups: ["<group>"]
resources: ["<resource>", "<resource>/finalizers"]
verbs: ["delete", "..."] # Add any additional verbs your use case requires
cluster to v4.2.0.cluster to v4.1.0.cluster to v4.0.3.cluster to v4.0.2.cluster to v4.0.1.cainjector-servicecoredns image to 1.13.1.coredns image to 1.13.0.WARNING: With Flatcar 4230.2.0, cgroups v1 backwards compatibility has been removed. This means that enabling legacy cgroups v1 is no longer supported and nodes still using them will fail to update.
cluster to v3.0.1..internal.advancedConfiguration.cgroupsv1 and .global.nodePools.().cgroupsv1 flags have been removed.cluster to v2.6.2.alloy ingress rules for cainjector metrics ingestion.coredns image to 1.12.3.kube-prometheus-stack-app to 18.1.0cluster-api-monitoring-app so that cluster_id label points to the workload cluster name as expected in some alert definitionskube-prometheus-stack to 77.0.1kube-prometheus-stack to 76.4.0This release fixes a permission issue with the Azure Cloud Controller Manager.
This release fixes a permission issue with the Azure Cloud Controller Manager.
cluster to v2.5.2.cluster to v2.5.0.cluster to v2.4.0.controller pods.prometheus.metrics.alloy-app from 0.10.0 to 0.11.0Alloy from 1.8.3 to 1.9.0alloy-app from 0.9.0 to 0.10.0Alloy from 1.7.1 to 1.8.3kube-prometheus-stack to 72.3.0kube-prometheus-stack to 72.3.0kube-prometheus-stack from 69.5.1 to 70.1.1promtailgrafana-agentpromtheus-agent.Values.disabled to .Values.enabled to follow best practices.policy-api-crds app to manage Policy API CRDs.trivy-operator (app) to v0.11.1.trivy (app) to v0.14.0.falco (app) to v0.10.1.cloudnative-pg (app) to v0.0.10.starboard-exporter (app) to v0.8.2.trivy (app) to v0.13.4.cloudnative-pg (app) to v0.0.7.starboard-exporter (app) to v0.8.1.kyverno-policy-operator (app) to v0.0.11.cloudnative-pg (app) to v0.0.9.global.metadata.preventDeletion to add the deletion prevention label to cluster resourcescluster chart with DNS policies enabled. This makes kube-system and giantswarm namespaces to be deny by default.giantswarm-cluster to all resources.providerSpecific.additionalResourceTags value.azurefile-csi-driver app as helmrelease.containerd configuration at cluster creation timecontroller-manager terminated-pod-gc-threshold to 125 ( consistent with vintage )api.<clusterName>.<baseDomain> (e.g. api.glippy.azuretest.gigantic.io)giantswarm.io/service-priority cluster label.0750 if it does not exist already to address issue with node-exporterlt 1.25.0cluster-shared , required by the PSP admission controllerrole=worker and giantswarm.io/machine-pool labelskube-reserved settings for nodes based on the available CPU and Memory using the formulas defined by GKEUserAssigned Identity for VM Identitycluster.x-k8s.io/watch-filter: capi to common labels.cluster to v2.2.3.cluster to v2.2.1.cluster to v2.2.0.cluster to v2.1.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 checksexternal-dns-private app depend on the prometheus-operator-crd app, because it uses ServiceMonitors.cluster to v1.4.1global.components.auditd.enabled.kube-controller-manager --node-cidr-mask-size flag.cluster to v1.2.2MachineDeployment Kubernetes version from releasecatalog from Release CR.cluster to v1.1.0. (#325)observability-policies.gsoci.azurecr.io registry. This is the new default behavior.global.apps.externalDnsPrivate to overwrite configuration of external-dns-private app.allowedSubscriptions parameter for multi-subscription use case..Values.global.managementCluster for teleport node labels.azurefile-csi-driver-app to 1.30.2-gs1cluster chart to v0.32.0. More details in cluster chart v0.32.0 release notes.cluster chart.cluster chart.cluster chart and delete the HelmRepositories from this chart. This adds the cluster-catalog.cluster chart from 0.21.0 to 0.26.0.cluster chart.3815.2.0.cluster chart as subchart.cluster chart.azurefile-csi-driver-app to 1.26.0-gs5.ins= label and remove cluster= label condition check, such that MC nodes have this label.privateEndpoints.privateEndpoints to subnets.Standard_D4s_v5 for control plane and worker nodes.1.25.16.1.25.15.gsoci.azurecr.io for kubeadm container images.gsoci.azurecr.io for sandbox container image (pause container).coredns to 1.21.0 to use gsoci.azurecr.io.cillium to 0.19.2 to use gsoci.azurecr.io.azure-cloud-controller-manager-app to 1.24.18-gs6 to use gsoci.azurecr.io.azure-cloud-node-manager-app to 1.24.18-gs6 to use gsoci.azurecr.io.azuredisk-csi-driver-app to 1.26.2-gs6 to use gsoci.azurecr.io.azurefile-csi-driver-app to 1.26.0-gs4 to use gsoci.azurecr.io.1.24.17default-apps-azure 0.0.24containerd,kubelet,root and etcd mounts for control plane nodes.providerSpecific.location value to a set of defined region names..metadata.labels object..providerSpecific.subscriptionId marked as required, constrained to UUID format.Enabled Admission Plugins is now handled dynamically based on the kubernetes version of the cluster that is being installedFeature Gates is now handled dynamically based on the kubernetes version of the cluster that is being installedcluster-shared dependency to 0.6.5exclusiveMinimum or minimum of zero.1.24.13kube-proxy during kubeadm init/join to replace with cilium-proxyidentity spec to hash calculation for bastion nodeconnectivity.allowedCIDRs to define a list of network addresses to connect to the API server.normalize-schema, validate-schema, generate-values.quay.io/giantswarm/pausecilium kube-proxy replacement - do not skip kube-proxykube-proxy during kubeadm init/join to replace with cilium-proxyContributor Role in the resourceGroup where the cluster Livesschema-normalize Make target to actually do the normalizeschemalint normalize output.managementCluster, baseDomain and provider properties to the schema because they are added by the AppOperator and the schema has additionalProperties: false0.0.0-dev in Chart.yaml since we use App Build SuiteidentityRef in the AzureClustercoredns installation phase in kubeadmbootstrapconfiguration , we install it as an Applabels in the ControlPlane AzureMachineTemplate when calculating name hash to avoid rolling control plane nodes unecessarilyMachineDeployment helper.internal values from values.schema.json.baseDomain from CI values.phoenix to cabbage.coredns image to 1.12.0.moveLeader. (#11)cluster into useClusterEndpoints. (#8)readOnlyRootFilesystem to true in the container security context.PolicyExceptions to v2beta1.go.mod and .nancy-ignore. (#242)PolicyExceptions to v2beta1.go.mod and .nancy-ignore. (#248)metrics-server.PolicyExceptions to v2beta1.go.mod. (#322)observability.giantswarm.io/rule-type: logsalloy to chart 0.9.0.alloy from to 1.5.1 to 1.7.1alloy to chart 0.8.0.alloy from to 1.5.0 to 1.6.1kube-prometheus-stack from 66.2.1 to 69.5.1security-bundle and all is componentskyverno-crds (app) to v1.13.1.kyverno (app) to v0.19.0.kyverno-crds (app) to v1.13.0.kyverno-policies (app) to v0.23.0.edgedb (app) to v0.1.0.falco (app) to v0.10.0.trivy (app) to v0.13.2.diag port 3000.