Uploaded image for project: 'External Secrets Operator for Red Hat OpenShift'
  1. External Secrets Operator for Red Hat OpenShift
  2. ESO-334

Implementation to support customizations at install time(env var)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • eso-1.1
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • OAPE Sprint 284
    • 1

      Currently, the External Secrets Operator manages environment variables for all components (ExternalSecretsCoreController, Webhook, CertController, BitwardenSDKServer) globally. There's no mechanism for users to add or override environment variables on a per-component basis for specific use cases like:  Custom logging configurations ,Feature flags for specific components.

      Acceptance criteria:

      1. Add OverrideEnv []corev1.EnvVar field to ComponentConfig API with validation to reject reserved prefixes (HOSTNAME, KUBERNETES_, EXTERNAL_SECRETS) 
      1. Implement environment variable merge logic that applies user-defined env vars from overrideEnv to matching component deployments, with user values taking precedence over operator defaults.
      1. Add unit tests and E2E tests.

       

              rh-ee-sbhor Siddhi Bhor
              rh-ee-sbhor Siddhi Bhor
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: