Repository navigation
[0.9.0] Install user provisioning RBAC during K3s setup - #241
Merged
sciabarracom merged 1 commit intoOct 24, 2026
Merged
Conversation
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
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.
Fresh K3s installations currently require a separate manual RBAC apply before the Secret-authorized user provisioning API can create tenants and their routes. Add
ops cloud k3s rbacand invoke it fromops cloud k3s createafter cert-manager setup.Related to Michele's request: https://github.com/nuvolaris/projects/issues/447.
Complements the Admin API implementation already merged into
0.9.0: apache/openserverless-admin-api#64.The task creates the
openserverlessnamespace if absent and applies a bundled copy of the existing provisioning Role/RoleBinding. The manifest is byte-for-byte identical todeploy/user-provisioning/rbac.yamlin Apache Admin API0.9.0. It binds the dedicated role toopenserverless-wsku; the service account can be created later by the OpenServerless installation. A separate CLI invocation after K3s installation picks up the newly generated kubeconfig.The task does not create or overwrite
openserverless-user-provisioning-token. The provisioning token remains externally managed, and existing broader roles are unchanged. Command usage and installation behavior are documented incloud/k3s/docopts.md.Validation: YAML parsing, exact manifest comparison against Apache Admin API
0.9.0, task discovery, dry-runs ofrbacand the fullcreatetask, andgit diff --checkpassed.Live validation on the existing K3s baseline VM also passed using this exact commit (
0fa6f0f):ops cloud k3s rbaccreated the dedicated Role/RoleBinding on the first run and reported both unchanged on the second. Ten authorization checks used the actual Admin API pod's mounted service-account token: all eight required provisioning permissions were allowed, while namespace and ClusterRoleBinding creation remained denied. All 92 pre-existing resource identities/specifications/policies and 49 application source files were preserved. The Admin API pod stayed Ready without restart; the provisioning token Secret was not created or modified. The Role and RoleBinding remain installed. The full K3s installation was not repeated.