[telco-hub] Fix kafka validations in kube-compare references #325
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.
Summary
This PR addresses validation issues in the cluster log forwarder configuration for kube-compare operations by implementing proper Kafka URL validation and fixing field ordering in pipeline definitions.
Problem
When doing cluster-compare directly against the kustomize-patched CRs, the following drift can be seen:
Changes Made
1. Enhanced Kafka URL Validation (
metadata.yaml
)clusterLogForwarder.yaml
inlineDiffFunc: regex
forspec.outputs.0.kafka.url
path to enable pattern-based comparison instead of exact string matching2. Updated Kafka URL Pattern (
clusterLogForwarder.yaml
){{ .kafka.url }}
with regex pattern"^(tcp|http|https)://.*$"
3. Fixed Pipeline Field Ordering
filterRefs
(first - for log filtering)inputRefs
(second - for log input types)name
(third - pipeline identifier)outputRefs
(fourth - output destinations)filterRefs
with fallback to defaulttelco-hub-labels
Signed-off-by: Leonardo Ochoa-Aday lochoa@redhat.com