Viachaslau Tsypylou
Viachaslau Tsypylou
1) Guess it would be better if I paste the whole pod description here. ``` # kubectl -n kube-system describe po kilo-8smsx Name: kilo-8smsx Namespace: kube-system Priority: 0 Node: test-kilo-0/159.100.245.14...
Actually, it is already deployed with the correct path `/etc/cni/net.d`. It was found and corrected from the very beginning of testing kilo.
> What do you mean? I didn't see any logs from Kilo that imply that. I want to say that if we compare logs from both kilo pods - logs...
> I spun up a two nice kubeadm cluster last night and haven't been able to replicate this issue yet. Also worth mentioning that it could be hw/os/etc issue on...
node1: ``` # iptables-save # Generated by iptables-save v1.6.1 on Thu Mar 4 07:24:07 2021 *mangle :PREROUTING ACCEPT [295400:215490847] :INPUT ACCEPT [293641:215410982] :FORWARD ACCEPT [1759:79865] :OUTPUT ACCEPT [292301:63812538] :POSTROUTING ACCEPT...
This is still the issue on version 0.24.0