Gaëlle Fournier

From what I can see: * v0.16.x relies on Kubernetes 1.28 libraries * v0.17.x relies on Kubernetes 1.29 librairies @squakez @lburgazzoli is there something that would prevent us from bumping...

Im curious about the resources, we have 3 path for them: * ./resources * /etc/camel/resources * /etc/camel/[conf.d -> resources.d]/_resources Do you know for what each one is used ?

@squakez I'm on it.

The task has been created, but I think we need to limit the number of versions added to the snapshot repository. I get the feeling it there will quickly be...

Is it supposed to be configured by the repository nexus or the project ? Because when I look here it is definitly more : https://repository.apache.org/content/repositories/snapshots-group/org/apache/camel/k/camel-k-catalog/3.6.0-SNAPSHOT/

Looks like we are good now.

Thank you for the workaround, I will test it. I don't know how efficient the lookup of the port can be after any improvment done. Since the default quarkus port...

Updating the existing test I saw that the code is making the assumption that both probes would have the same ports when they could each define their own SCHEME. Which...

Thanks for the feature request. It looks like a good improvment. We could probably leverage the map "PublishStrategyOptions" (`--build-publish-strategy-option`) available in the IntegrationPlatform CRD and use the value in https://github.com/apache/camel-k/blob/main/pkg/builder/jib.go....

There is a maintained fork for here that could be used : https://github.com/go-viper/mapstructure. But it is probably only a way to postpone the issue.