← WORK
WORK / 2026 SECURITY BUILDING

Tiger — SSL Certificate Inventory

Managed SSL/TLS certificates for the CDN fleet — a tenant-scoped inventory and issuance service on top of cert-manager, with Let's Encrypt account sharding and automated upload to the edge. Backend operational; partner console shipping.

Gocert-managerLet's EncryptKubernetesPostgreSQL

Why

The CDN fleet has two certificate problems at once. It has no single source of truth for certificate material, and it has to clear Let’s Encrypt rate limits at scale. Tiger answers both: an inventory to be that source of truth, and account sharding to stay under the limits.

The inventory is tenant-scoped because the fleet is multi-tenant: every cert row carries a tenant id and access is resolved from the caller’s JWT org claim, so a tenant can only list or fetch its own certificate material — never another tenant’s private keys.

Tiger sits on top of stock cert-manager and adds the inventory, the issuance facade, and the edge upload. The backend is already operational and verifiable; the partner console is still shipping.

Architecture

Two sub-components, each its own repo and image:

  • Control plane — a Gin HTTP service: tenant-scoped inventory plus an issuance facade (POST /certs, import, bundle), with a lean client SDK for consumers. The inventory is the single source of truth for cert material.
  • Uploader — a leader-elected Kubernetes controller: watches cert-manager Secrets and pushes issued certs to the edge (vEdge / EdgeNext). Also serves the shard-picker admission webhook.
G client client control control plane client->control pg Postgres inventory control->pg cert Certificate applied control->cert webhook shard-picker webhook stamps issuerRef cert->webhook certmgr cert-manager orders from Let's Encrypt webhook->certmgr secret issued Secret watched by uploader certmgr->secret pushedge pushed to vEdge / EdgeNext secret->pushedge

Account sharding

New certificates are issued without an issuerRef; the shard-picker webhook assigns one of N ClusterIssuer shards. Each prod shard registers its own Let’s Encrypt account, worked around LE’s account/IP/3h caps by staggering.

Evidence

End-to-end issuance is verifiable on Let’s Encrypt staging via DNS-01: apply a Certificate with no issuer, confirm the webhook fills a staging shard, and confirm the issued Secret is a real LE staging cert. Edge upload is exercised with an upload-targets annotation.

Status

Backend operational and verifiable; the partner console (issue / upload / renew / revoke + activity feed) is shipping.