-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add Fedora / CoreOS 37 #13
Conversation
Thanks! The microos build is failing, I opened another PR to fix it #14 |
Do you have an idea on how to allow the kube-apiserver to start again? Maybe something like the workaround from rancher/rke2#692 (comment)? |
Are you using RKE2 and did you install the rke2-selinux RPM? You may need to add a policy for fedora for that repo. The |
I am using RKE1. If i install this RPM the selinux check in rke passes but the kube-apiserver can't start up (that's as far as i've gotten). The system audit log shows some failed appends to |
What do the selinux audit logs say? There should already be existing rules in this package that apply to /opt/rke, possibly we need to add something special for fedora /~https://github.com/rancher/rancher-selinux/pull/13/files#diff-3ca1372da779b1babd4670b9d92963b813c9c5b6ec16698bc148c9f063d8da20R2 |
Here are some logs i gathered. The kube-apiserver has a bind mount from
I think some messages are unrelated to kubernetes but i'm not entirely sure. |
@bbaumgartl from those logs it looks like the audit log has type |
Sorry, it took me a while testing things. While updating the nodes i noticed that one node was fine (selinux in enforcing and kube-apiserver starting). Checking After setting Does it make sense to add this workaround (or setting |
when in doubt, especially with such mixed-mode-over-time scenarios, consider a recursive |
A |
@andypitcher let me know if you need RKE1 team help on this |
@bbaumgartl thanks for submitting this PR. FYI we will review and, if applicable, merge it as soon as we are done with the PR to support EL9 (and tested) and have the build pipelines fixed. CC @andypitcher |
Co-authored-by: Andy Pitcher <andy.pitcher@suse.com>
This is a proof of concept which allows RKE to be deployed to SELinux enabled Fedora >= 37
Currently this does not allow kube-apiserver to start because it can't write/append audit logs. Maybe this is related to /~https://github.com/rancher/rke2-selinux/pull/17/files