We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol#resource-warming
In the first version of Kuma 0.1. We had a problem with cluster warming. We fixed it with a custom implementation of the server https://github.com/kumahq/kuma/blob/master/pkg/xds/server/server.go#L302
A more elegant way without "forking" the server is to force a new version of the EDS when CDS changes. This way we can get rid of this code.
Additionally, we don't handle listener warming. We should send RDS change when we LDS changes.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Summary
https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol#resource-warming
In the first version of Kuma 0.1. We had a problem with cluster warming. We fixed it with a custom implementation of the server https://github.com/kumahq/kuma/blob/master/pkg/xds/server/server.go#L302
A more elegant way without "forking" the server is to force a new version of the EDS when CDS changes. This way we can get rid of this code.
Additionally, we don't handle listener warming. We should send RDS change when we LDS changes.
The text was updated successfully, but these errors were encountered: