feat(kube-stack): Add allowNamespaces and denyNamespaces support to targetAllocator.prometheusCR #1779
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1765
This PR adds support for
allowNamespaces
anddenyNamespaces
fields in thetargetAllocator.prometheusCR
configuration for theopentelemetry-kube-stack
Helm chart. These fields allow users to control which namespaces should be included or excluded from being scraped by the collector via the Target Allocator.Changes
allowNamespaces
anddenyNamespaces
fields to theOpenTelemetryTargetAllocatorPrometheusCR
schema invalues.schema.json
values.yaml
to include examples of the new fieldsExample Usage
Testing Done