Overview:

Customers often attach must-gather and inspect output when opening tickets. However they do not contains the ACS CRs, so we must either deduce their content, or ask for them explicitly, introducing a round-trip delay.

Research outcomes

There does not seem to be a way to avoid the round-trip.

• extending must-gather to gather things not in the OpenShift Cluster Version Operator payload is not accepted
• the list of resources gathered by running inspect on a namespace is only limited to built-in resources and the team is very reluctant to extend it

However, we could produce our own must-gather image and ask customers to run it via oc adm must-gather --image=acs-img. This is the recommended approach and what ACM and compliance operator already do: https://access.redhat.com/solutions/5459251 https://access.redhat.com/solutions/5126721

The idea is to disseminate the knowledge about the image such that customers know to run this command from the start.

This seems to be a bigger undertaking, and would make sense to sync with other teams such that the resulting must-gather output contains comprehensive information about ACS (i.e. include the ACS-specific debug bundle which is now gathered in a different way).

A couple more notes from rhn-support-edrich:

Tell customers to use the --all-images flag (or something like that).
https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/support/gathering-cluster-data#support_gathering_data_gathering-cluster-data
If that's used and ACS is installed (and presents the right annotations with its operaator) then the must-gather collection will have ACS data.
If you include ACS data in the default must-gather you have to ship your debuging stuff on OCP's schedule and keep ACS in line with OCP's life cycle.

The annotation likely refers to:

Collect must-gather data using the default image for all Operators on the cluster that are annotated with operators.openshift.io/must-gather-image.

Acceptance Criteria: