Skip to content

Conversation

@QuentinBisson
Copy link
Contributor

@QuentinBisson QuentinBisson commented Oct 16, 2025

PR Description

Registers the Kubernetes field index for spec.nodeName when node filtering is enabled. This prevents Index with name field:spec.nodeName does not exist errors when the node_filter configuration is used.

Notes to the Reviewer

The field index is registered conditionally (to avoid unnecessary field index registation) based on:

  • nodeFilterEnabled flag is true
  • getNodeFilterName() returns a non-empty string

PR Checklist

  • CHANGELOG.md updated
  • Documentation added
  • Tests updated
  • Config converters updated

….nodeName

Only register the Kubernetes field index for spec.nodeName when node filtering
is enabled. This prevents 'Index with name field:spec.nodeName does not exist'
errors when the node_filter configuration is used.

The field index is now registered conditionally based on:
- nodeFilterEnabled flag is true
- getNodeFilterName() returns a non-empty string

This optimization avoids unnecessary field index registration when node
filtering is not in use, improving performance and preventing runtime errors.
@QuentinBisson QuentinBisson requested a review from a team as a code owner October 16, 2025 11:56
@QuentinBisson
Copy link
Contributor Author

Hey @dehaansa and @kalleep do you think you could take a look?

@dehaansa
Copy link
Contributor

I'm not familiar with this issue, but I'm a bit confused looking at the diff - the changelog/description claims this changes behavior when node filter is not configured, but all the diff shows is new behavior when node filter is configured. Can you help me understand?

@QuentinBisson
Copy link
Contributor Author

@dehaansa you are totally right, the description and changelog entry were totally wrong. This pull request enables the field indexing if the node filtering is enabled

Copy link
Contributor

@kalleep kalleep left a comment

Choose a reason for hiding this comment

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

I was also a bit confused by the description and changelog before you change it.

LGTM thanks

@kalleep kalleep merged commit 0a5259d into grafana:main Oct 29, 2025
37 checks passed
@QuentinBisson
Copy link
Contributor Author

Thank you @kalleep :) Do you know when it might be released?

@kalleep
Copy link
Contributor

kalleep commented Oct 29, 2025

@QuentinBisson If we don't do a patch release this will be release around 2025-11-11 when we are scheduled for our next minor

@QuentinBisson
Copy link
Contributor Author

Thank you :)

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