-
Notifications
You must be signed in to change notification settings - Fork 326
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.
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
Support passing extra arguments to injected envoy binary #378
Conversation
<Co-authored-by: Iryna Shustava [email protected]>
<Co-authored-by: Iryna Shustava [email protected]>
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. Have a few minor questions but love this overall!!
this commit will be squashed
6068ce9
to
1fec181
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.
Re-requesting review: addressed PR comments, and added functionality to pass the envoy binary arguments via pod annotations as well.
Also planning to squash and merge this one when its ready since the git history on this one's a bit funky and there's a merge commit in here.
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 🎉 💃 ! I've left a couple of edits, but they are non-blocking.
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.
🥳 Brilliant!!
Update annotation docs
Changes proposed in this PR:
You can set it via either one, but if you set the args both ways, the pod annotation arguments will be used.
How I've tested this PR:
gcr.io/nitya-293720/consul-k8s-dev:extraEnvoyArgs
) and ran it on a cluster, while passing--log-level debug
as an extra envoy flag, and saw that when we deployed a connect-inject enabled service, the envoy logs were showing debug logs.How I expect reviewers to test this PR:
Checklist: