Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-3873

[KIALI] Kiali ingress.host accepted in the SMCP but is not configured properly in Kiali CR

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Normal
    • OSSM 2.4.0
    • OSSM 2.2.6, OSSM 2.3.2
    • Kiali, Maistra
    • None
    • Low

    Description

      The SMCP CR accepts the configuration of customized ingress.hosts for Kiali, however this is not configured on the Kiali CR and route doesn't change.

      spec:
      addons:
      grafana:
      enabled: true
      install:
      service:
      ingress:
      enabled: true
      jaeger:
      install:
      ingress:
      enabled: true
      storage:
      type: Memory
      kiali:
      enabled: true
      install:
      dashboard:
      enableGrafana: true
      enablePrometheus: true
      enableTracing: true
      service:
      ingress:
      enabled: true
      hosts:

      • kiali-istio-system.<my-custom-subdomain>

      In the appliedValues this is configured as well:

      kiali:
      dashboard:
      enableGrafana: true
      enablePrometheus: true
      enableTracing: true
      viewOnlyMode: false
      enabled: true
      ingress:
      enabled: true
      hosts:

      • kiali-istio-system.<my-custom-subdomain>
        install: true
        resourceName: kiali

      The problem seems to be in the operator helm resources as the Kiali CR only gets ingress.enabled value:

      https://github.com/maistra/istio-operator/blob/5b41497a44e22dbaba6d2813117061ae6a9caa9e/resources/helm/v2.3/istio-telemetry/kiali/templates/kiali-cr.yaml#L29

      For this to be configured we would probably need to implement the ingress.override_yaml which currently is not supported, since manually changing this in the Kiali CR the operator gets an error with not enough permissions to change Openshift Route specs:

      ingress:
      enabled: true
      override_yaml:
      spec:
      host: kiali-istio-system.<my-custom-subdomain>

       "message": "Route kiali: Failed to create object: b'{\"kind\":\"Status\",\"apiVersion\":\"v1\",\"metadata\":{},\"status\":\"Failure\",\"message\":\"Route.route.openshift.io \\\\\"kiali\\\\\" is invalid: [spec.host: Forbidden: you do not have permission to set the host field of the route, spec.to.name: Required value]\",\"reason\":\"Invalid\",\"details\":{\"name\":\"kiali\",\"group\":\"route.openshift.io\",\"kind\":\"Route\",\"causes\":[

      {\"reason\":\"FieldValueForbidden\",\"message\":\"Forbidden: you do not have permission to set the host field of the route\",\"field\":\"spec.host\"}

      ,

      {\"reason\":\"FieldValueRequired\",\"message\":\"Required value\",\"field\":\"spec.to.name\"}

      ]},\"code\":422}
      n'",

      It would be important to have this implemented in order to work with router sharding since we can already change grafana and prometheus routes to the desired host.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rhn-support-andcosta Andre Costa
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: