kube-score
stern
Our great sponsors
kube-score | stern | |
---|---|---|
8 | 10 | |
2,568 | 6,326 | |
- | - | |
8.0 | 0.0 | |
14 days ago | over 2 years 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-score
- GitHub - zegl/kube-score: Kubernetes object analysis with recommendations for improved reliability and security
-
What should readiness & liveness probe actually check for?
This is taken from: https://github.com/zegl/kube-score/blob/master/README_PROBES.md and I have read the same opinions elsewhere.
-
How do you take care of your manifests?
A developer's workflow should anyway deploy to a real, or close-to-production Kubernetes cluster before opening a merge request with the finished change. That means the developer definitely sees upfront if the manifest is super wrong. Tools like kube-score (which is quite opinionated), kubeval or OPA rules can help in addition to keep things consistent and secure. For such a developer workflow, I recommend Skaffold since it mostly just wraps Docker, kubectl and the templating tool you're using (e.g. kustomize/helm).
- Kube-Score v1.14
- kube-score v1.14 – Kubernetes object analysis with recommendations for improved reliability and security
-
Securing Kubernetes Deployments
apps/v1/Deployment semaphore-demo-ruby-kubernetes 💥 [CRITICAL] Container Resources · semaphore-demo-ruby-kubernetes -> CPU limit is not set Resource limits are recommended to avoid resource DDOS. Set resources.limits.cpu · semaphore-demo-ruby-kubernetes -> Memory limit is not set Resource limits are recommended to avoid resource DDOS. Set resources.limits.memory · semaphore-demo-ruby-kubernetes -> CPU request is not set Resource requests are recommended to make sure that the application can start and run without crashing. Set resources.requests.cpu · semaphore-demo-ruby-kubernetes -> Memory request is not set Resource requests are recommended to make sure that the application can start and run without crashing. Set resources.requests.memory [CRITICAL] Container Image Pull Policy · semaphore-demo-ruby-kubernetes -> ImagePullPolicy is not set to Always It's recommended to always set the ImagePullPolicy to Always, to make sure that the imagePullSecrets are always correct, and to always get the image you want. [CRITICAL] Pod NetworkPolicy · The pod does not have a matching NetworkPolicy Create a NetworkPolicy that targets this pod to control who/what can communicate with this pod. Note, this feature needs to be supported by the CNI implementation used in the Kubernetes cluster to have an effect. [CRITICAL] Pod Probes · Container is missing a readinessProbe A readinessProbe should be used to indicate when the service is ready to receive traffic. Without it, the Pod is risking to receive traffic before it has booted. It's also used during rollouts, and can prevent downtime if a new version of the application is failing. More information: https://github.com/zegl/kube-score/blob/master/README_PROBES.md [CRITICAL] Container Security Context · semaphore-demo-ruby-kubernetes -> Container has no configured security context Set securityContext to run the container in a more secure context. v1/Service semaphore-demo-ruby-kubernetes-lb ✅
-
Top 20 useful k8s tools
Link : https://github.com/zegl/kube-score
stern
-
stern VS stern - a user suggested alternative
2 projects | 11 Dec 2023
- Most efficient way to check all containers cluster wide for missing probes?
-
What are some useful Kubernetes tools you can share?
I love stern when interacting with Pod logs directly. https://github.com/wercker/stern
-
You started a new job, what are the first tools you install on your machine?
stern
-
Adventures in K8S Cloud Native App Development
Logging: Traditional ELK requires a lot of server resources and is not suitable for a lightweight cluster like ours. The easiest way is to run multiple Pods to see the logs, and there is a stern tool that helps us to query the logs across multiple Pods.
-
Top 20 useful k8s tools
Link : https://github.com/wercker/stern
-
What's the best CLI tailing tool for k8s logs?
https://github.com/wercker/stern is pretty handy
- Tail multiple pods on K8s and multiple containers within the pod
-
MacOS and Linux support for KTail - a Kubernetes log viewer with a GUI
I like https://github.com/wercker/stern
-
ktail 0.2.5 - a kubernetes log viewer
Also stern
What are some alternatives?
polaris - Validation of best practices in your Kubernetes clusters
kubetail - Bash script to tail Kubernetes logs from multiple pods at the same time
popeye - 👀 A Kubernetes cluster resource sanitizer
kail - kubernetes log viewer
kubeconform - A FAST Kubernetes manifests validator, with support for Custom Resources!
k9s - 🐶 Kubernetes CLI To Manage Your Clusters In Style!
datree - Prevent Kubernetes misconfigurations from reaching production (again 😤 )! From code to cloud, Datree provides an E2E policy enforcement solution to run automatic checks for rule violations. See our docs: https://hub.datree.io
krew - 📦 Find and install kubectl plugins
kubeval - Validate your Kubernetes configuration files, supports multiple Kubernetes versions
free4chat - free4.chat is a real-time audio chat service. It is designed by the local first and privacy first principle, and is very easy to use.
polaris - Shopify’s design system to help us work together to build a great experience for all of our merchants.
stern - ⎈ Multi pod and container log tailing for Kubernetes -- Friendly fork of https://github.com/wercker/stern