Uploaded image for project: 'OPCT - OpenShift Provider Compatibility Tool'
  1. OPCT - OpenShift Provider Compatibility Tool
  2. OPCT-325

Research HCP Management Cluster - one-off OPCT data collection on platform type None/provider AWS

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • CLI
    • 3

      Goal:

      • Run one-off default conformance workflow in a default HCP Management Cluster installed with platform type None on AWS provider to collect OPCT results of HCP to research a possible support path
      • Collect any potential hypershift e2e to compose the layered product on top of regular e2e coformance test executed by the default workflow

      It's not expect drift in the default conformance workflow when comparing with default AWS self-managed, as HCP management cluster would be a regular self-managed cluster.

              Unassigned Unassigned
              rhn-support-mrbraga Marco Braga
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: