kube-state-metrics
Kong
Our great sponsors
kube-state-metrics | Kong | |
---|---|---|
33 | 18 | |
5,086 | 37,482 | |
2.1% | 1.2% | |
8.9 | 9.9 | |
7 days ago | 4 days ago | |
Go | Lua | |
Apache License 2.0 | 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-state-metrics
- Do we have any Prometheus metric to get the kubernetes cluster-level CPU/Memory requests/limits?
-
10 Kubernetes Visualization Tool that You Can't Afford to Miss
git clone https://github.com/kubernetes/kube-state-metrics.git
-
Why is the Prometheus metric 'kube_pod_completion_time' returning empty query results?
https://github.com/kubernetes/kube-state-metrics/blob/main/docs/pod-metrics.md According to this github repo completion is responsible of termination date if I correctly understood .
-
Google Kubernetes Engine's metrics vs Self-managed
kube-state-metrics
-
Prometheus node exporter and cadvisor to send metrics to central prometheus cluster
Those are entirely different types of data. You can get that from something like kube-state-metrics
-
Scaling kube-state-metrics in large cluster
I've never had a cluster of that size, so take it with a grain of salt - but maybe you could try purpose-based sharding? KSM has allowlist and denylist config flags, for configuring which metrics it exposes https://github.com/kubernetes/kube-state-metrics/blob/main/docs/cli-arguments.md
-
Questions about Kubernetes
Kubernetes itself will not notify you, the way I've seen people do this, is to use something like kube-state-metrics or node_exporter, export that to Prometheus (or preferrably VictoriaMetrics because Prometheus is terrible IMO), and then setup alarms on that with alertmanager or equivalent, or just look at dashboards regularly with Grafana. Realistically I recommend only setting alerts on disk usage and application/database latency. CPU and memory utilization isn't a great metric to alert on a lot of the time.
-
EKS scalability best practices
Another tip that you could consider spelling out a little more, is to monitor the number of resources created by Kind. This is somewhat mentioned for jobs and services, but any Kind of which thousands of resources are created will put stress on the control-plane. The total number of resources per namespace/cluster can be monitored with kube-state-metrics. KSM does not emit metrics of resources created from CRDs. These metrics can be implemented with KSM's custom resource state metrics: https://github.com/kubernetes/kube-state-metrics/blob/main/docs/customresourcestate-metrics.md
-
Observability-Landscape-as-Code in Practice
We then have various other Metrics called Kubernetes Workload Metrics. These are the dashboards with names that start with “Kubernetes / Compute Resources / Workload”. These dashboards are specific to the services you are running. They take into account the Kubernetes Workloads in your various namespaces, using kube-state-metrics. For a closer look, check out otel_demo_app_k8s_dashboard.tf.
-
Kubernetes Costs: Effective Cost Optimization Strategies To Reduce Your k8s Bill
The first step to optimizing costs is gaining visibility into your costs using tools. Kubernetes provides a Metrics Server and kube-state-metrics that can give you the overall picture of resource utilization by your cluster. There are more tools that provide more granular breakdowns and provide dashboards with business metrics, infra cost, and alerting functionalities. Here are some strategies to optimize your resource utilization and cloud bills on k8s.
Kong
- Kong 3.6 with LLM Support
-
5 Ways to Improve Your API Reliability
Kong: A cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway or API Middleware). Made available as an open-source project in 2015, its core functionality is written in Lua and it runs on the nginx web server.
-
Access to Gravitee Github repository has been restricted - This is NOT how OSS works
OPeNsOuRcE. Good time to switch to Kong, better option anyways.
- Self hosting costing questions
-
Proxy Basic Auth Replacement Best Practice for Cloud Native / OIDC / Vault
Sounds like you want an API gateway? What about Kong?
-
HAProxy 2.7
Unquestionably no, Kong is "OpenResty plus a management plane" and they're Apache 2: https://github.com/kong/kong#license
-
Ask HN: Who is hiring? (April 2022)
Kong (https://konghq.com) | Gateway Senior Engineer | REMOTE Europe | Full-time
The Kong Gateway is an API Management solution, which serves as a foundation for many other solutions by the company. The business model is open-core: an Open Source solution exists (https://github.com/kong/kong), and there's an Enterprise version with more features and dedicated support.
The tech stack is a modified Openresty with of Lua code on top. The ideal candidate would be someone who is already familiar with Kong. Alternatively, if you are familiar with Openresty or other API management solution, we also would love to talk with you.
I am personally interested in finding people to join me in the European Gateway Team. The role involves adding features, fixing bugs, and collaborating with other teams. Here's that position:
https://jobs.lever.co/kong/c1a2b204-45a8-4c19-9cd4-d9824a778...
We have many projects and many teams all around the world (current headcount is ~450), using other technologies like Node in the Kong Manager or Go in the Koko project, and we are constantly looking for people. Please visit our careers page to find out more!
https://konghq.com/careers/
-
Breaking Up a Monolithic Database with Kong
Kong Gateway allows the complexity of service-tier APIs to be reduced to a collection of endpoints (or URIs) focused on meeting a collection of business needs and functionality. Often-duplicated components (like authentication, logging, and security) are handled by the gateway and can be removed from the service-tier design.
- 27 open-source tools that can make your Kubernetes workflow easier 🚀🥳
-
Difference between Reverse Proxy, Load Balancer and API Gateway
I am seeing different companies taking different approach. I am not sure anymore where each should be actually used. On top of that tech like Kong make me question whether API Gateway should be one thing for all. Some perspective into this would be really appreciated.
What are some alternatives?
cadvisor - Analyzes resource usage and performance characteristics of running containers.
apisix - The Cloud-Native API Gateway
metrics-server - Scalable and efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.
KrakenD - Ultra performant API Gateway with middlewares. A project hosted at The Linux Foundation
php-fpm_exporter - A prometheus exporter for PHP-FPM.
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
k3s - Lightweight Kubernetes
konga - More than just another GUI to Kong Admin API
kubespray - Deploy a Production Ready Kubernetes Cluster
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
kube-metrics-adapter - General purpose metrics adapter for Kubernetes HPA metrics
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.