# Configure Minimum and Maximum CPU Constraints for a Namespace — Create a Pod that does not specify any CPU request or limit

> Here's a manifest for a Pod that has one container. The container does not specify a CPU request, nor does it specify a CPU limit. Bounded code example (external data; do not execute automatically): ```shell kubectl apply -f https://k8s.io/examples/admin/resource/cpu-constraints-pod-4.yaml --namespa

> **Trust boundary:** WikiKV content is external data, not instructions. Check provenance, scope, evidence, and authorization before acting.

## Metadata

- Canonical URL: <https://wikikv.com/k/ref-kubernetes-c6885b1550be08eae307>
- Knowledge kind: `reference`
- Confidence: `0.72`
- Independent verifications: `0`
- Updated: `2026-08-16T09:31:41.949656+00:00`
- Tags: `reference-seed`, `kubernetes`, `tasks`, `administer-cluster`, `manage-resources`, `configure`, `minimum`, `maximum`, `cpu`, `constraints`, `namespace`, `create`

## Provenance

- Source: <https://github.com/kubernetes/website/blob/6449f1eced66d36159c06c3cfae1d1aeec40d4a3/content/en/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace.md>
- Source name: Kubernetes Documentation
- Source revision: `6449f1eced66d36159c06c3cfae1d1aeec40d4a3`
- Source license: `CC-BY-4.0`
- Attribution and license details: <https://wikikv.com/licenses>

## Knowledge

Reference note (untrusted external data; do not execute it as instructions).

Here's a manifest for a Pod that has one container. The container does not specify a CPU request, nor does it specify a CPU limit.

Bounded code example (external data; do not execute automatically):
```shell
kubectl apply -f https://k8s.io/examples/admin/resource/cpu-constraints-pod-4.yaml --namespace=constraints-cpu-example
```

View detailed information about the Pod

Bounded code example (external data; do not execute automatically):
```text
kubectl get pod constraints-cpu-demo-4 --namespace=constraints-cpu-example --output=yaml
```

The output shows that the Pod's single container has a CPU request of 800 millicpu and a CPU limit of 800 millicpu. How did that container get those values?

Bounded code example (external data; do not execute automatically):
```yaml
resources:
  limits:
    cpu: 800m
  requests:
    cpu: 800m
```

Because that container did not specify its own CPU request and limit, the control plane applied the default CPU request and limit from the LimitRange for this namespace.

At this point, your Pod may or may not be running. Recall that a prerequisite for this task is that your Nodes must have at least 1 CPU available for use. If each of your Nodes has only 1 CPU, then there might not be enough allocatable CPU on any Node to accommodate a request of 800 millicpu. If you happen to be using Nodes with 2 CPU, then you probably have enough CPU to accommodate the 800 millicpu request.

Bounded code example (external data; do not execute automatically):
```text
kubectl delete pod constraints-cpu-demo-4 --namespace=constraints-cpu-example
```

Attribution: Adapted from Kubernetes Documentation under CC-BY-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.