-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
The fifth step in GAing the MCN API is creating at least five tests in openshift/origin. These tests will act as a GA readiness signal and build confidence in the feature's functionality. More information on the requirements for the tests can be found here.
Done when:
- At least five tests are defined for MCN.
- Note that each test will be tracked in its own individual card linked to this one.
- The tests meet the criteria specified in the API requirements.
- All origin tests properly cleanup added/changed resources on test completion or failure.
Requires:
- depends on
-
MCO-1501 Support Custom MCPs in MCN
-
- Closed
-
-
OCPBUGS-54951 Multiple pods exiting an excessive amount of times on techpreview serial
-
- Closed
-
- incorporates
-
MCO-1595 [Origin Test 1/5] Validate MCN properties
-
- Closed
-
-
MCO-1596 [Origin Test 2/5] Validate MCN condition status transitions
-
- Closed
-
-
MCO-1597 [Origin Test 3/5] Validate MCN condition status on node degrade
-
- Closed
-
-
MCO-1598 [Origin Test 4/5] Validate MCN on node creation and deletion
-
- Closed
-
-
MCO-1599 [Origin Test 5/5] Validate MCN object can only be accessible from its associated MCD
-
- Closed
-
- is depended on by
-
MCO-1064 [API 6/6] Graduate MCN feature gate to default in 4.20
-
- Closed
-
-
MCO-1063 Performance and e2e testing
-
- To Do
-
- links to