node-feature-discovery
descheduler
Our great sponsors
node-feature-discovery | descheduler | |
---|---|---|
8 | 27 | |
675 | 4,012 | |
3.3% | 2.3% | |
9.5 | 0.0 | |
6 days ago | about 19 hours ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
node-feature-discovery
-
Those running Kubernetes, what is in your core stack? And what "gem" can you not live without?
node-feature-discovery and descheduler
-
How can Intel quick sync be exposed to a pod?
Take a look at the NFD repo, they have instructions for deploying without helm — https://github.com/kubernetes-sigs/node-feature-discovery
This one https://github.com/kubernetes-sigs/node-feature-discovery is an official method of node discovery that puts certain labels on nodes, but I can't see the label "feature.node.kubernetes.io/custom-intel-gpu" being created. Am I missing where that label comes from? Is that where the helm version comes in from https://github.com/billimek/k8s-gitops/blob/master/kube-system/node-feature-discovery/node-feature-discovery.yaml does this one apply that label named?
When deploying without the helm chart, you need to define that in the ConfigMap. Looks like it’s here: https://github.com/kubernetes-sigs/node-feature-discovery/blob/master/nfd-daemonset-combined.yaml.template#L137-L229
descheduler
-
Any advice to rebalance and reallocation pod to spread among low usage nodes with existing deployment
The Kubernetes Sig's deschedule sounds like what you want, it can be configured to move pods around such that an over or under utilized node will get pods removed or added: https://github.com/kubernetes-sigs/descheduler
- What Wishlist Features Would You Like To See From K8s?
-
Schedule on Least Utilized Node
maybe descheduler can help? https://github.com/kubernetes-sigs/descheduler
-
I have 3 nodes. One of the nodes suddenly went down. How do I make the pods spread evenly to the other nodes?
Surprised this wasn't suggested yet, you can also use a software like the k8s Descheduler that executes periodically to rebalance your workloads across the existing nodes.
-
Leader Election In Kubernetes
Here an example of coordination api in Go https://github.com/kubernetes-sigs/descheduler/commit/3cbae5e72ba53447a609e6001755ff395e6eeceb https://github.com/kubernetes-sigs/descheduler/commit/0a52af9ab82a52fd8c864a81f4033736f11aab34
-
Kubernetes Cordon: How It Works and When to Use It
You might want to take a look at descheduler: https://github.com/kubernetes-sigs/descheduler
- How do I define a maximum life time for a pod?
-
How to make sure node autoscaler scales nodes down after deployment's replicaset are scaled down?
Having said that, it seems like that the "best practice" is using https://github.com/kubernetes-sigs/descheduler#lownodeutilization. What do you think?
There's no built in descheduler, but there is https://github.com/kubernetes-sigs/descheduler
What are some alternatives?
autoscaler - Autoscaling components for Kubernetes
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
intel-device-plugins-for-kubernetes - Collection of Intel device plugins for Kubernetes
pod-reaper - Rule based pod killing kubernetes controller
nfs-subdir-external-provisioner - Dynamic sub-dir volume provisioner on a remote NFS server.
cri-tools - CLI and validation tools for Kubelet Container Runtime Interface (CRI) .
aws-ebs-csi-driver - CSI driver for Amazon EBS https://aws.amazon.com/ebs/
kube-scheduler-simulator - The simulator for the Kubernetes scheduler
threaded-cron-task-engine - An multi-threaded cron/supervisord replacement which offers a bit more and is dead simple
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
smarter