Dave Protasowski

/hold based on the comments in https://github.com/kubernetes-sigs/gateway-api/pull/3978 - there seems to be a misunderstanding of Route attachment semantics in this PR see: https://github.com/kubernetes-sigs/gateway-api/pull/3978#issuecomment-3211055462

I think we should remove the queue proxy image annotation change. I don't think that's something that we want users being able to manipulate given that's an operator concern.

> This means that during a knative upgrade pod updates of queue-proxy before the activator would cause issues, as activator would send the preface the go stdlib http2 implementation in...

I think we should scope this to just the queue proxy => user container as per this issue https://github.com/knative/serving/issues/15432 and for now ignore activator => queue proxy interaction given that...

FYI - I was playing with using the new go1.24 features of not needing the h2c package. See: https://github.com/knative/pkg/pull/3298 Though when I test it out it's failing on Kourier and...

@linkvt can we drop the queue proxy annotations from this PR

@liskl did you ever sort out why using the ContainerSource directly didn't work?

@christophd do you know why the use of the image with the `CAMEL_` env vars wouldn't work as a workaround?

> I think the Camel Kamelets have received some updates and fixes regarding AWS IAM connectivity recently, so we have to make sure that the images are using these updated...

@christophd @matzew I had someone test out the latest eventing-integration nightly images and `CAMEL_KAMELET_AWS_SQS_SOURCE_USE_DEFAULT_CREDENTIALS_PROVIDER` worked.