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

Study: Cleanup of Bitwarden deployment

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • 3
    • OAPE Sprint 279, OAPE Sprint 280, OAPE Sprint 281
    • 3

      When Bitwarden provider is disabled in ExternalSecretsConfig after being enabled, as of now the corresponding deployment is not deleted.

      We need to study what is the best approach to clean up the deployment, considering the fact that there can be a secretstore or clustersecretstore referring to the Bitwarden provider while the user attempts to disable the provider in the ExternalSecretsConfig.

              rh-ee-mykastur Mytreya Kasturi
              rh-ee-mykastur Mytreya Kasturi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: