-
Notifications
You must be signed in to change notification settings - Fork 350
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
Binding from a Strimzi CR is not properly decoded #4336
Labels
Milestone
Comments
so it turn out that the strimzi addon supports only the KafkaTopic CRD and I've tested that it works however, the camel-k operator should not fallback to |
christophd
added a commit
to christophd/camel-k
that referenced
this issue
May 8, 2023
- Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
christophd
added a commit
to christophd/camel-k
that referenced
this issue
May 9, 2023
- Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
squakez
pushed a commit
that referenced
this issue
May 9, 2023
- Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
christophd
added a commit
to christophd/camel-k
that referenced
this issue
May 9, 2023
- Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
christophd
added a commit
to christophd/camel-k
that referenced
this issue
May 9, 2023
…lpha1 - Also restrict v1alpha1 binding provider - Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
christophd
added a commit
to christophd/camel-k
that referenced
this issue
May 9, 2023
- Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
squakez
pushed a commit
that referenced
this issue
May 10, 2023
- Also restrict v1alpha1 binding provider - Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
christophd
added a commit
to christophd/camel-k
that referenced
this issue
May 10, 2023
- Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
squakez
pushed a commit
that referenced
this issue
May 10, 2023
- Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
squakez
pushed a commit
that referenced
this issue
May 10, 2023
- Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service)
squakez
pushed a commit
to jboss-fuse/camel-k
that referenced
this issue
May 10, 2023
- Only run the binding provider when Knative is installed on the cluster - Only run the binding provider when referencing a known Knative resource (e.g. broker, channel, service) (cherry picked from commit apache/camel-k@d7065e014)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've created the following
KameletBinding
using a pre-built container image that should bridge Kafka and Slack.However in the resulting integration code, the Kafka ref is translated to Knative
I would expect this binding to decode the Kafka ref to a kafka endpoint/kamelet in the generated code
The text was updated successfully, but these errors were encountered: