How GitLab Pages uses the GitLab API to serve content

What this post added

Introduced API-based configuration for GitLab Pages, replacing the legacy config.json file and NFS traversal. The Pages daemon now sources domain configuration from an internal API endpoint (`/api/v4/internal/pages?domain=...`) on demand and caches it. This significantly reduced daemon startup time on GitLab.com from ~25 minutes to under a minute. The post also details the transition plan to object storage and the potential for Kubernetes deployment, and provides guidance for self-managed instances to enable API-based configuration.