feat(009): fleet placement RBAC for the control-plane pod#62
Merged
Conversation
Spec 011's acceptance walk surfaced that the pod ran as the namespace default ServiceAccount with no cluster grants, so fleet placement and teardown died Forbidden at the API server. Adds the statecraft ServiceAccount, the statecraft-fleet ClusterRole scoped to the resource types fleet-native touches, and its binding; the pod template adopts the ServiceAccount.
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
1 participant
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.
Spec 011's acceptance walk surfaced that the pod ran as the namespace default ServiceAccount with no cluster grants, so every fleet placement and teardown died Forbidden at the API server (the rebuilt cluster never carried grants; spec 006's first-deploy finding predates the rebuild).
Adds
rbac.yamlto the statecraft manifests: a dedicatedstatecraftServiceAccount, astatecraft-fleetClusterRole scoped to exactly the resource types fleet-native touches (namespaces get/list/create; deployments, services, PVCs, jobs, ingresses, networkpolicies full lifecycle), and its ClusterRoleBinding. The Deployment's pod template adopts the ServiceAccount. ClusterRole because tenant namespaces (t-<tenantId>) are dynamic. Paired with a dated amendment in spec 009.