Handling Route status when multiple controllers are involved

[howardjohn]

Consider a route that selects many different gateways from many different controllers. This may cause issues in writing the route status.

At first glance, you could have each controller only update info about gateways they own. However, this makes it hard to handle removal of Gateways. For example, if I see existing status of gateways: [a, b, c, d], and now I see the route matches gateways a and b owned by my controller, I cannot tell if c and d are gateways controlled by another controller, or if they are gateways that used to be controlled by my controller but have since been removed.

[robscott]

This is a good catch! What would help with this? Maybe we need a class field in GatewayReference?

[howardjohn]

@robscott I think that would reduce but not eliminate the problem. A controller can handle many classes, they could remove one of the classes and we end up with a dangling reference still?

One option would be a controller reference but that feels ugly

[robscott]

Yeah, controller name feels like the safest way to avoid dangling references. It doesn't feel quite as natural as using something like GatewayClass, but it might be our best option here.

[stevesloka]

I agree controllerName could work. This could also happen if the selector on the Gateway is changed, leaving a set of resources that were once selected but now are not and need the status removed from them.

[hbagdi]

Since Rob already has a PR out for this.
/assign @robscott