Skip to content

Conversation

@loktev-d
Copy link
Contributor

@loktev-d loktev-d commented Nov 6, 2025

Description

Change KubeVirt SELinux launcher type from spc_t to container_kvm_t to comply with Deckhouse baseline pod security policies (D8SeLinux).

Why do we need it, and what problem does it solve?

What is the expected result?

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: kubevirt
type: fix
summary: use container_kvm_t SELinux type for KubeVirt pods for security compliance

Signed-off-by: Daniil Loktev <[email protected]>
@loktev-d loktev-d requested review from Isteb4k and fl64 as code owners November 6, 2025 18:14
@loktev-d loktev-d changed the title fix(kubevirt): use container_kvm_t SELinux type for KubeVirt pods for security compliance fix(kubevirt): use container_kvm_t SELinux type for hp pods for security compliance Nov 6, 2025
Signed-off-by: Daniil Loktev <[email protected]>
@loktev-d loktev-d marked this pull request as draft November 7, 2025 06:50
@loktev-d loktev-d added the e2e/run Run e2e test on cluster of PR author label Nov 7, 2025
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Nov 7, 2025

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants