Issue title: Kubernetes pod using all nodes vCPU
 Issue body: I have a 8vcpu/8core box worker node where we are running our nginx pods.  nginx pods are limited to use only 2cores max in
 
YAML definition i.e
request cpu:- 500m
limit cpu:- 2

nginx configuration as below,

worker_process 2
worker_cpu_affinity auto;

nginx is using only 1st 2 CPU00, CPU01 of the nodes with 2 child processes and rest of other 6 CPUs are idle.

whereas with below nginx configuration

worker_process auto
worker_cpu_affinity auto;

it is using all nodes CPU with that much number of processes.

Now query here is ,
1) Why nginx container is not limiting to use 2 cores which is defined in pod definition, why it is using all CPUs?
2) Why only first 2 CPU are utilized in former case where worker process are 2?
3) Can pod use all CPU cores of a node even after limiting it in YAML definition?




 Comments: 
 Comment 0: @Ankur7890: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
- `/sig <group-name>`
- `/wg <group-name>`
- `/committee <group-name>`

Please see the [group list](https://git.k8s.io/community/sig-list.md) for a listing of the SIGs, working groups, and committees available.


<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
</details>
 Comment 1: @Ankur7890: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the `triage/accepted` label and provide further guidance.

The `triage/accepted` label can be added by org members by writing `/triage accepted` in a comment.


<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
</details>
 Comment 2: please try the support channels:

 Comment 3: https://github.com/kubernetes/kubernetes/blob/master/SUPPORT.md
/close
 Comment 4: @neolit123: Closing this issue.

<details>

In response to [this](https://github.com/kubernetes/kubernetes/issues/95827#issuecomment-716180460):

>https://github.com/kubernetes/kubernetes/blob/master/SUPPORT.md
>/close


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
</details>
{'source': 'GithubIssues', 'repo_name_with_owner': 'kubernetes/kubernetes', 'issue_id': 728183199, 'repo_stars': 93454.0}