aws / aws/amazon-eks-pod-identity-webhook
Helm Chart for Deployments
- Dominant language
- Go
- Stars
- 691
- Forks
- 202
- Avg merge
- 4h 38m
- Merged PRs (30d)
- 1
Description
**What would you like to be added**: Helm chart for standardised deployment
**Why is this needed**: Helm is widely used in the k8s community for deploying resources across clusters. This would allow for teams to bake existing workflows in things like terraform, ansible, etc. more easily than the current Makefile, as well as allow more customisation where needed for teams that may have different access control needs or configuration needs wrt some of the resources created for this.
---
Looking at the Makefile, I don't think this is an insurmountable task at all :D Looks like the only iffy part might be the cert generation?
If I can find the spare cycles, I might just pick this one up myself.
Contributor guide
Research direction
Start by reading the existing Makefile to map the resources and deployment workflow that the chart must represent, paying particular attention to certificate generation. Done means a Helm chart supports standardized deployment while allowing teams to customize configuration and access control for the created resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, helm, kubernetes, terraform
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100