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
Why are you trying to protect against 2 clients on the same cluster connecting to the same provider twice? I can see use cases for such configurations and I don't; see any reason to disallow it.
The only limitation should be that we should not allow two client CR having the same name. But that is already covered by k8s itself.
The only limitation should be that we should not allow two client CR having the same name. But that is already covered by k8s itself.
Originally posted by @nb-ohad in #133 (comment)
The text was updated successfully, but these errors were encountered: