-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
If there are two control planes in the cluster, istio-must-gather fails to capture the complete data and shows the following errors in the log:
[must-gather-8lrn7] POD 2023-05-04T10:18:25.803747800Z Dumping resource istio-system2...
[must-gather-8lrn7] POD 2023-05-04T10:18:25.952326032Z error: the server doesn't have a resource type "istio-system2"
[must-gather-8lrn7] POD 2023-05-04T10:18:25.955040329Z
[must-gather-8lrn7] POD 2023-05-04T10:18:25.955040329Z Dumping resource ns/...
[must-gather-8lrn7] POD 2023-05-04T10:18:26.017946592Z error: arguments in resource/name form must have a single resource and name
[must-gather-8lrn7] POD 2023-05-04T10:18:26.024347518Z
[must-gather-8lrn7] POD 2023-05-04T10:18:26.024347518Z Dumping resource ns/...
[must-gather-8lrn7] POD 2023-05-04T10:18:26.091421661Z error: arguments in resource/name form must have a single resource and name
Additionally, when a mesh has multiple members, the istio-must-gather will only contain the core resources (deployments, services, pods, etc.) from one of those namespaces, but it will contain the ServiceMeshMember and Istio resources (as well as the envoy and pilot config) for all member namespaces.
It will also only contain one CRD (definition, not the actual CRs) instead of all of them.
