kube-score
kubectx
Our great sponsors
kube-score | kubectx | |
---|---|---|
8 | 40 | |
2,568 | 16,852 | |
- | - | |
8.0 | 3.3 | |
13 days ago | 5 days 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
kubectx
-
Building a Kubernetes Operator with the Operator Framework
kubectx: brew install kubectx
-
Jenkins Agents On Kubernetes
default is where any actions which require a namespace will go into if one is not explicitly defined in a default setup (tools such as kubens can alter this behavior). In the context of Jenkins, namespaces are a useful way to allow isolation of individual Jenkins instances that want to utilize the same Kubernetes cluster. Creation of a namespace is a simple option to kubectl:
-
Tool to manage kubeconfig configurations
Here you go: https://github.com/ahmetb/kubectx and https://kubecm.cloud/
-
Setting kubectl context via env var
check out kubectx/kubens https://github.com/ahmetb/kubectx very handy tool to permanently switch context/namespace
- Minikube broke my Kubectl config
- Managing local cluster config
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 1/2
kubectx + kubens v0.9.4
-
[ANN] Kele: Snappy Kubernetes cluster management in Emacs
For a peek at what's currently possible, visit the documentation site, in particular the Usage section. For this initial release, it has feature parity with kubectx and kubens and that's about it, but there's lots of room for growth.
-
Injecting secrets from Vault into Helm charts with ArgoCD
I also encourage you to install kubectx + kubens to navigate Kubernetes easily.
- What daily terminal based tools are you using for cluster management?
What are some alternatives?
polaris - Validation of best practices in your Kubernetes clusters
fzf-tab - Replace zsh's default completion selection menu with fzf!
popeye - 👀 A Kubernetes cluster resource sanitizer
kubie - A more powerful alternative to kubectx and kubens
kubeconform - A FAST Kubernetes manifests validator, with support for Custom Resources!
kubeswitch - The kubectx for operators.
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
kubecm - Manage your kubeconfig more easily.
kubeval - Validate your Kubernetes configuration files, supports multiple Kubernetes versions
kubectl-neat - Clean up Kubernetes yaml and json output to make it readable
polaris - Shopify’s design system to help us work together to build a great experience for all of our merchants.
k9s - 🐶 Kubernetes CLI To Manage Your Clusters In Style!