cephrgw-system: source cephrgw-credentials from Vault via VSO #262
Reference in New Issue
Block a user
Delete Branch "benvin/cephrgw-vault-vso"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Follow-up to the cephrgw-operator deploy (#261): source the operator's Ceph dashboard credentials from Vault via VSO instead of a hand-created Secret.
Changes
apps/base/cephrgw-system/vaultauth.yaml:VaultAuth(mountk8s/au/syd1, rolecephrgw-operator, SAcephrgw-operator,vaultConnectionRef: vso-system/default).apps/base/cephrgw-system/vaultstaticsecret.yaml: renders KVservice/cephrgw/dashboard-credentialsinto thecephrgw-credentialsSecret (keys copied verbatim → consumed by the Deployment viaenvFrom; the reloader annotation restarts the operator on rotation).Dependencies / ordering
cephrgw-credentialsSecret won't exist and the operator pod stays inCreateContainerConfigError(expected).Updated per review: now uses the shared
defaultk8s auth role + templated KV pathkubernetes/namespace/cephrgw-system/default/cephrgw-credentials, so terraform-vault #95 is no longer needed (closed). No terraform-vault change required. Seed values with: