-
Notifications
You must be signed in to change notification settings - Fork 117
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
Description of kiali_urls. Kiali URL to cluster name mapping. #672
Conversation
Server PR kiali/kiali#6452 |
Co-authored-by: John Mazzitelli <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Never mind these settings are used by the operator/helm-chart but are not part of the kiali config
|
It looks like they're present in the helm chart as well: https://github.com/kiali/helm-charts/blob/master/kiali-server/values.yaml#L96-L100 |
no, these are very important. This is how the operator (and helm charts) sets up the kiali remote cluster secrets. don't remove these :) kiali-operator/roles/default/kiali-deploy/tasks/main.yml Lines 722 to 736 in 8038592
kiali-operator/roles/default/kiali-deploy/templates/openshift/deployment.yaml Lines 125 to 129 in 8038592
|
We actually don't put them in the Kiali Config object because they aren't used by the server at all - these are one of the few settings that are for the operator (and helm charts) only - i.e. used only for installation. The Server never uses these settings so that is why they aren't in the Config object. |
Ah alright that makes sense. I'm always unsure of which configuration on the CR is just for the operator and which is for the kiali config. |
This is why I try to always make the Config object match the CR - only because its confusing if they don't match ("why is this in the CR but not in the Config object?"). I actually went against my instincts when I did not include these secret/cluster settings in the Config object. I convinced myself it was the right thing to do because these settings are essentially useless to the server - the server should never have a reason to look up their values. |
Well if there's ever a Kiali v2 with some breaking changes, perhaps we can separate the two on the CR. Something like
|
Issue kiali/kiali#6243