You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our setup is one csec where we track in one namespace a dynamic secret that changes roughly every ~6 hours via conrojb. This secret gets copied to all other namespaces to be available for imagePulls to ecr registry via clusterSecret.
We've recently went to using replace_existing(reference) in our helm chart on clusters but we are seeing issues in the pod logs with the namespace_watcher function. This was to avoid manually having to kill clusterSecret pod to have the upstream secret propagate to the other target namespaces. This doesn't seem to be working currently and we are seeing an exception in the handler.
In this example below here is somecoolnamespace that is one of the ones that is iterated over and throwing the exception on namespace_watcher
Our setup is one csec where we track in one namespace a dynamic secret that changes roughly every ~6 hours via conrojb. This secret gets copied to all other namespaces to be available for imagePulls to ecr registry via clusterSecret.
We've recently went to using
replace_existing
(reference) in our helm chart on clusters but we are seeing issues in the pod logs with the namespace_watcher function. This was to avoid manually having to kill clusterSecret pod to have the upstream secret propagate to the other target namespaces. This doesn't seem to be working currently and we are seeing an exception in the handler.In this example below here is somecoolnamespace that is one of the ones that is iterated over and throwing the exception on namespace_watcher
This is our applied values to the helm release
an example of the only custom resource of ClusterSecret declared for the operator to use
The text was updated successfully, but these errors were encountered: