feat: support env vars and secrets for sidecars#1725
feat: support env vars and secrets for sidecars#1725mergify[bot] merged 5 commits intoaws:mainlinefrom
Conversation
7c986cf to
786c8c0
Compare
786c8c0 to
e5c323f
Compare
e5c323f to
1a5c46e
Compare
| destination: | ||
| Name: cloudwatch | ||
| region: us-west-2 | ||
| region: us-east-1 |
There was a problem hiding this comment.
I'm just curious why you changed regions here...?
There was a problem hiding this comment.
good question it is because our e2e tests are deployed in us-east-1, so that firelens knows where to find the log group and create the log stream in it.
There was a problem hiding this comment.
but i do think we need to update the e2e test so that this error can be caught.
There was a problem hiding this comment.
ok now it should be able to catch it if the firelens is not able to create the log stream in the log group.
| @@ -1,2 +1,8 @@ | |||
| FROM nginx | |||
| COPY nginx.conf /etc/nginx/nginx.conf | |||
| FROM nginx:1.15-alpine | |||
There was a problem hiding this comment.
| port: 80 | ||
| image: %s # Image URL for sidecar container. | ||
| variables: | ||
| NGINX_PORT: %s |
There was a problem hiding this comment.
Is it possible to set variables or secrets per-environment, i.e. dev and prod?
There was a problem hiding this comment.
Yeah I think you can do the override like this
sidecars:
nginx:
port: 80
image: %s # Image URL for sidecar container.
variables:
NGINX_PORT: 80
environments:
dev:
sidecars:
nginx:
variables:
NGINX_PORT: 8080
prod:
sidecars:
nginx:
variables:
NGINX_PORT: 5000
fixes #1119
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.