-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable CiliumNetworkPolicy
between loki components
#3189
Comments
I will enable the cilium netpol from upstream. What are the affected MCs ?
|
@QuantumEnigmaa can you link the upstream issue here ? |
Sure ! There it is : grafana/loki#11838 |
Getting released into giantswarm/loki-app#284 |
This is not solved: For backend pods we have this:
Not sure what happens with the gateways:
Loki read pods:
I think a few of those issues are related to coredns not being accessible |
Sadly I cannot open hubble on gerbil |
Here is the list of blocked connections:
|
I've done some manual changes to the CNPs (which I'll push upstream) and it looks better for the write pods ;
However backend pods are not logging anything useful. Gateway pods are still having troubles :
|
Upstream issue to fix the CNPs : grafana/loki#11963 Adding a plain netpol to allow loki pods access to coredns helped having the gateway pods work :
|
Is there a way to fix all CNPs at once and have it in our app in the meantime? |
Or maybe we can disable cnps for loki until this is merged? |
Lucky this time : already merged upstream 😎 |
After adding additional CNPs for both write and backend pods to allow them egress access to the "world" entity, it finally works |
Now loki have upstream CNPs + custom ones (coredsn, egress to world for write, egress to world + kube-apiserver for backend) enabled by default for all capi installations. |
Can we create a new one to push them upstream? |
Due to a change in onprem MCs, we need to enable cilium network policy between all loki components, otherwise they cannot communicate with each other
The text was updated successfully, but these errors were encountered: