-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[grafana] feat(network policy): extend Ingress #3287
Conversation
Signed-off-by: C4tWithShell <[email protected]>
Signed-off-by: C4tWithShell <[email protected]>
Signed-off-by: MH <[email protected]>
@Sheikh-Abubaker @jkatsos @maorfr @torstenwalter @Xtigyro @zanhsieh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@C4tWithShell Thanks for the Contribution! Have you tested the proposed solution ?
Yes, I did |
Signed-off-by: Vladimir Shelkovnikov <[email protected]>
@C4tWithShell If I didn't get you wrong in the |
I believe we could achieve the same result, by adding the appropriate labels in the existing
I'd recommend you to first try and test using the existing Incase you want to accept traffic from some different namespace, you could utilize the helm-charts/charts/grafana/values.yaml Line 1326 in e930987
|
@C4tWithShell any updates on this one ? |
Hi! Yes, I was able to configure ingress network policy with adding the addition label to ingress-nginx pod. |
You mean by using the existing Network Policy right ? |
Yes. By adding the grafana-client label |
All right! shall I close this one then @C4tWithShell ? |
Add extraIngress parameter to network policy since it does not allow to specify additional sources from the grafana helm chart . For example, I can not set up load balancer in the cluster.