Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Updated README.md
Corrected yml definition in readme.md file for LimitRange
  • Loading branch information
rajparmar1004 authored Feb 2, 2025
commit 6a8d3f4c877ec22e61b7a4ee226fdce9e2a3de74
Original file line number Diff line number Diff line change
Expand Up @@ -33,19 +33,24 @@ metadata:
- Instead of specifying `resources like cpu and memory` in every container spec of a pod defintion, we can provide the default CPU & Memory for all containers in a namespace using `LimitRange`
```yaml
apiVersion: v1
kind: ResourceQuota
kind: Namespace
metadata:
name: dev3
---
apiVersion: v1
kind: LimitRange
metadata:
name: ns-resource-quota
name: default-cpu-mem-limit-range
namespace: dev3
spec:
limits:
- default:
cpu: "500m" # If not specified default limit is 1 vCPU per container
memory: "512Mi" # If not specified the Container's memory limit is set to 512Mi, which is the default memory limit for the namespace.
cpu: "500m" # If not specified default limit is 1 vCPU per container
defaultRequest:
cpu: "300m" # If not specified default it will take from whatever specified in limits.default.cpu
memory: "256Mi" # If not specified default it will take from whatever specified in limits.default.memory
cpu: "300m" # If not specified default it will take from whatever specified in limits.default.cpu
type: Container
type: Container
```

## Step-03: Update all k8s manifest with namespace
Expand Down