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

Upgrade controller-runtime to latest version #5211

Closed
lburgazzoli opened this issue Mar 4, 2024 · 5 comments
Closed

Upgrade controller-runtime to latest version #5211

lburgazzoli opened this issue Mar 4, 2024 · 5 comments
Assignees
Labels
dependencies Pull requests that update a dependency file status/never-stale
Milestone

Comments

@lburgazzoli
Copy link
Contributor

Requirement

Upgrade controller-runtime to latest version

Problem

The current controller-runtime version in camel-k is v0.15.2 whereas the latest released version is 0.17.2, we should try stay closed with the releases to reduce the complexity of migration

Proposal

No response

Open questions

No response

@lburgazzoli lburgazzoli added the kind/feature New feature or request label Mar 4, 2024
@lburgazzoli
Copy link
Contributor Author

@valdar ^^

@gansheer gansheer self-assigned this Mar 11, 2024
@gansheer
Copy link
Contributor

From what I can see:

  • v0.16.x relies on Kubernetes 1.28 libraries
  • v0.17.x relies on Kubernetes 1.29 librairies

@squakez @lburgazzoli
is there something that would prevent us from bumping the Kubernetes API ?

@lburgazzoli
Copy link
Contributor Author

According to the kubernetes-version-compatibility, we would support kubernetes from 1.25 to 1.29. As long as that range falls into also the OpenShift supported version e should probably be ok

@squakez
Copy link
Contributor

squakez commented Apr 8, 2024

@gansheer FYI, there are a few dependencies which will require attention once we bump to 0.16. They should be good to upgrade once the ctrl-runtime is updated.

Copy link
Contributor

github-actions bot commented Jul 8, 2024

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file status/never-stale
Projects
None yet
Development

No branches or pull requests

3 participants