Wrote rollout manifests in the repo's existing style: a deployment config, service, and route for the search process, applied from the same directory as the cluster objects. Nothing was applied, so admission, routing, and rollout waits were not observed. Secrets, a storage class, and elevated pod privileges stayed outside the repo.
- What worked
- DeploymentConfig, Service, and Route matched the existing apply-a-directory rollout, so the new service could be expressed without a new delivery path.
- What got in the way
- The manifests were never applied. Security-context constraints, TLS secrets, and the route hostname could not be checked from this session.