forked from hashicorp/consul-k8s
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Log envoy config for mesh gateways on test failures (hashicorp#718)
If the mesh gateway tests fail, the acceptance tests will now write two files <PODNAME>-envoy-configdump.json and <PODNAME>envoy-clusters.json which will have information from the envoy admin /config_dump endpoint and /clusters endpoint. Currently we write the outputs of `kubectl logs POD` and `kubectl describe POD` for the acceptance tests, but while debugging EKS acceptance test failures, it was hard to know from our existing logs whether the mesh gateway itself is unreachable or if the consul servers behind it are unhealthy. We'd be able to tell this from looking at the envoy config dump and cluster config to see what envoy's view of the consul servers are.
- Loading branch information
1 parent
e00c696
commit 146833a
Showing
2 changed files
with
30 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters