kube-no-trouble
Easily check your clusters for use of deprecated APIs (by doitintl)
gardener
Homogeneous Kubernetes clusters at scale on any infrastructure using hosted control planes. (by gardener)
| kube-no-trouble | gardener | |
|---|---|---|
| 21 | 9 | |
| 3,136 | 2,908 | |
| 3.3% | 2.1% | |
| 6.5 | 9.9 | |
| 12 days ago | 2 days ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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-no-trouble
Posts with mentions or reviews of kube-no-trouble.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-06-26.
-
Mitigating disruption during Amazon EKS cluster upgrade with blue/green deployment
There are several tools that help us find out the API deprecations in our clusters. One of them is “kube-no-trouble” aka kubent. At the time I write this document, the latest ruleset is for 1.29 in kubent. I run kubent with target version of 1.29 and got the below result. As you can see, kubent shows the deprecated APIs.
-
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.
gardener
Posts with mentions or reviews of gardener.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-10.
- Introducing Gardener, your ultimate companion for effortless Kubernetes cluster management!
-
How does managed kubernetes providers hide the control plane?
Now, if you want to dig further on how cloud providers operate, like I said, most are actually using Kubernetes to automate the client control plane management. There is a cloud-neutral project for this out there called Gardener, they have a few architecture documents which explain the concept a bit further. In their garden metaphor, the seed cluster hosts the client control planes, and the shoot clusters are the client clusters (which are only made of worker nodes, no control-plane node). Another more specialized implementation is Kubernikus for OpenStack.
- Where can I find managed K8s for the price of managed ECS?
-
Alternative to Rancher as a multi-cluster management platform?
Gardener: https://github.com/gardener/gardener RH HyperShift: https://github.com/openshift/hypershift
-
Can we use a worker node of one kubernetes cluster as master node of another k8s cluster?
Gardener does exactly that. One global cluster manages smaller per-region/cloud provider management clusters and those will contain the control planes of your workload clusters. This way you can have like 10 000 clusters and not deal with multi-tenant issues. One workload = 1 cluster.
-
Over a fifty K8s clusters?
We had cluster of cluster style management managing 100s of cluster. Check out https://github.com/gardener/gardener for an inspiration
- Why aren't there any manged Kubernetes Control Plane as a Service offering out there?
- Datenschutz: SAP und Arvato bauen Verwaltungs-Cloud mit Microsoft-Technik
-
Amazon EKS Anywhere
How does this compare against simply using Gardener [0]?
[0] https://github.com/gardener/gardener
What are some alternatives?
When comparing kube-no-trouble and gardener you can also consider the following projects:
kubepug - Kubernetes PreUpGrade (Checker)
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
pluto - A cli tool to help discover deprecated apiVersions in Kubernetes
crossplane - The Cloud Native Control Plane
silver-surfer - Kubernetes objects api-version compatibility checker and provides migration path for K8s objects and prepare it for cluster upgrades
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
polaris - Validation of best practices in your Kubernetes clusters
eks-distro - Amazon EKS Distro (EKS-D) is a Kubernetes distribution based on and used by Amazon Elastic Kubernetes Service (EKS) to create reliable and secure Kubernetes clusters.
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.
cloudpods - A cloud-native open-source unified multi-cloud and hybrid-cloud platform. 开源、云原生的多云管理及混合云融合平台
polaris - Shopify’s design system to help us work together to build a great experience for all of our merchants.
Pulumi - Pulumi - Infrastructure as Code in any programming language 🚀
kube-no-trouble vs kubepug
gardener vs terraformer
kube-no-trouble vs pluto
gardener vs crossplane
kube-no-trouble vs silver-surfer
gardener vs eks-anywhere
kube-no-trouble vs polaris
gardener vs eks-distro
kube-no-trouble vs Gravitational Teleport
gardener vs cloudpods
kube-no-trouble vs polaris
gardener vs Pulumi