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 a dump script to produce an archive containing all of the relevant state from your Kubernetes cluster:
Run via
curl
:$ curl https://raw.githubusercontent.com/istio/istio/release-1.7/tools/dump_kubernetes.sh | sh -s -- -z
Run locally, from the release directory’s root:
$ @tools/dump_kubernetes.sh@ -z
Then attach the produced istio-dump.tar.gz
with your reported problem.
If you are unable to use the dump script, please attach your own archive containing:
Pods, services, deployments, and endpoints across all namespaces:
$ kubectl get pods,services,deployments,endpoints --all-namespaces -o yaml > k8s_resources.yaml
Secret names in
istio-system
:$ kubectl --namespace istio-system get secrets
configmaps in the
istio-system
namespace:$ kubectl --namespace istio-system get cm -o yaml
Current and previous logs from all Istio components and sidecar
Istiod logs:
$ kubectl logs -n istio-system -l app=istiod
All Istio configuration artifacts:
$ kubectl get $(kubectl get crd --no-headers | awk '{printf "%s,",$1}END{printf "attributemanifests.config.istio.io\n"}') --all-namespaces
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 navigate to the page with the problem, then select the gear menu at the top right of this page, and finally chose Report a Site Bug.