Running Rancher v2.2.6, with 1 cluster. I’m unable to modify and/or delete any secrets that happen to be in the “All” namespace, here’s what I’ve tried so far:
Modifying secrets in All namespace (via Rancher UI):
– Update secret with new information
– Redeploy workload to use updated secret, but old secret still used
– Attempted as local admin, as well as an Active Directory account with permissions to the cluster
Deleting secrets in All namespace (via Rancher UI):
– In the Namespace column, the “All” value is grayed out
– Click on secret, choose Delete, and get prompted to continue. Continue, returns to UI with no error, yet secret is still present
– Attempted as local admin, as well as an Active Directory account with permissions to the cluster
Workaround:
– Removed secret using kubectl. Check secret list again and the secret is no longer there, yet it is still in the Rancher UI
– Created new secret in Rancher UI, and it worked to use the same name but put it in the Default namespace instead of All (Note that the UI shows 2 secrets with the same name in each namespace)
– Redeploy the workload (which is also in the Default namespace) and it does pick up the updated secret
– Unclear if the same named secret in the All namespace is even relevant/used
Is there a limitation as to not being able to modify/delete secrets if they are in the All namespace? If not, how can this be accomplished? Thanks.