The new Quay UI V2 is loading external resources from the internet, which makes it incomatible in air gapped or restricted environment (secured by firewalls).

Browser is showing an empty page for 85 seconds, until external http calls timeout out and UI v2 is shown.

Prerequisites

• Quay UI V2 enabled in config-bundle
• User is opening Quay UI v1 in a browser on a host that is in an
  • air gapped environment (without access to internet) or
  • restricted environment, without access to the external internet resources (e.g. firewall)

Reproduction

• User logs into Quay UI v1
• User toggles switch from Quay UI v1 to v2 or reloads/refreshes the active v2 UI
  • As soon as the switch is activated, the browser is showing an empty screen for 85 seconds
  • Reason for this seem to be 2 javascript resources, that are loaded from the internet
    • https://checkout.stripe.com/checkout.js

• • • https://cdn.statuspage.io/se-v2.js

• • As these resources are not reachable from the users host, the browser waits until the default connection timeout is reached and only shows the new UI v2 once the requests have timed out
    • See developer tools output
       
    • Note: Firewalls might behave differently in our case the request is not rejected and times out.

Expectation

• Javascript resources should either be packaged together with Quay (as others like jquery, ...)
• If these resources are not absolutely required, we should not block the loading of the UI due to connection timeouts, which are default in air gapped / restricted environments