This message was deleted.

Looks neat! The prometheus stuff looks interesting. What does Keptn use for the quality gates, is it using OPA+rego or something different?

Thanks 🙂 The setup is Keptn + Prometheus + Prometheus service + job executor service + infracost API The quality gate is out-of-the-box Keptn functionality so you get it “for free” with that

- name: "evaluation"

line. There are two files Keptn needs. An sli.yaml and slo.yaml. Partial files:

---
spec_version: '1.0'
indicators:
  infracost_total_hourly_cost: keptn_infracost_totalHourlyCost{ci_platform="keptn",keptn_project="infracost",keptn_service="microservice1",keptn_stage="dev-precheck"}

slo.yaml (partial)

spec_version: '1.0'
comparison:
  compare_with: "single_result"
  include_result_with_score: "pass"
  aggregate_function: avg
objectives:
  - sli: infracost_total_monthly_cost
    pass:
      - criteria:
          - "<700"
          - "<=+10%"
    warning:
      - criteria:
          - "<=695"
total_score:
  pass: "90%"
  warning: "75%"

The job executor service is configured to listen for the

checkcost.triggered

event and run an image that has Python, requests + prom client installed. The

app.py

queries infracost API and pushes metrics to a backend (Prometheus in this case) during the

checkcost.triggered

cloudevent task. Then the built-in quality gate takes action during the

evaluation.triggered

task and does it’s thing, retrieving metrics from Prom and giving a score.

@high-shoe-19425 this is awesome! Maybe post it as a new thread so everyone sees.