Skip to content

[grafana] Allow specifying IP block for network policy#93

Merged
QuentinBisson merged 1 commit intografana-community:mainfrom
jullianow:grafana-np
Feb 16, 2026
Merged

[grafana] Allow specifying IP block for network policy#93
QuentinBisson merged 1 commit intografana-community:mainfrom
jullianow:grafana-np

Conversation

@jullianow
Copy link
Copy Markdown

What this PR does / why we need it

This change adds the ability to define IP blocks to allow entry to the Grafana pod only for specific IPs.

This is essentially necessary, for example, when we want to allow specific traffic from GCP Health Check IPs when using Gateway API, for example.

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

  • fixes #

Special notes for your reviewer

Checklist

  • DCO signed
  • Chart Version bumped
  • Title of the PR starts with chart name (e.g. [grafana])

Copy link
Copy Markdown

@QuentinBisson QuentinBisson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@QuentinBisson
Copy link
Copy Markdown

@jullianow can you please fix the lint?

@jullianow
Copy link
Copy Markdown
Author

jullianow commented Feb 16, 2026

@jullianow can you please fix the lint?

I tried to fix it, but super-lint is reporting problems with natural language.

For example, it expects you to write YAML. This is not possible. Therefore, I couldn't fix it.
image
What do you suggest to fix it?

@QuentinBisson
Copy link
Copy Markdown

You are right, your changes did not cause this. I'll merge this PR for now @TheRealNoob and @jkroepke are you already working on a fix for this or should I?

@QuentinBisson QuentinBisson merged commit 2e62c4f into grafana-community:main Feb 16, 2026
6 of 7 checks passed
@jullianow jullianow deleted the grafana-np branch February 16, 2026 15:40
@jkroepke
Copy link
Copy Markdown
Member

Could you do that? The fix is basicly fix the terms in the values.yaml, since helm-docs just generate the README based on the comments from the values.yaml

@QuentinBisson
Copy link
Copy Markdown

For sure, I just wanted to avoid duplicate effort :)

@QuentinBisson
Copy link
Copy Markdown

I think my recent PRs did :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants