Revision 517946092c83293f02eab594a77fd87ff3649405 authored by Marco Iorio on 06 June 2024, 16:54:57 UTC, committed by Julian Wiedmann on 18 June 2024, 05:58:31 UTC
Let's explicitly mention that the output of the cilium-dbg troubleshoot command refers to the connections from the agents to the local clustermesh-apiserver when KVStoreMesh is enabled, as potentially confusing. In this case, it is expected that the output is the same for all the clusters the agents are connected to. Differently, the connectivity to the remote clusters can be troubleshooted using the dedicated kvstoremesh-dbg command. Suggested-by: Bruno M. Custódio <bruno@isovalent.com> Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
1 parent c46e6be
| File | Mode | Size |
|---|---|---|
| ISSUE_TEMPLATE | ||
| actions | ||
| workflows | ||
| ariane-config.yaml | -rw-r--r-- | 3.2 KB |
| gcp-vm-startup.sh | -rw-r--r-- | 892 bytes |
| kind-config-ipv6.yaml | -rw-r--r-- | 523 bytes |
| kind-config.yaml | -rw-r--r-- | 500 bytes |
| kind-config.yaml.tmpl | -rw-r--r-- | 565 bytes |
| labeler.yml | -rw-r--r-- | 345 bytes |
| maintainers-little-helper.yaml | -rw-r--r-- | 500 bytes |
| pull_request_template.md | -rw-r--r-- | 1.2 KB |
| renovate.json5 | -rw-r--r-- | 16.2 KB |
Computing file changes ...
