search

kubernetes-sigs / security-profiles-operator

The Kubernetes Security Profiles Operator
Apache License 2.0
716 stars 106 forks source link

The Operator creates SeccompProfile even though in the ProfileRecording kind=SelinuxProfile #2463

Open nev888 opened 2 months ago

nev888 commented 2 months ago

spod-zjn2z_security-profiles-operator.log security-profiles-operator-webhook.log security-profiles-operator.log

What happened:

I'm trying to create SelinuxProfile using ProfileRecordings however SeccompProfile is created instead.

What you expected to happen:

I expected SelinuxProfile to be created.

How to reproduce it (as minimally and precisely as possible):

installation followed: https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/installation-usage.md

profile recording followed: https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/installation-usage.md#record-profiles-from-workloads-with-profilerecordings

restricted it to single namespace: https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/installation-usage.md#restricting-to-a-single-namespace-with-upstream-deployment-manifests

Environment:

Openshift environment

nev888 commented 2 months ago

profilerecording.txt pod2.txt

ccojocar commented 1 month ago

Did you change the kind in ProfileRecoding to SelinuxProfile ? It supports only the log recorder for Selinux. Could you share the ProfileRecording CR that you are creating?

Also there are some more guidelines in https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/installation-usage.md#create-a-selinux-profile.

nev888 commented 1 month ago

Yes, the kind is set to SelinuxProfile and the recording is log. The profile is also attached profilerecoding.txt