-
Notifications
You must be signed in to change notification settings - Fork 164
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make sure that K3s service prefix is routed via cluster interface
Ensure that packets destined for K3s services do not use the default route, but are instead routed through the cluster port. This guarantees that traffic handled by kube-proxy is properly SNATed to the cluster IP. That's the theory at least. We're not entirely certain. Without this route, however, some Longhorn pods fail to access K3s services when the cluster IP is configured on a non-default port. Signed-off-by: Milan Lenco <milan@zededa.com>
- Loading branch information
1 parent
f79132c
commit a85bf88
Showing
2 changed files
with
61 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters