Changed
- Align files according to platform standards in #156 by @giantswarm-align-files[bot]
Full Changelog: https://github.com/giantswarm/klaus-operator/compare/v0.0.104...v0.0.105
Full Changelog: https://github.com/giantswarm/klaus-operator/compare/v0.0.104...v0.0.105
MCPServer / Workflow) now follow the app-owned CRDs pattern instead of riding the agentic-platform-crds bundle. The meta-package’s generic component loop gains an optional crds policy field (rendered into the child HelmRelease’s spec.install.crds / spec.upgrade.crds); the muster component sets crds: CreateReplace and no longer dependsOn the bundle, so its CRDs travel with the muster app chart at the same resolved version and upgrade atomically on every release (Flux CreateReplace overcomes Helm’s “never upgrades crds/-dir CRDs” limitation). agentic-platform-mcps now dependsOn: [muster, agentic-platform-crds] (its MCPServer CRs need the muster-owned CRD; its agentgateway CRs still need the bundle). The agentic-platform-crds bundle drops its muster-crds dependency (it still ships agentgateway / kagent / agent-sandbox CRDs). The handoff is non-destructive: the live muster CRDs carry helm.sh/resource-policy: keep, so dropping the bundle dependency does not delete them — the muster release adopts and upgrades them on its next reconcile. Requires a muster app chart that ships its CRDs in crds/ (tracked separately).muster application chart now ships its own MCPServer and Workflow CRDs in helm/muster/crds/ (Helm 3 crds/ directory), with helm.sh/resource-policy: keep baked in. Combined with Flux install.crds: CreateReplace / upgrade.crds: CreateReplace on the muster HelmRelease, the CRDs travel with the app at the same version and upgrade atomically on every release, removing CRD-vs-app drift. The standalone muster-crds chart is retained for non-Flux/standalone consumers; make generate-crds now writes both locations from the same Go-type source. Chart docs (NOTES, README, values) now explain the CRD handling for plain-Helm users: fresh helm install includes the CRDs automatically, while CRD upgrades must be applied out-of-band (helm show crds giantswarm/muster | kubectl apply --server-side -f -) because Helm does not manage crds/ upgrades natively — an intentional, still-current Helm design decision (HIP-0011), unchanged in Helm 4. The previous bundle-split docs that claimed the app chart “no longer ships the CRDs” were corrected.Full Changelog: https://github.com/giantswarm/muster/compare/v0.10.0...v0.11.0
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.224...v0.0.225
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.223...v0.0.224
Full Changelog: https://github.com/giantswarm/agentic-platform/compare/v1.6.3...v1.6.4
Full Changelog: https://github.com/giantswarm/klaus-operator/compare/v0.0.103...v0.0.104
Full Changelog: https://github.com/giantswarm/agentic-platform/compare/v1.6.2...v1.6.3
Full Changelog: https://github.com/giantswarm/agentic-platform/compare/v1.6.1...v1.6.2