Open MOZGIII opened 4 years ago
@MOZGIII Can you clarify what the status here is?
This is on hold. Queued to be implemented after the transform (as there will be a lot of merge conflicts if implemented together). It is also a nice-to-have, so it's low-priority.
This is outlined in the RFC here.
This is not the same as filtering
Pod
by the namespace name they are running at: we can already do this via custom field selectors.This will require us implementing support for the dynamic state-sync algorithm reconfiguration at runtime and organizing a hierarchy of watches. This is a significant amount of work on the internal components, but it will also unlock even more advanced filtering capabilities in the future: filtering by the labels on the correlated resources, filtering with runtime reconfiguration, annotation of metadata from the correlated resources, etc. This groundwork will also allow us to greatly expand the capabilities of our annotating transform once it's landed. It will most likely conflict with the annotating transform work, so we should schedule this work sequentially.