Open ckt114 opened 4 days ago
Hi, we haven't seen this before so we believe this has to be triggered by something in your environment.
What happens if you reboot and instead of:
sudo k0s stop
sudo k0s install controller --single --force
sudo k0s start
You just do:
sudo k0s stop
sudo k0s start
IMPORTANT, don't do this immediately after the reboot, give it some time, maybe 5 minutes after the reboot because we suspect it may be a timing issue regarding network interfaces not being ready just yet.
Finally would it be possible to provide k0s logs after the reboot?
Before creating an issue, make sure you've checked the following:
Platform
Linux 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
Version
v1.31.1+k0s.1
Sysinfo
`k0s sysinfo`
What happened?
After I restart the OS I get the error below when running any kubectl command.
To fix it I had to run
again then kubectl works again.
This is my
/etc/k0s/k0s.config
file.After the system I rebooted and kubectl throws tls error and I ran
sudo k0s kubeconfig admin
I saw that the sever cluster address is127.0.0.1
instead of192.168.2.10
. Also, I don’t know where the10.96.0.1
IP in the error message comes from.Steps to reproduce
Expected behavior
K0s should retain the api.address from the installation config.
Actual behavior
K0s reverted the api address to 127.0.0.1 after system reboot instead of retaining the custom 192.168.2.10 api address.
Screenshots and logs
No response
Additional context
No response