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

trustee operator requires SSL objects even if if is configured for http

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Medium Medium
    • None
    • 0.1.0
    • trustee-operator
    • None
    • False
    • None
    • False
    • 3
    • 0
    • Low

      Description

      <What were you trying to do that didn't work?>

      Trying to configure trustee operator with http

      Steps to reproduce

      <What actions did you take to hit the bug?>
      1. Set "insecure" to true in kbs-config-cm
      2. Did all non-ssl related config steps 
      3. waited for trustee pod to start

      Expected result

      <What did you expect to happen?>

      Configure trustee with http without all the ssl related secrets

      Actual result

      <What actually happened?>

      Controller did not start trustee because it was missing required objects

      Impact

      <How badly does this interfere with using the software?>

      Trustee wont start until you create all the ssl related objects

      Env

      <Where was the bug found, i.e. OCP build, operator build, kata-containers build, cluster infra, test case id>

      OCP 4.16.11

      Trustee Operator 0.1.0 (pre-release) 

      Additional helpful info

      <logs, screenshot, doc links, etc.>

              Unassigned Unassigned
              cmeadors@redhat.com Cameron Meadors
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: