K8s: 在Pod里面对容器进行配额管理和相关原理

本文主要是介绍K8s: 在Pod里面对容器进行配额管理和相关原理，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

Pod里面对容器进行配额管理

在生产环境中，内存占用通常很大，如果里面有死循环，会导致内存和cpu过大导致影响其他pod运行资源
需要让资源在受控的环境下运行，一般都是加上 resources limits 的配置才能达到最佳实践
默认cpu是0.5个cpu, 一般定义的时候参数是最高的门槛，不会超过这个设置
创建一个命名空间，以便将本练习中创建的资源与集群的其余部分资源隔离
- $ kubectl create namespace cpu-stress

创建 cpu-limit.yaml

apiVersion: v1
kind: Pod
metadata:name: cpu-stress-demonamespace: cpu-stresslabels:name: cpu-stress-demo
spec:containers:- name: nginx-stressimage: registry.cn-beijing.aliyuncs.com/qingfeng666/stressargs:- -cpus- "2"  # 指定使用2个CPU核心进行压力测试resources:limits:cpu: "1"  # 设置CPU上限为1个核心requests:cpu: "0.5"  # 设置CPU请求为0.5个核心（可选，根据集群策略设置）restartPolicy: Never  # 设置重启策略为Never，因为这是一个一次性任务

$ kubectl create -f cpu-limit.yaml
```
pod/cpu-stress-demo created
```

$ kubectl get po -n cpu-stress -w

NAME              READY   STATUS    RESTARTS   AGE
cpu-stress-demo   1/1     Running   0          7s

$ kubectl get po cpu-stress-demo -n cpu-stress -o yaml

apiVersion: v1
items:
- apiVersion: v1kind: Podmetadata:creationTimestamp: "2024-04-18T22:34:13Z"labels:name: cpu-stress-demoname: cpu-stress-demonamespace: cpu-stressresourceVersion: "81301"uid: f423a147-4bac-4f82-a791-0e851d67366cspec:containers:- args:- -cpus- "2"image: registry.cn-beijing.aliyuncs.com/qingfeng666/stressimagePullPolicy: Alwaysname: nginx-stressresources:limits:cpu: "1"requests:cpu: 500mterminationMessagePath: /dev/termination-logterminationMessagePolicy: FilevolumeMounts:- mountPath: /var/run/secrets/kubernetes.io/serviceaccountname: kube-api-access-mg68jreadOnly: truednsPolicy: ClusterFirstenableServiceLinks: truenodeName: node2.k8spreemptionPolicy: PreemptLowerPrioritypriority: 0restartPolicy: NeverschedulerName: default-schedulersecurityContext: {}serviceAccount: defaultserviceAccountName: defaultterminationGracePeriodSeconds: 30tolerations:- effect: NoExecutekey: node.kubernetes.io/not-readyoperator: ExiststolerationSeconds: 300- effect: NoExecutekey: node.kubernetes.io/unreachableoperator: ExiststolerationSeconds: 300volumes:- name: kube-api-access-mg68jprojected:defaultMode: 420sources:- serviceAccountToken:expirationSeconds: 3607path: token- configMap:items:- key: ca.crtpath: ca.crtname: kube-root-ca.crt- downwardAPI:items:- fieldRef:apiVersion: v1fieldPath: metadata.namespacepath: namespacestatus:conditions:- lastProbeTime: nulllastTransitionTime: "2024-04-18T22:34:13Z"status: "True"type: Initialized- lastProbeTime: nulllastTransitionTime: "2024-04-18T22:34:16Z"status: "True"type: Ready- lastProbeTime: nulllastTransitionTime: "2024-04-18T22:34:16Z"status: "True"type: ContainersReady- lastProbeTime: nulllastTransitionTime: "2024-04-18T22:34:13Z"status: "True"type: PodScheduledcontainerStatuses:- containerID: docker://12668f59353306dda08a395bf7dd36c0eae699b0ed1350ec96b8ffc3705b6a5eimage: registry.cn-beijing.aliyuncs.com/qingfeng666/stress:latestimageID: docker-pullable://registry.cn-beijing.aliyuncs.com/qingfeng666/stress@sha256:155d7266cb7ed6fecd34b2e4f8a25c2b21eb77723658fb4ab2db630d41118c7dlastState: {}name: nginx-stressready: truerestartCount: 0started: truestate:running:startedAt: "2024-04-18T22:34:15Z"hostIP: 10.211.55.12phase: RunningpodIP: 10.244.2.12podIPs:- ip: 10.244.2.12qosClass: BurstablestartTime: "2024-04-18T22:34:13Z"
kind: List
metadata:resourceVersion: ""selfLink: ""