rate_limit_quota: [API] Support Envoy node info in RateLimitQuotaUsageReports#24014
rate_limit_quota: [API] Support Envoy node info in RateLimitQuotaUsageReports#24014tyxia wants to merge 5 commits intoenvoyproxy:mainfrom
RateLimitQuotaUsageReports#24014Conversation
…geReports` Signed-off-by: tyxia <tyxia@google.com>
|
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
Signed-off-by: tyxia <tyxia@google.com>
Signed-off-by: tyxia <tyxia@google.com>
Signed-off-by: tyxia <tyxia@google.com>
Signed-off-by: tyxia <tyxia@google.com>
|
/retest deflake |
|
Retrying Azure Pipelines: |
|
@htuch Thanks for the review! PTAL. (The CI failure is caused by CI/CD infra that one agent is not responding... I will re-test it before submitting this PR). |
|
/retest |
|
Retrying Azure Pipelines: |
|
/retest |
|
Retrying Azure Pipelines: |
|
@tyxia do you want to fold in the implementation PR into this one? I'm pretty sure that combined this is a small PR. |
Yea, the implementation should be pretty straightforward. We just need to set this info by the Node from |
|
/retest |
|
Retrying Azure Pipelines: |
|
Yep, I suggest merging in the implementation with this PR and let's review together. |
|
/wait |
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
/wait I will update this PR once other parts of RLQS are ready. |
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
I will work on this once other parts of impl are merged. Then I will merge corresponding impl into this proto change, as Harvey suggested. |
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
Is this PR still in progress? |
Yes, this PR is currently on-hold to wait for other pieces of project to be merged first. But I will revisit this PR soon. |
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
This pull request has been automatically closed because it has not had activity in the last 37 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
Even though our (Google) RLQS server doesn't need this, there are needs/use cases from other RLQS customers that the RQLS server will receive reports from many envoy nodes across various regions, clusters and tenants. And the customers will use this Envoy node which contains all of this information to distinguish the tenant/region/cluster and to apply the appropriate rate limiting policies.
This PR addresses #23585.
Signed-off-by: tyxia tyxia@google.com
Risk Level: LOW
Testing: N/A