Changes and Releases
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Fixed
- (deps) Update module github.com/prometheus/client_golang to v1.24.0 in #411 by @renovate[bot]
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.278...v0.0.279
Added
login: new --api-endpoint flag enables a fully offline direct-OIDC workload cluster login. When set together with --oidc-issuer, --oidc-client-id and --api-ca-file, the login skips all management cluster access, so the user needs no RBAC on the management cluster.template cluster: support --provider aks for templating AKS workload clusters via the cluster-aks / release-aks chart. Reuses --region, --azure-subscription-id, and --management-cluster for the required Azure inputs.template cluster: new --azure-cluster-identity-name and --azure-cluster-identity-namespace flags for both capz and aks, setting global.providerSpecific.azureClusterIdentity. Omitted when unset so the chart’s built-in defaults apply.
Changed
- Release binaries now include darwin/amd64, darwin/arm64, windows/amd64, and windows/arm64 alongside the existing linux targets. Windows binaries are named
kubectl-gs-windows-<arch>.exe. - krew manifest updated to reference bare binaries directly instead of tarballs, and extended with
windows/arm64 support. - (CAPA): Derive the number of VPC chunks from
--az-usage-limit. This enables small single-AZ VPC layouts (e.g. a /24 VPC with a /25 private subnet and a /26 public subnet).
Added
- Create a per-organization ClusterRoleBinding granting the org’s
automation ServiceAccount the kamaji-datastore-manager ClusterRole, so cluster apps using Kamaji can manage their kamaji.clastix.io/datastores CR. The referenced ClusterRole is provisioned by the global Kamaji app. - RBAC: Create
patch-charts Role for automation ServiceAccounts.
Changed
Fixed
- Return an error from GetClient when a backend has no live client in #985 by @QuentinBisson
Full Changelog: https://github.com/giantswarm/muster/compare/v1.0.7...v1.0.8
Fixed
- Allow full
affinity and podSecurityContext values by setting additionalProperties: true on their $ref-based schema entries, which were previously rejecting all keys (e.g. affinity.podAntiAffinity).