Description of problem:

When a user happens to be the one who triggers auto-scaling, the message displayed is as follows:

This is problematic. 

• Section (1) talks about an "Error creating notebook container".
  It's not an error yet. the pod is pending, waiting for the new node to come online. 
• Section (2) has a Red exclamation point (scary!).
  But if you read the message, it's good news: this pod has triggered a scale up and now we just need to wait for the node to come online fully. 
• Most users will get scared by this and will hit the blue "close" button, which cancel their pod/notebook requests. 

Compared to the way that JupyterHub worked, this is a regression, IMO. 

Instead, we should have an "info" tag, or maybe a "warning" saying this might take longer than usual due to having to wait for the node to come online. 

By Comparison, this message is warranted:

Essentially, it says "your pod is too big to fit anywhere, and even if add a machine, it won't fit there either, so I won't bother". 

In this case, we do want to tell the user to try something else because no amount of patience will work. 

Prerequisites (if any, like setup, operators/versions):

Use a cluster where auto-scaling is enabled. 

Steps to Reproduce

1. Ask for a large enough notebook that it forces a scale-up of the environment. 

Actual results:

See screenshot above. 

Expected results:

I would want to see a softer message that explains that it's actually ok, this is not an error, and if the user is patient, their notebook will spin up as soon as the new node is ready. 

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

1.16

Workaround:

Knowing that you should do nothing and NOT CLICK ON THE CLOSE BUTTON. 

Additional info: