Runlevel Health Indicator Signals Wrong State in Runlevel MAINTENANCE

When the Content Server is switched to runlevel MAINTENANCE either during startup or manually, the health/runlevel endpoint signals the server is UP. This makes it impossible to use the indicator for a readiness probe in Kubernetes, because the pod will be added to the services endpoint too early and UAPI clients that listen on a services availability would fail during the creation of the repository connection.

Follow Section, “Runlevel Health Indicator Signals Wrong State in Runlevel MAINTENANCE” for upgrade information.

(CMS-21355)