Vector v0.47 in CLO 6.0

[vparfonov]

Description

Vector v0.37.1 → v0.47.0: Updates the collector engine, adapting internal config generation to Vector v0.47 requirements: secret backend format, kubernetes_logs source fields, VRL function signatures and stream field relocation.

• secret backend: type="file" → type="directory"
• VRL fixes: join!() → fallible join()
• upgrade Loki test image to 3.0+ grafana/loki:3.3.2, because of this: Issue with Loki (version < 3) Sink After Upgrading to Vector v0.43.1 vectordotdev/vector#22276

/cc @Clee2691
/assign @jcantrill

Links

• Depending on PR(s):
• GitHub issue:
• JIRA: https://redhat.atlassian.net/browse/LOG-9888
• Enhancement proposal:

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 78fa3ed9-c132-4b89-b832-3143830988bb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[vparfonov]

/test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vparfonov
Once this PR has been reviewed and has the lgtm label, please assign jcantrill for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vparfonov]

/test all

[vparfonov]

/test functional-target

[vparfonov]

/test functional-target

[vparfonov]

/test all

[vparfonov]

/test functional-target

[vparfonov]

/test all

[vparfonov]

/hold

[vparfonov]

/test functional-target

[vparfonov]

/test functional-target

[vparfonov]

/retest-required

[vparfonov]

/retest-required

[vparfonov]

/test functional-target

[vparfonov]

/test functional-target

[vparfonov]

/test functional-target

[vparfonov]

/test lint

[vparfonov]

/test images

[vparfonov]

/test functional-target

[vparfonov]

/test functional-target

[vparfonov]

/retest-required

[vparfonov]

/retest-required

[vparfonov]

/retest-required

[vparfonov]

/test functional-target

[openshift-ci]

@vparfonov: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.