-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
False
-
User Experience
RFE for the OSSM gather:
presently, the OSSM gather fails to collect OSSM operator OLM info, subscription/installplans that can be very handy for some support questions, as well as including the pod logging for the namespace: upgrades play a big part in some of our current cases
also, member namespaces for meshes do not show up fully in the OSSM gather: having the logging+configuration info for members is often crucial in dealing w support issues, including those in the gather itself would be helpful and would forestall going back to the cu and requesting another data dump in the form of an inspection of the single namespace
lastly, being able to specify a single mesh in the cluster would be helpful: a few cu have multiple meshes: being able to specify the particular mesh that is at issue, along w its member namespaces, could help w the size of the resulting file-bundle and assist support in focusing its investigation
all of the above would assist in cutting down the back-n-forth and number of data requests that support makes in the course of assisting on OSSM issues
- relates to
-
OSSM-2435 Improve UX for istio must-gather
- Closed