Added
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.144.1...v0.145.0
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.144.1...v0.145.0
values.yaml comments to the # @schema / # -- (helm-docs) convention and remove section-header dividers, so values.schema.json and the chart README.md are generated from the values file. Rendered manifests are unchanged.forward, cache, and kubernetes block parameters in the structured zone config:forward: maxIdleConns, maxConnectAttempts, dohMethod, tls, tlsServername, next, nextOnNodata, failfastAllUnhealthyUpstreams, failover, resolver.cache: zones, serveStale.verifyTimeout, disable.successZones, disable.denialZones.kubernetes: endpoint, tls, kubeconfig, apiserverQPS, apiserverBurst, apiserverMaxInflight, namespaceLabels, fallthroughZones, multicluster, startupTimeout.health directive in only the . server block. The health plugin is process-wide and can be enabled in just one Server Block, so emitting it in every zone block was invalid. ready is kept in every block (its readiness is aggregated across blocks).coredns.*.cache.serveStale.refreshMode schema enum to immediate/verify (was immediate/background), matching the CoreDNS cache plugin.coredns.* layout; all old paths remain backward compatible.coredns.public.* for the forward zone: autopath and a structured forward map mirroring the CoreDNS forward block, including maxConcurrent (max_concurrent).coredns.* interface.coredns.cluster.* for the in-cluster zone: domains, serviceCIDR, podCIDR, and a structured kubernetes map mirroring the CoreDNS kubernetes block.coredns.custom.controlPlane.*, securityContext.*, service.clusterIP, and ports.metrics.port.coredns.public.*, coredns.cluster.*, and each coredns.additionalZones[].*), replacing the former global coredns.cache, coredns.log, and coredns.loadbalance (removed). A zone that omits them falls back to the deprecated paths, then to built-in defaults.coredns.additionalLocalZones (a list of zone-name strings) with coredns.additionalZones, a list of fully-templated zone objects. The deprecated top-level additionalLocalZones string list still renders as kubernetes zones, now inheriting the coredns.cluster.* cache, log, and loadbalance config.Full Changelog: https://github.com/giantswarm/muster/compare/v0.21.0...v0.21.1
Full Changelog: https://github.com/giantswarm/muster/compare/v0.20.0...v0.21.0
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.144.0...v0.144.1
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.251...v0.0.252
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.143.7...v0.144.0
kube-prometheus-stack and prometheus-operator-crd to 22.0.0alloy-app to 0.21.0Full Changelog: https://github.com/giantswarm/backstage/compare/v0.143.6...v0.143.7
85.2.1)v0.32.1 to v0.33.0v3.11.3-distroless to v3.12.0-distroless12.3.3 to 12.7.17.4.0 to 7.5.11.8.3 to 1.8.4prometheus.prometheusSpec.containers and initContainers are now rendered through tpl (87.3.0), so templated values inside them are evaluated. We do not set these values, so no impact.Note: Update the matching-major
prometheus-operator-crdapp (to the v0.92.0 CRDs) before/alongside this upgrade. ThePrometheusTopologyShardingandPrometheusShardRetentionPolicyfeature gates are now enabled by default in v0.92.0.