Loren Lisk

Would love to see this move forwards and willing to sponsor someone to get it done. If anyone wants to take me up on the offer I imagine other might...

so i've tried this with ContainerSource using AWS Pod Identity I've setup the ServiceAccount to have a role with SQS permissions, and can't see how this is not working. ```...

@prashanthm10 @matzew @christophd it seems there currently is no way to use IntegrationSource with the DEFAULT_CREDENTIALS_PROVIDER or IRSA, or using AWS PodIdentities, cause it requires presently the spec.aws field, hence...

Nope never did get this working in v1.17, I can try again shortly as I just updated to v1.18 and see where we are currently. But I don't think anything...

> I need to find the time to reproduce this. I do not see any reason why `CAMEL_` env vars shouldn't work with ContainerSource. > > [@matzew](https://github.com/matzew) is the `gcr.io/knative-nightly`...

> [@christophd](https://github.com/christophd) [@matzew](https://github.com/matzew) I had someone test out the latest eventing-integration nightly images and `CAMEL_KAMELET_AWS_SQS_SOURCE_USE_DEFAULT_CREDENTIALS_PROVIDER` worked. Could you show me an example of this? I'll be trying this out next...

> @liskl Here is a sample ContainerSource that is using the `aws-sqs-source` nightly image and the Camel `useDefaultCredentialsProvider=true` property. We are using IRSA so you'll notice that the Deployment template...