Skip to content
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

[Documentation] SELinux #2058

Closed
davidnuzik opened this issue Jul 23, 2020 · 10 comments
Closed

[Documentation] SELinux #2058

davidnuzik opened this issue Jul 23, 2020 · 10 comments
Labels
kind/documentation Improvements or additions to documentation

Comments

@davidnuzik
Copy link
Contributor

davidnuzik commented Jul 23, 2020

K3s has limited SELinux support and we are working to improve this support. We expect to be at a point soon where we consider this complete. This issue is for tracking necessary changes when we consider SELinux to be stable and out of experimental state.. RKE2 documentation on SELinux will have precedence at this time, however we need to work on K3s docs on SELinux as soon as able after this.

More details to come. For now we're using this issue as a placeholder for this work that needs to be done.

@davidnuzik davidnuzik added [zube]: Next Up kind/documentation Improvements or additions to documentation labels Jul 23, 2020
@davidnuzik davidnuzik added this to the v1.19 - September milestone Jul 23, 2020
@brandond brandond changed the title [Documetnation] SELinux [Documentation] SELinux Jul 23, 2020
@davidnuzik
Copy link
Contributor Author

We need to document how to set up the YUM repo and the correct package to install for selinux policy/support. We need to explain that if you change the --data-dir you will need to manually re-label appropriately.

@ShylajaDevadiga
Copy link
Contributor

We also need to document enabling selinux explicitly from with v1.19.1-rc1+k3s1 onwards using flag --selinux=true or using config file with SELinux is set to Enforcing mode

@davidnuzik
Copy link
Contributor Author

I created #2247 to track the need to update docs to indicate the need for the --selinux flag. This issue may take a while longer before we can merge it in. We likely will stand by on this issue until a future v1.19.x release before we call SELinux stable.

I have updated the issue body of this issue to make it more clear this is for tracking selinux when it's out of experimental phase.

@catherineluse
Copy link
Contributor

@ShylajaDevadiga can you please provide an example snippet from the config file in which the SELinux option is enabled? I think it might help to have it in the docs.

@davidnuzik what do you mean, manually re-label the data dir?

@ShylajaDevadiga
Copy link
Contributor

@catherineluse To enable SELinux on k3s using config file

cat /etc/rancher/k3s/config.yaml
selinux: true

@catherineluse
Copy link
Contributor

I have added the config file snippet to the docs PR.

@davidnuzik
Copy link
Contributor Author

davidnuzik commented Sep 16, 2020

Regarding my statement

We need to document how to set up the YUM repo and the correct package to install for selinux policy/support. We need to explain that if you change the --data-dir you will need to manually re-label appropriately.

I filled this in during a meeting. I don't have context on it. @cjellick or @dweomer would need to explain.
cc: @catherineluse

@dweomer
Copy link
Contributor

dweomer commented Sep 16, 2020

Regarding my statement

We need to document how to set up the YUM repo and the correct package to install for selinux policy/support. We need to explain that if you change the --data-dir you will need to manually re-label appropriately.

I filled this in during a meeting. I don't have context on it. @cjellick or @dweomer would need to explain.
cc: @catherineluse

I would go so far as to state that running with a custom --data-dir under SELinux is not supported. Users should not opt for this unless they know what they are doing. Point them to the containers/container-selinux and rancher/k3s-selinux repositories and let them know they will most likely have to write and install their own custom policy.

@catherineluse
Copy link
Contributor

I've added the warning about the custom --data-dir to the SELinux docs PR. rancher/docs#2686 (comment)

@catherineluse
Copy link
Contributor

Closing this issue because rancher/docs#2686 was merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants