From 6a8d3f4c877ec22e61b7a4ee226fdce9e2a3de74 Mon Sep 17 00:00:00 2001 From: Raj Parmar <60355409+rajparmar1004@users.noreply.github.com> Date: Sun, 2 Feb 2025 20:46:00 +1030 Subject: [PATCH 1/3] Updated README.md Corrected yml definition in readme.md file for LimitRange --- .../16-02-Namespaces-LimitRange-default/README.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md b/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md index d6c8527b..1f34c8e5 100644 --- a/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md +++ b/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md @@ -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 From ca10c67f6fa28be475c6601f94e269ac09c9b349 Mon Sep 17 00:00:00 2001 From: Raj Parmar <60355409+rajparmar1004@users.noreply.github.com> Date: Sun, 2 Feb 2025 20:47:18 +1030 Subject: [PATCH 2/3] Update README.md Corrected yml definition of LimitRange in readme.md file --- .../16-02-Namespaces-LimitRange-default/README.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md b/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md index 1f34c8e5..e2fda3e1 100644 --- a/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md +++ b/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md @@ -31,12 +31,7 @@ metadata: ## Step-02: Create LimitRange manifest - 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: Namespace -metadata: - name: dev3 ---- +```yaml apiVersion: v1 kind: LimitRange metadata: From 7c101125edb63b7423a4ecbf0bc4382a24807651 Mon Sep 17 00:00:00 2001 From: Raj Parmar <60355409+rajparmar1004@users.noreply.github.com> Date: Sun, 2 Feb 2025 20:59:20 +1030 Subject: [PATCH 3/3] Update README.md corrected comments --- .../16-02-Namespaces-LimitRange-default/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md b/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md index e2fda3e1..7cd44648 100644 --- a/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md +++ b/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md @@ -40,7 +40,7 @@ metadata: spec: limits: - default: - cpu: "500m" # If not specified default limit is 1 vCPU per container + cpu: "500m" # If not specified default limit is 0.5 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. defaultRequest: cpu: "300m" # If not specified default it will take from whatever specified in limits.default.cpu