Skip to content

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

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-6.3from
vparfonov:vector-v0.47-clo-6.3
Jan 13, 2026
Merged

[release-6.3]LOG-8138:Update CLO code to use Vector v0.47.0#3164
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-6.3from
vparfonov:vector-v0.47-clo-6.3

Conversation

@vparfonov
Copy link
Copy Markdown
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
@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
Copy Markdown

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
Copy Markdown
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
Copy Markdown
Contributor

jcantrill commented Dec 11, 2025

/approve

@openshift-ci
Copy link
Copy Markdown
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
Merged
@vparfonov vparfonov force-pushed the vector-v0.47-clo-6.3 branch from 9959589 to e4f1620 Compare January 13, 2026 12:00
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 13, 2026

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

@jcantrill
Copy link
Copy Markdown
Contributor

jcantrill commented Jan 13, 2026

/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 13, 2026
@jcantrill
Copy link
Copy Markdown
Contributor

jcantrill commented Jan 13, 2026

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 3445228 into openshift:release-6.3 Jan 13, 2026
7 checks passed
@vparfonov vparfonov deleted the vector-v0.47-clo-6.3 branch April 30, 2026 08:07
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

@jcantrill jcantrill

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. 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