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
1.8 Documentation updates #11892
1.8 Documentation updates #11892
Conversation
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.
LGTM, one minor comment below.
Would be nice to get a second view from someone like @seanmwinn / @jedsalazar .
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.
LGTM, when I looked at #11868 yesterday, I noticed that we have two of the same Helm deploy instructions for AWS / EKS / ENI. See EKS guide and ENI guide. It'd be nice if we can consolidate these two Helm instruction sections into one, by putting the shared info into a separate file and referencing it in the two sections. This would help avoid an inconsistency cropping up like the above issue.
-------------------- | ||
|
||
eBPF-based | ||
The eBPF-based implementation is the most efficient |
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.
Once this PR is emerged, I will extend this section to add more info about device selection.
Signed-off-by: Thomas Graf <thomas@cilium.io>
There is nothing nulti-node specific about this section. Rename it to just networking. Signed-off-by: Thomas Graf <thomas@cilium.io>
Fixes: #11369 Signed-off-by: Thomas Graf <thomas@cilium.io>
Fixes: #11868
Fixes: #11369