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
[Multicluster] provide links to external Kialis without requiring istio secrets #6243
Comments
That seems reasonable. Did the former secrets do anything for us other than establish the link? Users would still have to log into the remote Kiali, etc, right? |
AFAIK, that's all the old secrets did for us. It told us the name of the remote cluster and helped us determine the remote kiali URL. |
So how would we handle the situation that someone was already using the experimental feature and has secrets already, but isn't trying to set up our new MC ability? Just documentation/release notes to delete the secrets and optionally add this proposed config? |
They still need the istio secrets - those are required for istio MC to work. They just need the kiali secrets so kiali can work. |
This isn't working like I would expect. I want to use this feature for Kiali to show multiple clusters on the "mesh" page without giving access to those clusters. My kiali config in the "east" cluster looks like:
|
I didn't look at any of this but... |
The |
@nrfox right, this feature was implemented partly, I saw your PR, so assigning this to you, thank you. |
Today Kialis in "single cluster" mode require secrets to create links to external kialis. This is effectively putting the Kiali instance in "multi cluster" mode. There needs to be a way to for Kiali to generate links to external Kialis without requiring access to external clusters. This can be a simple as adding a config value that Kiali would use to generate these links. Something like
externalKialis: {"name": ..., "url": ...}
.The text was updated successfully, but these errors were encountered: