-
Notifications
You must be signed in to change notification settings - Fork 214
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
Add egress documentation #1884
Add egress documentation #1884
Conversation
Signed-off-by: Zahari Dichev <[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.
I've suggested some wording changes but this is really helpful, thanks much!! 🙂
Co-authored-by: Flynn <[email protected]>
Signed-off-by: Zahari Dichev <[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.
Four more tiny things -- let me know if you'd rather I just merge these! Many thanks. 🙂
Co-authored-by: Flynn <[email protected]>
Signed-off-by: Flynn <[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.
Thanks! Looks good to me but let's see if @wmorgan can chime in quickly. 🙂
Signed-off-by: Flynn <[email protected]>
Signed-off-by: Flynn <[email protected]>
Signed-off-by: Flynn <[email protected]>
|
||
{{< warning >}} | ||
|
||
No service mesh can provide a strong security guarantee about egress traffic |
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.
Just fine tuning: Even a meshed application can bypass its proxy in certain conditions, so I would generalize the first statement (cf. https://blog.howardjohn.info/posts/bypass-egress/). I would also probably generalize the last sentence a bit since I am not convinced that just adding CNI config on top of the existing egress setup is by itself sufficient.
Signed-off-by: Flynn <[email protected]>
…gress-docs * 'zd/egress-docs' of github.com:linkerd/website: Rate Limiting docs (#1877) Signed-off-by: Flynn <[email protected]>
Signed-off-by: Flynn <[email protected]>
* add egress documentation Signed-off-by: Zahari Dichev <[email protected]> * Apply suggestions from code review by @kflynn Co-authored-by: Flynn <[email protected]> * lint Signed-off-by: Zahari Dichev <[email protected]> * Apply suggestions from code review Co-authored-by: Flynn <[email protected]> * Warnings per William Signed-off-by: Flynn <[email protected]> * Effing lint... Signed-off-by: Flynn <[email protected]> * 🤦♂️ Syntax correctness would help. Signed-off-by: Flynn <[email protected]> * C'mon, lint, tell me all the errors at once... Signed-off-by: Flynn <[email protected]> * Warning tweaks after William's feedback Signed-off-by: Flynn <[email protected]> * 🤦♂️ Signed-off-by: Flynn <[email protected]> --------- Signed-off-by: Zahari Dichev <[email protected]> Signed-off-by: Flynn <[email protected]> Co-authored-by: Flynn <[email protected]> Co-authored-by: Flynn <[email protected]> Signed-off-by: Ivan Porta <[email protected]>
Signed-off-by: Zahari Dichev [email protected]