Uploaded image for project: 'OpenShift API Server'
  1. OpenShift API Server
  2. API-1789

CI implementation: Create TLS artifacts registry

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • CI implementation: Create TLS artifacts registry
    • Strategic Product Work
    • 5
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-709 - [internal] All OCP internal certificate chains must have clear ownership
    • 75% To Do, 25% In Progress, 0% Done

      Epic Goal

      This is the epic tracking the work to collect a list of TLS artifacts (certificates, keys and CA bundles).

      This list will contain a set of required an optional metadata. Required metadata examples are ownership (name of Jira component) and ability to auto-regenerate certificate after it has expired while offline. In most cases metadata can be set via annotations to secret/configmap containing the TLS artifact.

      Components not meeting the required metadata will fail CI - i.e. when a pull request makes a component create a new secret, the secret is expected to have all necessary metadata present to pass CI.

      This PR will enforce it WIP API-1789: make TLS registry tests required

              wk2019 Ke Wang
              cucushift-bot Cucushift Bot
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: