Skip to content
This repository was archived by the owner on Oct 1, 2026. It is now read-only.

Migrate from golang-external-secrets to External Secrets Operator (ESO) - #402

Open
OAharoni-RedHat wants to merge 1 commit into
validatedpatterns:mainfrom
OAharoni-RedHat:eso-migration
Open

OAharoni-RedHat wants to merge 1 commit into
validatedpatterns:mainfrom
OAharoni-RedHat:eso-migration

Conversation

@OAharoni-RedHat

Copy link
Copy Markdown

Summary

Migrates the secrets backend from the community golang-external-secrets Helm chart to the Red Hat supported External Secrets Operator (ESO).

Note: values-hub.yaml is a symlink to values-datacenter.yaml — all changes are in values-datacenter.yaml.

Changes

  • Namespaces: Replace golang-external-secrets with external-secrets-operator and external-secrets
  • Subscriptions: Add eso subscription for openshift-external-secrets-operator (channel: stable-v1)
  • Applications: Replace secrets-operator (golang-external-secrets chart 0.2.) with openshift-external-secrets (chart 0.0.)
  • Projects: Remove now-unused golang-external-secrets ArgoCD project

Pattern

Follows the same ESO migration pattern established in layered-zero-trust.

Made with Cursor

- Replace golang-external-secrets namespace with external-secrets-operator and external-secrets
- Add ESO operator subscription (openshift-external-secrets-operator, stable-v1 channel)
- Replace golang-external-secrets Helm chart application with openshift-external-secrets (0.0.*)
- Remove now-unused golang-external-secrets ArgoCD project
- Follows the same ESO migration pattern as layered-zero-trust

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant