From 2cf4159e076c22ccd15d3c43533cf64741f349dc Mon Sep 17 00:00:00 2001 From: ashleyvjoy Date: Tue, 18 Jun 2024 13:10:15 +0000 Subject: [PATCH 1/3] add docs for rbac changes to support Neptune --- content/docs/deployment/csmoperator/_index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md index aad628b7a3..e8572098b5 100644 --- a/content/docs/deployment/csmoperator/_index.md +++ b/content/docs/deployment/csmoperator/_index.md @@ -409,3 +409,4 @@ The specification for the Custom Resource is the same for all the drivers.Below **nodeSelector** - Used to specify node selectors for the driver StatefulSet/Deployment and DaemonSet. >NOTE: The `image` field should point to the correct image tag for version of the driver you are installing. +>NOTE: Since CSM Operator 1.6 is a pre-requisite for onboarding brownfield clusters to Apex Navigator For Kubernetes, a role/rolebinding will be created in the namespace that has csm objects to when dell connectivity client is deployed and removed when the connectivity client is uninstalled. If the client already exists in the cluster and csm is deployed/deleted, the roles and rolebindings will be created/deleted respectively as part of csm reconciliation. This is to allow the client access to the secrets in the namespace. From c485f711cfd985b2f47fb64031d7bd65176dd59f Mon Sep 17 00:00:00 2001 From: ashleyvjoy Date: Wed, 19 Jun 2024 06:04:43 +0000 Subject: [PATCH 2/3] fix linting --- content/docs/deployment/csmoperator/_index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md index e8572098b5..33dbe37f2d 100644 --- a/content/docs/deployment/csmoperator/_index.md +++ b/content/docs/deployment/csmoperator/_index.md @@ -409,4 +409,5 @@ The specification for the Custom Resource is the same for all the drivers.Below **nodeSelector** - Used to specify node selectors for the driver StatefulSet/Deployment and DaemonSet. >NOTE: The `image` field should point to the correct image tag for version of the driver you are installing. + >NOTE: Since CSM Operator 1.6 is a pre-requisite for onboarding brownfield clusters to Apex Navigator For Kubernetes, a role/rolebinding will be created in the namespace that has csm objects to when dell connectivity client is deployed and removed when the connectivity client is uninstalled. If the client already exists in the cluster and csm is deployed/deleted, the roles and rolebindings will be created/deleted respectively as part of csm reconciliation. This is to allow the client access to the secrets in the namespace. From 4b650068e7024f6caa460031a11a11a966493d97 Mon Sep 17 00:00:00 2001 From: ashleyvjoy Date: Wed, 19 Jun 2024 10:20:22 +0000 Subject: [PATCH 3/3] rephrase --- content/docs/deployment/csmoperator/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md index 33dbe37f2d..05e41186a9 100644 --- a/content/docs/deployment/csmoperator/_index.md +++ b/content/docs/deployment/csmoperator/_index.md @@ -410,4 +410,4 @@ The specification for the Custom Resource is the same for all the drivers.Below >NOTE: The `image` field should point to the correct image tag for version of the driver you are installing. ->NOTE: Since CSM Operator 1.6 is a pre-requisite for onboarding brownfield clusters to Apex Navigator For Kubernetes, a role/rolebinding will be created in the namespace that has csm objects to when dell connectivity client is deployed and removed when the connectivity client is uninstalled. If the client already exists in the cluster and csm is deployed/deleted, the roles and rolebindings will be created/deleted respectively as part of csm reconciliation. This is to allow the client access to the secrets in the namespace. +>NOTE: The CSM Operator 1.6 is pre-requisite for onboarding brownfield clusters with Apex Navigator For Kubernetes. When the Dell connectivity client is installed, a role and rolebinding will be established in the namespace containing CSM objects, and these will be removed when the client is uninstalled. If the client is already present in the cluster and CSM is deployed or deleted, the roles and rolebindings will be correspondingly created or removed during CSM reconciliation. This process ensures that the client can access the secrets in the namespace.