feat(keystone): system-scope service account - #2242
Merged
Merged
Conversation
automation-infrasetup-system.yaml.tpl — modelled on the existing automation-infrasetup.yaml.tpl: a Password generator plus an ExternalSecret producing Secret infrasetup-system, labelled keystone-role: system-readwrite, whose clouds.yaml sets system_scope: "all" and carries no project keys. sensor-keystone-automation-user-upsert.yaml — new system-readwrite case granting reader + member on --system all. member is the minimum SYSTEM_MEMBER requires; no cloud-wide admin.
cardoe
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
automation-infrasetup-system.yaml.tpl — modelled on the existing automation-infrasetup.yaml.tpl: a Password generator plus an ExternalSecret producing Secret infrasetup-system, labelled keystone-role: system-readwrite, whose clouds.yaml sets system_scope: "all" and carries no project keys.
sensor-keystone-automation-user-upsert.yaml — new system-readwrite case granting reader + member on --system all. member is the minimum SYSTEM_MEMBER requires; no cloud-wide admin.
What does this change do?
Upgrade impact
upgrade-impactlabel and a release note: runscriv createfrom therepository root and describe the required action in the generated
changelog.d/file. See RELEASING.md.Operator action means anything a deployment has to do beyond a normal resync:
deploy repo or values changes, new or removed secrets, enabling or disabling a
component, or a manual one-time step.