Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-627

Placeholder for cert-manager review activities

    XMLWordPrintable

Details

    • Feature
    • Resolution: Obsolete
    • Major
    • None
    • None
    • Security & Compliance
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Impediment
    • 100
    • 100% 100%
    • 0
    • 0

    Description

      Epic Goal

      • Review design and development PRs that require feedback from NE team.

      Why is this important?

      • Customer requires certificates to be managed by cert-manager on configured/newly added routes.

      Acceptance Criteria

      • All PRs are reviewed and merged.

      Dependencies (internal and external)

      1. CFE team dependency for addressing review suggestions.

      Done Checklist

      • DEV - All related PRs are merged.

      Attachments

        Issue Links

          depends on

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-704 As a developer, I want to get approval for enhancement proposals that describe route integration design and api changes.

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-706 As a developer, I want to develop updates of route tls config based on tls secret reference

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-758 As a developer, I want to develop e2e test cases to validate secret injection on routes

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is cloned by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-172 Cert-manager support router to load secrets

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • In Progress
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CM-16 [long-term] Better Route Support

          • Undefined - Priority not specified.
          • New

          Activity

            People

              ddharwar@redhat.com Deepthi Dharwar
              tgeer@redhat.com Trilok Geer
              Thejas N (Inactive), Trilok Geer
              Melvin Joseph Melvin Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: