[EnMasse] Upcoming REST API changes

[Gordon Sim]

On 08/05/18 11:13, Ulf Lilleengen wrote:
> One of my goals with this work is that we in the future could migrate 
> all components today working on configmaps to use this API instead 
> (through the kubernetes master). This would allow us to change how we 
> persist the data from configmaps to something more fitting.  My worry is 
> that if we put all addresses into the address space definition, we would 
> end up facing issues in standard-controller and agent due to status 
> updates needing to fetch/query a lot of data when one of the addresses 
> change.

At present they need to do that anyway, as there is no reliable way of 
tracking changes (especially deletions) except by periodically 
retrieving the whole list.

Would the same 'watch' approach be used with these APIs also or would 
there be something different?