RBAC (api/internal/authz) is live on /query and /dashboards, backed by a new enterprise/ module (session issuance, audit logging, RBAC storage, OIDC/SAML protocol wiring) that core never imports -- only calls over HTTP. Found and fixed a real cross-tenant vulnerability in dashboards (no tenant_id filtering at all) while writing the threat model doc. Two things are explicitly NOT done, documented rather than hidden: tenant isolation for log data itself (/query still shares one ClickHouse connection and Tantivy index across every tenant -- RBAC controls who can query, not what a query can see), and human SSO login (protocol wiring exists, no HTTP handler calls it yet). See docs/security/threat-model.md and docs/phase-4-runbook.md. Also adds deploy/ (Go Operator + Helm chart, validated offline only -- no cluster was reachable in this environment).
13 lines
536 B
Docker
13 lines
536 B
Docker
# Same shape as every other Go service's Dockerfile in this repo
|
|
# (alerting/Dockerfile, enterprise/Dockerfile) -- context is
|
|
# deploy/operator/ itself, no /proto dependency.
|
|
# docker build -f deploy/operator/Dockerfile -t sentry-tenant-operator deploy/operator/
|
|
FROM golang:1.25-alpine AS builder
|
|
WORKDIR /src
|
|
COPY . .
|
|
RUN CGO_ENABLED=0 GOOS=linux go build -o /out/tenant-operator ./cmd/tenant-operator
|
|
|
|
FROM gcr.io/distroless/static-debian12
|
|
COPY --from=builder /out/tenant-operator /tenant-operator
|
|
ENTRYPOINT ["/tenant-operator"]
|