feat: Add new sub-module for creating IAM roles for service accounts

[bryantbiggs]

⚠️ I don't know how I feel about this yet so don't get your heart set on it ⚠️

Description

• Add new sub-module for creating IAM roles for service accounts

On one hand I can see this making some sense, but here are my current reservations:

• We already have this -> https://github.com/terraform-aws-modules/terraform-aws-iam/tree/master/modules/iam-assumable-role-with-oidc
• Which extended to then also add this -> https://github.com/terraform-aws-modules/terraform-aws-iam/tree/master/modules/iam-eks-role

Why do I like these ☝🏽?

• They only have one provider which is the AWS provider. This change sort of sneakily adds in the Kubernetes provider which if you don't set the proper configs it just errors out with an obscure dial tcp 127.0.0.1:80: connect: connection refused

Why am I not (yet) drawn to this 👇🏽 change?

• What do we really gain? Service account and namespace creation? I do not like managing Kubernetes manifests in Terraform - I think they should be handled by whatever tool you use to deploy your applications. For IRSA, all we need to do is provide an IAM role really and if you see above, we have two module that already do that

Why this could be useful:

• Folks come here for EKS guidance and maybe they don't see the IRSA roles. Maybe moving it to a first-class supported sub-module here increases that visibility for them

Motivation and Context

• Add optional IRSA provisioning for most common EKS components ?  #1825

Breaking Changes

How Has This Been Tested?

• I have tested and validated these changes using one or more of the provided examples/* projects

[bryantbiggs]

direction is to enable opt-in IAM policies under the https://github.com/terraform-aws-modules/terraform-aws-iam/tree/master/modules/iam-eks-role module

[github-actions]

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.