Skip to content

Update CLO to use Vector v0.54.0#3224

Open
vparfonov wants to merge 1 commit intoopenshift:masterfrom
vparfonov:vector-v0.54.0
Open

Update CLO to use Vector v0.54.0#3224
vparfonov wants to merge 1 commit intoopenshift:masterfrom
vparfonov:vector-v0.54.0

Conversation

@vparfonov
Copy link
Copy Markdown
Contributor

@vparfonov vparfonov commented Mar 16, 2026

Description

Update CLO to use Vector v0.54.0
Switch to Syslog encoder from upstream instead of forked

Temporary use Vector image from own repository for checking tests

Depends on:

/cc @cahartma @Clee2691
/assign @jcantrill

Links

  • Depending on PR(s):
  • GitHub issue:
  • JIRA:
  • Enhancement proposal:

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 16, 2026
@openshift-ci openshift-ci bot requested review from Clee2691 and alanconway March 16, 2026 08:23
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 16, 2026

[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 cahartma 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:

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

@vparfonov vparfonov changed the title WIP: Update CLO to use Vector v0.54.0 Update CLO to use Vector v0.54.0 Mar 18, 2026
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 18, 2026
})
})

//TODO: Enrichment and PayloadKey not supporting by Syslog form upstream
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are the implications here? I'm not certain why enrichment was ever passed on as it was our concept that did not need to be passed on? It was an indicator to add the kube info. Same with Payload key which was an indicator from CLF on how to populate the message field.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not actual, already fixed but forgot remove comment
see: 8f32b77#diff-9da62957a4d8f525b14cf8934bd55180d99abee9e3046cb79d2d2574cfe6e152R210

@vparfonov vparfonov changed the title Update CLO to use Vector v0.54.0 WIP:Update CLO to use Vector v0.54.0 Mar 20, 2026
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 20, 2026
@vparfonov vparfonov marked this pull request as draft March 20, 2026 17:56
@vparfonov
Copy link
Copy Markdown
Contributor Author

/test all

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 20, 2026
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 20, 2026
@vparfonov
Copy link
Copy Markdown
Contributor Author

/test all

@vparfonov
Copy link
Copy Markdown
Contributor Author

/retest

@vparfonov
Copy link
Copy Markdown
Contributor Author

/test e2e-target

@vparfonov
Copy link
Copy Markdown
Contributor Author

/test functional-target

1 similar comment
@vparfonov
Copy link
Copy Markdown
Contributor Author

/test functional-target

Switch to Syslog encoder from upstream instead of forked one
@vparfonov vparfonov changed the title WIP:Update CLO to use Vector v0.54.0 Update CLO to use Vector v0.54.0 Mar 21, 2026
@vparfonov vparfonov marked this pull request as ready for review March 21, 2026 14:04
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 21, 2026
@openshift-ci openshift-ci bot requested a review from jcantrill March 21, 2026 14:04
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 21, 2026

@vparfonov: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/functional-target c9333f4 link true /test functional-target

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants