#Problem
VectorPipeline validates against all VectorAggregator resources that match selector labels, regardless of namespace. It should only validate against aggregators in the same namespace.
Validations fails (env undefined) in case you have different set of secrets for pipelines/aggregators
#Current Behavior
In pipeline_controller.go, the code:
Fetches all VectorAggregator resources from all namespaces via listVectorAggregators()
Filters by namespace in the loop (line 196)
Validates against all matching aggregators, even if they're in different namespaces
#Expected Behavior
VectorPipeline should only validate against VectorAggregator resources in the same namespace, as it only configures aggregators in that namespace.
#Location
internal/controller/pipeline_controller.go lines 82-247
#Impact
Unnecessary validation against aggregators in other namespaces
Potential validation failures from aggregators in different namespaces
Performance overhead from processing irrelevant aggregators
#Suggested Fix
Filter VectorAggregator resources by namespace before validation, or fetch only aggregators from the pipeline's namespace
main...val16384:vector-operator:fix/vectorpipeline-vs-aggregator-validation
Note: I'm not a real plumber.