Infer a default namespace

[MikaelSmith]

Many of our support bundles don't include the default namespace. The generated config should set the current namespace to a namespace that exists in the support bundle.

[chris-sanders]

I'm not sure we should. From a user perspective I expect commands issues without a namespace to go to the default namespace. It would be a bit surprising to issue a command and get results from a different namespace. If nothing was collected from the default namespace shouldn't it just say that like any other namespace?

[MikaelSmith]

For a user with Kubernetes experience yes. For less experienced folks, if they're grabbing a support bundle for an app, that app is probably running in one namespace and the out-of-the-box experience should show the details of their app.

[banjoh]

For a user with Kubernetes experience yes. For less experienced folks, if they're grabbing a support bundle for an app, that app is probably running in one namespace and the out-of-the-box experience should show the details of their app.

Wouldn't this be confusing, and perhaps mislead users to think that they are addressing the default namespace?

Also, for a support bundle that has multiple namespaces, which one should be picked?

I'd say the default behaviour of kubectl should remain the same as is when users interact with other live clusters.