Rename SupportsSELinux to SELinuxRelabel

[jsafrane]

What type of PR is this?

/kind cleanup
/sig storage

What this PR does / why we need it:

The field SupportsSELinux in fact says that the container runtime should relabel a volume when running a container with it, it does not say that the volume supports SELinux. For example, NFS can support SELinux, but we don't want NFS volumes relabeled, because they can be shared among several Pods.

This is just internal cleanup, nobody should use the Attributes struct outside of k/k.

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

@jsafrane: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jsafrane]

/priority backlog

[jsafrane]

/retest
data race in k8s.io/apiserver/pkg/server/filters ?!

[gnufied]

/retest

[gnufied]

The failures here looks unrelated.

/lgtm

[jsafrane]

/assign @sjenning @mrunalp
for approval - there is a small change in kubelet_pods.go and IMO it looks better now.

[jsafrane]

/sig node

[sjenning]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, sjenning

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/kubelet/OWNERS [sjenning]
• pkg/volume/OWNERS [jsafrane]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-ci-robot]

@jsafrane: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-e2e-capz-azure-disk	525b8e5	link	false	/test pull-kubernetes-e2e-capz-azure-disk
pull-kubernetes-e2e-gce-iscsi-serial	525b8e5	link	false	/test pull-kubernetes-e2e-gce-iscsi-serial
pull-kubernetes-e2e-capz-azure-file	525b8e5	link	false	/test pull-kubernetes-e2e-capz-azure-file
pull-kubernetes-e2e-capz-azure-disk-vmss	525b8e5	link	false	/test pull-kubernetes-e2e-capz-azure-disk-vmss
pull-kubernetes-e2e-gce-iscsi	525b8e5	link	false	/test pull-kubernetes-e2e-gce-iscsi
pull-kubernetes-e2e-capz-azure-file-vmss	525b8e5	link	false	/test pull-kubernetes-e2e-capz-azure-file-vmss

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[pacoxu]

/skip
/test pull-kubernetes-unit
for TestStart flake