-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.17.4+k3s1 CoreDNS and LocalPathProvisioner pods crashlooping #1583
Comments
@erikwilson Could this be a related to f2a4e1d which introduced a toleration if the node has Can you share the list of taints on your nodes? |
Hi @benfairless I dont see any taints here
Hope it helps I think the following must be key to the problem: |
Might be related cri-o/cri-o#528 |
f2a4e1d is not in 1.17.4, we don't use cri-o but did add selinux support to cri. So now that selinux is turned on in containerd for 1.17.4 this is probably causing the issue. You can revert to the old behavior by disabling selinux with the
Ultimately we would like to recommend using k3s rpm installation through a repo which will require the k3s-selinux policy, but still have a few things that need to happen for that process. Apologies that this was a problem & thanks for your patience while we iron this out. |
To test, we just need to verify that when we follow the instructions for properly installing the k3s selinux policies, coredns and localPathProvisioner do not go into a crash loop |
Verified using 1.18.2-rc2+k3s1. Install following packages as in installation docs https://rancher.com/docs/k3s/latest/en/advanced/
|
Version:
v1.17.4+k3s1
Does not reproduce in the same setup (vagrant generic/centos7 box) with v1.17.3+k3s1
K3s arguments:
Describe the bug
CoreDNS and LocalPathProvisioner pods are unable to start
To Reproduce
Expected behavior
CoreDNS and Local Path Provisioner are started and operating normally
Actual behavior
CoreDNS and LocalPathProvisioner pods crashlooping
Additional context / logs
The text was updated successfully, but these errors were encountered: