draino
pluto
| draino | pluto | |
|---|---|---|
| 2 | 18 | |
| 606 | 1,965 | |
| 0.5% | 0.9% | |
| 0.0 | 5.8 | |
| about 1 month ago | about 1 month 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.
draino
-
Seeking inspiration for auto remediation of nodes
draino (cordon and drain node)
-
Interesting tools?
Drain node upon a condition: Draino
pluto
-
Upgrading Hundreds of Kubernetes Clusters
We also leverage tools like Kubent, popeye, kdave, and Pluto to help us manage API deprecations (when Kubernetes deprecates features in updates) and ensure the overall health of our infrastructure.
- Updating from 1.25.15 to 1.26.10
-
How do you handle continuous k8s cluster version upgrades in your organization?
You have to constantly run tools like https://github.com/doitintl/kube-no-trouble / https://github.com/FairwindsOps/pluto.
- How do you guys monitor K8s core services new versions
-
eks cluster upgrade Anyone has done eks cluster upgrade to upgrade the cluster from 1.21 to 1.22 there are some api resources kind need to changed, which need changes in manifest file changes. how do we identify the helm charts that are using these resources ? https://docs.aws.amazon.com/eks/lat
You might like https://github.com/FairwindsOps/pluto
- Kubernetes upgrade
-
Upgrading EKS from k8s version 1.21 to 1.24
Run Pluto against the old cluster to check for outdated APIs in your namespaces: https://github.com/FairwindsOps/pluto
-
kubernetes provider resources v1 vs non-v1 is it just me or is this dumb?
I knew it was unsupported so about 6 months ago I had started an effort to switch to Kyverno, which is far better and actually supported. The version of Kyverno I was using had a v1beta1 AdmissionController. Fortunately that was in a helm chart so easily caught by pluto before my upgrade.
-
Helm chart - fluent-bit
If you're looking for API deprecations specifically you can look into pluto from fairwinds.
-
Updating EKS to 1.22: dealing with deprecated APIs on ALB Ingresses
you can use https://github.com/FairwindsOps/pluto to check for api deprecations before updating the cluster.
What are some alternatives?
node-problem-detector - This is a place for various problem detectors running on the Kubernetes nodes.
kube-no-trouble - Easily check your clusters for use of deprecated APIs
kured - Kubernetes Reboot Daemon
silver-surfer - Kubernetes objects api-version compatibility checker and provides migration path for K8s objects and prepare it for cluster upgrades
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)
helm - The Kubernetes Package Manager
rook - Storage Orchestration for Kubernetes
rbac-manager - A Kubernetes operator that simplifies the management of Role Bindings and Service Accounts.
stern - ⎈ Multi pod and container log tailing for Kubernetes -- Friendly fork of https://github.com/wercker/stern
helmfile - Deploy Kubernetes Helm Charts
devtron - Tool integration platform for Kubernetes
polaris - Validation of best practices in your Kubernetes clusters