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.

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

Update Kubernetes client libraries and generators to 0.30.z #2332

Open
rzetelskik opened this issue Jan 13, 2025 · 0 comments
Open

Update Kubernetes client libraries and generators to 0.30.z #2332

rzetelskik opened this issue Jan 13, 2025 · 0 comments
Assignees
@rzetelskik
Labels
kind/machinery Categorizes issue or PR as related to Makefile, scripts or similar changes. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
v1.16.0

Comments

@rzetelskik
Copy link
Member

We need to update our k8s.io dependencies to v0.30.z and beyond but Kubernetes has changed the machinery in 1.30 to support go workspaces and get rid of the GOPATH.

I expect there will be some debugging and certainly adjustments needed for our machinery.

Ref #2028

/kind machinery
/priority important-soon
/triage accepted
@scylla-operator-bot scylla-operator-bot bot added kind/machinery Categorizes issue or PR as related to Makefile, scripts or similar changes. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 13, 2025
@rzetelskik rzetelskik added this to the v1.16.0 milestone Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rzetelskik rzetelskik

Labels
kind/machinery Categorizes issue or PR as related to Makefile, scripts or similar changes. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
v1.16.0
Development

No branches or pull requests
1 participant
@rzetelskik