Operations -> Environments -> Terminal Broken (xterm.css returns 401)

Summary

As an operator, with a deployed Kubernetes environment. When opening the page to connect to the deployed pod terminal, I can't type inside the terminal. The text box is in the wrong place. Also there's a W flying below the text box.

Important note: https://assets.gitlab-static.net/stylesheets/xterm.css returns 401.

Steps to reproduce

1. Added a Kubernetes Cluster on project level
2. Enabled Auto DevOps
3. Deployed the node-express GitLab template to any environment
4. Go to "Operations -> Environments"
5. Click on the Terminal button to access the terminal page

Example Project

Example project is here but I guess special user level might be needed to access the page

https://gitlab.com/Alexand/talk-autodevops/edit

What is the current bug behavior?

1. The text box where we type terminal commands is showing outside the terminal (it also seems a bit buggy)
2. There is a W flying around below the text box.
3. https://assets.gitlab-static.net/stylesheets/xterm.css returns 401

What is the expected correct behavior?

1. Shouldn't see a white text box but rather type inside the terminal

2. No flying W

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

401s on CSS file usually happens when the folder, in this case stylesheets isn't public. Was this file moved lately? Or has this folders permission changed?