From 776cfc6d5b9cc54b8f11fa4e1be52c6f18ef62af Mon Sep 17 00:00:00 2001 From: Alexandre Menezes Date: Tue, 15 Nov 2022 18:16:33 -0500 Subject: [PATCH] CHANGE capability level description to independent (#6134) - CHANGED accumulating for independent levels on cap description Signed-off-by: acmenezes Signed-off-by: acmenezes --- website/content/en/docs/overview/operator-capabilities.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/en/docs/overview/operator-capabilities.md b/website/content/en/docs/overview/operator-capabilities.md index 8f8a873a9c..2e550254f9 100644 --- a/website/content/en/docs/overview/operator-capabilities.md +++ b/website/content/en/docs/overview/operator-capabilities.md @@ -8,7 +8,7 @@ Operators come in different maturity levels in regards to their lifecycle manage ![operator-capability-level](/operator-capability-level.png) -Each capability level is associated with a certain set of management features the Operator offers around the managed workload. Operator that do not manage a workload and/or are delegating to off-clusters orchestration services would remain at Level 1. Capability levels are accumulating, i.e. Level 3 capabilities require all capabilities desired from Level 1 and 2. +Each capability level is associated with a certain set of management features the Operator offers around the managed workload. Operator that do not manage a workload and/or are delegating to off-clusters orchestration services would remain at Level 1. Capability levels are designated from level 1 to level 5. Each capability represents its own set of features and may be independent of each other. ## Terminology