Search Results for "run chart"

...Kong Ingress Controller configures Kong Gateway as a software load balancer that runs in the cluster and is typically exposed as a LoadBalancer service. Kong recommends using the Kong/ingress Helm chart to deploy the Kong Ingress Controller. This chart supports both DB-less and DB-backed deployments. If you’re not sure which to choose, we recommend choosing DB-less which treats the Kubernetes API server as the source of truth.

A GitOps style continuous delivery platform that provides consistent deployment and operations experience for any applications. Automatically trigger a new deployment when a defined event has occurred (e.g. container image pushed, helm chart published, etc). Support multiple application kinds on multi-cloud including Kubernetes, Terraform, Cloud Run, AWS Lambda, Amazon ECS. Support multiple analysis providers including Prometheus, Datadog, Stackdriver, and more. Easy to operate multi-cluster, multi-tenancy by separating control-plane and piped.

Prometheus exporter for various metrics about Elasticsearch, written in Go. The exporter fetches information from an Elasticsearch cluster on every scrape, therefore having a too short scrape interval can impose load on ES master nodes, particularly if you run with --es.all and --es.indices. We suggest you measure how long fetching /_nodes/stats and /_all/_stats takes for your ES cluster to determine whether your scraping interval is too short. As a last resort, you can scrape this exporter...