-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable_irsa=true creates OIDC provider with audience pointing to global sts endpoint (sts.amazonaws.com) #1145
Comments
The local endpoints are usually handled by the VPC module, and I think it should probably stick that way to keep the complexity of this module to a minimum. The fix for this is probably documentation on how to easily create the endpoint with the VPC module in an example. |
I think @toytown is simply asking for a new variable to allow setting the audience, (the I am probably going to want this also as I have to use VPC endpoints in order to reach the STS API without using a proxy. |
Deploying to CN accounts, in regions like "Incorrect Token Audience" will be seen because the |
does this is not working in this use case: Line 47 in 1e2c324
or this is related to OIDM role module used in examples? |
The code you've pasted here works as expected, but cluster-autoscaler, velero, etc -- almost any service that uses IAM Roles for Service Accounts needs to use It would be nice if we had a variable here to add more. |
ok, but in that case I believe change is applicable to module https://github.com/terraform-aws-modules/terraform-aws-iam/tree/v4.1.0/modules/iam-assumable-role-with-oidc which is used in example: terraform-aws-eks/examples/irsa/irsa.tf Lines 1 to 9 in 9022013
|
I don't understand where |
This is what I think needs changing: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/irsa.tf#L12 AWS docs instruct using
|
just to confirm (as I dont have any experience with cn region), https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/irsa.tf#L12 should be pointing always to |
When using IAM Roles for Service Accounts, this is the only thing that works for me. I don't see any harm in having both |
@daroga0002 could you take another look or weigh in on the PR? |
ok, I understand now your pain I also checked docs: |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I have issues
I'm submitting a...
What is the current behavior?
EKE- 1.18, Fargate
when enable_irsa = true an OIDC provider is created correctly and the audience is set to "sts.amazonaws.com". However, in most corporate network one is encouraged to use local endpoint "sts.eu-central-1.amazonaws.com". In most of the corporate network I have experienced the "sts.amazonaws.com" is blocked which creates issues for role assumption by containers.
If this is a bug, how to reproduce? Please include a code sample if relevant.
What's the expected behavior?
Either based on region setting of the EKS cluster or through explicit setting of sts endpoint it would be nice to have to be able to configure OIDC audience (sts endpoint) explicitly with some property like
oidc_audience = sts.xxxx.com (if irsa is set tot true)
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details
Any other relevant info
The text was updated successfully, but these errors were encountered: