Skip to content
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.

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

LOG-6722: Update operator k8s dependencies #2996

Merged
merged 2 commits into from
Mar 28, 2025

Conversation

jcantrill
Copy link
Contributor

Description

This PR:

  • Updates the golang builder to 1.23
  • Updates kube, openshift prometheus client dependencies
  • Operator sdk to v1.39.1
  • code and manifest changes to support operator sdk v1.39.1

Links

cc @xperimental @cahartma @Clee2691 @vparfonov

@openshift-ci openshift-ci bot requested review from cahartma and Clee2691 March 24, 2025 17:02
@openshift-ci openshift-ci bot added the midstream/Dockerfile A Dockerfile.in sync is needed with midstream label Mar 24, 2025
Copy link
Contributor

openshift-ci bot commented Mar 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill

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

The pull request process is described here

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 Mar 24, 2025
@jcantrill jcantrill changed the title Log6722 LOG-6722: Update operator k8s dependencies Mar 25, 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 Mar 25, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 25, 2025

@jcantrill: This pull request references LOG-6722 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.8.0" version, but no target version was set.

In response to this:

Description

This PR:

  • Updates the golang builder to 1.23
  • Updates kube, openshift prometheus client dependencies
  • Operator sdk to v1.39.1
  • code and manifest changes to support operator sdk v1.39.1

Links

cc @xperimental @cahartma @Clee2691 @vparfonov

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 Author

/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 Mar 26, 2025
@jcantrill
Copy link
Contributor Author

/retest

@jcantrill
Copy link
Contributor Author

/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 Mar 28, 2025
@jcantrill
Copy link
Contributor Author

/test upgrade

@Clee2691
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 28, 2025
Copy link
Contributor

openshift-ci bot commented Mar 28, 2025

@jcantrill: all tests passed!

Full PR test history. Your PR dashboard.

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.

@openshift-merge-bot openshift-merge-bot bot merged commit beb7200 into openshift:master Mar 28, 2025
8 checks passed
@jcantrill jcantrill deleted the log6722 branch March 28, 2025 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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. midstream/Dockerfile A Dockerfile.in sync is needed with midstream release/6.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants