Appendix. Common Errors
This is a list of errors you may encounter during the course of the exercises and how to fix them. Most of these errors are caused by the minikube cluster or Vagrant VM restarting.
| Error | Solution |
|---|---|
On Kubernetes you get an error: Internal error occurred: failed calling webhook mutate-... Post https://consul-controller-... x509: certificate signed by unknown authority |
Restart the webhook certificate manager: $ kubectl rollout restart \
deploy/consul-webhook-cert-manager \
-n consul |
On Kubernetes, services are not showing up in the UI. |
Check the Consul client logs: $ kubectl logs -l component=client -n consul If you see $ kubectl rollout restart ds/consul-client \
-n consul |
On Kubernetes, the state of the ingress gateway pod is stuck at Init. |
Ensure minikube tunnel is running. |
You get a |
Restart the On Kubernetes, run: $ kubectl rollout restart deployment/frontend On VMs, run: $ sudo systemctl restart frontend |
Metrics aren’t showing up in Consul UI or Grafana. |
Restart Prometheus. On Kubernetes, run: $ kubectl rollout restart \
deploy/prometheus-server -n consul
On VMs, run: $ sudo systemctl restart prometheus |
On VMs, you get an error accessing Birdwatcher: upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: TLS error:.. CERTIFICATE_VERIFY_FAILED ... |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access