samples: Add a pod manifest for uvm test container

[Ankita13-code]

Merge Checklist

• Followed patch format from upstream recommendation: https://github.com/kata-containers/community/blob/main/CONTRIBUTING.md#patch-format
  • Included a single commit in a given PR - at least unless there are related commits and each makes sense as a change on its own.
• Aware about the PR to be merged using "create a merge commit" rather than "squash and merge" (or similar)
• The upstream/missing label (or upstream/not-needed) has been set on the PR.

Summary

Test Methodology

[ms-mahuber]

Does it need to run privileged?

[Ankita13-code]

When I tested it manually, sudo was always needed. So I thought probably it would be required here as well.

[ms-mahuber]

Let's please clarify which test exactly requires this and only enable when needed. We will want this if we run this container on the host as a runc container so that we can e.g. detect if /dev/mshv is present

[ms-mahuber]

This won't succeed without memory or cpu limits

[Ankita13-code]

@ms-mahuber What is meant by memory and cpu limits here? Is it something we need to set up explicitly while creating the VMs?

[ms-mahuber]

in the pod manifest resources->limits->cpu|memory

[ms-mahuber]

We internally also run this pod YAML against the vanilla handler where the observed memory values may diverge between kata and kata-cc - let's talk.