1. Proposed title of this feature request
Enable oc port-forward for a pod that uses kata runtimeClass

2. What is the nature and description of the request?
The oc port-forward to a pod that uses kata runtimeClass is not possible. (non-kata works fine)

Steps to reproduce
1. Run a web server
$ python -m http.server
 
2. On another terminal:
$ oc -n mnamespace port-forward python-kata-xxxxxxxxx-xxxxx 8000
$ curl 127.0.0.1:8000

Expected result
It is possible to access the port that is forwarded via oc port-forward to a pod that uses kata runtimeClass. If the pod is not using Kata containers, we get an HTML directory listing back.

Environment:
$ oc get clusterversion
4.15.11

KataConfig is the standard one:

spec:
  checkNodeEligibility: false
  enablePeerPods: false
  kataConfigPoolSelector:
    matchLabels:
      kata: 'true'
  loglevel: info

3. Why does the customer need this?
   Without this feature, it is harder to debug pods using kata containers.
  
4. List any affected packages or components.
   Openshift sandboxed containers (KATA Containers)

Additional Info:
This was first logged as a bug but was considered a feather in KATA-3202.

Upstream issues:

• Add kubernetes CRI Port-Forward support #1693
  https://github.com/kata-containers/kata-containers/issues/1693 

• Add Portforward Support #5979
  https://github.com/kata-containers/kata-containers/pull/5979