1. Proposed title of this feature request
Allow must-gather to run in specific, pre-defined/pre-created namespace

2. What is the nature and description of the request?
In Enterprise organization, the creation of a namespace is usually done via Self-Service Portal and not something done directly via command line to add organizational specific details such as annotations, labels and other configuration options.

It's therefore desired to apply the same concept for must-gather and have a pre-created namespace available where the must-gather pod can be created (to include the required organizational information in the namespace).

Further, this allows better control of must-gather already running and potentially also allows some pruning of long running jobs in case they are stuck, without having some random namespaces created that are not clearly defined, if and how they are being used.

3. Why does the customer need this? (List the business requirements here)
Enterprise Organization need to create namespaces according specific workflow with organizational information incuded. Having must-gather bypassing this is not acceptable as it does expose some risk of having unmanaged/uncontrolled namespaces in the OpenShift Container Platform 4 - Cluster.

Instead. oc should provide an option to use a pre-created/pre-defined namespace where must-gather can run to gain control, apply all required organizational details and eventually even implement pruning or clean-up of hung must-gather tasks

4. List any affected packages or components.
oc CLI