kube-no-trouble
k9s
kube-no-trouble | k9s | |
---|---|---|
20 | 128 | |
2,836 | 25,166 | |
5.8% | - | |
7.0 | 9.3 | |
6 days ago | 1 day ago | |
Go | Go | |
MIT License | 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.
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?
k9s
- Ask HN: Interesting TUIs (text user interfaces), maybe forgotten ones?
-
Upgrading Hundreds of Kubernetes Clusters
Pierre: The first tool I recommend is K9s. It's not just a time-saver but a productivity booster. With its intuitive interface, you can speed up all the usual kubectl commands, access logs, edit resources and configurations, and more. It's like having a personal assistant for your cluster management tasks.
-
Easy Access to Terminal Commands in Neovim using FTerm
The last thing you really need is a common set of tools that you want fingertip access to. I really commonly use LazyGit and K9s in my day job so those are the tools I will show off in this article.
-
π Five tools to make your K8s experience more enjoyable π
K9s is your best friend (get it? πΆ) when exploring your cluster via the terminal. It shares commonality with Vim for its interaction style using shortcuts and starting commands with: but donβt let that discourage you. K9s keeps a vigilant eye on Kubernetes activities, providing real-time information and intuitive commands for resource interaction.
-
Building a Kubernetes Operator with the Operator Framework
k9s: brew install k9s
-
Harlequin: SQL IDE for Your Terminal
I would like to put in a vote for k9s, which is also on the list at Terminal Trove. [0] It's the most convenient tool I've ever found for Kubernetes management. Based on that experience I'll definitely be checking out Harlequin.
[0] https://k9scli.io/
-
Your First K8S+Istio
$ wget https://github.com/derailed/k9s/releases/download/v0.29.1/k9s_Darwin_amd64.tar.gz $ tar -xzf k9s_Darwin_amd64.tar.gz $ sudo mv k9s /usr/local/bin/
-
Seeking Guidance for Transitioning to Kubernetes and SRE/DevOps for traditional infrastructure team
All in all, run things, do some kubectl apply -f something.yml every day, install k9s, and try to configure a big one cluster at some point.
-
Architecting for Resilience: Crafting Opinionated EKS Clusters with Karpenter & Cilium Cluster Mesh β Part 1
(K9s is one of my favorite tools for navigating Kubernetes clusters through the CLI).
-
Top 10 CLI Tools for DevOps Teams
K9s is an open-source, terminal-based UI for interacting with your Kubernetes clusters, making navigating, observing, and managing your apps easier. If you use Kubectl but wish it was easier and faster to use, K9s might be just what you're looking for!
What are some alternatives?
kubepug - Kubernetes PreUpGrade (Checker)
lens - Lens - The way the world runs Kubernetes
silver-surfer - Kubernetes objects api-version compatibility checker and provides migration path for K8s objects and prepare it for cluster upgrades
k8s - How to deploy Portainer inside a Kubernetes environment.
pluto - A cli tool to help discover deprecated apiVersions in Kubernetes
minikube - Run Kubernetes locally
gardener - Kubernetes-native system managing the full lifecycle of conformant Kubernetes clusters as a service on Alicloud, AWS, Azure, GCP, OpenStack, vSphere, KubeVirt, Hetzner, EquinixMetal, MetalStack, and OnMetal with minimal TCO.
popeye - π A Kubernetes cluster resource sanitizer
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.
k3s - Lightweight Kubernetes
polaris - Validation of best practices in your Kubernetes clusters
stern - β Multi pod and container log tailing for Kubernetes