crooked-cat-2136509/20/2022, 1:11 PM
, but apparently this doesn't affect routing. The pods on the worker node still use eno1 for outgoing traffic only, probably because thats the default route on the worker nodes. The dedicated eno3 interface connected to the external gateway is ignored. I wonder if it is possible to configure networking beyond --address and --internal-address on the rancher-agent command line? The whole docker command line to configure my worker nodes looks like this
--address eno3 --internal-address eno1
Do I have to "struggle" with canal to change routing manually? Every helpful hint is highly appreciated.
docker run -d \ --privileged \ --restart=unless-stopped \ --net=host \ -v /etc/kubernetes:/etc/kubernetes \ -v /var/run:/var/run \ rancher/rancher-agent:v2.6.8 \ --server <https://rancher01.example.com> \ --address eno3 \ --internal-address eno1 \ --token xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx \ --worker