Describe the bug
A clear and concise description of what the bug is.
I flashed Raspbian Lite for my Raspberry Pi 4 (4GB) and updated / upgraded packages with apt:
Linux k4s-3 4.19.58-v7l+ rancher/k3s#1245 SMP Fri Jul 12 17:31:45 BST 2019 armv7l GNU/Linux
I did this on 3 separate RPis and ran the curl / sh script to install k3s as a server on each. I then tried to access Traefik on port 80 with the Node's IP (using my laptop). It did not respond.
If I use curl from on the RPi it does respond with 404 not found.
I then deployed OpenFaaS with the following:
git clone https://github.com/openfaas/faas-netes && cd faas-netes && sudo kubectl apply -f namespaces.yml,yaml_armhf
The pods which rely on networking failed to start, namely the ones which talk to Prometheus on start-up, or the ones which talk to NATS on start-up.
Additional context
Add any other context about the problem here.
This worked well for me every time I tried it previously. The only thing which I think is different is having run sudo apt upgrade. I did not run the firmware update command.
Describe the bug
A clear and concise description of what the bug is.
I flashed Raspbian Lite for my Raspberry Pi 4 (4GB) and updated / upgraded packages with apt:
I did this on 3 separate RPis and ran the curl / sh script to install k3s as a server on each. I then tried to access Traefik on port 80 with the Node's IP (using my laptop). It did not respond.
If I use
curlfrom on the RPi it does respond with 404 not found.I then deployed OpenFaaS with the following:
The pods which rely on networking failed to start, namely the ones which talk to Prometheus on start-up, or the ones which talk to NATS on start-up.
Additional context
Add any other context about the problem here.
This worked well for me every time I tried it previously. The only thing which I think is different is having run
sudo apt upgrade. I did not run the firmware update command.