Doc task

Section to update: Resource requirements for OpenShift sandboxed containers

Original bug:
Description of problem:

Missing info in the section on "Resource requirements for peer-pods in OpenShift sandboxed containers"

Version-Release number of selected component (if applicable):

1.4.0

How reproducible:

Steps to Reproduce:

1.
2.
3.

Actual results:

Expected results:

Additional info:

Following is the original text:

"The total capacity of the peer-pod VMs running in the cloud is defined as Kubernetes Node extended resources. This enables the Kubernetes scheduler to handle capacity tracking and accounting. The extended resource is named kata.peerpods.io/vm, and defines the maximum number of peer pods that you can create in the cluster.

A mutating webhook adds the extended resource kata.peerpods.io/vm to the pod specification. It also removes any resource-specific entries from the pod specification, if present. This enables the Kubernetes scheduler to account for these extended resources, ensuring the peer-pod is only scheduled when resources are available."

Suggested modification:

"The total capacity of the peer-pods per worker node is defined as Kubernetes Node extended resources. This per-node limit and set as part of the `limit` attribute in the `peerpodConfig` custom resource named `peerpodconfig-openshift` in the OpenShift sandboxed containers operator namespace (`openshift-sandboxed-containers-operator`). Following is a snippet of the default values:

```

  spec:
    cloudSecretName: peer-pods-secret
    configMapName: peer-pods-cm
    limit: "10"
    nodeSelector:
      node-role.kubernetes.io/kata-oc: ""

```

The default per-node limit is 10, and you can modify the `limit` attribute of the custom resource as required for your environment.

The extended resource is named kata.peerpods.io/vm, and enables the Kubernetes scheduler to handle capacity tracking and accounting.

A mutating webhook adds the extended resource kata.peerpods.io/vm to the pod specification. It also removes any resource-specific entries from the pod specification, if present. This enables the Kubernetes scheduler to account for these extended resources, ensuring the peer-pod is only scheduled within the limit set in the `peerpodConfig` custom resource."

Further, please remove this line:

"The webhook adds an annotation to the pod that specifies the instance type that is used when the VM is created in the cloud environment."