Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-3272

Dev console Environment page GA

    XMLWordPrintable

Details

    • Environment page GA
    • False
    • None
    • False
    • To Do
    • SECFLOWOTL-96 - [On Hold] Dev console Environment page GA
    • 0
    • 0% 0%

    Description

      Epic Goal

      Make the Environment page in the Developer perspective of OpenShift console Generally Available. 

      Why is this important?

      The Environment page has been available as Tech Preview in OpenShift GitOps since v1.1. Since the introduction of dynamic plugins, the team is now able to wholly own the implementation and support of GitOps-related pages in the console. 

      With our dynamic plugin going live in OCP 4.15, we should make this page officially GA and be confident in our ability to support customers in using it. 

      Acceptance Criteria (Mandatory)

      • Deprecation: The static plugin is removed from OCP 4.15 onwards and the dynamic plugin is the standard
      • Dependencies: All dependencies are on the latest versions (i.e. dynamic plugin SDK)
      • Version support: The Environment page works in all supported versions of the OpenShift GitOps operator, on all supported versions of OCP
      • Integration requirements: The team has researched and are aware of all testing (integration, accessibility, etc.) that may be required by the console team for a dynamic plugin
      • Team familiarity: At least two team members in different timezones are familiar with the relevant code, these people are known to the rest of the team as SMEs for the Environment page
      • Testing: CI is passing and includes automated tests for the relevant part of the codebase
      • Test coverage: The team is satisfied with the test coverage for the relevant part of the code
      • Documentation: A page or section exists in the official OCP docs for the dynamic plugin
      • Support resources: CEE team members have an instructional/training document for the Environment page, including information about the static vs dynamic plugin. This training is linked here: https://docs.google.com/spreadsheets/d/1Px40DbUVZCXZdPyNQtrS4FJ9Fagmzmvl219ACnkvpFM/edit#gid=0 

       

      Dependencies (internal and external)

      1. Static plugin removal https://issues.redhat.com/browse/GITOPS-2369
      2. Dynamic plugin SDK updates https://issues.redhat.com/browse/GITOPS-2316 
      3. Previously reported bugs:
        1. https://issues.redhat.com/browse/GITOPS-2746
        2. https://issues.redhat.com/browse/GITOPS-2493 (dynamic plugin only)
        3. https://issues.redhat.com/browse/GITOPS-1322 
        4. https://issues.redhat.com/browse/GITOPS-2306 
        5. https://issues.redhat.com/browse/GITOPS-2677 
        6. https://issues.redhat.com/browse/GITOPS-2735
        7. https://issues.redhat.com/browse/GITOPS-3627

      Previous Work (Optional):

      1. Dynamic plugin implementation epic: https://issues.redhat.com/browse/GITOPS-1313 

      Open questions:

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

      Attachments

        Activity

          People

            Unassigned Unassigned
            halawren@redhat.com Harriet Lawrence
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: