Skip to content

[release-6.3]LOG-8138:Update CLO code to use Vector v0.47.0 #3164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
vparfonov wants to merge 2 commits into
base: release-6.3
Choose a base branch
from
Open

[release-6.3]LOG-8138:Update CLO code to use Vector v0.47.0 #3164

vparfonov wants to merge 2 commits into from

Conversation

@vparfonov
Copy link
Contributor

@vparfonov vparfonov commented Dec 2, 2025

Description

Update CLO code to use Vector v0.47.0

/cc @cahartma
/assign @jcantrill

Links

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

@openshift-ci openshift-ci bot requested review from cahartma and jcantrill December 2, 2025 13:32
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 2, 2025

@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.

@vparfonov vparfonov changed the title Update CLO code to use Vector v0.47.0 [release-6.3]Update CLO code to use Vector v0.47.0 Dec 2, 2025
@vparfonov vparfonov changed the title [release-6.3]Update CLO code to use Vector v0.47.0 [release-6.3]LOG-8138:Update CLO code to use Vector v0.47.0 Dec 2, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 2, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 2, 2025 •
edited by openshift-ci bot
Loading

@vparfonov: This pull request references LOG-8138 which is a valid jira issue.

Details

In response to this:

Description

Update CLO code to use Vector v0.47.0

/cc @cahartma
/assign @jcantrill

Links

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

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 openshift-eng/jira-lifecycle-plugin repository.

@jcantrill
Copy link
Contributor

jcantrill commented Dec 11, 2025

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 11, 2025
@jcantrill
Copy link
Contributor

jcantrill commented Dec 11, 2025

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, vparfonov

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 11, 2025
@vparfonov vparfonov mentioned this pull request Dec 12, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cahartma cahartma Awaiting requested review from cahartma

@jcantrill jcantrill Awaiting requested review from jcantrill

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. release/6.3

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@vparfonov @openshift-ci-robot @jcantrill