Cross Namespace Secret Synchronization
Opened this issue · 5 comments
I'm assuming it was an intentional design decision to limit the GSM Controller to only be able to update secrets within it's own namespace rather than any namespace in the k8s cluster, correct?
I tried putting a secret in another namespace and using the same annotations in the example and it is not being updated because I believe gsm-controller can only update what is in it's namespace. It would be kinda nice to not have to deploy the controller to every namespace I want to use it in, unless there's some granularity of access to secrets feature I'm missing.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
/remove-lifecycle stale
Sorry for the delated response, yeah we should make a cluster scoped deployment too. Will try and take a pop at that shortly.
I would also be interested in using gsm-controller if it were handling the whole cluster as we use namespaces for different environments.