"Please hold" landing pages for slow scale from zero scenarios #874

worldspawn · 2024-01-04T05:51:10Z

Proposal

If the service is scaling from zero and maybe needs to wait for a new node to provision a nicer user XP might be to just land on a page that says "Teamcity is starting up... please wait". Could be enabled and configured in the http scaled object resource. MVP could be a very simple page saying "{SomeValueFromHttpResource} is start up please wait" and it polls.

Use-Case

Nodes can be slow (well a cpl of minutes) to start up. The experience scaling from zero in this case is pretty ordinary. The default wait time is only 30s and then you Bad Gateway or something like that.

I nice web page telling people to sit tight and wait for the magic would be a lot nicer.

Is this a feature you are interested in implementing yourself?

Maybe

Anything else?

No response

JorTurFer · 2024-01-04T20:09:06Z

Hum...
It's an interesting feature, but I'm not sure about how we can implement this. I mean, a simple message it's nice, but I'm afraid about if this has to scale to serve complex HTML and how we can do this.
WDYT @tomkerkhove ?
Maybe we can allow custom messages for HTTP Errors somehow (at HTTPScaledObject level)

thincal · 2024-01-19T00:11:34Z

I come up with similar requirement, just customizing the error message is enough for me.

JorTurFer · 2024-01-19T07:01:25Z

@tomkerkhove ?

lenglet-k · 2024-02-14T14:01:32Z

i'm interesting too for this feature. Maybe have a light custom HTML by httpsScaleObject. For not afraid user, just only print a loading message.

zroubalik · 2024-02-14T15:20:24Z

Yeah, this should be imho configurable. And serve the light custom HTML for users that want to. They should be able to provide their custom HTLM file.

JorTurFer · 2024-02-14T16:01:31Z

make sense, but maybe I'd add another CRD for this, as it's something that can be reusable (or not). WDYT?
I guess that we could include the info in a more structured way, by content and return code

thincal · 2024-03-06T10:24:23Z

by content and return code

+1

thincal · 2024-04-12T15:15:28Z

Any progress here

JorTurFer · 2024-04-12T15:31:19Z

No, currently there isn't anybody working on this, are you willing to tackle it?

thincal · 2024-04-14T14:06:50Z

No, currently there isn't anybody working on this, are you willing to tackle it?

Yes, I could have a try. My quick idea is to add the customized response content and code into existing http-scaled-object, but it seems that there is suggestion about using a new CRD, could help explain the consideration behind?

JorTurFer · 2024-04-14T15:17:59Z

Yeah, I suggested the new CRD because I can imagine a scenario where you have multiple services behind the proxy, and you want to provide a custom message for all of them.
The new CRD could be just something like:

spec:
  httpStatus: XXX (number)
  html: |
    <html>....</html>

and then, we can include in the HTTPScaledObject with something like:

spec:
  loadingTemplate: xxxxxxx
  minReplicaCount: 0
  ....

Currently, these templates can be cluster scoped and maybe in the future we can support both, clustered and namespaced.
This will keep the HTTPScaledObject cleaner because if you have to introduce the HTML within the HTTPScaledObject, it can introduce a lot of new lines (even more when you want to reuse them)

Does it make sense to you? Maybe I'm overthinking the case, and we could go just adding something inline and iterate in the future if it's something that users use

stale · 2024-06-13T20:54:51Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

calvinbui · 2024-06-26T05:53:39Z

Sablier has this feature: https://acouvreur.github.io/sablier/#/strategies

stale · 2024-08-25T18:47:09Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

stale · 2024-09-01T21:09:23Z

This issue has been automatically closed due to inactivity.

kahirokunn · 2024-10-21T01:24:03Z

It would be great if we could automatically inject JavaScript into the HTML to implement polling and have the feature automatically access the HTTP server as soon as it becomes available.

julopezc-acciona · 2024-11-29T12:04:33Z

I have a annotation using https://github.com/kubernetes/ingress-nginx/ which allows to handle custom http errors:

    nginx.ingress.kubernetes.io/custom-http-errors: "502"
    nginx.ingress.kubernetes.io/default-backend: keda-autoscale-502-error-svc

keda-autoscale-502-error-svc is a service that lives in the same namespace that keda is installed and has a simple nginx deployment with a default.conf that reloads the current page:

    server {
        listen 80;
        location / {

            add_header Content-Type text/html;
            return 200 '<!DOCTYPE html>
            <html>
            <head>
                <title>Application Scaling</title>
                <style>
                    body {
                        font-family: Arial, sans-serif;
                        text-align: center;
                        padding-top: 50px;
                        background-color: #f0f0f0;
                    }
                    h2 {
                        color: #333;
                    }
                    p {
                        color: #666;
                    }
                </style>
                <script>
                    setTimeout(function() {
                        window.location.reload();
                    }, 5);
                </script>
            </head>
            <body>
                <h2>Application $host scaling up.</h2>
                <p>Please wait, this page will automatically refresh...</p>
            </body>
            </html>';
        }
    }

florianbeer · 2024-11-29T12:23:33Z

@julopezc-acciona did you set the custom-http-errors annotation globally via ConfigMap?
According to nginx' documentation the default-backend works in conjunction with the former annotation but only in the same namespace. Do you have an ingress object in keda's namespace?

julopezc-acciona · 2024-12-02T12:57:25Z

Yes, I do have a ingress object in keda's namespace, then it routes the incoming traffic to the relevant service in another namespace

florianbeer · 2024-12-03T08:50:57Z

Then this probably won't work for my use case. I'd need one central "wake up" page for multiple workloads with ingresses in their own namespaces.

But very nice solution nevertheless 👍

keda-automation added this to Roadmap - KEDA HTTP Add-On Jan 4, 2024

github-project-automation bot moved this to To Triage in Roadmap - KEDA HTTP Add-On Jan 4, 2024

JorTurFer mentioned this issue Apr 4, 2024

Roadmap to GA #911

Open

19 tasks

JorTurFer added the help wanted Extra attention is needed label Apr 4, 2024

stale bot added the stale All issues that are marked as stale due to inactivity label Jun 13, 2024

zroubalik removed the stale All issues that are marked as stale due to inactivity label Jun 14, 2024

stale bot added the stale All issues that are marked as stale due to inactivity label Aug 25, 2024

stale bot closed this as completed Sep 1, 2024

github-project-automation bot moved this from To Triage to Done in Roadmap - KEDA HTTP Add-On Sep 1, 2024

JorTurFer reopened this Sep 2, 2024

stale bot removed the stale All issues that are marked as stale due to inactivity label Sep 2, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

"Please hold" landing pages for slow scale from zero scenarios #874

"Please hold" landing pages for slow scale from zero scenarios #874

worldspawn commented Jan 4, 2024

JorTurFer commented Jan 4, 2024 •

edited

Loading

thincal commented Jan 19, 2024

JorTurFer commented Jan 19, 2024

lenglet-k commented Feb 14, 2024

zroubalik commented Feb 14, 2024

JorTurFer commented Feb 14, 2024 •

edited

Loading

thincal commented Mar 6, 2024

thincal commented Apr 12, 2024

JorTurFer commented Apr 12, 2024

thincal commented Apr 14, 2024 •

edited

Loading

JorTurFer commented Apr 14, 2024 •

edited

Loading

stale bot commented Jun 13, 2024

calvinbui commented Jun 26, 2024

stale bot commented Aug 25, 2024

stale bot commented Sep 1, 2024

kahirokunn commented Oct 21, 2024

julopezc-acciona commented Nov 29, 2024

florianbeer commented Nov 29, 2024

julopezc-acciona commented Dec 2, 2024

florianbeer commented Dec 3, 2024

"Please hold" landing pages for slow scale from zero scenarios #874

"Please hold" landing pages for slow scale from zero scenarios #874

Comments

worldspawn commented Jan 4, 2024

Proposal

Use-Case

Is this a feature you are interested in implementing yourself?

Anything else?

JorTurFer commented Jan 4, 2024 • edited Loading

thincal commented Jan 19, 2024

JorTurFer commented Jan 19, 2024

lenglet-k commented Feb 14, 2024

zroubalik commented Feb 14, 2024

JorTurFer commented Feb 14, 2024 • edited Loading

thincal commented Mar 6, 2024

thincal commented Apr 12, 2024

JorTurFer commented Apr 12, 2024

thincal commented Apr 14, 2024 • edited Loading

JorTurFer commented Apr 14, 2024 • edited Loading

stale bot commented Jun 13, 2024

calvinbui commented Jun 26, 2024

stale bot commented Aug 25, 2024

stale bot commented Sep 1, 2024

kahirokunn commented Oct 21, 2024

julopezc-acciona commented Nov 29, 2024

florianbeer commented Nov 29, 2024

julopezc-acciona commented Dec 2, 2024

florianbeer commented Dec 3, 2024

JorTurFer commented Jan 4, 2024 •

edited

Loading

JorTurFer commented Feb 14, 2024 •

edited

Loading

thincal commented Apr 14, 2024 •

edited

Loading

JorTurFer commented Apr 14, 2024 •

edited

Loading