[EKS] [request]: EKS Addon of cert-manager misssing configuration for IRSA/PodIdentity
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
There are no configuration setting for the cert-manager addon for adding IRSA/PodIdentity
**Which service(s) is this request for?**
EKS, EKS Addon
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
when using cert-manager issuer with DNS01 challenge, the cert-manager-controller required Route53 permission, https://cert-manager.io/docs/configuration/acme/dns01/route53/ . When using EKS AutoMode, the AMI Amazon Linux 2023 being used was having the IMDSv2 as required and hop limit set as 1. So we won't be able to use the node role from the pod.
**Are you currently working around this issue?**
Currently, to enable cert-manager-controller performing properly. I am patching k8s cart-manager Service Account annotation with the correct IAM role.
**Additional context**
Anything else we should know?
**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Contributor guide
Research direction
Begin with the EKS Add-ons configuration documentation and the cert-manager Route53 DNS01 documentation linked in the issue. Compare the available IRSA and Pod Identity mechanisms, then define the supported settings and validation needed for the cert-manager controller; done means it can receive Route53 permissions without manually patching its ServiceAccount.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- authorization, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100