k8s-prometheus-adapter
kube-no-trouble
k8s-prometheus-adapter | kube-no-trouble | |
---|---|---|
13 | 20 | |
1,841 | 2,836 | |
1.5% | 5.8% | |
6.3 | 7.0 | |
8 days ago | 8 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.
k8s-prometheus-adapter
-
Upgrading Hundreds of Kubernetes Clusters
The last one is mostly an observability stack with Prometheus, Metric server, and Prometheus adapter to have excellent insights into what is happening on the cluster. You can reuse the same stack for autoscaling by repurposing all the data collected for monitoring.
-
Helm: Is there a way to access templates of a sibling subchart
I'm deploying kube-prometheus-stack along with prometheus-adapter in my monitoring stack for custom metrics.
-
Deploy prometheus-adapter with kube-prometheus-stack monitoring stack?
I would like to see if anyone deployed prometheus-adapter and kube-prometheus-stack together for monitoring?
-
Horizontal Pod Autoscale
For us it is saturation of CPU and thread pool. It's implemented by exposing metrics of the thread pool to prometheus and turning that into a custom metric. (see) Looking at scaling based on job queue length next.
-
Steps to write own adaptor
If you are using Prometheus or kube-prometheus-stack, you will need https://github.com/kubernetes-sigs/prometheus-adapter We are using it to scale our Pods based on number of messages in RabbitMQ queue. There also a walkthrough on https://github.com/kubernetes-sigs/prometheus-adapter/blob/master/docs/walkthrough.md
-
Monitoring Your Spacelift Account via Prometheus
A prometheus-adapter installation.
-
Advanced Features of Kubernetes' Horizontal Pod Autoscaler
Prometheus adapter to get custom/external metrics from Prometheus instance into Kubernetes API.
-
Pod spread by percentage
I never tested this but you have customized metrics API if the value % is available should work from my point of view Check this here https://github.com/kubernetes-sigs/prometheus-adapter
-
Practical Introduction to Kubernetes Autoscaling Tools with Linode Kubernetes Engine
CPU and memory might not be the right metrics for your application to make scaling decisions. In such cases, you can use HPA (or VPA) with custom metrics as an alternative. To use custom metrics for autoscaling, you can use a custom metrics adapter instead of the Kubernetes Metrics Server. Popular custom metrics adapters are the Prometheus adapter and Kubernetes Event-Driven Autoscaler (KEDA).
- How to scale containers that are unrelated to physical traits like CPU or Memory?
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?
What are some alternatives?
keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
kubepug - Kubernetes PreUpGrade (Checker)
metrics-server - Scalable and efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.
silver-surfer - Kubernetes objects api-version compatibility checker and provides migration path for K8s objects and prepare it for cluster upgrades
k9s - 🐶 Kubernetes CLI To Manage Your Clusters In Style!
pluto - A cli tool to help discover deprecated apiVersions in Kubernetes
cluster-proportional-autoscaler - Kubernetes Cluster Proportional Autoscaler Container
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.
spring-auto-scaling-k8
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.
prometheus - The Prometheus monitoring system and time series database.
polaris - Validation of best practices in your Kubernetes clusters