Changed
- Updated chart metadata
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
tl;dr: Please first upgrade your existing cluster to Giant Swarm Release v33.2.0 for VMware Cloud Director or newer before upgrading to this release! Otherwise, you risk service outage and severe issues.
Giant Swarm Release v34.0.0 for VMware Cloud Director comes with Kubernetes v1.34. This version contains etcd v3.6, which makes use of the so-called v3 store by default. Before, with etcd v3.5, the v2 store was used by default and synchronized to the already existing v3 store.
Different flaws could lead to an inconsistency between the old v2 store and the already present but unused standby v3 store in etcd v3.5 and before. Because of this, new etcd v3.6 members, which first start to use this v3 store, might suffer from these inconsistencies.
This can come into play when upgrading a cluster to this and future releases from any release older than Giant Swarm Release v33.2.0 for VMware Cloud Director. For this reason, we require you to first upgrade your cluster to Giant Swarm Release v33.2.0 for VMware Cloud Director or newer before upgrading to this or future releases.
This release introduces optional support for Kubernetes Structured Authentication Configuration for OIDC providers. We recommend testing this feature on a non-production cluster first.
global:
controlPlane:
oidc:
structuredAuthentication:
enabled: true
issuers:
- issuerUrl: https://your-idp.example.com
clientId: kubernetes
global:
controlPlane:
oidc:
structuredAuthentication:
enabled: true
issuers:
- issuerUrl: https://your-idp.example.com
clientId: kubernetes
usernameClaim: email # Optional: use 'email' instead of 'sub'
groupsClaim: roles # Optional: use 'roles' instead of 'groups'
usernamePrefix: "oidc:" # Optional: prefix usernames
groupsPrefix: "oidc:" # Optional: prefix groups
If you already use OIDC with the legacy configuration, add structuredAuthentication.enabled: true to migrate:
global:
controlPlane:
oidc:
issuerUrl: https://your-idp.example.com
clientId: kubernetes
structuredAuthentication:
enabled: true
This will automatically convert your legacy configuration to the new structured format.
Additional configuration options are available for more complex setups, including:
audiences, audienceMatchPolicy)discoveryUrl)caPem)claimValidationRules, userValidationRules)claimMappings)Refer to the Kubernetes Structured Authentication documentation for details.
fix-dns-nic-allocation.sh Ignition script to attach DNS servers to correct network interfaces.priority-classes default app, enabled by default. This app provides standardised PriorityClass resources like giantswarm-critical and giantswarm-high, which should replace the previous inconsistent per-app priority classes."helm.sh/resource-policy": keep annotation to VCDCluster CR so that it doesn’t get removed by Helm when uninstalling this chart. The CAPI controllers will take care of removing it, following the expected deletion order./run/metadata/coreos.ntpd unit.cluster to v5.1.2.cluster to v5.1.1.cluster to v5.1.0.cluster to v5.0.0.kube_servicemonitor_info and kube_podmonitor_info for ServiceMonitor and PodMonitor resourceskube_podlog_info for PodLog resourcekube-prometheus-stack-app to 19.0.0edgedb to gel.cloudnative-pg (app) to v0.0.12.gel (app) to v1.0.1.tl;dr: Please first upgrade your existing cluster to Giant Swarm Release v33.1.1 for vSphere or newer before upgrading to this release! Otherwise, you risk service outage and severe issues.
Giant Swarm Release v34.0.0 for vSphere comes with Kubernetes v1.34. This version contains etcd v3.6, which makes use of the so-called v3 store by default. Before, with etcd v3.5, the v2 store was used by default and synchronized to the already existing v3 store.
Different flaws could lead to an inconsistency between the old v2 store and the already present but unused standby v3 store in etcd v3.5 and before. Because of this, new etcd v3.6 members, which first start to use this v3 store, might suffer from these inconsistencies.
This can come into play when upgrading a cluster to this and future releases from any release older than Giant Swarm Release v33.1.1 for vSphere. For this reason, we require you to first upgrade your cluster to Giant Swarm Release v33.1.1 for vSphere or newer before upgrading to this or future releases.
This release introduces optional support for Kubernetes Structured Authentication Configuration for OIDC providers. We recommend testing this feature on a non-production cluster first.
global:
controlPlane:
oidc:
structuredAuthentication:
enabled: true
issuers:
- issuerUrl: https://your-idp.example.com
clientId: kubernetes
global:
controlPlane:
oidc:
structuredAuthentication:
enabled: true
issuers:
- issuerUrl: https://your-idp.example.com
clientId: kubernetes
usernameClaim: email # Optional: use 'email' instead of 'sub'
groupsClaim: roles # Optional: use 'roles' instead of 'groups'
usernamePrefix: "oidc:" # Optional: prefix usernames
groupsPrefix: "oidc:" # Optional: prefix groups
If you already use OIDC with the legacy configuration, add structuredAuthentication.enabled: true to migrate:
global:
controlPlane:
oidc:
issuerUrl: https://your-idp.example.com
clientId: kubernetes
structuredAuthentication:
enabled: true
This will automatically convert your legacy configuration to the new structured format.
Additional configuration options are available for more complex setups, including:
audiences, audienceMatchPolicy)discoveryUrl)caPem)claimValidationRules, userValidationRules)claimMappings)Refer to the Kubernetes Structured Authentication documentation for details.
priority-classes default app, enabled by default. This app provides standardised PriorityClass resources like giantswarm-critical and giantswarm-high, which should replace the previous inconsistent per-app priority classes."helm.sh/resource-policy": keep annotation to VSphereCluster CR so that it doesn’t get removed by Helm when uninstalling this chart. The CAPI controllers will take care of removing it, following the expected deletion order."helm.sh/resource-policy": keep annotation to the provider secret. This is to ensure that it isn’t removed by Helm, thus leading to a race condition when deleting the cluster as the vSphere cleaner needs it to clean up resources in vSphere.cluster to v5.1.2.cluster to v5.1.1.cluster to v5.1.0.cluster to v5.0.0.cluster to v4.6.0.cluster to v4.5.1.cluster to v4.5.0.1.34.0.kube_servicemonitor_info and kube_podmonitor_info for ServiceMonitor and PodMonitor resourceskube_podlog_info for PodLog resourcekube-prometheus-stack-app to 19.0.0edgedb to gel.cloudnative-pg (app) to v0.0.12.gel (app) to v1.0.1.v3.3.1affinity and tolerations configurable in values.yaml.tl;dr: Please first upgrade your existing cluster to Giant Swarm Release v33.1.1 for Azure or newer before upgrading to this release! Otherwise, you risk service outage and severe issues.
Giant Swarm Release v34.0.0 for Azure comes with Kubernetes v1.34. This version contains etcd v3.6, which makes use of the so-called v3 store by default. Before, with etcd v3.5, the v2 store was used by default and synchronized to the already existing v3 store.
Different flaws could lead to an inconsistency between the old v2 store and the already present but unused standby v3 store in etcd v3.5 and before. Because of this, new etcd v3.6 members, which first start to use this v3 store, might suffer from these inconsistencies.
This can come into play when upgrading a cluster to this and future releases from any release older than Giant Swarm Release v33.1.1 for Azure. For this reason, we require you to first upgrade your cluster to Giant Swarm Release v33.1.1 for Azure or newer before upgrading to this or future releases.
This release introduces optional support for Kubernetes Structured Authentication Configuration for OIDC providers. We recommend testing this feature on a non-production cluster first.
global:
controlPlane:
oidc:
structuredAuthentication:
enabled: true
issuers:
- issuerUrl: https://your-idp.example.com
clientId: kubernetes
global:
controlPlane:
oidc:
structuredAuthentication:
enabled: true
issuers:
- issuerUrl: https://your-idp.example.com
clientId: kubernetes
usernameClaim: email # Optional: use 'email' instead of 'sub'
groupsClaim: roles # Optional: use 'roles' instead of 'groups'
usernamePrefix: "oidc:" # Optional: prefix usernames
groupsPrefix: "oidc:" # Optional: prefix groups
If you already use OIDC with the legacy configuration, add structuredAuthentication.enabled: true to migrate:
global:
controlPlane:
oidc:
issuerUrl: https://your-idp.example.com
clientId: kubernetes
structuredAuthentication:
enabled: true
This will automatically convert your legacy configuration to the new structured format.
Additional configuration options are available for more complex setups, including:
audiences, audienceMatchPolicy)discoveryUrl)caPem)claimValidationRules, userValidationRules)claimMappings)Refer to the Kubernetes Structured Authentication documentation for details.
priority-classes default app, enabled by default. This app provides standardised PriorityClass resources like giantswarm-critical and giantswarm-high, which should replace the previous inconsistent per-app priority classes."helm.sh/resource-policy": keep annotation to AzureCluster CR so that it doesn’t get removed by Helm when uninstalling this chart. The CAPI controllers will take care of removing it, following the expected deletion order.cluster to v5.1.2.cluster to v5.1.1.cluster to v5.1.0.cluster to v5.0.0.1.19.0.discovery.k8s.io/endpointslices permission only when using service source.Service source to support EndpointSlices.automountServiceAccountToken and serviceAccount.automountServiceAccountToken to true in Helm chart values.txtPrefix and txtSuffix arguments when both are provided.helm plugin schema.imagePullSecrets via helm global value.labelFilter and managedRecordTypes via dedicated helm values.serviceaccount.annotations keys and values, by rendering them using the tpl built-in function.extraContainers argument.excludeDomains argument.dnsConfig.kube_servicemonitor_info and kube_podmonitor_info for ServiceMonitor and PodMonitor resourceskube_podlog_info for PodLog resourcekube-prometheus-stack-app to 19.0.0edgedb to gel.cloudnative-pg (app) to v0.0.12.gel (app) to v1.0.1.Full Changelog: https://github.com/giantswarm/muster/compare/v0.0.177...v0.0.178
Full Changelog: https://github.com/giantswarm/muster/compare/v0.0.176...v0.0.177
Full Changelog: https://github.com/giantswarm/muster/compare/v0.0.175...v0.0.176
Full Changelog: https://github.com/giantswarm/muster/compare/v0.0.174...v0.0.175
Full Changelog: https://github.com/giantswarm/muster/compare/v0.0.173...v0.0.174
Full Changelog: https://github.com/giantswarm/muster/compare/v0.0.172...v0.0.173