Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I also looked into the scheduler plugin NodeResourcesAllocatable with the „Least“ option. This seems to be the solution to our problem, but I don‘t get how this can be applied. Our cluster is running on in-house nodes, however it is managed via Mirantis, so I don‘t know whether we could actually apply scheduler configurations.
maybe descheduler can help? https://github.com/kubernetes-sigs/descheduler
If you are using the docker socket just for building container images, you might want to look into kaniko. It doesn't use docker to build images. If you use the socket also for starting containers (we are actually doing that in our CI pipelines), you could think about limiting the pods Kubernetes schedules on a node (you can change the default of 110 using the kubelet config file).