Skip to content
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

fix: Correct DNS suffix for OIDC provider #2026

Merged
merged 2 commits into from
Apr 20, 2022

Conversation

xchan
Copy link
Contributor

@xchan xchan commented Apr 20, 2022

Description

This is a supplement fix for
#1904

Motivation and Context

This MR is a combined fix for succefully launching Karpenter 0.8.2 on AWS EKS on China Region (cn-northwest-1)

Breaking Changes

N/A

How Has This Been Tested?

  • [*] I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

AWS EKS version 1.22 + Karpenter 0.8.2 launched succefully with this fix with node scaling test done.

@bryantbiggs
Copy link
Member

thank you @xchan - can you update your PR title to something like fix: Correct DNS suffix for OIDC provider

@bryantbiggs bryantbiggs changed the title Patch sts dns suffix fix: Correct DNS suffix for OIDC provider Apr 20, 2022
Copy link
Member

@bryantbiggs bryantbiggs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you!

@bryantbiggs bryantbiggs merged commit 5da692d into terraform-aws-modules:master Apr 20, 2022
antonbabenko pushed a commit that referenced this pull request Apr 20, 2022
### [18.20.4](v18.20.3...v18.20.4) (2022-04-20)

### Bug Fixes

* Correct DNS suffix for OIDC provider ([#2026](#2026)) ([5da692d](5da692d))
@antonbabenko
Copy link
Member

This PR is included in version 18.20.4 🎉

spr-mweber3 pushed a commit to spring-media/terraform-aws-eks that referenced this pull request Apr 26, 2022
Co-authored-by: Xin Chen <chenxin@konvery.com>
Co-authored-by: Bryant Biggs <bryantbiggs@gmail.com>
spr-mweber3 pushed a commit to spring-media/terraform-aws-eks that referenced this pull request Apr 26, 2022
it-without-politics pushed a commit to it-without-politics/terraform-aws-eks that referenced this pull request May 23, 2022
Co-authored-by: Xin Chen <chenxin@konvery.com>
Co-authored-by: Bryant Biggs <bryantbiggs@gmail.com>
it-without-politics pushed a commit to it-without-politics/terraform-aws-eks that referenced this pull request May 23, 2022
baibailiha added a commit to baibailiha/terraform-aws-eks that referenced this pull request Sep 13, 2022
@DmitriyStoyanov
Copy link

I try to migrate cluster from v17.24.0 to v18.29.0 and faced with deployment to AWS China, that error appears:

Error: error updating IAM Role (XXXXXXX) assume role policy: MalformedPolicyDocument: Invalid principal in policy: "SERVICE":"eks.amazonaws.com.cn"
│       status code: 400, request id: XXXXXXXX

Fixed by adding variable
cluster_iam_role_dns_suffix = "amazonaws.com"

so looks like in China we have the same principal - "eks.amazonaws.com", but not "eks.amazonaws.com.cn" as currently module tried to create

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants