Changes compared to v27.1.1
Components
- cluster-aws from v1.3.2 to v1.3.3
- Kubernetes from v1.27.14 to v1.27.16
cluster-aws v1.3.2…v1.3.3
Changed
- Chart: Update
cluster
to v1.0.2.- Chart: Add OS tooling named template.
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
cluster
to v1.0.2.cluster
to v1.0.2.This release does not contain any changes to components or apps, but makes use of an updated machine image, which includes a fix for accessing private Elastic Container Registries (ECR).
cluster-aws
version 2.1.0Do not allow additional properties in the following fields in order to avoid unnoticed typos:
global.connectivity.network
global.connectivity.network.pods
global.connectivity.network.services
global.connectivity.subnets[]
global.connectivity.topology
global.controlPlane
global.controlPlane.additionalSecurityGroups[]
global.controlPlane.machineHealthCheck
global.controlPlane.oidc
global.providerSpecific
global.providerSpecific.instanceMetadataOptions
If you were using values like global.controlPlane.containerdVolumeSizeGB
and global.controlPlane.kubeletVolumeSizeGB
, please move to the new .global.controlPlane.libVolumeSizeGB
which defines the size of disk volume used for /var/lib
mount point.
This release does not contain any changes to components or apps, but makes use of an updated machine image, which includes a fix for accessing private Elastic Container Registries (ECR).
dashboardsversion 3.24.0
alloy-app version 0.5.2 introduces the following changes:
kyverno-policies-observability version 0.5.0
ServiceMonitor
and PodMonitor
relabelling schemas as we no longer need the enforcement.fluent-logshipping-app version 5.2.2
logging-operator version 0.12.1
resource
label, filename
label, and output stream
label.node_name
label into node
to match the metric label.observability-bundle version 1.6.2:
alloyMetrics
catalogobservability-operator version 0.6.0:
alloyMetrics
catalogue in observability-bundleprometheus-meta-operator version 4.79.0:
#alert
and #alert-test-installation
slack integration.prometheus-rules version 4.15.2:
MimirHPAReachedMaxReplicas
operation recipe linkslo:current_burn_rate:ratio
slo.MimirHPAReachedMaxReplicas
alert to detect when Mimir’s HPAs have reached maximum capacity.IRSAACMCertificateExpiringInLessThan60Days
to IRSAACMCertificateExpiringInLessThan45Days
. The ACM certificate is renewed 60 days before expiration, and the alert can fire prematurely.tekton-dashboard-loki-proxy version 0.4.0:
app.giantswarm.io/*
labels to application.giantswarm.io/
aws-pod-identity-webhook version 1.17.0:
Deployment
nameaws-crossplane-cluster-config-operator version 0.3.0
ProviderConfig
to use the CAPA controller role directly without going through a middleman. For this to work, the CAPA controller must have the correct trust policy granting access to the Crossplane provider’s service account.oidcDomains
to the config map containing all service account issuer domains, as defined by the new aws.giantswarm.io/irsa-trust-domains
annotation on the AWSCluster. The primary domain is still written to value oidcDomain
.customNodeLabels
and customNodeTaints
, because they are not deprecated.kube-controller-manager
--node-cidr-mask-size
flag.providerIntegration.controlPlane.kubeadmConfig.clusterConfiguration.apiServer.serviceAccountIssuer
to plural providerIntegration.controlPlane.kubeadmConfig.clusterConfiguration.apiServer.serviceAccountIssuers
and render them in the specified order as --service-account-issuer
parameters for the API server.customNodeLabels
value to the kubelet node-labels
argument in the KubeadmConfig
when customNodeLabels
is defined.kyverno-policies-dx version 0.5.1
Enforce
and Audit
validationFailureAction.kyverno-policies-ux version 0.7.3
cluster-names
now targets Cluster by GVKEnforce
validationFailureAction.kyverno-app version 0.18.0
Kyverno
to the upstream version v1.12.5.kyverno-crds version 1.12.0
kyverno-policies version 0.21.0
Kyverno Policies
version 1.12.5.Kyverno Policies
version 1.12.5.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.