Replies: 2 comments 3 replies
-
Looking at the network policy that strimzi generates makes me think I might be missing something for the cluster-operator which is in another namespace:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Strimzi normally creates its own network policies to ensure the components can talk with each other. So I'm not sure why do you need to create some additional policies for that. The operators obviously also need to talk to Kubernetes APIs. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have a network policy that blocks pretty much everything by default:
I was able to target the different pods in my dev namespace with another network policy so that zookeeper/kafka/entity operator can talk to each other but I'm still getting an error in the topic operator which I'm not able to track(Very similar network policies are being used in our staging env and it works) The log of the topic operator if anyone has any idea:
Beta Was this translation helpful? Give feedback.
All reactions