-
Notifications
You must be signed in to change notification settings - Fork 385
Support passing extra arguments to injected envoy binary #675
Conversation
b5663ee
to
4328b74
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great 🎉
The one thing that this needs is to add this new value to the values.yaml
and document it with a comment, e.g. connectInject.imageConsul. This is the pattern we've been using with our helm chart for all other values and so I think we should follow it. We'll also need a changelog entry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, I haven't tested it. Will wait to see wording on values.yaml docs.
4328b74
to
0a41688
Compare
Thanks for your comments! Re-requesting review for the changelog entry and values.yml comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 great work!
When a user sets connectInject.envoyExtraArgs value, they can send arguments to the injected envoy sidecar binary. For example, in a development environment, we could consider enabling debug logs in all sidecars. Usage: ``` connectInject: enabled: true envoyExtraArgs: "--log-level debug --disable-hot-restart" ```
0a41688
to
c163481
Compare
When a user sets
connectInject.envoyExtraArgs
value, they can sendarguments to the injected envoy sidecar binary. For example, in a
development environment, we could consider enabling debug logs in all
sidecars.
Sample values file:
Corresponding consul-k8s PR: hashicorp/consul-k8s#378