kubepug
kube-no-trouble
kubepug | kube-no-trouble | |
---|---|---|
9 | 21 | |
1,572 | 3,216 | |
2.7% | 1.3% | |
8.5 | 7.5 | |
3 days ago | 24 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.
kubepug
-
New IBM LinuxONE 4 Express – Rack-mounted pre-configured Linux mainframe
Agreed. The tooling around upgrades is painfully atrocious, and stuff like kubepug [1] should be part of the Kubernetes core.
[1] https://github.com/kubepug/kubepug
-
Top 15 Kubectl plugins for security engineers
Not strictly related to security, but I find kubepug awesome when planning upgrades, especially if you need to jump across 2 or 3 major versions.
- Kubernetes upgrade
-
Kubernetes 1.21 - Going EOL on major cloud providers in early 2023
Also kubepug - https://github.com/rikatz/kubepug
-
Essential plugins for Kubectl CLI
References Kubepug net-forward Krew
-
How do you verify all of your resources and manifests support before upgrading a Kubernetes version?
Verify with a tool like kubepug, something like
- rikatz/kubepug: Kubernetes PreUpGrade (Checker)
-
Making Kubernetes Operations Easy with kubectl Plugins
kube-pug - is a plugin known as deprecations in krew. Every cluster needs to be upgraded sooner or later and at some point you will run into API deprecations and/or removals. Finding what's being deprecated can be long and error-prone process and this plugin tries to simplify that. All you need to do is run kubectl deprecations --k8s-version=v1.XX.X and you will get list of all the instances of API objects in cluster that will be deprecated or removed in the specified version.
-
SilverSurfer - An OpenSource project to check ApiVersion Status and provide Migration path for Kubernetes objects when upgrading Kubernetes to 1.22 or any other.
Kubepug - Only checks whether the existing objects have any Deprecated ApiVersions
kube-no-trouble
-
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.
What are some alternatives?
ksniff - Kubectl plugin to ease sniffing on kubernetes pods using tcpdump and wireshark
pluto - A cli tool to help discover deprecated apiVersions in Kubernetes
kubeval - Validate your Kubernetes configuration files, supports multiple Kubernetes versions
silver-surfer - Kubernetes objects api-version compatibility checker and provides migration path for K8s objects and prepare it for cluster upgrades
ketall - Like `kubectl get all`, but get really all resources
gardener - Homogeneous Kubernetes clusters at scale on any infrastructure using hosted control planes.
polaris - Validation of best practices in your Kubernetes clusters
kubectl-dig - Deep kubernetes visibility from the kubectl
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.
kubectx - Faster way to switch between clusters and namespaces in kubectl
polaris - Shopify’s design system to help us work together to build a great experience for all of our merchants.