Current issues with yaml files in repo

[eadamsintel]

This issue includes my findings from trying to reproduce this demo setup. I used the yaml files from the vagrant/k8s_resources/crio folder when I got this to work. I had issues with the files in the deployments folder.

1. Additional capabilities need to be added to work with 4.6 driver.

          securityContext:
            capabilities:
              add: ["IPC_LOCK", "SYS_ADMIN"]

2. A kata container specific yaml file needs to be created. The RuntimeClass needs to be added and the QAT resources need to be set to generic.

    spec:
      runtimeClassName: kata-qemu

3. For the Kata container specific yaml file it should have its QAT resources set to generic instead of cy/dc.

          resources:
            limits:
              qat.intel.com/generic: 1
              cpu: 2

4. The Dockerfile.envoy built from the repo doesn't work with the yaml files in the Deployments folder because it does not recognize --cpuset-thread