Open danielloader opened 3 months ago
👍 for this. - of the supported values are below, None
makes the most sense as it should fall back on AWS_CONTAINER_CREDENTIALS_FULL_URI
and AWS_CONTAINER_AUTHORIZATION_TOKEN
from the SDK, I think?
The ProviderConfig "aws-provider" is invalid: spec.credentials.source: Unsupported value: "yeet": supported values: "None", "Secret", "IRSA", "WebIdentity", "Upbound"
Please Check #1254
What problem are you facing?
I’d like to utilise pod identity controller associations to give my AWS providers the correct IAM privileges, instead of IRSA.
How could Official AWS Provider help solve your problem?
I’m not sure if it’s possible or not as the documentation doesn’t seem to indicate it is, if it is I’d love to see a sample ProviderConfig object for this authentication and authorisation mechanism.