Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bug 1976894: Idling a StatefulSet seems to work however accessing the Services Route does not wake up the application ("Application is not available" error page is returned). #1026

Merged
merged 1 commit into from Jan 28, 2022
Merged

Bug 1976894: Idling a StatefulSet seems to work however accessing the Services Route does not wake up the application ("Application is not available" error page is returned). #1026

merged 1 commit into from Jan 28, 2022

Commits on Jan 28, 2022

  1. This commit fixes Bug 1976894. 

    Idling a StatefulSet seems to work however accessing the Services Route does not wake up the application ("Application is not available" error page is returned).
So, with this fix we will return an error saying that we don't support idling of stateful sets as the accessing the routes for the service which is idled does not work. For that a feature work will be required. But, for now we need to add a error whenever a customer tries to idle a stateful service.
    @miheer
    miheer committed Jan 28, 2022
    Configuration menu
    Copy the full SHA
    0315dde View commit details
    Browse the repository at this point in the history