Metadata for tracking instance to deployed artifacts to enable service graphs about service-catalog HOT 8 CLOSED

To restate this w/o using the word "instance" on both sides.... I think what's being asked for is:
how do we go from a consumer's 'service instance' resource to the K8s deployment artifacts that make up that instance?

For example, when a consumer asks for an instance of a mongoDB, the consumer can see a "serviceInstance" resource but at best there's just a reference to that instance's access coordinates, there's nothing in that service instance resource that allows the consumer to then traverse over to the environment where the mongoDB instance is actually deployed and then query the K8s platform for the deployment/replicaSet/PetSet/whatever... that makes up that instance.

This could be as simple as adding an "object reference" (assuming that can be used for remote k8s clusters) to be returned in the createServiceInstance() response message - and then store it in the "serviceInstance" resource that the consumer can see. But we'll see...

from service-catalog.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from service-catalog.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from service-catalog.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from service-catalog.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from service-catalog.

/remove-lifecycle rotten
/lifecycle frozen

from service-catalog.

This project is being archived, closing open issues and PRs.
Please see this PR for more information: kubernetes/community#6632

/close

from service-catalog.

@mrbobbytables: Closing this issue.

from service-catalog.