官方文檔:https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/node
Pod和Container的資源請求和限制:
• spec.containers[].resources.limits.cpu
• spec.containers[].resources.limits.memory
• spec.containers[].resources.requests.cpu
• spec.containers[].resources.requests.memorymysql
一、建立測試實例
vim pod.yamlnginx
apiVersion: v1 kind: Pod metadata: name: frontend spec: containers: - name: db image: mysql env: - name: MYSQL_ROOT_PASSWORD value: "password" resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" - name: wp image: wordpress resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m"
二、查看pod建立實例sql
NAME READY STATUS RESTARTS AGE
frontend 2/2 Running 1 63s
三、查看pod詳情,找到分配到的Nodevim
kubectl describe pod frontend
四、Node 跑的Pod資源利用率api
kubectl describe nodes 192.168.1.111frontend
..... Kube-Proxy Version: v1.12.1 Non-terminated Pods: (4 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits --------- ---- ------------ ---------- --------------- ------------- default frontend 500m (12%) 1 (25%) 128Mi (9%) 256Mi (18%) default nginx-7b67cfbf9f-p8d69 0 (0%) 0 (0%) 0 (0%) 0 (0%) default nginx-7b67cfbf9f-xlvnz 0 (0%) 0 (0%) 0 (0%) 0 (0%) default nginx-deployment-d55b94fd-rpsgm 0 (0%) 0 (0%) 0 (0%) 0 (0%) Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) # 限制說明 Resource Requests Limits -------- -------- ------ cpu 500m (12%) 1 (25%) memory 128Mi (9%) 256Mi (18%) attachable-volumes-azure-disk 0 0 Events: <none>
注:limits是對資源的總限制、requests是最低分配的資源。requests通常要比limits要小一些。ide
注:250m/單核CPU的白分之25/0.25wordpress
注:資源限制 cpu能夠直接設置爲數字 「1」爲1核「2」爲2核。測試