User Stories

As a ROSA hypershift customer, I can use the ocm web ui for ROSA hypershift clusters the same ways I can use them for ROSA classic clusters, and the interfaces make subtle changes depending on which topology I'm currently using. For example, when I have a classic cluster, I can CRUD machinepools. When I have a hypershift cluster, instead I can CRUD nodepools.

TODO what are all the differences besides nodepools? I expect the only differences to be NodePools and Updates.

Acceptance Criteria

• All the things that have to be done for the feature to be ready to
  release.

Default Done Criteria

• All existing/affected SOPs have been updated.
• New SOPs have been written.
• Internal training has been developed and delivered.
• The feature has both unit and end to end tests passing in all test
  pipelines and through upgrades.
• If the feature requires QE involvement, QE has signed off.
• The feature exposes metrics necessary to manage it (VALET/RED).
• The feature has had a security review.* Contract impact assessment.
• Service Definition is updated if needed.* Documentation is complete.
• Product Manager signed off on staging/beta implementation.

Dates

Integration Testing:
Beta:
GA:

Current Status

GREEN | YELLOW | RED
GREEN = On track, minimal risk to target date.
YELLOW = Moderate risk to target date.
RED = High risk to target date, or blocked and need to highlight potential
risk to stakeholders.

References

Links to Gdocs, github, and any other relevant information about this epic.