ProofedMesh/deploy/trillian/20-logserver.yaml
CTO 951f22f80e
Some checks failed
build-images / signing-service image (push) Failing after 14s
validate / JSON Schema (ajv) (push) Successful in 21s
validate / Rego (opa fmt + opa test) (push) Successful in 14s
validate / Go (vet + test) (push) Successful in 30s
transparency-log: real Trillian backend wiring + agent-trust deploy (DEV-604)
- services/transparency-log/pkg/backend/trillian.go: real gRPC client
  on github.com/google/trillian v1.6.1. Submit() does QueueLeaf with the
  canonical DSSE envelope as LeafValue and the raw content_hash bytes as
  LeafIdentityHash, then polls GetLatestSignedLogRoot +
  GetInclusionProofByHash until the leaf is sequenced. Idempotency uses
  Trillian's ALREADY_EXISTS signal on the inner QueuedLogLeaf.Status, so
  a repeated submit still returns 200 OK with the originally-assigned
  log_index + a valid proof against the current STH.
- Unconfigured backend (missing endpoint or LogID) returns the historical
  ErrTrillianUnavailable so the httpapi layer keeps mapping it to 503
  instead of silently 500. Existing stub-returns-503 test updated.
- cmd/transparency-log: pointer-receiver Trillian wiring; flag docs
  mention the production SRV name.
- services/transparency-log/Dockerfile: distroless multi-stage build
  used by deploy/trillian/40-transparency-log.yaml.

- deploy/trillian/: full K8s stack for the agent-trust namespace —
  MySQL 8.4 StatefulSet (schema init ConfigMap vendored from upstream
  storage.sql v1.6.1), Trillian LogServer + LogSigner Deployments on
  gcr.io/trillian-opensource-ci:v1.6.1, createtree Job that writes
  the TreeID to a ConfigMap (re-apply safe), transparency-log
  Deployment with --backend=trillian pulling TRILLIAN_LOG_ID from
  the ConfigMap.
- deploy/trillian/README.md: first-time apply + smoke-test + secret
  rotation + signer-key clarification (STH key is Trillian-internal;
  DSSE envelope signing stays with signing-service / OpenBao).

- services/admin-api: go.mod / go.sum pick up the new transitive deps
  (trillian + grpc) via the local replace on transparency-log.
- services/transparency-log/README.md: Backends table updated; next-
  steps list no longer carries Trillian-deployment as a follow-up.

Deployed to the live cluster from this heartbeat: MySQL + LogServer +
LogSigner running in agent-trust, tree id 8482455225499059043, service
smoke-tested end-to-end (201 on first POST, 200 on idempotent repeat,
409 on content_hash mismatch, tree_size=2 with correct audit path).

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-10-25 18:39:44 +00:00

71 lines
1.8 KiB
YAML

apiVersion: v1
kind: Service
metadata:
name: trillian-log-server
namespace: agent-trust
spec:
selector:
app.kubernetes.io/name: trillian-log-server
ports:
- name: grpc
port: 8090
targetPort: 8090
- name: metrics
port: 8091
targetPort: 8091
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: trillian-log-server
namespace: agent-trust
labels:
app.kubernetes.io/name: trillian-log-server
app.kubernetes.io/part-of: proofedmesh
spec:
replicas: 1
selector:
matchLabels:
app.kubernetes.io/name: trillian-log-server
template:
metadata:
labels:
app.kubernetes.io/name: trillian-log-server
spec:
containers:
- name: log-server
image: gcr.io/trillian-opensource-ci/log_server:v1.6.1
args:
- --storage_system=mysql
- --mysql_uri=$(MYSQL_URI)
- --rpc_endpoint=0.0.0.0:8090
- --http_endpoint=0.0.0.0:8091
- --alsologtostderr
envFrom:
- secretRef:
name: trillian-mysql
ports:
- containerPort: 8090
name: grpc
- containerPort: 8091
name: metrics
readinessProbe:
# Trillian's /metrics endpoint only comes up once DB connectivity is
# ready, which is exactly the readiness semantics we want.
httpGet:
path: /metrics
port: 8091
initialDelaySeconds: 10
periodSeconds: 5
livenessProbe:
httpGet:
path: /metrics
port: 8091
initialDelaySeconds: 60
periodSeconds: 20
resources:
requests:
cpu: "50m"
memory: "128Mi"
limits:
memory: "512Mi"