-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how could I start a spontaneous DeltaDiscoveryRequests in my own extension? #8948
Comments
What you are asking for is what we are calling "on demand" vs. "basic delta xDS." I'm not sure of the current status of "on demand." AFAIK OSS development hasn't started for anything other than VHDS. cc @htuch @wgallagher @fredlas |
Adding @dmitri-d, the author of the VHDS work. |
We have most of the hooks in place for on-demand CDS, as we have built this internally at Google.
|
Thanks. your answer clear up my confusion to some extent. if I expose in void updateClusterInterest(const std::set<std::string>& update_to_these_names) override {
subscription_->updateResourceInterest(update_to_these_names);
} and I set |
I think this is the right direction, but you probably don't want to expose the ability to change the full resource set; instead, you want to have an additive method, i.e. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions. |
I saw that envoy added delta cds support in the latest release version. the official docs showed that envoy client could start a spontaneous DeltaDiscoveryRequests to the discovery service.
we developed an extension for our middleware in our team, but we did not intent to allocate all cds resources, because the price ( the large size of "state-of-the-world" resources ) was too heavy to afford. so we wanted to start a spontaneous DeltaDiscoveryRequests when the envoy proxy was running (not at the start of envoy).
I queried the source code of envoy, and I did not find the appropriate api to call in our extension. what should I do to solve this problem ?
The text was updated successfully, but these errors were encountered: