Mike Beaumont
Mike Beaumont
We probably need to take advantage of something like https://github.com/kubernetes-sigs/controller-runtime/pull/1435
@mhkarimi1383 can I ask if you know how you have `kuma.io/system-namespace` set on the `cert-manager` Namespace in the first place? How exactly are you installing Kuma? [The Helm chart adds...
@mhkarimi1383 Why? I've [opened a docs PR](https://github.com/kumahq/kuma-website/pull/1895). It should only be set if you want Kuma's Secret webhook to run on that namespace, which I don't think you want for...
Can you open an issue for that? You shouldn't set or have to set that label for other namespaces
I'm gonna close this issue since the problem was due to that label which shouldn't be set
@mhkarimi1383 can you describe the problem more completely? Ideally in another issue so we can track it properly
You just had no access to the API from any Pod in the namespace? And just adding this label fixed access to the k8s API? What made you add it?...
I'm assuming Kuma sidecar injection wasn't enabled on those namespaces. Without any more information I don't see how Kuma could interfere with k8s API server communication from Pods in such...
> Waiting on feedback from user on MeshProxyPatch