No logs in dashboard about skooner

[thiscantbeserious]

@herbrandson it would be awesome if we could have an toast for API-Errors - so that regular users will notice them as well and just don't see nothing. I'll see what I can do when I find time ...

[duckman]

So I dug into things more and it looks like the metrics server doesnt like WebSockets, so I had to disable it on /apis/metrics.k8s.io/.
Here is a rough idea of what my nginx config looks like incase it helps anyone:

	location / {
		include proxy.conf;
		proxy_pass http://k8dash/;
		proxy_http_version 1.1;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection "upgrade";
	}

	location /apis/metrics.k8s.io/ {include proxy.conf;
		proxy_pass http://k8dash/apis/metrics.k8s.io/;
	}

[infrabyte]

[herbrandson]

Hey @infrabyte. I'm so sorry you're having this issue. I haven't heard of anyone running into this before. Would you mind taking at the networking tab in the developer tools and see if there are any errors with the api calls?

[herbrandson]

@thiscantbeserious There's a "toaster" feature in notifier.js. Checkout addUserNotification. Thanks!

[kyleyankan]

I'm also having this issue, and am getting a HTTP 403 on the WSS request.
Request URL: wss:/k8s.ingress.tld/api/v1/namespaces/default/pods?watch=1&fieldSelector=metadata.name%3Dtest-pod-for-github (modified for public sharing) returns a
Error during WebSocket handshake: Unexpected response code: 403

[alex-tabachuk]

+1

domain -> aws alb -> service in aws eks

[duckman]

I ran into this issue and it turned out to caused by using nginx as a reverse proxy and not setting it up to handle websockets.
So that's working great now, but my metrics stopped working... so I'm working on that now :P.