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

chore: bump k8s deps to 1.24 & makefile go 1.18 support #242

Merged

Conversation

everettraven
Copy link
Contributor

@everettraven everettraven commented May 19, 2022

Description of change

  • Bump k8s dependencies to 1.24
  • Modify Makefile to support Go 1.18

Motivation for the change

Kubernetes 1.24 has been released and is built with Go 1.18, so we need to update this library to support k8s 1.24 so the rest of the Operator Framework tools can begin making changes to support k8s 1.24. This also modifies the Makefile to allow for the support of Go 1.18 when it comes time to make the Go version bump

Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
go.mod Outdated Show resolved Hide resolved
Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
@everettraven everettraven changed the title chore: bump k8s deps to 1.24 and go version to 1.18 chore: bump k8s deps to 1.24 & makefile go 1.18 support May 23, 2022
@rashmigottipati
Copy link
Member

I did mention to Bryce we should be bumping 1.18 as k8s 1.24 is built using Go 1.18.
@everettraven however, I agree with Camila's point, so I'm good with switching to use go 1.17 here.

Copy link
Member

@varshaprasad96 varshaprasad96 left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 23, 2022
Copy link
Member

@rashmigottipati rashmigottipati left a comment

Choose a reason for hiding this comment

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

/lgtm

Copy link
Contributor

@camilamacedo86 camilamacedo86 left a comment

Choose a reason for hiding this comment

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

That shows fine 🥇

/approved

@camilamacedo86
Copy link
Contributor

/lgtm

Copy link
Member

@dinhxuanvu dinhxuanvu left a comment

Choose a reason for hiding this comment

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

I don't see any problems with this PR specifically. However, given registry and olm repos do vendor api, these two repos will need to do a k8s 1.24 bump as well. Registry is still in 1.22 while olm is on 1.23 already. Assuming they have no problems with 1.24 bump, then this PR should be good to go.
@joelanford FYI

@njhale
Copy link
Member

njhale commented May 24, 2022

/approve

@openshift-ci
Copy link

openshift-ci bot commented May 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, njhale

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 May 24, 2022
@njhale
Copy link
Member

njhale commented May 24, 2022

go-apidiff is complaining about ClusterName being deprecated. IIUC, it wasn't used outside of KCP upstream anyway.

/override Go/go-apidiff

@openshift-ci
Copy link

openshift-ci bot commented May 24, 2022

@njhale: /override requires a failed status context or a job name to operate on.
The following unknown contexts were given:

  • Go/go-apidiff

Only the following contexts were expected:

  • Build
  • tide
  • verify

In response to this:

go-apidiff is complaining about ClusterName being deprecated. IIUC, it wasn't used outside of KCP upstream anyway.

/override Go/go-apidiff

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/test-infra repository.

@everettraven
Copy link
Contributor Author

As per @njhale

/override go-apidiff

@openshift-ci
Copy link

openshift-ci bot commented May 24, 2022

@everettraven: everettraven unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file.

In response to this:

As per @njhale

/override go-apidiff

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/test-infra repository.

@everettraven
Copy link
Contributor Author

I don't see any problems with this PR specifically. However, given registry and olm repos do vendor api, these two repos will need to do a k8s 1.24 bump as well. Registry is still in 1.22 while olm is on 1.23 already. Assuming they have no problems with 1.24 bump, then this PR should be good to go. @joelanford FYI

@dinhxuanvu Are you suggesting that OLM and Registry are updated to support k8s 1.24 before this PR is merged?

@dinhxuanvu
Copy link
Member

I don't see any problems with this PR specifically. However, given registry and olm repos do vendor api, these two repos will need to do a k8s 1.24 bump as well. Registry is still in 1.22 while olm is on 1.23 already. Assuming they have no problems with 1.24 bump, then this PR should be good to go. @joelanford FYI

@dinhxuanvu Are you suggesting that OLM and Registry are updated to support k8s 1.24 before this PR is merged?

No. This PR should go in first and then should be vendored into registry and olm soon and bump k8s at the same time.

@dinhxuanvu
Copy link
Member

/override go-apidiff

@openshift-ci
Copy link

openshift-ci bot commented May 24, 2022

@dinhxuanvu: /override requires a failed status context or a job name to operate on.
The following unknown contexts were given:

  • go-apidiff

Only the following contexts were expected:

  • Build
  • tide
  • verify

In response to this:

/override go-apidiff

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/test-infra repository.

@dinhxuanvu dinhxuanvu merged commit 725ffce into operator-framework:master May 24, 2022
@everettraven everettraven deleted the chore/bump-k8s-1.24 branch May 24, 2022 19:00
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants