hard20 pts · first answer countsgitopssecrets-managementargo-cd

Secrets in a GitOps repo

Your team uses Argo CD and wants everything in Git, including database credentials. Which approach keeps GitOps without storing plaintext secrets in Git?

A.Commit ExternalSecret references synced from a secret manager, or encrypted values with Sealed Secrets or SOPS.B.Commit plain Kubernetes Secret YAML to a private repo, since only the team can read a private repo.C.Base64 encode every value twice before committing, so nobody browsing the repo can read them.D.Keep secrets only as Argo CD UI parameter overrides, which are never saved anywhere outside the UI.

Discussion 0

Join free to post in the discussion.

Secrets in a GitOps repo

Discussion 0

Related questions