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: Extend kubeproxy-free GSG wrt multi-dev #12054
Conversation
Please set the appropriate release note label. |
4 similar comments
Please set the appropriate release note label. |
Please set the appropriate release note label. |
Please set the appropriate release note label. |
Please set the appropriate release note label. |
Please also add a full new GSG sub-section including setup-verification for multi-dev howto for the scenarios of public iface exposed to world and private for backends. |
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 besides what Daniel already mentioned ☝️
Removing the release-blocker label, as it's a documentation change which can be merged after we release the v1.8.0 image and still be shown in the docs. |
Such device is denoted with "(DR)", e.g.: KubeProxyReplacement: Strict [eth0 (DR), eth1] [NodePort (SNAT, 30000-32767, XDP: DISABLED), HostPort, ExternalIPs, HostReachableServices (TCP, UDP), SessionAffinity] Signed-off-by: Martynas Pumputis <m@lambda.lt>
a22626c
to
d8658c8
Compare
d8658c8
to
ca338e8
Compare
test-me-please |
Extended the existing section to avoid overbloating the guide. |
Signed-off-by: Martynas Pumputis <m@lambda.lt>
This PR:
KubeProxyReplacement
incilium status
(denoted with(DR)
).