kiali: [Operator/UI] istio_namespace doesn't work with istio_component_namespaces

General remarks

https://github.com/kiali/kiali-operator/blob/master/deploy/kiali/kiali_cr.yaml#L47-L65

Describe the bug

istio_namespace is ignored when istio_component_namespaces is present.

Screen Shot 2020-09-10 at 2 54 33 PM

Versions used Kiali: 1.23.0 Istio: 1.7.0 Kubernetes flavour and version: 1.17.5

To Reproduce

istiod -> istio-system
istio-ingressgateway -> istio-system
kiali -> istio-observe
prometheus -> istio-observe

istio_component_namespaces:
  prometheus: istio-observe
istio_namespace: istio-system

Expected behavior

The namespace for istiod and istio-ingressgateway should be inherited from istio_namespace since it’s not defined in istio_component_namespaces. It shouldn’t use Kiali’s deploy namespace.

Minor bug, the workaround is just to define the istiod and istio-ingressgateway namespaces separately

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 21 (10 by maintainers)

Most upvoted comments

@xeviknal Thanks, I’ll try out 1.24 when it’s out

PatrickDuncan on Sep 16, 2020

How exactly are we supposed to configure Kiali when components such as Prometheus, Grafana and Jaeger are in other namespaces?

Prometheus: https://github.com/kiali/kiali-operator/blob/v1.26/deploy/kiali/kiali_cr.yaml#L481-L520 Grafana: https://github.com/kiali/kiali-operator/blob/v1.26/deploy/kiali/kiali_cr.yaml#L395-L449 Jaeger: https://github.com/kiali/kiali-operator/blob/v1.26/deploy/kiali/kiali_cr.yaml#L522-L567

jmazzitelli on Nov 5, 2020

@PatrickDuncan a solution is in the way in here: https://github.com/kiali/kiali/pull/3211 Feel free to add any review or comment in there.

xeviknal on Sep 15, 2020

I am fine also by moving this namespace into each component_status object in grafana, prometheus, jaeger and istio. Does this makes more sense? Just to specify the namespace next to each component?

I think that would make sense - otherwise, we are requiring people to put values in the istio-component-namespaces field and they have to know to enter (and not have any typos in) the key names “prometheus” and “grafana”, etc.

jmazzitelli on Sep 14, 2020

@jmazzitelli If this field is removed, I’d need another field for users to specify where they istio components are installed in. Otherwise, we will be auto-discovering and guessing values which I don’t think is a good idea.

I am fine also by moving this namespace into each component_status object in grafana, prometheus, jaeger and istio. Does this makes more sense? Just to specify the namespace next to each component?

xeviknal on Sep 14, 2020