mirrors/kube-router
1
0
Fork 0
mirror of https://github.com/cloudnativelabs/kube-router.git synced 2025-11-30 01:11:05 +01:00
Code Issues Packages Projects Releases Wiki Activity

doc(DSR): add /etc/iproute2/rt_tables caveat

Browse Source
This commit is contained in:
Aaron U'Ren 2024-03-18 17:27:30 -05:00 committed by Aaron U'Ren
parent 19099187b9
commit 614d47285c
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
daemonset/kubeadm-kuberouter-all-features-dsr.yaml
View File

@ -91,6 +91,9 @@ spec:
- name: run - name: run
mountPath: /var/run/docker.sock mountPath: /var/run/docker.sock
readOnly: true readOnly: true
- name: rt_tables
mountPath: /etc/iproute2/rt_tables
readOnly: false
- name: xtables-lock - name: xtables-lock
mountPath: /run/xtables.lock mountPath: /run/xtables.lock
readOnly: false readOnly: false
@ -140,6 +143,9 @@ spec:
- name: run - name: run
hostPath: hostPath:
path: /var/run/docker.sock path: /var/run/docker.sock
- name: rt_tables
hostPath:
path: /etc/iproute2/rt_tables
- name: kube-router-cfg - name: kube-router-cfg
configMap: configMap:
name: kube-router-cfg name: kube-router-cfg

7
docs/dsr.md
View File

@ -27,6 +27,7 @@ Requirements:
* `hostIPC: true` must be set for the pod * `hostIPC: true` must be set for the pod
* `hostPID: true` must be set for the pod * `hostPID: true` must be set for the pod
* The container runtime socket must be mounted into the kube-router pod via a `hostPath` volume mount. * The container runtime socket must be mounted into the kube-router pod via a `hostPath` volume mount.
* `/etc/iproute2/rt_tables` must be read/write mounted into the kube-router pod via a `hostPath` volume mount.
* A pod network that allows for IPIP encapsulated traffic. The most notable exception to this is that Azure does not * A pod network that allows for IPIP encapsulated traffic. The most notable exception to this is that Azure does not
transit IPIP encapsulated packets on their network. In this scenario, the end-user may be able to get around this transit IPIP encapsulated packets on their network. In this scenario, the end-user may be able to get around this
issue by enabling FoU (`--overlay-encap=fou`) and full overlay networking (`--overlay-type=full`) options in issue by enabling FoU (`--overlay-encap=fou`) and full overlay networking (`--overlay-type=full`) options in
@ -85,6 +86,9 @@ spec:
- name: run - name: run
hostPath: hostPath:
path: /var/run/docker.sock path: /var/run/docker.sock
- name: rt_tables
hostPath:
path: /etc/iproute2/rt_tables
... ...
containers: containers:
- name: kube-router - name: kube-router
@ -94,6 +98,9 @@ spec:
- name: run - name: run
mountPath: /var/run/docker.sock mountPath: /var/run/docker.sock
readOnly: true readOnly: true
- name: rt_tables
mountPath: /etc/iproute2/rt_tables
readOnly: false
... ...
``` ```