Support of tolerations and node selectors in aws-sigv4-proxy-admission-controller/
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
**Is your feature request related to a problem?**
Unable to use node selectors and tolerations when deploying aws-sigv4-proxy-admission-controller HELM Chart. This is needed as in complex setups nodes are typically tainted for specific infrastructure use and this HELM chart is a good example of the infrastructure component that has to be deployed in a separate "instances" group
**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
aws-sigv4-proxy-admission-controller/
**Describe the solution you'd like**
Ability to pass standard tolerations and nodeSelector's in the HELM Chart value
**Describe alternatives you've considered**
None
Contributor guide
Research direction
Start with the aws-sigv4-proxy-admission-controller Helm chart and its values to trace how deployment scheduling options are configured. Verify how standard nodeSelector and tolerations values should be supplied, then confirm that the rendered chart places them on the controller workload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100