Skip to content

Commit

Permalink
Update doc/whitepaper/Accelerating_Cloud_Native_in_Telco.md
Browse files Browse the repository at this point in the history
Co-authored-by: Taylor Carpenter <taylor@vulk.coop>
Signed-off-by: Tom Kivlin <52716470+tomkivlin@users.noreply.github.com>
  • Loading branch information
tomkivlin and taylor authored Nov 6, 2023
1 parent faca14d commit 64c6db5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion doc/whitepaper/Accelerating_Cloud_Native_in_Telco.md
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,7 @@ collaboration with existing communities, and included in existing well-establish

1. **Pre-validation.** The pre-validation of CNF needs to be performed against a reference that is common for all players,
which is the upstream Kubernetes and components from the CNCF ecosystem.
1. Each CNF shall be validated, including the implementation of any adaptations that may be required, within 3 months of
1. Each CNF shall be validated, including the implementation of any adaptations that may be required, within 4 months of
the Kubernetes release.
1. Every CNF shall certify adherence to cloud native principles and best practices using CNF Test Suite ([https://github.com/cncf/cnf-testsuite](https://github.com/cncf/cnf-testsuite)) as a vendor-neutral validation tool.
1. Pre-validating CNF against additional commercial distributions such as OpenShift, Tanzu, Rancher, and Hyperscaler solutions is a plus, but not mandatory.
Expand Down

0 comments on commit 64c6db5

Please sign in to comment.