Camel K seems to fail with Knative 0.23 #2343
Assignees
Labels
Comments
|
Yes, we have to do a round of upgrade to the latest Knative API versions, and drop the ones that have been deprecated / removed from recent Knative versions. I've been holding it back because of #2195. We need to make sure Knative test suite runs on newest versions. |
|
@astefanutti Is there anything we should consider for OpenShift 3 support when upgrading Knative like Ingress #2084? Or can we simply jump into the latest version if the test suite passes? |
|
@tadayosi we should not concern with OpenShift 3. As soon as the test suite passes with the latest version, it's good to go. |
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 21, 2021
Due to apache#2195 and apache#2343, eventing is still required to stay lower than v0.18.0.
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 22, 2021
Upgrading to Knative Eventing 0.23 drops support for the following API versions: * messaging.knative.dev/v1beta1 * sources.knative.dev/v1alpha1 * sources.knative.dev/v1alpha2
astefanutti
pushed a commit
that referenced
this issue
Jun 22, 2021
Upgrading to Knative Eventing 0.23 drops support for the following API versions: * messaging.knative.dev/v1beta1 * sources.knative.dev/v1alpha1 * sources.knative.dev/v1alpha2
|
Fixed with #2424. Thanks! |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably it's because for example
messaging.knative.dev/v1beta1is dropped and now Knative supports onlymessaging.knative.dev/v1:https://knative.dev/docs/reference/api/eventing/
All the examples that still use
messaging.knative.dev/v1beta1InMemoryChannelare not deployable with Knative 0.23.The text was updated successfully, but these errors were encountered: