Hi Timothy, the specification looks good (a part the needed indentation, of course). It seems that some resource is missing, likely the Kamelets. You can try to list in the namespace via `kamel kamelet get`. It would be nice also to have a look at operator Pod log and see what kind of error is reported (ie, `stern camel-k-operator`). Also, please verify that the kamel CLI you're using to run is compatible with the operator (`kamel version --all`). I've just discovered a bug [1] but it does not look the kind of issue you're experiencing. Please, report any useful information for further troubleshooting.
Regards, Pasquale. [1] https://github.com/apache/camel-k/issues/4117 On Thu, Mar 9, 2023 at 5:28 PM Timothy Dilbert <timothy.dilb...@bmt.ky.invalid> wrote: > Hello, > > I am trying to do a quick proof-of-concept on Camel-K, deploying a > KameletBinding into OpenShift. I'm having a hard time deploying into my > Camel K Operator. > > All of my attempts are basically getting stuck on the "Creating" stage, > then eventually failing with the following message: > ``` > Integration "integration-name" does not have a readiness condition > ``` > Below is an example of a basic YAML deployment: > > apiVersion: camel.apache.org/v1alpha1 > kind: KameletBinding > metadata: > name: integration-name > spec: > source: > ref: > apiVersion: camel.apache.org/v1alpha1 > name: timer-source > kind: Kamelet > properties: > period: '10000' > message: Hello > sink: > ref: > apiVersion: camel.apache.org/v1alpha1 > name: log-sink > kind: Kamelet > properties: > showHeaders: 'true' > > Any chance I can get a little help from you to identify the issue here? > > I'm using OpenShift v4.12.5 with the Camel K Operator v1.12.0. > > Kind regards, > > Timothy Dilbert >
