Antonin Stefanutti

Yes, that's surprising the cAdvisor logs are empty. I've checked on one of my setups and can see lots of statements. Could you check the events for the cAdvisor pods,...

This looks normal. Could you run: ``` $ kubectl get --raw "/api/v1/namespaces/cadvisor/pods/cadvisor-jlwb9/proxy/api/v2.0/spec?recursive=true" ```

Thanks, this is clearly the issue. Here is the output that I have: ```console $ kubectl get --raw "/api/v1/namespaces/cadvisor/pods/cadvisor-rd24x/proxy/api/v2.0/spec?recursive=true" {"/":{"creation_time":"2021-01-28T11:27:47.669999981Z","has_cpu":true,"cpu":{"limit":1024,"max_limit":0,"mask":"0-3"},"has_memory":true,"memory":{"limit":3959975936,"reservation":8796093018112,"swap_limit":104853504},"has_custom_metrics":false,"has_processes":false,"processes":{},"has_network":true,"has_filesystem":true,"has_diskio":true}... ``` Could you run: ``` $ kubectl get --raw "/api/v1/namespaces/cadvisor/pods/cadvisor-jlwb9/proxy"...

Thanks, if your cluster supports it, it'd be useful to run, as a final check: ``` $ kubectl debug -it -n cadvisor cadvisor-jlwb9 --image=busybox # curl http://localhost:8080/ ``` For some...

Kubebox expects cAdvisor to be deployed in the `cadvisor` namespace. Also there are a couple of things to be done to make sure cAdvisor is configured for the container runtime...

@widnyana it's `kubectl debug`: https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/#ephemeral-container-example. I forgot to add `kubectl` by mistake.

That may depend on the Ingress controller that's configured on your cluster, and if it support target rewriting for path based routing. For example with the NGINX Ingress controller, the...

Thanks for the feedback. Right, that'd be useful to be able to set the base location the reverse proxy is serving from.

By default, when deploying the console with the `Kubernetes.yaml`, it uses the `kubebox` ServiceAccount token to authenticate the console to the API server. It's possible to pass a token, but...

Ah ok, my guess would be that the ServiceAccount you've created is a bit too restrictive. They are a couple of requests that Kubebox assumes it's granted permission to perform,...