Docker Kubernetes监控----kubernetes容器资源限制和容器资源监控

1. kubernetes容器资源限制

• Kubernetes采用request和limit两种限制类型来对资源进行分配。
  request(资源需求)：即运行Pod的节点必须满足运行Pod的最基本需求才能运行Pod。
  limit(资源限额)：即运行Pod期间，可能内存使用量会增加，那最多能使用多少内存，这就是资源限额。

• 资源类型:
  CPU 的单位是核心数，内存的单位是字节。
  一个容器申请0.5个CPU，就相当于申请1个CPU的一半，你也可以加个后缀m 表示千分之一的概念。比如说100m的CPU，100豪的CPU和0.1个CPU都是一样的。
  内存单位：
  K、M、G、T、P、E #通常是以1000为换算标准的。
  Ki、Mi、Gi、Ti、Pi、Ei #通常是以1024为换算标准的。

1.1 内存限制

[root@server1 docker]# docker search stress
[root@server1 harbor]# docker pull progrium/stress
[root@server1 harbor]# docker tag progrium/stress:latest reg.westos.org/library/stress:latest
[root@server1 harbor]# docker push reg.westos.org/library/stress:latest

[root@server2 ~]# mkdir limit/
[root@server2 ~]# cd limit/
[root@server2 limit]# vim pod.yaml 
apiVersion: v1
kind: Pod
metadata:
  name: memory-demo
spec:
  containers:
  - name: memory-demo
    image: stress
    args:
    - --vm
    - "1"
    - --vm-bytes
    - 200M
    resources:
      requests:
        memory: 50Mi
      limits:
        memory: 100Mi   ##限制200M 

[root@server2 limit]# kubectl apply -f pod.yaml 
pod/memory-demo created
[root@server2 limit]# kubectl get pod 
NAME          READY   STATUS             RESTARTS   AGE
memory-demo   0/1     CrashLoopBackOff   2          42s
[root@server2 limit]# kubectl get pod -o wide
NAME          READY   STATUS             RESTARTS   AGE   IP             NODE      NOMINATED NODE   READINESS GATES
memory-demo   0/1     CrashLoopBackOff   3          53s   10.244.22.40   server4   <none>           <none>
#如果容器超过其内存限制，则会被终止。如果可重新启动，则与所有其他类型的运行时故障一样，kubelet 将重新启动它。
#如果一个容器超过其内存请求，那么当节点内存不足时，它的 Pod 可能被逐出。

[root@server2 limit]# kubectl delete -f pod.yaml 
pod "memory-demo" deleted
[root@server2 limit]# vim pod.yaml 
[root@server2 limit]# kubectl apply -f pod.yaml 
pod/memory-demo created
[root@server2 limit]# kubectl get pod 
NAME          READY   STATUS    RESTARTS   AGE
memory-demo   1/1     Running   0          29s
[root@server2 limit]# kubectl get pod -o wide
NAME          READY   STATUS    RESTARTS   AGE   IP             NODE      NOMINATED NODE   READINESS GATES
memory-demo   1/1     Running   0          35s   10.244.22.41   server4   <none>           <none>

1.2 CPU限制

调度失败是因为申请的CPU资源超出集群节点所能提供的资源,但CPU 使用率过高，不会被杀死

[root@server2 limit]# kubectl delete -f pod.yaml 
pod "memory-demo" deleted
[root@server2 limit]# vim pod.yaml 
apiVersion: v1
kind: Pod
metadata:
  name: cpu-demo
spec:
  containers:
  - name: cpu-demo
    image: stress
    resources:
      limits:
        cpu: "10"
      requests:
        cpu: "5"
    args:
    - -c
    - "2"
[root@server2 limit]# kubectl get pod
NAME       READY   STATUS    RESTARTS   AGE
cpu-demo   0/1     Pending   0          22s
[root@server2 limit]# kubectl delete -f pod.yaml 
pod "cpu-demo" deleted
[root@server2 limit]# vim pod.yaml 
      limits:
        cpu: "10"  ##上限太高
      requests:
        cpu: "2"
[root@server2 limit]# kubectl apply -f pod.yaml 
pod/cpu-demo created
[root@server2 limit]# kubectl get pod
NAME       READY   STATUS    RESTARTS   AGE
cpu-demo   0/1     Pending   0          14s

[root@server2 limit]# kubectl delete -f pod.yaml 
pod "cpu-demo" deleted
[root@server2 limit]# vim pod.yaml 
[root@server2 limit]# kubectl apply -f pod.yaml 
pod/cpu-demo created
[root@server2 limit]# kubectl get pod
NAME       READY   STATUS    RESTARTS   AGE
cpu-demo   1/1     Running   0          13s
[root@server2 limit]# kubectl delete -f pod.yaml 
pod "cpu-demo" deleted

1.3 为namespace设置资源限制

root@server2 limit]# vim ns-limit.yaml

[root@server2 limit]# kubectl apply -f ns-limit.yaml 
limitrange/limitrange-demo created
[root@server2 limit]# kubectl get limitranges 
NAME              CREATED AT
limitrange-demo   2021-03-25T08:38:04Z
[root@server2 limit]# kubectl describe limitranges limitrange-demo 
Name:       limitrange-demo
Namespace:  default
Type        Resource  Min    Max  Default Request  Default Limit  Max Limit/Request Ratio
----        --------  ---    ---  ---------------  -------------  -----------------------
Container   cpu       100m   1    100m             500m           -
Container   memory    100Mi  1Gi  256Mi            512Mi 

[root@server2 limit]# vim pod.yaml 
apiVersion: v1
kind: Pod
metadata:
  name: cpu-demo
spec:
  containers:
  - name: cpu-demo
    image: nginx
[root@server2 limit]# kubectl apply -f pod.yaml 
pod/cpu-demo created
[root@server2 limit]# kubectl get pod
NAME       READY   STATUS    RESTARTS   AGE
cpu-demo   1/1     Running   0          19s
[root@server2 limit]# kubectl describe pod cpu-demo  ##查看默认分配的资源限制
[root@server2 limit]# kubectl describe limitranges         -

为namespace设置资源限制

[root@server2 limit]# kubectl delete -f pod.yaml 
pod "cpu-demo" deleted
[root@server2 limit]# vim pod.yaml 
apiVersion: v1
kind: Pod
metadata:
  name: cpu-demo
spec:
  containers:
  - name: cpu-demo
    image: nginx
    resources:
      limits:
        cpu: "2"
      requests:
        cpu: "0.1"
[root@server2 limit]# kubectl apply -f pod.yaml 
Error from server (Forbidden): error when creating "pod.yaml": pods "cpu-demo" is forbidden: maximum cpu usage per Container is 1, but limit is 2

[root@server2 limit]# kubectl delete -f pod.yaml 
[root@server2 limit]# vim pod.yaml 
    resources:
      limits:
        cpu: "1"
        memory: "2Gi"
      requests:
        cpu: "0.1"    
[root@server2 limit]# kubectl apply -f pod.yaml 
Error from server (Forbidden): error when creating "pod.yaml"