Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Try to isolate k8s and non-k8s dashboards where its reasonable #129

Open
consideRatio opened this issue Apr 18, 2024 · 1 comment
Open

Comments

@consideRatio
Copy link
Member

If we can decouple one or more dashboards from kubernetes stuff, then maybe we could make use of those for non-k8s deployments of jupyterhub as well?

Currently. I know that the activity dashboard for example is relying entirely on JupyterHub metrics without anything else - so that could be used to trial for a non-k8s-based deployment of jupyterhub.

Related

@consideRatio consideRatio changed the title Try to isolate k8s and non-k8s dashboards Try to isolate k8s and non-k8s dashboards where its reasonable Apr 18, 2024
@Paul2708
Copy link

Paul2708 commented May 7, 2024

Since we are running JupyterHub on Docker Swarm instead of Kubernetes, I tried out the dashboard activity.jsonnet.
After facing issues like google/jsonnet#421 due to my WSL environment, I eventually generated a JSON file that could be easily imported.
The dashboard works just fine.

However, to be fair, the dashboard provided by IDRIS-CNRS visualizes even more JupyterHub metrics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants