Feature Description
The current implementation of the topology data in Extended Distributed Key Value (ETCD) stores both internal and external data with specific prefixes, and the application creates context for all the data and handles all the changes in the ETCD data. This behaviour results in lot of traffic towards ETCD from each pod, including some pods that aren’t interested in these notifications and records.
To address this issue, this feature allows the pods to opt in/out for these notifications and reloads. This “restricted notifications” and “reload” functionality is optional. With this feature, the notifications are only received for subscribed services and peer data.
Note | It’s important to retain the current key structure to avoid any impact on the existing production deployment during the upgrade. |
ETCD traffic optimization improves the reliability, performance, scalability, and security of distributed systems that rely on ETCD for configuration management and service discovery.