Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-1638

[RFE] Not excluding DeploymentConfig out-of-the box when deploying Kiali in Service Mesh

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • Developer Experience
    • False
    • False
    • Undefined

      1. Proposed title of this feature request
      Not excluding DeploymentConfig out-of-the box when deploying Kiali in Service Mesh

      2. What is the nature and description of the request?
      When deploying in our meshed applications through DeploymentConfig, they are not detected out-of-the-box by Kiali. Every time a control plane is created, the following  Kiali CR  must be configured to not exclude DeploymentConfig by adding this is spec section:

      kubernetes_config:
      excluded_workloads:

      • CronJob
      • Job

      The problem is this CR is controlled by Service Mesh operator (istio-operator) and this  modification can potentially be erased. There needs to be a way to allow this in the operator config directly, or at least make Kiali allow Deployment configs out-of-the box.

      3. Why does the customer need this? (List the business requirements here)

      4. List any affected packages or components.
      Kiali operator
      Service Mesh Operator

              jlongmui@redhat.com Jamie Longmuir
              rhn-support-agomezpr Alvaro Gomez Prado (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: