Changed
- Align files according to platform standards in #622 by @giantswarm-align-files[bot]
Full Changelog: https://github.com/giantswarm/starboard-exporter/compare/v1.2.13...v1.2.14
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Full Changelog: https://github.com/giantswarm/starboard-exporter/compare/v1.2.13...v1.2.14
Full Changelog: https://github.com/giantswarm/starboard-exporter/compare/v1.2.12...v1.2.13
Full Changelog: https://github.com/giantswarm/starboard-exporter/compare/v1.2.11...v1.2.12
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.218.2...v0.218.3
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.218.1...v0.218.2
architecture value ("" | amd64 | arm64) to pin the workload to a CPU architecture. Setting arm64 renders both the kubernetes.io/arch node selector and the toleration for the kubernetes.io/arch=arm64:NoSchedule taint that Giant Swarm arm64 node pools carry – both are required, and setting only one fails in a different, non-obvious way, so a single value drives both. Defaults to "", which renders nothing, so output is unchanged for existing users. The scheduling logic lives in the hello-world.podScheduling helper and merges with the explicit nodeSelector/tolerations values.nodeSelector, which the generated schema rejected via additionalProperties: false – any entry failed with “additional properties ‘affinity/podSecurityContext fix in 3.0.4.oidc.responseTypes to ["code"] only, disabling the insecure OAuth2 implicit flow by default. Any client relying on the implicit or hybrid flow without setting oidc.responseTypes explicitly will stop working. Set oidc.responseTypes explicitly to ["code", "token", "id_token"] to keep them.architect orb from 9.4.1 to 10.1.2.Full Changelog: https://github.com/giantswarm/backstage/compare/v0.218.0...v0.218.1
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.217.0...v0.218.0