Skip to content

All Event Source Should Handle Multiple Secondary Resource for a Primary  #1162

Closed
@csviri

Description

@csviri

Currently Context.getSecondaryResource() returns only one optional resource. This is done from the cache of an event source. (Note that ideally there is only one event source for one type of resource.) But a reconciler could manage multiple resources of a same type. For example manage multiple Deployment for a custom resource.

So we should probably add Context.getSecondaryResources() (plural) that returns a list. See this handled in this PR:
#1161

We should probably extend this to all event source, so from the mentioned PR to have all ResourceEventSource implement MultiResouceOwners. Since this is generally a something can occur with any resources.

For dependent resource, since one dependent resource always represents one resource not multiple, there would be a discriminator mechanism to distinguish to which resource it belongs to among related resources.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions