Description

<What were you trying to do that didn't work?>

I created a kataconfig which should start a deamonset for the kata-monitor process.  The pods do not start.

Steps to reproduce

<What actions did you take to hit the bug?>
1.
2.
3.

Expected result

<What did you expect to happen?>

Kata monitor pods start

Actual result

<What actually happened?>

They do not start.  The logs have:

/usr/bin/kata-monitor: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /usr/bin/kata-monitor)

Impact

<How badly does this interfere with using the software?>

No metrics for kata pods

Env

<Where was the bug found, i.e. OCP build, operator build, kata-containers build, cluster infra, test case id>

OCP 4.13 nightly

OSC 1.4.0-38

KATA_MONITOR_IMAGE=registry.redhat.io/openshift-sandboxed-containers/osc-monitor-rhel9@sha256:e8b4fc692b6cee1eaeb4d81fcff8b1db16c66f1023367c2be3a9d946a1680776  (which is 1.4.0-24)

Additional helpful info

<logs, screenshot, doc links, etc.>