Skip to content

Commit 3e96f1a

Browse files
authored
Update cnf-best-practices-expectations-permissions.adoc
1 parent eb18735 commit 3e96f1a

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

modules/cnf-best-practices-expectations-permissions.adoc

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -305,22 +305,24 @@ See test case link:https://github.com/test-network-function/cnf-certification-te
305305

306306
* CNFs need to be prepared for nodes to reboot or shut down without notice
307307

308-
* CNFs shall configure pod disruption budget appropriately to maintain service continuity during platform upgrades
308+
* CNFs shall configure pod disruption budget appropriately to maintain service continuity during platform upgrades See test case link:https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md#observability-pod-disruption-budget[observability-pod-disruption-budget]
309309

310310
* Applications should not be tied to a specific version of Kubernetes or any of its components
311311

312312
[IMPORTANT]
313313
====
314314
Applications MUST specify a pod disruption budget appropriately to maintain service continuity during platform upgrades. The budget should be defined with a balance such that it allows operational flexibility for the cluster to drain nodes, but restrictive enough so that the service is not degraded over upgrades.
315315
316-
See test cases link:https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md#lifecycle-pod-recreation[lifecycle-pod-recreation], link:https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md#observability-pod-disruption-budget[observability-pod-disruption-budget]
316+
See test case link:https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md#lifecycle-pod-recreation[lifecycle-pod-recreation]
317317
====
318318

319319
.CNF requirement
320320
[IMPORTANT]
321321
====
322322
Pods that perform the same microservice and that could be disrupted if multiple members of the service are
323323
unavailable must implement pod disruption budgets to prevent disruption in the event of patches/upgrades.
324+
325+
See test case link:https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md#observability-pod-disruption-budget[observability-pod-disruption-budget]
324326
====
325327

326328
[id="cnf-best-practices-taints-and-tolerations"]

0 commit comments

Comments
 (0)