Pasquale Congiusti

I had a look at this and I am able to reproduce the error. However, just for the sake of understanding. The patching piece of code you've posted is not...

@hernanDatgDev thanks for the help offered. You can keep troubleshooting trying to apply the KSVC generated by Camel K manually and see if the same error happens.

I think the problem is because of this feature that need to be explicitly enabled: https://knative.dev/docs/serving/configuration/feature-flags/#kubernetes-emptydir-volume - however, it's strange it does work when you set the KSVC from CLI.

Okey, I think I got to understand what's going on. Camel K is using a server side patch based application of the resources, and this is triggering some webhook on...

Cool, thanks @hernanDatgDev . Please, keep us posted.

I think what the server side apply patch does is something like `--server-side --force-conflicts --field-manager=camel-k-operator`. I think I managed to reproduce the same error also from CLI even without server...

I think I finally managed to find a quick workaround to the problem. I think the Knative Webhook is wrongly thinking that `spec.template.spec.volumes[2].emptyDir` is empty and the check is only...

I understand you're working on this right, can I assign the issue?

It's reasonable. Right now the equipment of JDK is hardcoded in the operator container image (from which it is inherited). We probably need to develop some mechanism to let the...

@diegovisentin you can test this using the JDK21 container image in nightly release in https://hub.docker.com/r/testcamelk/camel-k/tags - upcoming 2.6.0 will be provided with JDK21 as well, feel free to run a...