Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-4754

Make the external secrets operator a supported Red Hat operator

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Auth
    • None
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

      Proposed title of this feature request

      Make the external secrets operator a supported Red Hat operator

      What is the nature and description of the request?

      The external secrets operator is a important piece of software that acts as middleware for the various vault solutions and provides multi-tenancy between the tenants on a openshift cluster. The operator is now a community operator with no support from RedHat, the community operator index is as-is, so we cannot use this as a trusted source to create a index for air-gapped environments. Because we are going to use this operator in production we need to get it supported, or at least have enough control over the operator that we can control all the aspects, with the community operator index we simply cannot do this.

      Why does the customer need this? (List the business requirements here)

      We are a large openshift customer (33 production clusters as time of writing) and the number of clusters will go up. We use gitops way of working (argocd, tekton etc) to use the most out of the available tooling on openshift. But we need a good multi tenancy vault layer, with external secrets operator this is possible, but we need to have a supported version.
      Without a supported version, the toolset for Openshift is missing features and will cause the adoption of openshift to stagnate on our location.

      List any affected packages or components.

      external secrets operator - https://github.com/external-secrets/external-secrets

            atelang@redhat.com Anjali Telang
            rhn-support-andbartl Andy Bartlett
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: