odo catalog list components does not work without kubeconfig

[dgolovin]

/kind bug

What versions of software are you using?

Operating System: Linux

Output of odo version: odo v2.0.7 (f6a819c)

How did you run odo exactly?

odo catalog list components -o json

Actual behavior

{
  "kind": "Error",
  "apiVersion": "odo.dev/v1alpha1",
  "metadata": {
    "creationTimestamp": null
  },
  "message": "invalid configuration: no configuration has been provided\nPlease login to your server: \n\nodo login https://mycluster.mydomain.com\n"
}

Expected behavior

Should print out components for configured registries. That would help devs who never ever worked with any of k8s related tools and do not have kubeconfig yet.

Any logs, error output, etc?

N/A

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.