Our container SME noticed that there was a new namespace created a couple days ago which appears “empty” for the most part. This page talks about it but sort of implies it requires manual steps to set up.
Nobody did anything to push this into the cluster, and, we protect 4 distinct clusters with cvlt yet only one of them has this new namespace in it. All 4 are backing up just fine (all namespaces that is) so, what is it and why does it appear to be randomly created in our clusters?
thanks!
Hello
Thanks for the question and details. Looking around i can see there are some internal threads talking about the following symptoms:
Issue description:
- When a customer creates their first Resource Modifier in Command Center, Commvault pushes (creates) the Custom Resource Definition (CRD) for resourcemodifier kind on the Kubernetes cluster. This is a cluster-wide or non-namespaced resource.
- But Creation of the first Resource Modifier will fail if the customer has not manually created the cv-config namespace
This tells me that the Resource Modifier could be created and have no use. Given it is empty you can go ahead and remove it would any issue. If Commvault need it back, we will create a new one.
The following goes over the steps to remove it:
Kind regards
Albert Williams
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.