Skip to content
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: Document some caveats of kube-proxy replacement #13640

Merged
merged 2 commits into from
Oct 20, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions Documentation/gettingstarted/kubeproxy-free.rst
Original file line number Diff line number Diff line change
Expand Up @@ -442,6 +442,10 @@ advised to first check whether the NodePort request actually arrived on the node
containing the backend. If this was not the case, then switching back to the default
SNAT mode would be advised as a workaround.

Also, in some public cloud provider environments, which implement a source /
destination IP address checking (e.g. AWS), the checking has to be disabled in
order for the DSR mode to work.

Above helm example configuration in a kube-proxy-free environment with DSR-only mode
enabled would look as follows:

Expand Down Expand Up @@ -1179,6 +1183,9 @@ Limitations
resources to corresponding ``EndpointSlices`` and thus allowing backing ``Endpoints``
to work. For a more detailed discussion see
`#12438 <https://github.com/cilium/cilium/issues/12438>`__.
* As per `k8s Service <https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types>`__,
Cilium's eBPF kube-proxy replacement disallow access of a ClusterIP service
from outside a cluster.

Further Readings
################
Expand Down