On Monday, May 24, 2021 12:56:36 PM CEST Thorsten Kukuk wrote:
On Sun, May 23, Marc Balmer wrote:
Am 23.05.2021 um 21:57 schrieb Thorsten Kukuk
: On Sun, May 23, Marc Balmer wrote:
Kubic is at the moment in a non-working state.
Hm, I wonder why it works out of the box for me on my Kubic clusters? If you mean your poblem with Rancher, I doubt that this is a kubic problem.
Rancher not working is only a "second stage" problem. The Kubic nodes need "sysctl -a --system" to be manually applied to get access to the outside world (e.g. DNS resolution). When that is done, the pods can resolve adresses, but have no route to them (like the rancher cluster-agent pod not being able to access the rancher system). So there is, I guess, an iptables issue of some sort. As written in boo#1186125, delete /etc/sysctl/70-yast.conf
Thorsten
Does this fix the forwarding issues? I recently came across this problem a few days ago scratching my head for the cause of various services to fail (CoreDNS and access to an external PostgreSQL server) which I manually fixed by enabling forwarding for the ethernet card responsible for network access. Daniel Sonck