mirror of
https://github.com/status-im/consul.git
synced 2025-02-26 20:30:39 +00:00
c9c49ea3a2
* new docs for consul and consul-k8s troubleshoot command * add changelog * add troubleshoot command * address comments, and update cli output to match * revert changes to troubleshoot upstreams, changes will happen in separate pr * Update .changelog/16284.txt Co-authored-by: Nitya Dhanushkodi <nitya@hashicorp.com> * address comments * update trouble proxy output * add missing s, add required fields in usage --------- Co-authored-by: Nitya Dhanushkodi <nitya@hashicorp.com>
38 lines
1.6 KiB
Plaintext
38 lines
1.6 KiB
Plaintext
---
|
|
layout: commands
|
|
page_title: 'Commands: Troubleshoot Upstreams'
|
|
description: >-
|
|
The `consul troubleshoot upstreams` lists the available upstreams in the Consul service mesh from the current service.
|
|
---
|
|
|
|
# Consul Troubleshoot Upstreams
|
|
|
|
Command: `consul troubleshoot upstreams`
|
|
|
|
The `troubleshoot upstreams` lists the available upstreams in the Consul service mesh from the current service.
|
|
|
|
## Usage
|
|
|
|
Usage: `consul troubleshoot upstreams [options]`
|
|
|
|
#### Command Options
|
|
|
|
- `-envoy-admin-endpoint=<value>` - Envoy admin endpoint address for the local Envoy instance.
|
|
Defaults to `127.0.0.1:19000`.
|
|
|
|
## Examples
|
|
|
|
Display all transparent proxy upstreams in Consul service mesh from the current Envoy instance.
|
|
|
|
```shell-session
|
|
$ consul troubleshoot upstreams
|
|
==> Upstreams (explicit upstreams only) (0)
|
|
|
|
==> Upstreams IPs (transparent proxy only) (1)
|
|
[10.4.6.160 240.0.0.3] true map[backend.default.dc1.internal.e08fa6d6-e91e-dfe0-f6e1-ba097a828e31.consul backend2.default.dc1.internal.e08fa6d6-e91e-dfe0-f6e1-ba097a828e31.consul]
|
|
|
|
If you cannot find the upstream address or cluster for a transparent proxy upstream:
|
|
- Check intentions: Tproxy upstreams are configured based on intentions. Make sure you have configured intentions to allow traffic to your upstream.
|
|
- To check that the right cluster is being dialed, run a DNS lookup for the upstream you are dialing. For example, run `dig backend.svc.consul` to return the IP address for the `backend` service. If the address you get from that is missing from the upstream IPs, it means that your proxy may be misconfigured.
|
|
```
|