Christoph Deppisch

@boskoop are you able to further work on this issue in order to rebase and adjust some changes as requested? Many thanks!

we really need to update the Kubernetes client library! I am pretty sure that the Kubernetes API has evolved a lot and the client needs to be updated.

Sorry no timeline yet. As an idea you could have a look into the Kubernetes test actions provided in YAKS. This is fully compatible with Citrus and uses some up...

This would be the action builder for your test https://github.com/citrusframework/yaks/blob/main/java/steps/yaks-kubernetes/src/main/java/org/citrusframework/yaks/kubernetes/actions/KubernetesActionBuilder.java

yes I have a look. What happens if you run the integration? is it being reconciled by the operator? also do you have a WATCH_NAMESPACE env set for the local...

@squakez yes, I have started some investigation but got distracted by other stuff. I also wanted to ask: In your scenario do you have another traditional operator running on the...

Camel K has stopped supporting BSD/macOS sed recently (see #3372 and #3398) Instead MacOS users are encouraged to install gnu-sed. Could you please install gnu-sed on your machine (e.g. `brew...

When no IntegrationPlatform is present it gets created automatically with the 1st integration. So it should also work if you just install the operator and run the integration. The default...

would be good to see the error from the logs so I can have an idea what went wrong. Are you using a global operator? where is that operator running...

what does it mean if you say ` the operator is running locally`? you are running the operator namespace scoped on a single namespace or on your local machine?