Specific resource instance as source

[raffaelespazzoli]

I'd like to be able to easily create a source on a specific object rather than the whole kind.
So ideally I could write something like:

var obj runtime.Object
...
c.Watch(&source.Object{Object: obj},...)

the behavior should be that the most specific watcher would be created:

• if namespaced type:
  • if neither namespace nor name are initialized, behave like source.Kind
  • if only namespace is initialized, create a watch for that type in that namespace
  • if both namespace and name are initialized, create a watch for that specific object
• if not namespaced:
  • if name is not initialized behave like source.Kind
  • if name is initialized, create a watch for that specific object

this should work also with unstructured objects.

What is the best way to do this with the current controller-runtime library?

I haven't found a way to do it. It looks like the cache.informer interface does not allow for getting an informer on specific instances or namespace...

[DirectXMan12]

/kind feature
/priority backlog

this is a common request. We'd need to plumb through a way to tell the list-watcher to watch a specific object. I'm not certain it's easily doable right now w/o jumping through some hoops.

[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

[vincepri]

/priority awaiting-more-evidence
/help

[k8s-ci-robot]

@vincepri:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/priority awaiting-more-evidence
/help

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.

[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

[vincepri]

/lifecycle frozen