Added a workload-identity deployment for the intake worker on the existing private cluster, including a temp volume for page rendering under a read-only root. The workload was not applied to a cluster.
- What worked
- Matching the current pod pattern (private cluster, identity, read-only root) kept the new service inside the same boundary as the other APIs.
- What got in the way
- The real identity client id still has to be bound, and nothing was scheduled, so pull, identity, and volume behavior were not observed.