-
Notifications
You must be signed in to change notification settings - Fork 345
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
Update to Knative v1.5.0 #3381
Comments
We must make sure that the dependencies used are not needing some conflicting kubernetes dependencies of the ones we support. |
@squakez yes, Knative v1.5.0 uses |
Thanks for checking. We need to keep them aligned then, waiting for us to use that version before bumping knative. |
@christophd @squakez Knatvie v1.2.0 (the version we use now) is very old already. At least Knative v1.3.0 still uses K8s API v0.22.5, so we should upgrade to v1.3.0 before releasing Camel K 1.10.0. |
I'd even consider moving k8s api forward. However I don't know which is the impact there. @astefanutti may add his opinion about that. But yes, we can move a little step forward for Knative and evaluate in parallel what it does take to move forward k8s dependencies (maybe for 1.11?). |
Serving v1.3.0 (0.30.0) is the last version that uses k8s.io/api v0.22.5.
Serving v1.3.0 (0.30.0) is the last version that uses k8s.io/api v0.22.5.
Serving v1.3.0 (0.30.0) is the last version that uses k8s.io/api v0.22.5.
Use latest Knative v1.5.0 for eventing and serving
The text was updated successfully, but these errors were encountered: