我有一個沙盒Kubernetes集羣,其中我在晚上關閉了所有豆莢,因此它可以通過cluster-autoscaler
加載項縮小比例。強制一些豆莢安排在同一個節點
問題是,它幾乎總是保持主加2節點運行。
展望cluster-autoscaler
日誌,我看這個問題似乎是這樣的:
Fast evaluation: node ip-172-16-38-51.ec2.internal cannot be removed: non-deamons set, non-mirrored, kube-system pod present: dns-controller-3586597043-531v5
Fast evaluation: node ip-172-16-49-207.ec2.internal cannot be removed: non-deamons set, non-mirrored, kube-system pod present: heapster-564189836-3h2ts
Fast evaluation: node ip-172-16-49-207.ec2.internal cannot be removed: non-deamons set, non-mirrored, kube-system pod present: kube-dns-1321724180-c0rjr
Fast evaluation: node ip-172-16-49-207.ec2.internal cannot be removed: non-deamons set, non-mirrored, kube-system pod present: kube-dns-autoscaler-265231812-dv17j
Fast evaluation: node ip-172-16-49-207.ec2.internal cannot be removed: non-deamons set, non-mirrored, kube-system pod present: kubernetes-dashboard-2396447444-6bwtq
Fast evaluation: node ip-172-16-49-207.ec2.internal cannot be removed: non-deamons set, non-mirrored, kube-system pod present: monitoring-influxdb-grafana-v4-50v9d
Fast evaluation: node ip-172-16-51-146.ec2.internal cannot be removed: non-deamons set, non-mirrored, kube-system pod present: cluster-autoscaler-776613730-kqgk2
因爲這些豆莢蔓延,集羣自動配置器最終保持2個或多個節點工作,即使是沒有在運行默認名稱空間...
有沒有強制或誘導Kubernetes將所有這些豆莢一起排列的方法?
這個想法是讓集羣只在主節點和一個節點上運行。如果沒有,我想在AutoScale Group
上增加一個Scheduled Action
,所以它將被強制運行在同一個節點上。
這似乎是目前爲止最好的選擇。將研究這一點。謝謝! – caarlos0