Skip to content
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

Ingress traffic rejected by NetworkPolicy in Loki chart 6.5.0 (3.0.0) #12906

Open
vholer opened this issue May 7, 2024 · 0 comments · May be fixed by #12907
Open

Ingress traffic rejected by NetworkPolicy in Loki chart 6.5.0 (3.0.0) #12906

vholer opened this issue May 7, 2024 · 0 comments · May be fixed by #12907
Labels
area/helm type/bug Somehing is not working as expected

Comments

@vholer
Copy link

vholer commented May 7, 2024

Describe the bug

If network policy is enabled in Helm chart via networkPolicy.enabled=true and networkPolicy.ingress is configured, the traffic is still being rejected. This is due to a wrong port name reference http in NetworkPolicy:

while related Service port names are http-metrics:

Recent change in gateway's Service broke this: 79b876b#diff-431f854797520c4320975bebaa267bcac088a12671e360093d87bf7193abd438R31

Expected behavior
Network policies should enable ingress traffic to gateway or reader/writer.

Environment:

  • Infrastructure: Kubernetes
  • Deployment tool: helm
@vholer vholer changed the title Ingress traffic rejected by wrong NetworkPolicy in Loki chart 6.5.0 (3.0.0) Ingress traffic rejected by NetworkPolicy in Loki chart 6.5.0 (3.0.0) May 7, 2024
@JStickler JStickler added area/helm type/bug Somehing is not working as expected labels May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm type/bug Somehing is not working as expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants