Skip to content

docs: Inform multiple region support not an option for iam-role-eks #299

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

Conversation

sepulworld
Copy link
Contributor

Description

Improve docs for iam-eks-role - inform user that this sub module will not work for multiple regions

Motivation and Context

Will help save time if the end user has a multi region setup. This module doesn't support creating a role for multiple EKS clusters in more than 1 region.

Breaking Changes

None

How Has This Been Tested?

Docs change for clarity

projects

  • I have executed pre-commit run -a on my pull request

@sepulworld sepulworld changed the title docs: inform multiple region support not an option for iam-role-eks Docs: inform multiple region support not an option for iam-role-eks Nov 1, 2022
@sepulworld sepulworld changed the title Docs: inform multiple region support not an option for iam-role-eks docs: Inform multiple region support not an option for iam-role-eks Nov 1, 2022
@@ -7,6 +7,7 @@ Creates an IAM role that can be assumed by one or more EKS `ServiceAccount` in o
- Support multiple `ServiceAccount` in the same cluster, for example when a workload runs in multiple namespaces
- More suitable for non-cluster admins as implementation is simpler
- More suitable for when the IAM role and cluster resources are in separate Terraform configurations
- Does not support multiple regions, consider using [iam-assumable-role-with-oidc](https://github.com/terraform-aws-modules/terraform-aws-iam/blob/master/modules/iam-assumable-role-with-oidc/) if role needs to support clusters in multiple regions
Copy link
Member

Choose a reason for hiding this comment

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

Can we update/combine this with the 2nd bullet since I think they are related. It supports multiple clusters, but the caveat is that it does not support multiple regions due to the use of the aws_eks_cluster data source

Suggested change
- Does not support multiple regions, consider using [iam-assumable-role-with-oidc](https://github.com/terraform-aws-modules/terraform-aws-iam/blob/master/modules/iam-assumable-role-with-oidc/) if role needs to support clusters in multiple regions
- Does not support multiple regions, consider using [iam-role-for-service-accounts-eks](https://github.com/terraform-aws-modules/terraform-aws-iam/blob/master/modules/iam-role-for-service-accounts-eks/) if role needs to support clusters in multiple regions

cc @max-rocket-internet

Copy link
Contributor

Choose a reason for hiding this comment

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

Hey 👋

@sepulworld

inform user that this sub module will not work for multiple regions

There is a note already in the README that says "The EKS cluster needs to exist first, in the current AWS account and region". I think that's pretty clear, no?

consider using iam-role-for-service-accounts-eks

I don't think this is great advice since the iam-role-for-service-accounts-eks module is stated for "commonly used controllers/custom resources" (quite specific) whereas iam-role-eks has no specific use case like this, it's simply to create a general IRSA role that could be used for anything. The existing readme already details differences compared to iam-assumable-role-with-oidc, perhaps we recommend using this for multi-region?

@sepulworld
Copy link
Contributor Author

sepulworld commented Nov 2, 2022 via email

@max-rocket-internet
Copy link
Contributor

@sepulworld cool, merge it 👍

@antonbabenko antonbabenko merged commit fc093dd into terraform-aws-modules:master Nov 3, 2022
@antonbabenko
Copy link
Member

This PR is included in version 5.5.6 🎉

@github-actions
Copy link

github-actions bot commented Dec 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 Dec 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.

4 participants