-
Epic
-
Resolution: Done
-
Undefined
-
openshift-4.14
-
None
-
CNCF certification process
-
Strategic Product Work
-
False
-
-
False
-
Done
-
OCPSTRAT-44 - MicroShift CNCF certification
-
OCPSTRAT-44MicroShift CNCF certification
-
0% To Do, 0% In Progress, 100% Done
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- Submit certification results for MicroShift as a Kubernetes distribution.
- See https://www.cncf.io/certification/software-conformance/
Why is this important?
- Recognise MicroShift as a certified Kubernetes distribution
Scenarios
- Provide a "simple" workflow to set up MicroShift certification environment and successfully run the tests
Acceptance Criteria
- Have MicroShift pass all CNCF tests
- Set up CNCF CI
- Submit CNCF tests and have them approved
Dependencies (internal and external)
- CNCF certification environment and MicroShift fixes
- CNCF can only certify a released version of the s/w
Open questions::
- What needs to be done for the certification process besides passing the CNCF tests?
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- is blocked by
-
USHIFT-390 CNCF certification environment and MicroShift fixes
- Closed
- relates to
-
USHIFT-1368 Submit a CNCF certification PR using MicroShift 4.14 GA builds
- Closed