`odo describe component` should display actual resources created and not just their Devfile component names

[valaparthvi]

/kind user-story

User Story

As a user I want to odo describe component to show the k8s resources that are managed by odo and not just the name of the Devfile component So that I know what the resource really is.

Acceptance Criteria

• [ ] It should show k8s resource in the form of <devfile component name>: <Resource>/<Resource Name>

$ odo describe component
--- omitted for brevity ---

Container components:
 •  runtime : registry.access.redhat.com/ubi8/nodejs-14:latest

Kubernetes components:
 •  outerloop-deployment: Deployment/my-nodejs-app
 •  outerloop-service: Service/my-nodejs-app
 •  outerloop-url: Ingress/my-nodejs-app

Links

• Related Epic (mandatory):

/kind user-story

Reproduction steps

1. Use the Devfile defined in the advanced guide(https://odo.dev/docs/user-guides/advanced/deploy/nodejs/) to create a component.
2. odo deploy to deploy it on the cluster.
3. odo describe component and check the section on "Kubernetes Component"

[kadel]

I agree that the new suggested output is better, but this is not a bug.

It works as it was originally intended (https://github.com/redhat-developer/odo/issues/5661)

This is a feature request or feature enhancement.

It should be converted to a user story. I'm adding needs-information label as a reminder that it needs to be converted to user-story

[github-actions[bot]]

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

[github-actions[bot]]

This issue was closed because it has been inactive for 30 days since being marked as stale.

[rm3l]

/remove-lifecycle rotten /remove-lifecycle stale /lifecycle frozen /reopen

Still relevant.

[openshift-ci[bot]]

@rm3l: Reopened this issue.

In response to this:

/remove-lifecycle rotten /remove-lifecycle stale /lifecycle frozen /reopen

Still relevant.

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.