9 Commits (99f270b4fd98164369d4c387308265969e24a7fc)

Author	SHA1	Message	Date
Nitya Dhanushkodi	8dab825c36	troubleshoot: fixes and updated messages (#16294)	2 years ago
malizz	c10ba43eb3	get clusters from route if listener uses RDS (#16243)	2 years ago
malizz	ba862ab6ad	troubleshoot basic envoy stats for an upstream (#16215) ... * troubleshoot basic envoy stats for an upstream * remove envoyID arg	2 years ago
malizz	f5391ef142	update troubleshoot CLI, update flags and upstreams output (#16211) ... * update troubleshoot CLI, update flags and upstreams output * update troubleshoot upstreams output	2 years ago
Nitya Dhanushkodi	1f25289048	troubleshoot: output messages for the troubleshoot proxy command (#16208)	2 years ago
malizz	0a544809c9	get upstream IPs (#16197) ... * get upstream IPs * separate test data * fix lint issue * fix lint issue	2 years ago
malizz	9881aa3f39	add cert tests (#16192)	2 years ago
malizz	3be514ac02	exclude inbound/outbound listeners from upstreams output (#16184)	2 years ago
Nitya Dhanushkodi	b8b37c2357	refactor: remove troubleshoot module dependency on consul top level module (#16162) ... Ensure nothing in the troubleshoot go module depends on consul's top level module. This is so we can import troubleshoot into consul-k8s and not import all of consul. * turns troubleshoot into a go module [authored by @curtbushko] * gets the envoy protos into the troubleshoot module [authored by @curtbushko] * adds a new go module `envoyextensions` which has xdscommon and extensioncommon folders that both the xds package and the troubleshoot package can import * adds testing and linting for the new go modules * moves the unit tests in `troubleshoot/validateupstream` that depend on proxycfg/xds into the xds package, with a comment describing why those tests cannot be in the troubleshoot package * fixes all the imports everywhere as a result of these changes Co-authored-by: Curt Bushko <cbushko@gmail.com>	2 years ago