Skip to content

Adds documentation for adding environment variables to the envoy sidecar #654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 15, 2022
Merged

Adds documentation for adding environment variables to the envoy sidecar #654

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 24 additions & 1 deletion docs/reference/injector.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

In order to use AWS App Mesh in Kubernetes, pods in the mesh must be running the AWS App Mesh sidecar proxy (Envoy).

The following sections describe methods for injecting sidecar/Envoy into a pod for Virtual Nodes and Virtual Gateways
The following sections describe methods for injecting sidecar/Envoy into a pod for Virtual Nodes and Virtual Gateways.

## Envoy injection for virtual nodes

Expand Down Expand Up @@ -171,3 +171,26 @@ spec:
ports:
- containerPort: 8088
```


## Custom Environment Variables For Envoy

Additional environment variables can be passed to the envoy sidecar container by
adding an `appmesh.k8s.aws/sidecarEnv` annotation to the application's
deployment:

```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: ingress-gw
namespace: ns
spec:
template:
metadata:
annotations:
appmesh.k8s.aws/sidecarEnv: "CUSTOM_VAR=value1"
```

Multiple variables can be set by passing a comma-delimited list -
`appmesh.k8s.aws/sidecarEnv: "CUSTOM_VAR_1=a, CUSTOM_VAR_2=b"`.