Changed
- (deps) Update azure/setup-helm action to v5.0.1 in #361 by @renovate[bot]
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.233...v0.0.234
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.233...v0.0.234
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.232...v0.0.233
Full Changelog: https://github.com/giantswarm/muster/compare/v0.18.1...v0.18.2
Full Changelog: https://github.com/giantswarm/klausctl/compare/v0.2.15...v0.2.16
Full Changelog: https://github.com/giantswarm/muster/compare/v0.18.0...v0.18.1
Full Changelog: https://github.com/giantswarm/agentic-platform/compare/v1.15.2...v1.15.3
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.231...v0.0.232
Full Changelog: https://github.com/giantswarm/klaus-oci/compare/v0.0.54...v0.0.55
Full Changelog: https://github.com/giantswarm/klaus-operator/compare/v0.0.107...v0.0.108
kagent.oauth2-proxy: request the offline_access scope and set cookie-refresh: "10m" so oauth2-proxy refreshes the upstream Dex id_token before it expires. Without this, a session older than the Dex id_token TTL forwarded an expired bearer as the on-behalf-of subject token, muster rejected it (subject_token_validation_failed, “token is expired”), and the agent silently fell back to its ServiceAccount (M2M) identity. Applied to both the umbrella agentic-platform and the agentic-platform-connectivity values.yaml (kept in sync; the umbrella copy is the one deployed in meta-package installs).