kube-beacon
kube-no-trouble
| kube-beacon | kube-no-trouble | |
|---|---|---|
| 1 | 20 | |
| 63 | 2,865 | |
| - | 4.1% | |
| 4.6 | 6.9 | |
| 13 days ago | 23 days ago | |
| Go | Go | |
| Apache License 2.0 | MIT License |
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.
kube-beacon
kube-no-trouble
-
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.
- Best Practices for Upgrading Kubernetes?
-
Updating from 1.25.15 to 1.26.10
kubent has been my goto for this - you point it at your cluster, tell it the target version you want to use, and it'll let you know if you have any depreciated resources and what you'll need to change. It's simple to use, quick, and just does the job.
-
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.
-
Upgrading our EKS from 1.21 to 1.22
A great tool for checking depreciations is kubent/kube-no-trouble: https://github.com/doitintl/kube-no-trouble
-
strategy to upgrade eks cluster
https://github.com/doitintl/kube-no-trouble can be used to check for deprecated/removed APIs - you'll need to fix these in your codebase. You should fix these before upgrading your cluster
- choose from Two strategies we can implement to upgrade eks cluster
- Amazon EKS now support Kubernetes version 1.25
-
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
Just upgraded a few clusters from 1.21 to 1.24 the past few weeks. Used kubent (Kube No Trouble https://github.com/doitintl/kube-no-trouble) before upgrading and reviewed the output. Pretty painless process all in all.
- Best practices for upgrades?
What are some alternatives?
kube-bench-exporter - :whale: :rocket: Helps you to export your kube-bench reports to multiple targets like Amazon S3 buckets with ease.
kubepug - Kubernetes PreUpGrade (Checker)
kube-bench - Checks whether Kubernetes is deployed according to security best practices as defined in the CIS Kubernetes Benchmark
silver-surfer - Kubernetes objects api-version compatibility checker and provides migration path for K8s objects and prepare it for cluster upgrades
pluto - A cli tool to help discover deprecated apiVersions in Kubernetes
gardener - Homogeneous Kubernetes clusters at scale on any infrastructure using hosted control planes.
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.
polaris - Validation of best practices in your Kubernetes clusters
polaris - Shopify’s design system to help us work together to build a great experience for all of our merchants.
php-k8s - Unofficial PHP client for Kubernetes. It supports any form of authentication, the exec API, and it has an easy implementation for CRDs.
teleport - Virtual KVM for macOS
eksup - EKS cluster upgrade guidance