Auto-select selinuxd image based on nodeInfo.OSImage

[jhrozek]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Cluster nodes might be upgraded between major OS releases where the
libselinux major version is incompatible. This means that the selinuxd
image must be based on images matching the OS release and the libselinux
major version.

But SPO must also be able to select the images based on what OS are the
cluster nodes running.

To implement that, this patch adds a new key to the
security-profiles-operator-profile configmap that maps regexes matching
nodeInfo.OSImage to selinuxd images. The operator then selects the right
selinuxd image, falling back to using the RELATED_IMAGE_SELINUXD environment
variable.

Which issue(s) this PR fixes:

Fixes #1576

Does this PR have test?

some unit tests

Special notes for your reviewer:

I'll hold this patch before I can install a RHEL-9 based cluster - I've
been having issues with that. But I wanted to get some early feedback.

Does this PR introduce a user-facing change?

SPO now autoselects the appropriate selinuxd image based on mapping in the
security-profiles-operator-profile. If none of the entries match, SPO falls back
to the image provided by `RELATED_IMAGE_SELINUXD`.

[jhrozek]

/hold
for RHEL-9 testing (the installer is having issues it seems)

[jhrozek]

In case someone is going wtf is this change..because I changed the spo role by adding a new permission, this overlay would have removed a permission at the wrong index:

diff --git a/deploy/webhook-operator.yaml b/deploy/webhook-operator.yaml
index cad32631..ed2ae5f8 100644
--- a/deploy/webhook-operator.yaml
+++ b/deploy/webhook-operator.yaml
@@ -2171,9 +2171,9 @@ rules:
   - list
   - watch
 - apiGroups:
-  - ""
+  - admissionregistration.k8s.io
   resources:
-  - services
+  - mutatingwebhookconfigurations
   verbs:
   - create

[jhrozek]

/hold cancel
I finally got hold of a RHEL-9 cluster and the right image was selected and a smoke test passed (a SELinux policy was installed)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhrozek, saschagrunert

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:

• OWNERS [jhrozek,saschagrunert]

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