Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-1774

Handle byo certs in management ingress after Grafana changes to use oauth-proxy sidecar

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • Future
    • None
    • Observability
    • False
    • None
    • False
    • None

      https://github.com/stolostron/backlog/issues/23999

      Value Statement

      This function should be handled by OpenShift since we are a route now.
      The only work needed is validation that the openshift configured BYO certs (wildcard) work for the route.

      Acceptance Criteria

      •  How to handle the case that ingress has byo certs and client accesses Grafana using custom cert before?

      Definition of Done for Engineering Story Owner (Checklist)

      Development Complete

      •  Code is complete.
      •  Functionality is working.
      •  Any required downstream Docker file changes are made.

      Tests Automated

      •  Unit/function tests have been automated and incorporated into build.
      •  100% automated unit/function test coverage for new or changed APIs.

      Secure Design

      •  Security has been assessed and incorporated into your threat model.

      Multidisciplinary Teams Readiness

      •  Create an informative documentation issue using the Customer Portal_doc_issue template, and ensure doc acceptance criteria is met. Link the development issue to the doc issue.
      •  Provide input to the QE team, and ensure QE acceptance criteria (established between story owner and QE focal) is met.

      Support Readiness

      •  The must-gather script has been updated.

              Unassigned Unassigned
              dbennett@redhat.com Disaiah Bennett
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: