Listener start without waiting for the route config or secret received

[hzxuzhonghu]

This is not correct, we should wait until all the dependencies of a listener ready before starting it

[Eeshu-Yadav]

/assign

[dawid-nowak]

In Envoy you can configure a listener without any routes (or the routes will be updated over XDS channel). In this case Envoy will start a listener and return an error message.

[hzxuzhonghu]

Envoy listener will have a warming stage When a listener is added, it will be “warmed” before taking traffic

FYI https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/lds

I think we need to redesign to better handle reliability when it handle xds configuration.

[dawid-nowak]

I am not sure if this is needed. In Envoy it is perfectly fine to start a listener with no routes configured for example this bootstrap is perfectly fine from Envoy's perspective:

static_resources:
  listeners:
    - name: listener_http
      address:
        socket_address: { address: 0.0.0.0, port_value: 11100 }
      filterChains:
        - name: filter_chain_http
          filter_chain_match:
            destination_port: 11100
          filters:

Similarly it is fine to start Envoy with a route that is going to be populated at some stage later with RDS. We don't really know when the route is actually going to be added. Perhaps never.

[dawid-nowak]

@hzxuzhonghu @Eeshu-Yadav I really don't think this is a bug and we should close this issue.

[Eeshu-Yadav]

@hzxuzhonghu @Eeshu-Yadav I really don't think this is a bug and we should close this issue.

OK

[hzxuzhonghu]

This should be an enhancement, without this support, orions cannot provide reliable proxing