envoyproxy / envoyproxy/envoy

[rfc] xDS-Failover on Envoy startup

Open
#28,099 2 comments 0 reactions 0 assignees View on GitHub
area/xds enhancement no stalebot
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
428

Description

*[rfc] xDS-Failover on Envoy startup*

*Description*:
We [propose](https://docs.google.com/document/d/1qG7QHBg6uDbDRGUCkP18kA0-gNZxTuLJDzyRF38nv2g/edit#heading=h.2vjb7smqryrm) adding a failover mechanism for xDS sources when the primary xDS server cannot be reached during Envoy startup.

Currently the ApiConfigSource defines multiple [grpc_services](https://github.com/envoyproxy/envoy/blob/b4f37553d6887447f942a1aedbc8c2dacae45537/api/envoy/config/core/v3/config_source.proto#L99), but only supports the first entry.
This proposal suggests adding the ability to failover to the second entry during Envoy’s startup, and use this as a secondary xDS server.
Envoy will only use the secondary server if the primary cannot be accessed. If the secondary server is used, Envoy will continuously attempt to reconnect to the primary server, and fetch the config from it.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.