What happened?
I am accessing via an https terminating proxy server. When I load the page, it appears to come up with the data, but the stylesheet is not loading. When I look a the debug console for the browser, I see
Refused to execute inline event handler because it violates the following Content Security Policy directive: "script-src-attr 'none'". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
I tried this in both Chrome and Safari, and both complain with similar error.
What did you expect to happen?
Page to load completely, including with stylesheets
How can we reproduce it (as minimally and precisely as possible)?
Run kubernetes-dashboard via http behind an https terminating load balancer
Anything else we need to know?
Seems to work if accessing directly via http. It seems to be something about the https termination that triggers the browsers to find the HTML insecure.
What browsers are you seeing the problem on?
Chrome, Safari
What happened? I am accessing via an https terminating proxy server. When I load the page, it appears to come up with the data, but the stylesheet is not loading. When I look a the debug console for the browser, I see
Refused to execute inline event handler because it violates the following Content Security Policy directive: "script-src-attr 'none'". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
I tried this in both Chrome and Safari, and both complain with similar error.
What did you expect to happen? Page to load completely, including with stylesheets
How can we reproduce it (as minimally and precisely as possible)? Run kubernetes-dashboard via http behind an https terminating load balancer
Anything else we need to know? Seems to work if accessing directly via http. It seems to be something about the https termination that triggers the browsers to find the HTML insecure.
What browsers are you seeing the problem on? Chrome, Safari
Kubernetes Dashboard version 2.7.0
Kubernetes version 1.24
Dev environment No response