Determine openebs ns from the CLI.

[Abhinandan-Purkait]

We might need to rethink out K8sClient structure, as of now there are two candidates for similar resource fields

• namespace i.e. resource namespace for user created resources like pvc, pod, etc
• openebs-namespace i.e. the namespace where a specific Storage engine is installed

The -n flag is used to take the pvc namespace and same cannot be used to take the openebs namespace simultaneously.
Determining the openebs ns from the cli would help here.

[kmova]

• Check with ClusterRoleBinding or ServiceAccountName ( existence of openebs.io in labels)
• Consider the possibility of jiva and openebs in different namespaces

[vharsh]

Final verdict: Lets stick to figuring out the namespace by using the openebs.io/component-type label KVs present on the CSI controller.

There might be some really old versions of OpenEBS(e.g. 2.1) which might not support this as the CSI controller pods are running in the kube-system namespace.

[Abhinandan-Purkait]

We are tracking our approach and questionnaires in the respective document.
https://docs.google.com/document/d/1Zi8rPPWsxzpfTZrCScwoT4sAV_QSySMh2tjrpeKMqkE/edit