Skip to content
querdian-devPublic

About

Multi-tenant, label-based access proxy for Prometheus/Thanos, Loki and Tempo

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

6 stars

Watchers

0 watching

Forks

Latest commit

 

History

372 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Querdian logo

Querdian

Querdian (query + guardian) is an Apache-2.0, Kubernetes-native reverse proxy that enforces label-based access control on read queries against Prometheus/Thanos (PromQL), Loki (LogQL) and Tempo (TraceQL). Policies are Kubernetes CRDs, queries are rewritten with real parsers, and everything fails closed: unknown endpoints, unknown users and unparseable queries are rejected.

OpenSSF Best Practices OpenSSF Scorecard Artifact Hub

Status: alpha, v0.1.2 is the latest release. It is not ready for production use: the policy API is v1alpha1 and may change incompatibly, and there are no production adopters yet. The proxy, the policy CRDs and the PromQL, LogQL and TraceQL enforcers are covered by unit, fuzz, envtest and container-based differential/equivalence suites (make e2e) against real Prometheus, Loki and Tempo. Read the release notes and the known limitations before you evaluate it. See also CHANGELOG.md and ROADMAP.md.

Install

helm install querdian oci://ghcr.io/querdian-dev/charts/querdian --version 0.1.2 \
  --namespace querdian --create-namespace -f my-values.yaml
  • Helm chart: oci://ghcr.io/querdian-dev/charts/querdian, also on Artifact Hub; values in the chart README.
  • Container image: ghcr.io/querdian-dev/querdian:0.1.2 (linux/amd64, linux/arm64).
  • Binaries, checksums and SBOMs: the GitHub release.
  • Everything is signed with cosign (keyless) and has build-provenance attestations; see Verify.

To see it working first, run the quickstart.

How it works

The path of a query through Querdian

Querdian verifies the OIDC token of the user, finds the rules of the user in the policies, rewrites the query with a real parser and sends it to the backend. It rejects each request that it cannot check. How Querdian works explains the parts, also for a hub with spoke clusters.

Inspired by evoila/janus.

See PLAN.md for the design and TASKS.md for the work breakdown.

The website (landing page and rendered documentation) is built from site/ and docs/ and published at https://querdian.dev, see site/README.md.

Documentation

Contributing and reporting

Building

make build test lint

License

Apache-2.0, see LICENSE.

About

Multi-tenant, label-based access proxy for Prometheus/Thanos, Loki and Tempo

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

6 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages