Currently Envoy reads all runtime config info from the filesystem. Changes to runtime need to be done on a separate copy of the filesystem tree, followed by a symlink swap.

For certain deployment scenarios, it might be easier and flexible to pull runtime info from a REST/gRPC backend similar to the SDS API.

If one were to add a network backend to the runtime, in addition to a file system backend, how should the APIs look like?