Please try again later.
responseStatusCode: 503 retryAfter: 30s ``` ### Example of Customizing Cold-Start Waiting Page with ConfigMap As an alternative, it’s possible to define cold-start waiting page parameters per namespace in a `ConfigMap` with the same keys `coldStartWaitingPageBody` / `coldStartWaitingPageStatusCode` / `coldStartWaitingPageRetryAfter` and then setting `coldStartWaitingPageConfigMapRef` on trigger metadata. ```yaml spec: triggers: - type: kedify-http metadata: coldStartWaitingPageEnabled: "true" coldStartWaitingPageConfigMapRef: waiting-page-cm ``` The `ConfigMap` example: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: waiting-page-cm data: coldStartWaitingPageBody: |-Please try again later.
coldStartWaitingPageStatusCode: "503" coldStartWaitingPageRetryAfter: "60s" ``` ### Example of Customizing Cold-Start Waiting Page with Inlined Configuration The global and namespaced defaults can be further fine tuned by inlining directly on the `ScaledObject` as ```yaml spec: triggers: - type: kedify-http metadata: coldStartWaitingPageEnabled: "true" coldStartWaitingPageBody: |-Please try again later.
coldStartWaitingPageStatusCode: "503" coldStartWaitingPageRetryAfter: "60s" ``` ## Custom Maintenance Page When you want to make the application temporarily unavailable for any reasons, e.g. scheduled maintenance, and prevent traffic reaching your service, you can configure Kedify to serve a static maintenance page instead of the default 503 Service Unavailable response. This allows you to inform users about the maintenance and provide an estimated time for when the service will be back online. There is a 256 KiB limit on the size of the maintenance page body. This is also enabled per `ScaledObject` that has `kedify-http` scaler with trigger metadata `maintenancePageEnabled` set to `true`: ```yaml spec: triggers: - type: kedify-http metadata: maintenancePageEnabled: "true" ``` The difference is that when maintenance page is enabled, the traffic for this particular `ScaledObject` is served directly by the `interceptor` **always** and http metrics for the target are discarded by the `scaler`. The `/queue` endpoint on the `interceptor` will still show the metrics as if they were accounted, but `scaler` discards the values and sets `active` status for particular application to `false`. The default status code is `503`, and HTTP body reads a simple message: ```plaintext Service is temporarily under maintenance. Please try again later. ``` ### Customizing Maintenance Page with Global Defaults These defaults can be configured globally in the Kedify HTTP Addon helm chart: ```yaml interceptor: maintenancePage: body: |-Please try again later.
responseStatusCode: 503 ``` ### Example of Customizing Maintenance Page with ConfigMap As an alternative, it’s possible to define maintenance page parameters per namespace in a `ConfigMap` with the same keys `maintenancePageBody` / `maintenancePageStatusCode` and then setting `maintenancePageConfigMapRef` on trigger metadata. ```yaml spec: triggers: - type: kedify-http metadata: maintenancePageEnabled: "true" maintenancePageConfigMapRef: maintenance-page-cm ``` The `ConfigMap` example: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: maintenance-page-cm data: maintenancePageBody: |-Please try again later.
maintenancePageStatusCode: "503" ``` ### Example of Customizing Maintenance Page with Inlined Configuration The global and namespaced defaults can be further fine tuned by inlining directly on the `ScaledObject` as ```yaml spec: triggers: - type: kedify-http metadata: maintenancePageEnabled: "true" maintenancePageBody: |-Please try again later.
maintenancePageStatusCode: "503" ``` ## Configuration Precedence Maintenance page and cold-start waiting page configurations follow this precedence (highest to lowest): 1. Inline configuration in ScaledObject 2. Namespace-scoped `ConfigMap` referenced by `maintenancePageConfigMapRef` or `coldStartWaitingPageConfigMapRef` 3. Global defaults configured on http-add-on chart The `ConfigMaps` for `maintenancePage` and `coldStartWaitingPage` can be the same. ## Continue with this topic **Choose:** [Scale to zero or keep warm capacity](https://docs.kedify.io/guides/scale-to-zero/). **Reference:** [HTTP scaler and inference configuration](https://docs.kedify.io/reference/http-scaler/). **Related capabilities:** [HTTP scaling](https://docs.kedify.io/scalers/http-scaler/) · [Diagnose HTTP requests with logs and error metrics](https://docs.kedify.io/how-to/kedify-proxy-access-logs-and-metrics/). --- Canonical: https://docs.kedify.io/how-to/configure-waiting-and-maintenance-pages-for-http-scaler/ Source: src/content/docs/how-to/configure-waiting-and-maintenance-pages-for-http-scaler.md Documentation index: https://docs.kedify.io/llms.txt