-
Notifications
You must be signed in to change notification settings - Fork 479
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
Fullscreen mode for graphs #3309
Comments
Hi @thearegee, we are looking at having fullscreen options for pages in the UI. Also, we do already offer "kiosk mode" for embedding kiali into other places. See Embedding Kiali, maybe this is what you are looking for. |
@thearegee I'm currently working the fullscreen options (full monitor dimensions) right now: #3155 |
@jshaughn thank you for sending me that, I never saw that in the documentation. It is pretty close to what I want and a great start for my project. It would be good if I could toggle the header off: It would also be powerful if we could select display options: With query params, so I could embed this into a dashboard with animations on and other options. By the way, we love Kiali at YNAP 😃 |
Thanks, @thearegee! As for the header, I thought we fixed that in v1.21 *(see #2946). Are you using an older version? |
we are on |
I would love to see some of the above added but I'm happy to close this |
Thanks, @thearegee. We are actively looking at the F11-style full-screen options and it may show up in a near release if it's feasible. |
Problem
I want to include in our documentation and our out of hours support application a quick architecture / topology diagram of our stack. There are various tools available but they go out of date quickly. Kiali graph generates a dynamic an realtime snapshot of our infrastructure, simple example shown below:
However this is embedded within Kiali, I would like to be able to use this elsewhere.
Solution
I would like Kiali to offer a fullscreen mode that is acessible via a URL (query param option maybe), this could offer the following user flows:
I think this would be a really simple yet powerful big for the platform.
The text was updated successfully, but these errors were encountered: