-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
docs: Update egress gateway limitations #24244
docs: Update egress gateway limitations #24244
Conversation
We mention that the egress gateway is for IPv4 traffic, but we never explictly say that IPv6 isn't supported. This is apparently not obvious to everyone so let's state it here. This commit moves the feature incompatibilies subsection under the Preliminary Considerations section. Another subsection will be added there by the next commit. Signed-off-by: Paul Chaignon <paul@cilium.io>
This delay can have a security impact if the egress gateway masquerading is used to enforce policies in appliances outside the cluster. Signed-off-by: Paul Chaignon <paul@cilium.io>
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.
First commit description says:
This commit moves the feature incompatibilies subsection under the
Preliminary Considerations section.
It renames the section, but doesn't appear to move it?
Checkpatch caught a typo in the same commit description (explictly
).
Other than these, looks all good.
It kind of moves it if you considered the rendered output. The text doesn't move but the incompatibility subsection is now under the Preliminary Considerations section when it used to be its own section. So it's "move under" as in "in the hierarchy" not as in "move below". |
See commits.