Metadata for tracking instance to deployed artifacts to enable service graphs

[judkowitz-zz]

At the offsite, we discussed how to make service graphs. We have almost everything we need in the current design except a way to map instances to instances. Namespaces/label-selectors bind to instances so if we want to figure out the instance to instance binding, we need to have the instance to namespace/label-selector mapping so that we can traverse the chain (permissions allowing).

This is probably just a matter of storing one more piece of metadata somewhere on the binding operation. This issue to to figure out the best implementation and to add that to the design.

[duglin]

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...

[fejta-bot]

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

[fejta-bot]

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

[fejta-bot]

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

[fejta-bot]

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

[mszostok]

/remove-lifecycle rotten
/lifecycle frozen

[mrbobbytables]

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

/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

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

/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.