Thanks for testing, yes, it seems to be more of a problem on the Knative side. I'll close the voting and continue the release later during the day or tomorrow early morning then.
Cheers, Pasquale. On Mon, Aug 5, 2024 at 4:03 PM Miguel de Barros <mig...@debarros.me> wrote: > +1 > > We have picked up the following issues when running with Knative enabled: > > 1. Jolokia port naming issue seems to be resolved, but unfortunately there > is subsequent issue with Knative enabled: > *error during apply resource: camel-k/template-health-check: admission > webhook "validation.webhook.serving.knative.dev > <http://validation.webhook.serving.knative.dev>" denied the request: > validation failed: more than one container port is set: > spec.template.spec.containers[*].ports Only a single port is allowed across > all containers* > > This seems to be a limitation of Knative and I am not sure this is > something that can be resolved as per the "design" of Knative itself. > > 2. The new mount.emptyDirs Mount Trait capability works without Knative, > however it fails when Knative is enabled with the following error: > *Warning IntegrationError 25s camel-k-integration-controller Cannot > reconcile Integration template-health-check: error executing post actions - > 1/1 failed: [error during apply resource: camel-k/template-health-check: > admission webhook "validation.webhook.serving.knative.dev > <http://validation.webhook.serving.knative.dev>" denied the request: > validation failed: expected exactly one, got neither: > spec.template.spec.volumes[5].configMap, > spec.template.spec.volumes[5].emptyDir, > spec.template.spec.volumes[5].projected, > spec.template.spec.volumes[5].secret]* > > This seems to be a compatibility/approach issue from Knative's side. > > We have reached out to the Knative community for assistance > > Kind Regards, > Miguel de Barros > > > On Mon, 29 Jul 2024 at 16:35, Pasquale Congiusti < > pasquale.congiu...@gmail.com> wrote: > > > Hello, > > > > This is a vote to release Apache Camel K 2.4.0. This release contains > > several new features and bug fixes [1]. > > > > Camel K release files: > > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.4.0/ > > > > Camel K Tag: > > https://github.com/apache/camel-k/releases/tag/v2.4.0 > > > > Camel K CRD Java dependency staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1738 > > > > Staging container image repository (multi architecture manifest): > > > > > https://hub.docker.com/layers/camelk/camel-k/2.4.0/images/sha256-307b048a8c9913c167d19521ebd2c889cb98fe135c4bc2964ac8ec8f95c242b1?context=explore > > > > It's possible to install all staging artifacts with a single command > > (preferably using the kamel CLI you find in Camel K release files): > > > > $ kamel install --operator-image=camelk/camel-k:2.4.0 --olm=false > > > > Please test this release candidate and cast your vote. > > > > [ ] +1 Release Apache Camel K 2.4.0 > > [ ] -1 Veto the release (provide specific comments) > > > > The vote is open for at least 72 hours. > > > > I start the vote with my +1 (binding). > > > > Thanks and regards, > > Pasquale Congiusti > > > > [1] https://github.com/apache/camel-k/milestone/49?closed=1 > > >
