[aws-cloudwatch-metrics] Possibility to add extra envs into container template
- 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?**
I've encountered a problem when pod has to connect to AWS Cloudwatch through proxy. Chart does not support adding extra container envs for http and https proxy URL's.
**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
aws-cloudwatch-metrics
**Describe the solution you'd like**
able to add extra envs to daemonset chart
**Describe alternatives you've considered**
Right now I'm running a script, using `kubectl set env` option, to inject http and https proxy URL variables after deployment. I understand that I could fork the chart and make the appropriate changes myself, but I think an upstream approach would be better.
Contributor guide
Research direction
Start with the aws-cloudwatch-metrics Helm chart and locate the DaemonSet container template. Determine how the chart should accept extra HTTP and HTTPS proxy environment variables, then verify that a rendered deployment includes those variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100