Uploaded image for project: 'OpenShift API Server'
  1. OpenShift API Server
  2. API-1825 Document feasibility of KMS on OCP
  3. API-1691

Research the pros and cons of managing the KMS plugins

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 5
    • None
    • None
    • None
    • None

      For every KMS/TPM we would want to support, a platform specific plugin will need to be run. Do we want to manage it via our operators, or should we leave that to the customers?

      For this spike, it would be great to have a list of the benefits and disadvantages of managing it ourselves compared to leaving it to the customer.

      FWIW, HyperShift is managing the plugins for the customers.

              dgrisonn@redhat.com Damien Grisonnet
              dgrisonn@redhat.com Damien Grisonnet
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: