obsctl-reloader

This tool uses obsctl to sync rules from your cluster to Observatorium Rules API via prometheus-operator’s PrometheusRule CRD.

Usage

The full usage documentation can be found in the Red Hat Monitoring Group Handbook.

Usage of obsctl-reloader:
  -audience string
    	The audience for whom the access token is intended, see https://openid.net/specs/openid-connect-core-1_0.html#IDToken.
  -issuer-url string
    	The OIDC issuer URL, see https://openid.net/specs/openid-connect-discovery-1_0.html#IssuerDiscovery.
  -kubeconfig string
    	Paths to a kubeconfig. Only required if out-of-cluster.
  -managed-tenants string
    	The name of the tenants whose rules should be synced. If there are multiple tenants, ensure they are comma-separated.
  -observatorium-api-url string
    	The URL of the Observatorium API to which rules will be synced.
  -sleep-duration-seconds uint
    	The interval in seconds after which all PrometheusRules are synced to Observatorium API. (default 15)

Note: this project is still experimental.

The tenant K8s secret must have a tenant metadata label and the following data fields, for it to be auto-detected by obsctl-reloader.

• client-id or client_id
• client-secret or client_secret