-
Notifications
You must be signed in to change notification settings - Fork 33
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
Flannel >= 0.17.0 is crashing with enforced SELinux #779
Comments
Can be reverted once: flatcar/Flatcar#779 done Signed-off-by: Mathieu Tortuyaux <[email protected]>
Can be reverted once: flatcar/Flatcar#779 done Signed-off-by: Mathieu Tortuyaux <[email protected]>
@tormath1 Perhaps I misunderstand but what more work has to be done here. Doesn't the successful incorporation of sec-policy/selinux-container solve this? Thanks! |
If this is the case, the docs should be updated to reflect the fix |
@krishjainx thanks for the heads-up. Pulling |
Description
While integrating
kubernetes-1.24.1
, we bumped theflannel
tested version from0.16.3
to0.18.1
- we notified that thekube-flannel
daemon set is unable to start because of missing SELinux rule:The issue has always been there but silently ignored until this commit: flannel-io/flannel@9dfcc87#diff-27988e531dd370eec963c5e4e9be79bb158baa292798a2f59a13a031e1ab8f6aR196
Impact
Unable to run Kubernetes with
flannel
CNI in enforced SELinux environmentEnvironment and steps to reproduce
kubeadm.v1.23.4.flannel.base
Additional information
SELinux
(sudo setenforce 0
)container_t
(a.k.asvirt_lxc_net_t
) toiptables_t
The text was updated successfully, but these errors were encountered: