Environment

  1. Get the version of Kubernetes that you run in each cluster.

      kubectl version -o yaml
      
  2. List the infrastructure provider that hosts your environment, such as AWS or GCP.

  3. In multicluster setups, list the regions and zones where your clusters run.

Istio

  1. Get the Istio version that you run in each cluster.

      istioctl version
      
  2. Get the configuration that you used for your Istio installation.

    • Helm:
        helm get all <release-name> --namespace istio-system > istio_installation_helm.yaml
        
    • Gloo Operator:
        kubectl describe servicemeshcontroller -n gloo-mesh managed-istio
        
  3. Get the logs for the istiod control plane in the cluster where you notice service mesh issues.

      kubectl logs -n istio-system deploy/istiod | > istiod-logs.txt
      

Solo UI

  1. Get the Helm manifests for the Solo UI management chart release.

      helm get all --kube-context ${context1} management --namespace solo-enterprise > solo_ui_mgmt_helm.yaml
      
  2. For multicluster setups, get the Helm manifests for the Solo UI relay chart releases. Repeat this command for all other clusters in your setup.

      helm get all --kube-context ${context2} relay --namespace solo-enterprise > solo_ui_relay_helm.yaml
      

Issue

  1. Provide a detailed description of the issue. Make sure to include the following information:

    • If reproducible, steps to reproduce the issue.
    • Number of clusters in a multicluster setup.
    • Federated trust details, such as self-signed certificates or certificates provided by a certificate management provider.
    • High-level diagram of the clusters showing where Solo Enterprise for Istio components and applications are running.
    • If you use segments, details of how the segments are configured.
    • Details of the Istio installation and configuration.
  2. Describe the impact of the issue. For example, the issue might block an update or a demo, or cause the loss of data or an entire system.

  3. Export the relevant configuration files that are related to the issue. For example, you can use the following command in each cluster to create Istio bug reports that you can attach to your support request.

      istioctl bug-report --istio-namespace istio-system