fix(gitea-gke): configure ESO SecretStore to use workload identity with gitea SA
This commit is contained in:
@@ -16,8 +16,15 @@ spec:
|
|||||||
provider:
|
provider:
|
||||||
gcpsm:
|
gcpsm:
|
||||||
projectID: neuron-785695
|
projectID: neuron-785695
|
||||||
# Workload Identity is used automatically — no explicit auth needed
|
# Workload Identity — ESO impersonates the gitea-gke GCP SA to access
|
||||||
# when the pod's ServiceAccount has the iam.gke.io/gcp-service-account annotation.
|
# Secret Manager. The gitea SA has secretAccessor on gitea-db-password.
|
||||||
|
auth:
|
||||||
|
workloadIdentity:
|
||||||
|
clusterLocation: us-central1
|
||||||
|
clusterName: neuron-platform
|
||||||
|
serviceAccountRef:
|
||||||
|
name: gitea
|
||||||
|
namespace: gitea
|
||||||
---
|
---
|
||||||
# gitea-db — Gitea database password, pulled from GCP Secret Manager.
|
# gitea-db — Gitea database password, pulled from GCP Secret Manager.
|
||||||
# The Secret Manager secret "gitea-database-url" stores the full DSN, but we
|
# The Secret Manager secret "gitea-database-url" stores the full DSN, but we
|
||||||
|
|||||||
Reference in New Issue
Block a user