Run Copy Collector Against Wildcard Namespaces

[Nick]

I followed what was mentioned in this other topic, and this worked for us:

Possible to collect pod logs from all namespaces, or a selector of namespaces?

Reading through the docs on the pod logs collector spec: Pod Logs - Troubleshoot Docs - Troubleshoot Docs It seems you can target a namespace via namespace but you cannot target multiple namespaces, or namespaces that you may not know the name of since they could be randomly generated. Our product is beginning to act as a kubernetes operator and will create namespaces with randomized names that we would like to be able to include in a support bundle. These namespaces are labeled appropriately,…

Basically, we just don’t set the namespace: for the copy collector and used a selector that was shared across the deployments across multiple namespaces and we were able to collect the logs across namespaces.