Reporting Bugs

Oh no! You found a bug? We’d love to hear about it.

Product bugs

Search our issue database to see if we already know about your problem and learn about when we think we can fix it. If you don’t find your problem in the database, please open a new issue and let us know what’s going on.

If you think a bug is in fact a security vulnerability, please visit Reporting Security Vulnerabilities to learn what to do.

Kubernetes cluster state archives

If you’re running on Kubernetes, consider including a cluster state archive with your bug report. For convenience, you can run the istioctl bug-report command to produce an archive containing all of the relevant state from your Kubernetes cluster:

  1. $ istioctl bug-report

Then attach the produced bug-report.tgz with your reported problem.

If your mesh spans multiple clusters, run istioctl bug-report against each cluster, specifying the --context or --kubeconfig flags.

The istioctl bug-report command is only available with istioctl version 1.8.0 and higher but it can be used to also collect the information from an older Istio version installed in your cluster.

If you are running bug-report on a large cluster, it might fail to complete. Please use the --include ns1,ns2 option to target the collection of proxy commands and logs only for the relevant namespaces. For more bug-report options, please visit the istioctl bug-report reference.

If you are unable to use the bug-report command, please attach your own archive containing:

  • Output of istioctl analyze:

    1. $ istioctl analyze --all-namespaces

  • Pods, services, deployments, and endpoints across all namespaces:

    1. $ kubectl get pods,services,deployments,endpoints --all-namespaces -o yaml > k8s_resources.yaml

  • Secret names in istio-system:

    1. $ kubectl --namespace istio-system get secrets

  • configmaps in the istio-system namespace:

    1. $ kubectl --namespace istio-system get cm -o yaml

  • Current and previous logs from all Istio components and sidecars. Here some examples on how to obtain those, please adapt for your environment:

    • Istiod logs:

      1. $ kubectl logs -n istio-system -l app=istiod

    • Ingress Gateway logs:

      1. $ kubectl logs -l istio=ingressgateway -n istio-system

    • Egress Gateway logs:

      1. $ kubectl logs -l istio=egressgateway -n istio-system

    • Sidecar logs:

      1. $ for ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}') ; do kubectl logs -l service.istio.io/canonical-revision -c istio-proxy -n $ns ; done

  • All Istio configuration artifacts:

    1. $ kubectl get istio-io --all-namespaces -o yaml

Documentation bugs

Search our documentation issue database to see if we already know about your problem and learn about when we think we can fix it. If you don’t find your problem in the database, please report the issue there. If you want to submit a proposed edit to a page, you will find an “Edit this Page on GitHub” link at the bottom right of every page.