Skip to content

Latest commit

 

History

History
51 lines (38 loc) · 1.93 KB

README.md

File metadata and controls

51 lines (38 loc) · 1.93 KB
Raw

terraform-kubernetes-google-slo-generator

An extremely opinionated module, that deploys [omni-slo-generator][omni-slo-gnerator] based on Google's SLO generator into GKE.

Assumptions made

  • Prometheus backend is a mimir cluster
    • Mimir is running in monitoring namespace and has a nginx pod mimir-nginx for proxying (as mimir helm chart does it)
    • This can be overridden variable prometheus-backend-url
  • You want to keep the default policies as shown in slo-exporter's examples (1h, 12h, 7d, 28d)
  • You are using ingress nginx controller (this is configurable)
  • GKE cluster has workload identity enabled
  • You are running prometheus operator (monitoring.coreos.com/v1 in your cluster)

Diagram

Diagram

Note: Ingress is deployed optionally, if you want to run your job inside kubernetes, you don't need to expose it outside the cluster.

Usage

module "slo-generator" {
  source = "heureka/google-slo-generator/kubernetes"
  version = "2.0.3"

  gke-project     = "company-k8s"
  storage-project = "todo-app"
  namespace       = "todo-app"
  ingress-host    = "slo-generator.example.com"  # optional
  bucket-name     = "company-todo-app-slos"
}

After that, you can upload your SLO manifests to the SLOs bucket, which the generator will automatically go through and calculate SLOs for

Additional configuration

Please check the input tab of this module's page on terraform registry to see all available options and their descriptions.