descheduler
Reloader
descheduler | Reloader | |
---|---|---|
27 | 34 | |
4,072 | 6,769 | |
1.1% | 1.9% | |
0.0 | 9.2 | |
about 7 hours ago | 3 days 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.
descheduler
- Any advice to rebalance and reallocation pod to spread among low usage nodes with existing deployment
- 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
-
Ask HN: Who else is working/on call over Christmas?
This is something a (now former) colleague of mine pointed out: that the kubernetes descheduler can enforce a maximum lifetime[0] that sort of forces continual reboots. So if your system cannot tolerate running for a long time continously, this is one method to gracefully restart long running pods.
[0]: https://github.com/kubernetes-sigs/descheduler#podlifetime
- Cluster auto heal?
-
K8S Operators - How do you reserve on every node resources for system daemonsets ?
no it does not... thats why tools like https://github.com/kubernetes-sigs/descheduler exist..
- Kubernetes Descheduler
-
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
Reloader
-
How are people managing env vars for Static Applications?
You can combine this approach with something like https://github.com/stakater/Reloader to automatically restart pods when a certain secret value changes. So if your static code needs to be rebuilt when certain values change, you can use an init container to run the build on startup.
-
Containers are crashing due to memory exhaustion caused by secret rotation every minute.
This is not a cron job? I'm not sure if it helps, but you can have pods do a rolling restart on secret updates: https://github.com/stakater/Reloader that would clear the resources each run, but I'm not entirely clear on what you're looking to achieve.
-
True Secrets Auto Rotation with ESO and Vault
If you use secrets as Environment Variables you will need to use something to make workloads get the new credentials, if they just loose connection. You can use the Reloader project for that.
-
Automating Configuration Updates in Kubernetes with Reloader
Reloader is designed to simplify the process of updating application configurations in Kubernetes. It monitors ConfigMaps and Secrets for changes and triggers rolling upgrades for associated resources such as Deployments, StatefulSets, DaemonSets, and more. Reloader eliminates the need for manual intervention and reduces the risk of errors during the configuration update process.
-
How to start a Go project in 2023
The go k8s packages are pretty bloated - this may also just be a niche case. If you are looking to get secrets with hot reloading, you might also consider mounting a file or setting env vars and coupling it with this reloading operator: https://github.com/stakater/Reloader
-
What Wishlist Features Would You Like To See From K8s?
For the auto restart this has been a staple install in all clusters for years for me: https://github.com/stakater/Reloader
-
Flux & Helm noob here - How do I pass secret values to Helm charts being handled by Flux?
If you didn't want to use SOPS, for some reason, you can certainly take advantage of external secrets as another commenter proposed, but you won't be able to accomplish (2) without an external tool adding to the mix, like Reloader: https://github.com/stakater/Reloader – that's because something has to update the HelmRelease in order to trigger it to upgrade. (You could just wait for the reconciler to come along, but the tendency is to set the polling interval longer than the default, so Helm won't be re-trying as often, in case something goes wrong...)
- Create new pods upon secret/configmap change in pipeline
-
Environment variables - manifest or configMap?
You can install https://github.com/stakater/Reloader And then it's just matter of a single annotation and it restarts automatically when there are changes.
- AWS secret store CSI Driver provider - how to reload pod after SecretProvider update?
What are some alternatives?
autoscaler - Autoscaling components for Kubernetes
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
kubernetes-reflector - Custom Kubernetes controller that can be used to replicate secrets, configmaps and certificates.
pod-reaper - Rule based pod killing kubernetes controller
k8s-configmap-watcher
nfs-subdir-external-provisioner - Dynamic sub-dir volume provisioner on a remote NFS server.
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
aws-ebs-csi-driver - CSI driver for Amazon EBS https://aws.amazon.com/ebs/
helm-charts - Misc helm charts
kube-scheduler-simulator - The simulator for the Kubernetes scheduler
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.