AWS AppMesh Controller - Add configuration to update ENVOY LOG FORMAT
- 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 want to be able to remove the "%REQ(X-FORWARDED-FOR)%" from the envoy access logs from sidecar container as it does not meet my project's compliance requirements.
Standalone Envoy has the ability to do this: https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/access_log/usage#default-format-string
**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
appmesh-controller
**Describe the solution you'd like**
I'd like a parameter called sidecar.logFormat that allows me to update the default envoy LOG format
**Describe alternatives you've considered**
Since we have the AWS AppMesh Controller installed in our EKS cluster using the helm chart, there isn't much we can do since the controller is adding envoy to our virtual nodes as a sidecar.
This is pretty important for us since we are failing to meet our compliance requirements due to this.
Contributor guide
Research direction
Start with the appmesh-controller Helm chart and the linked Envoy access-log documentation to find how sidecar configuration is generated. Define what the sidecar.logFormat parameter should control, then verify that the resulting Envoy access logs omit the requested field and that the chart renders the setting correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100