Skip to content

fix: allow config update jobs to create temporary secrets #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vthwang merged 1 commit into from
Sep 24, 2026
Merged

fix: allow config update jobs to create temporary secrets #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions helm/vtafarm-api/templates/vtafarm-api/clusterrole.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,14 @@ rules:
resources: ["roles", "rolebindings"]
verbs: ["get", "list", "create", "delete"]
# VTA setup wizard: config injection, storage, networking, jobs, deployments.
# The master seed lives in HashiCorp Vault (not a K8s Secret), so vtafarm-api
# no longer needs secrets permissions or the secret-manager ClusterRole bind.
# Configuration updates pass TOML through temporary Secrets and remove them
# after the write or rollback Job finishes. No Secret read access is needed.
- apiGroups: [""]
resources: ["configmaps"]
verbs: ["get", "list", "create", "delete"]
- apiGroups: [""]
resources: ["secrets"]
verbs: ["create", "delete"]
- apiGroups: [""]
resources: ["persistentvolumeclaims"]
verbs: ["get", "list", "create", "delete", "watch"]
Expand Down
Loading