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.
lb Security Group to Karpenter nodes.azs-getter.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.g6f.xlarge come with some drivers that require a larger disk.cluster to v4.3.0.node.legacyXFS: true as workaround.blockExpress parameter is deprecated for io2 volumes (now always uses 256,000 IOPS cap).debugLogs parameter for maximum verbosity logging and debugging.metadataSources configuration option for node metadata handling.disableMutation parameter for service account mutation control.MutableCSINodeAllocatableCount feature gate (Kubernetes 1.33+).enablePrometheusAnnotations values for controller and node components.minAllowed CPU to 50m. Otherwise VPA will set the CPU to tiny values that will cause CPU throttling.iam:PassRole resource to old worker role ARN (the one used before crossplane started managing the IAM Roles) when workersIamRole is not provided. This is needed to make our tests automation to work, regardless of the version of this app used.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.
terminationGracePeriod in the karpenter node pools.startupTaints to help karpenter ignore pending Pods due to these taints that will be removed after the node starts, avoiding unnecessary instance provisioning:node.cluster.x-k8s.io/uninitialized:NoSchedulenode.cilium.io/agent-not-ready:NoScheduleebs.csi.aws.com/agent-not-ready:NoExecutenode.legacyXFS: true as workaround.blockExpress parameter is deprecated for io2 volumes (now always uses 256,000 IOPS cap).debugLogs parameter for maximum verbosity logging and debugging.metadataSources configuration option for node metadata handling.disableMutation parameter for service account mutation control.MutableCSINodeAllocatableCount feature gate (Kubernetes 1.33+).enablePrometheusAnnotations values for controller and node components.gsoci.azurecr.io as the default container image registry.updateStrategy.rollingUpdate.maxUnavailable to 25% in DaemonSet to speed up rolling update.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.This release improves the stability of Karpenter node pools.
capa-karpenter-taint-remover to handle CAPA - Karpenter taint race condition.capa-karpenter-taint-remover app.terminationGracePeriod default to 30m, to avoid having karpenter nodes stuck in Deleting state due to Pods blocking the deletion i.e. PDBs.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
terminationGracePeriod in the karpenter node pools.cluster to v4.2.0.gsoci.azurecr.io, regardless of the cluster region. The mirroring feature of containerd will make sure the right registry is used.karpenter and karpenter-crossplane-resources charts.HelmReleases api version to v2.startupTaints to help karpenter ignore pending Pods due to these taints that will be removed after the node starts, avoiding unnecessary instance provisioning:node.cluster.x-k8s.io/uninitialized:NoSchedulenode.cilium.io/agent-not-ready:NoScheduleebs.csi.aws.com/agent-not-ready:NoExecutecilium ENI mode pod CIDRs in the NodePort Services security group ingress rules.capi-node-labeler app. From now on, the worker nodes won’t have the node-role.kubernetes.io/worker or node.kubernetes.io/worker labels.gsoci.azurecr.io as the default container image registry.updateStrategy.rollingUpdate.maxUnavailable to 25% in DaemonSet to speed up rolling update.cainjector-serviceVolumeAttachments. (#345)coredns image to 1.13.1.coredns image to 1.13.0.iam:ListInstanceProfiles for release 1.7.1WARNING: 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.
global.connectivity.network.nodePortIngressRuleCidrBlocks value to allow configuring the CIDRs in the NodePort security group ingress rules.machinepool values to configure the karpenter node pools:consolidateAfterconsolidationBudgetsconsolidationPolicycluster to v3.0.1..internal.advancedConfiguration.cgroupsv1 and .global.nodePools.().cgroupsv1 flags have been removed.cluster to v2.6.2.cluster to v2.6.1.cluster chart nodepool fields to the schema.alloy ingress rules for cainjector metrics ingestion.coredns image to 1.12.3.v1.6.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 updates the cluster-aws chart to fix an issue around Helm values schema validation when using certain node pool fields.
cluster chart nodepool fields to the schema.This release updates the cluster-aws chart and the underlying cluster chart to address an issue around Helm values schema validation uncovered by newer Helm versions.
cluster to v2.5.1.This release updates the cluster-aws chart and the underlying cluster chart to address an issue around Helm values schema validation uncovered by newer Helm versions.
cluster to v2.2.2.This release backports a fix for reducing IMDS Response Hop Limit to 2 if pod networking is in ENI mode to increase security. For clusters in ENI mode, all nodes are rolled when upgrading to this release.