{
  "id": "topic:aggregated-api-server",
  "_kind": "Topic",
  "_file": "domain/products/krate.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "Aggregated API Server Pattern",
    "description": "A Kubernetes extension mechanism where a custom API server registers\nitself with the main kube-apiserver via an APIService resource. Requests\nto the custom API group are proxied to the aggregated server, which can\nuse any backing store (Postgres, Redis, etc.) instead of etcd. This\nenables high-volume mutable state (e.g., pull request comments, pipeline\nlogs) to live in a relational database while still being accessible\nthrough the standard Kubernetes API surface — kubectl, RBAC, admission\nwebhooks, and watch semantics all work transparently. Krate uses this\npattern for its 23 data-plane resource kinds.\n"
  },
  "outgoingEdges": [
    {
      "from": "topic:aggregated-api-server",
      "to": "domain:platform-engineering",
      "kind": "applies_to"
    },
    {
      "from": "topic:aggregated-api-server",
      "to": "domain:software-engineering",
      "kind": "applies_to"
    }
  ],
  "incomingEdges": [
    {
      "from": "domain:platform-engineering",
      "to": "topic:aggregated-api-server",
      "kind": "contains",
      "attributes": {
        "notes": "K8s API extension pattern used by platform engineering"
      }
    }
  ]
}