Currently, onConfigure appears to be executed for every plugin instance (listener context in Envoy) even when it's the same config. This has a bad implication of stalling xDS when the number of listeners is large. The result of canary validation should be cached, just like the VM config application is cached.
Currently, onConfigure appears to be executed for every plugin instance (listener context in Envoy) even when it's the same config. This has a bad implication of stalling xDS when the number of listeners is large. The result of canary validation should be cached, just like the VM config application is cached.