You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ For managing consistency, we had like our certified partners to integrate the co
14
14
15
15
1) Partner runs the conformance tests for every major/minor version pre-releases of their Kubernetes distribution prior to at least 7 days of its public/stable release, (alpha and production also called as public preview and GA at Microsoft respectively).
16
16
- Instruction for running conformance tests are here.
17
-
- Partners will validate the latest, latest-1 and latest-2 Kubernetes distro.
17
+
- Partners will validate the latest, latest-1 and latest-2 Kubernetes distro.
18
18
2) Partner publishes the conformance test results emitted by test automation tool, sonobuoy, into partner results folder on validation GitHub repository.
19
19
- Partner K8s distro version is conformant when test results are positive.
20
20
- If test suite failed, partner can verify failure reason emitted by the test automation tool and optionally raise an issue on validation GitHub for Microsoft review.
0 commit comments