Adding SELinux Documentation #900
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
NET:[VulnCheck / Analysis (pull_request) ] fix is on #901 |
ravindk89
reviewed
Apr 13, 2024
|
PTAL @cniackz |
cniackz
force-pushed
the
selinux-documentation-apr13
branch
2 times, most recently
from
62e070b to
c48433d
Compare
ravindk89
previously approved these changes
Jul 26, 2024
cniackz
force-pushed
the
selinux-documentation-apr13
branch
from
2d6baf8 to
4f32cb7
Compare
Comment on lines
+10
to
+13
|
|
||
| ## SELinux in OpenShift: | ||
|
|
||
| If you encounter the `relabel failed` error after executing the `suspend` or `resume` commands, you should set `spc_t` at Pod's level or Container's level, for example: |
There was a problem hiding this comment.
I have modified the text more appropriately as OpenShift < 4.12 are deprecated and added a complete example.
Suggested change
| ## SELinux in OpenShift: | |
| If you encounter the `relabel failed` error after executing the `suspend` or `resume` commands, you should set `spc_t` at Pod's level or Container's level, for example: | |
| ## SELinux in OpenShift | |
| In a SELinux enabled system, pod may fail to start due to `relabel failed` error on suspended volume. As the suspended volumes are read-only, Kublet tries to do SELinux relabeling by `lsetxattr` system call to write extended attributes. This issue is fixable by adding `spec.securityContext.seLinuxOptions.type: spc_t` at pod level or container level along with appropriate Security Context Constraints (SCCs) in place. A complete detail is available at https://access.redhat.com/solutions/7025337. The following example shows how to set `spc_t` SELinux settings at pod level: |
Comment on lines
+16
to
+20
| kind: Pod | ||
| spec: | ||
| securityContext: | ||
| seLinuxOptions: | ||
| type: "spc_t" # This applies to all containers unless overridden |
There was a problem hiding this comment.
Suggested change
| kind: Pod | |
| spec: | |
| securityContext: | |
| seLinuxOptions: | |
| type: "spc_t" # This applies to all containers unless overridden | |
| apiVersion: v1 | |
| kind: Pod | |
| metadata: | |
| name: sleep-pod | |
| spec: | |
| securityContext: | |
| seLinuxOptions: | |
| type: "spc_t" # Setting to fix the issue | |
| volumes: | |
| - name: sleep-volume | |
| persistentVolumeClaim: | |
| claimName: sleep-pvc | |
| containers: | |
| - name: sleep-container | |
| image: example.org/test/sleep:v0.0.1 | |
| volumeMounts: | |
| - mountPath: "/mnt" | |
| name: sleep-volume |
Comment on lines
+22
to
+25
|
|
||
| Ensure that the appropriate Security Context Constraints (SCCs) are in place, as illustrated in the following link: https://access.redhat.com/solutions/7025337. | ||
|
|
||
| Additionally, this issue has been observed in OpenShift version 4.12 and later. Pods that use suspended drives or volumes may fail due to the kubelet attempting to perform SELinux relabeling. This happens because the `lsetxattr` system call fails on a read-only filesystem. The problem can affect any pod that consumes a suspended volume, not just MinIO Tenant pods. |
There was a problem hiding this comment.
Suggested change
| Ensure that the appropriate Security Context Constraints (SCCs) are in place, as illustrated in the following link: https://access.redhat.com/solutions/7025337. | |
| Additionally, this issue has been observed in OpenShift version 4.12 and later. Pods that use suspended drives or volumes may fail due to the kubelet attempting to perform SELinux relabeling. This happens because the `lsetxattr` system call fails on a read-only filesystem. The problem can affect any pod that consumes a suspended volume, not just MinIO Tenant pods. |
|
PTAL @cniackz |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective:
When
resumingorsuspendinga drive in anOpenShiftcluster, we may encounter arelabelissue. Various solutions exist for this problem, but here I am documenting the one we believe to be the best approach.