Service to service troubleshooting

[curtbushko]

Things to still do:

• Clean up text strings based on designer input
• Add acceptance test when troubleshoot package is working with validation
• Remove hardcoded replace in go.mod when branches are merged into the consul repo

Changes proposed in this PR:

How I've tested this PR:

How I expect reviewers to test this PR:

Checklist:

• Tests added
• CHANGELOG entry added

  HashiCorp engineers only, community PRs should not add a changelog entry.
  Entries should use present tense (e.g. Add support for...)

[ndhanushkodi]

Amazing!! Left a few comments!

This could definitely come in a future PR, but could we add a case for testing with a config entry (deploy like static-server1 and static-server2 and do a splitter between them) to the acceptance test?

[ndhanushkodi]

Could we validate that exactly one or the other is provided also? That way it's known that both aren't required early on. cc @malizz this would be good to add the the consul CLI as well if it's not already there!

[curtbushko]

I think I have it:

None:

$ ./cli/bin/consul-k8s troubleshoot proxy -pod static-client-5644c6f9c9-rl8kf

! Invalid argument: -upstream-envoy-id OR -upstream-ip is required.
Please run consul troubleshoot upstreams to find the corresponding upstream.

Both:

$ ./cli/bin/consul-k8s troubleshoot proxy -pod static-client-5644c6f9c9-rl8kf -upstream-ip 10.96.217.21 -upstream-envoy-id 1234
! Invalid argument: -upstream-envoy-id OR -upstream-ip is required.
Please run consul troubleshoot upstreams to find the corresponding upstream.

[ndhanushkodi]

Amazing!!!