Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-3194

Can't add new secret to trustee

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • trustee-operator
    • None
    • Kata Sprint #255
    • 0
    • 0.000

      Description

      It is not possible to add a new secret to trustee after trustee-operator has been deployed.

      Steps to reproduce

      • Create new secret:
      kubectl create secret generic super-secret --from-literal key=hello -n kbs-operator-system
      • Edit KbsConfig CRD by adding a reference to the newly created secret:

       

      kbsSecretResources:
      - super-secret
      

       

      Expected result

      trustee deployment is updated with new secret volume mount and secret is present in trustee file system.

      Actual result

      The trustee deployment is not updated, hence the new secret is not mounted into trustee file system

            rh-ee-lmilleri Leonardo Milleri
            rh-ee-lmilleri Leonardo Milleri
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: