Support listing devfile v2 components in odo

[johnmcollier]

/kind user-story
/area devfile

User Story

As a user, I want to be able to list the running devfile components on my system (Either Kube cluster or Docker) and see which devfile they belong to, using odo list.

Acceptance Criteria

• odo list should be able to list all of the running devfile components in a given namespace
• odo list should specify which devfile each component is part of (e.g. openLiberty, java-springboot, etc)
• If running on an OpenShift cluster with both s2i and devfile components, it needs to support listing both

/kind user-story

[kadel]

• odo list should be able to list all of the running devfile components in a given namespace

Currently odo list filters the component based on the application (using app or app.kubernetes.io/part-of label). Would we want to do the same?

Each component belongs to the application, and if you do odo list it lists components in the current application.

[dharmit]

As for the possible state of the component, please refer #2773 (comment).

[adisky]

IMO, for devfiles odo list should list components from cluster only in the current namespace, odo describe should describe component in the current context folder from cluster/local config both. Keeping odo list to list down components from cluster would keep it simple and easy to understand.

[kadel]

/priority high

[girishramnani]

Do we need to implement the —all flag and —path flag to support compatibility for vscode?
That would definitely increase the complexity and we need to consider a situation where there are components in path which are deployed on kube using devfile and s2i on openshift.

[adisky]

Not sure about the --path flag but the flag --all-apps lists List all components from all applications for the current set project.
The first question is do we want to have app concept for devfiles?

[girishramnani]

we dont have the app concept for devfiles, that is one thing we need to address as part of this PR as well. might be a good idea to add that as part of the AC.

[girishramnani]

• we would be able to fetch all the components by going over all the deployments ( maybe using a label selector ) searching for component label https://github.com/openshift/odo/blob/master/pkg/devfile/adapters/kubernetes/component/adapter.go#L199, might also be a good idea to have managed-by label in place like we used to have for openshift components.
  - change the odo list output to have cluster type as an extra field which could for now have openshift, kubernetes and docker/local value? or have a different table to each of these types like we have for operator services and catalog services.

[adisky]

• we would be able to fetch all the components by going over all the deployments ( maybe using a label selector ) searching for component label https://github.com/openshift/odo/blob/master/pkg/devfile/adapters/kubernetes/component/adapter.go#L199, might also be a good idea to have managed-by label in place like we used to have for openshift components.
• change the odo list output to have cluster type as an extra field which could for now have openshift, kubernetes and docker/local value? or have a different table to each of these types like we have for operator services and catalog services.

IIUC from a single odo session, i guess it would be difficult to list down from different clusters, if you are thinking to list down locally then an additional field needs to be added locally.