Oh, this makes total sense. Once v1.18 has cut, we can land this in main.

I had a wild idea: we could theoretically expose a histogram of policy map pressure; given that histograms are intended to expose sampled data. The only problem is that histograms, as implemented in prometheus-go are intended for "streaming", e.g. individual request duration. There's no obvious easy way to fill all the buckets at once.

Anyways, no need to take this seriously, just some brain cells this PR ticked.

On a more relevant note: the documentation CI job is failing. Please run make -C Documentation update-cmdref

Oh, this makes total sense. Once v1.18 has cut, we can land this in main.

Don't you mind if we backport it to 1.17 as well?

@pasteley seems like you need to update couple of tests: https://github.com/cilium/cilium/actions/runs/15878956787/job/44773797407?pr=40188
and also Documentation: https://github.com/cilium/cilium/actions/runs/15878956808/job/44773797208?pr=40188 by running make -C Documentation update-helm-values

@squeed We need your review here again

/test

@cilium/fqdn looks like this still needs approval from your codeowners, @squeed is on vacation currently.

@pasteley this PR has conflicts against main that need to be resolved, would you mind doing one more rebase?

Ah - unfortunately I lack the power to dismiss @squeed's review - hence when I removed his review request so that this PR can progress, GitHub translated that back to a "Changes Requested". Could a committer dismiss his review (I feel it's adequately addressed) so this PR can progress, once rebased?

Normally there's some box near the bottom of the page that allows committers to dismiss the review and post a text comment why, but I'm not seeing that UI element on the page right now.

Based on the UI state it looks like this is non-blocking however, I can click the 'Merge when ready' button. I will do so and kick off the tests.

/test

/test

@pasteley Can you rebase your code. The failing check was fixed in the main stream.