charts
keda
charts | keda | |
---|---|---|
28 | 102 | |
15,373 | 9,073 | |
- | 1.7% | |
2.1 | 9.4 | |
about 3 years ago | 1 day ago | |
Go | Go | |
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.
charts
- Nginx ingress resource - Redirect from to www (SSL doesn't work)
-
Prometheus: Monitor all services without creating ServiceMonitor for each service?
I'm using this prometheus helm chart.
-
Loading Kibana dashboards using Metricbeat through HELM charts
I did this using the incubator/raw chart ( https://github.com/helm/charts/tree/master/incubator/raw ), by creating a k8s Job.
-
K8S - using Prometheus to monitor another prometheus instance in secure way
I've installed Prometheus operator 0.34 (which works as expected) on cluster A (main prom)Now I want to use the federation option,I mean collect metrics from other Prometheus which is located on other K8S cluster B
-
Customize helm chart from stable repository
So I am using the helm chart stable/traefik to deploy a reverse proxy to my cluster. I need to customise it beyond what is possible with the variables I can set for the template.
- Helm Test best practices
-
✅ Updated guide for MetalLB v0.13+ (CRDs, baby!) with Flux, incl goofy diagrams illustrating L3 vs L2 👍
It may be that we just migrated to Bitnami's chart when the old "stable" chart was deprecated
-
Helm delete release and clear associated storage
Edit: I'm using Postgresql Stable Chart version 5.3.10
-
How to silence Prometheus Alertmanager using config files?
I'm using the official stable/prometheus-operator chart do deploy Prometheus with helm.
-
Airflow scheduler fails to start with kubernetes executor
I am using using https://github.com/helm/charts/tree/master/stable/airflow helm chart and building v1.10.8 puckle/docker-airflow image with kubernetes installed on it and using that image in the helm chart,But I keep getting
keda
-
How We Cut Our Azure Cloud Costs by 3x — Solda.Ai’s Experience
If you’re looking to implement a similar pattern, it’s worth noting that tools like KEDA can help you scale workloads based on event sources such as queue length. In our case, we decided to write a custom operator instead — mainly to retain full control and avoid relying on KEDA availability or support in our specific cloud provider setup.
-
Enabling HTTP-based Autoscaling in GKE with KEDA HTTP Add-on
kubectl apply -f https://github.com/kedacore/keda/releases/download/v2.4.0/keda-operator.yaml
-
Resolving CRD Size Limit Issues with KEDA on Kubernetes
Error from server (Request Entity Too Large): error when creating "https://github.com/kedacore/keda/releases/download/v2.12.1/keda-2.12.1.yaml": etcdserver: request is too large
-
Scaling Spin Apps With KEDA
KEDA (Kubernetes Event-Driven Autoscaling) extends Kubernetes’ scaling capabilities by allowing workloads to scale based on event-driven metrics such as message queue length, HTTP requests, or custom Prometheus queries. Unlike traditional Horizontal Pod Autoscalers (HPA) that rely solely on CPU or memory metrics, KEDA provides fine-grained control and adaptability to diverse application needs. For developers using SpinKube, KEDA enables efficient scaling of Spin apps based on application-specific metrics, making it easier to handle event-driven workloads in a Kubernetes environment. KEDA has a vast amount of built-in scalers to simplify integration with services running inside and outside of Kubernetes itself.
-
We've shipped App Hibernation feature in 3 days
To address our goal, we had to look for a solution that could automatically scale resources based on HTTP request volumes. Fortunately, we quickly discovered KEDA, a Kubernetes-based Event-Driven Autoscaler, which proved to be an ideal fit for our needs. KEDA enables the scaling of any container in Kubernetes in response to event volumes from sources such as Kafka, RabbitMQ, or Prometheus. It was a perfect match, and we were thrilled to find a solution that met our requirements so seamlessly. With KEDA, the solution became surprisingly straightforward.
-
What :really: is Keda?
My instinct is that Keda is a relatively simple piece of software. There's basically one file for managing the scaledobject and scaledjob
-
12 Tools that will make Kubernetes management easier in 2024
Keda (Kubernetes Event-Driven Autoscaling) is an event-driven autoscale for Kubernetes workloads. Simply defined, it can scale an application based on the number of events needing to be handled.
-
Building the Same App Using Various Web Frameworks
> lambda apps
Yes, SST [1] uses lambdas heavily but makes it more seamless and less visible, just the place your code runs.
I’ve also found Azure Container Apps to hit the right balance. It’s kubernetes under the hood, which you don’t have to mess with at all, except that it can use KEDA [2] scaling rules to scale your containers to zero, then scale up with any of the supported KEDA scalers like when a message hits a queue.
[1] https://sst.dev/
[2] https://keda.sh/
-
Deploy scalable, cost-effective event-driven workloads with Amazon EKS, KEDA, and Karpenter
KEDA is a Kubernetes-based autoscaler that dynamically adjusts the number of pods in your cluster based on the number of events needing to be processed. It is a lightweight, single-purpose component that integrates seamlessly with any Kubernetes cluster.
-
A skeptic's first contact with Kubernetes
Look for example at the metrics exposed by kube state metrics: https://github.com/kubernetes/kube-state-metrics/tree/main/d...
With controllers metrics + kube state metrics about most Kubernetes resources, you can easily build alerts when a resource fails to reconcile.
> Basically, Horizontal Pod Autoscaler but with sensors which are not just "CPU"
Take a look at KEDA, it's exactly this: https://keda.sh/
What are some alternatives?
external-dns - Configure external DNS servers dynamically from Kubernetes resources
argo - Workflow Engine for Kubernetes
prometheus-operator - Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes
k8s-prometheus-adapter - An implementation of the custom.metrics.k8s.io API using Prometheus
volcano - A Cloud Native Batch System (Project under CNCF)
istio - Connect, secure, control, and observe services.