kubie
stern
kubie | stern | |
---|---|---|
13 | 16 | |
1,778 | 2,796 | |
- | 2.9% | |
7.7 | 6.0 | |
13 days ago | 8 days ago | |
Rust | Go | |
zlib 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.
kubie
- Tool to manage kubeconfig configurations
-
Setting kubectl context via env var
Kubie is what you need.
-
kxkn - Simple cli tool for switching between kubernetes namespace and cluster
Kubie
-
Sharing a simple function to switch kube configs per shell session
I can highly recommend kubie: https://github.com/sbstp/kubie I use it exactly because it launches a sub-shell with the choosen context and no other.
-
konf: Manage Lots of Local Kubeconfigs
I have been using a similar tool [kubie](https://github.com/sbstp/kubie), would love to check how you are doing it
-
Best three tools for working with many Kubernetes contexts
I've been using https://github.com/sbstp/kubie and has served me well
-
Kubesess - Session management tool for kubctl!
I currently use kubie (https://github.com/sbstp/kubie). Any idea how both compare?
-
Kubernetes is a cloud operating system
Yeah, fair points.
Regarding (3) there are tools for that like kubie. I've still shot myself in the foot before.
https://github.com/sbstp/kubie
-
What are your favorite tools you use to manage/work with kubernetes?
kubie. I don't use it for context switching (still prefer kubectx!) but kubie exec is a really powerful tool for executing the same command across multiple contexts at once.
-
Grafana multi-tenant configuration with Terraform
Kubie (not necessary)
stern
-
☸️ Kubernetes: From your docker-compose file to a cluster with Kompose
deploy: stage: deploy image: alpine/k8s:1.29.1 variables: NAMESPACE: $CI_COMMIT_REF_SLUG before_script: # init namespace - kubectl config use-context $KUBE_CONTEXT - kubectl create namespace $NAMESPACE || true # download tools - curl --show-error --silent --location https://github.com/stern/stern/releases/download/v1.22.0/stern_1.22.0_linux_amd64.tar.gz | tar zx --directory /usr/bin/ stern && chmod 755 /usr/bin/stern && stern --version - curl --show-error --silent --location https://github.com/kubernetes/kompose/releases/download/v1.32.0/kompose-linux-amd64 -o /usr/local/bin/kompose && chmod a+x /usr/local/bin/kompose && kompose version # show logs asynchronously. Timeout to avoid hanging indefinitely when an error occurs in script section - timeout 1200 stern -n $NAMESPACE "app-" --tail=0 --color=always & # in background, tail new logs if any (current and incoming) pod with this regex as name - timeout 1200 kubectl -n $NAMESPACE get events --watch-only & # in background, tail new events in background script: # first delete CrashLoopBackOff pods, polluting logs - kubectl -n $NAMESPACE delete pod `kubectl -n $NAMESPACE get pods --selector app.kubernetes.io/component=$MODULE | awk '$3 == "CrashLoopBackOff" {print $1}'` || true # now deploying - kompose convert --out k8s/ - kubectl apply -n $NAMESPACE -f k8s/ - echo -e "\e[93;1mWaiting for the new app version to be fully operational...\e[0m" # waiting for successful deployment - kubectl -n $NAMESPACE rollout status deploy/app-db - kubectl -n $NAMESPACE rollout status deploy/app-back - kubectl -n $NAMESPACE rollout status deploy/app-front # on any error before this line, the script will still wait for these threads to complete, so the initial timeout is important. Adding these commands to after_script does not help - pkill stern || true - pkill kubectl || true after_script: # show namespace content - kubectl config use-context $KUBE_CONTEXT - kubectl -n $NAMESPACE get deploy,service,ingress,pod
-
stern VS stern - a user suggested alternative
2 projects | 11 Dec 2023
The old repo is dead
-
🦊 GitLab CI: 10+ Best Practices to Avoid Widespread Anti-patterns
node-and-git: image: node:18.10-alpine before_script: - apk --no-cache add git kubectl-and-stern: image: alpine/k8s:1.22.13 before_script: # install stern - curl --show-error --silent --location https://github.com/stern/stern/releases/download/v1.22.0/stern_1.22.0_linux_amd64.tar.gz | tar zx --directory /usr/bin/ stern && chmod 755 /usr/bin/stern playwright-and-kubectl: image: mcr.microsoft.com/playwright:v1.35.1-focal before_script: # install kubectl - curl --show-error --silent --location --remote-name https://storage.googleapis.com/kubernetes-release/release/v1.25.3/bin/linux/amd64/kubectl && chmod +x ./kubectl && mv ./kubectl /usr/local/bin/
-
K9s: A lazier way to manage Kubernetes Clusters
I'll add stern (https://github.com/stern/stern) to that - follow logs from multiple pods easily.
-
What k8s related tool you wish you knew earlier?
Multi pod and container log tailing for Kubernetes https://github.com/stern/stern
- What's your "IDE" of choice nowadays?
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 1/2
stern v1.22.0
-
Getting started with kubectl plugins
Link to GitHub Repository
-
Julia Evans: Tips for Analyzing Logs
If you are using Kubernetes, I highly recommend using https://github.com/stern/stern
-
What daily terminal based tools are you using for cluster management?
Stern: https://github.com/stern/stern for log streaming
What are some alternatives?
kubectx - Faster way to switch between clusters and namespaces in kubectl
kubetail - Bash script to tail Kubernetes logs from multiple pods at the same time
kubeswitch - The kubectx for operators.
awesome-k8s-resources - A curated list of awesome Kubernetes tools and resources.
kubecm - Manage your kubeconfig more easily.
kail - kubernetes log viewer
kube - Rust Kubernetes client and controller runtime
cw - The best way to tail AWS CloudWatch Logs from your terminal
kubeswitch
openlens-node-pod-menu - Node and pod menus for OpenLens
kconf - Manage multiple kubeconfigs easily
saw - Fast, multi-purpose tool for AWS CloudWatch Logs