feat: allow pinning the pipeline role with spec.role - #283
Open
stigglor wants to merge 1 commit into
Open
Conversation
Adds an optional `spec.role` to `VectorPipeline` and `ClusterVectorPipeline` that picks which Vector the pipeline goes to, instead of inferring it from the source types. Inference classifies every source against two hardcoded lists, so a type on neither list fails the pipeline, a type on both can never reach an aggregator, and kaasops#218 reports adding an unused source purely to flip the result. Unset keeps the current behavior, and leaves the config hash untouched so pipelines do not re-reconcile on upgrade. An aggregator pipeline in a namespace may no longer use a source that reads the node (`kubernetes_logs`, `file`, `journald`, `docker_logs`, `host_metrics`), which the shared aggregator collects across namespaces. Mixing one of those with a network source already routed to the aggregator, so such a pipeline goes invalid on upgrade. Move it to a ClusterVectorPipeline, or leave the host sources on the agent. Closes kaasops#218
stigglor
force-pushed
the
role-override
branch
from
August 17, 2026 21:58
5f12acd to
69b0eb4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds an optional
spec.roletoVectorPipelineandClusterVectorPipelinethat pickswhich Vector the pipeline goes to, instead of inferring it from the source types.
Inference classifies every source against two hardcoded lists, so a type on neither list
fails the pipeline, a type on both can never reach an aggregator, and #218 reports adding
an unused source purely to flip the result. Unset keeps the current behavior, and leaves
the config hash untouched so pipelines do not re-reconcile on upgrade.
An aggregator pipeline in a namespace may no longer use a source that reads the node
(
kubernetes_logs,file,journald,docker_logs,host_metrics), which the sharedaggregator collects across namespaces. Mixing one of those with a network source already
routed to the aggregator, so such a pipeline goes invalid on upgrade. Move it to a
ClusterVectorPipeline, or leave the host sources on the agent.
Closes #218