jwt_authn: RemoteJwks to support RetryPolicy config #16319#16924
jwt_authn: RemoteJwks to support RetryPolicy config #16319#16924lizan merged 12 commits intoenvoyproxy:mainfrom
Conversation
|
Hi @alichnewsky, welcome and thank you for your contribution. We will try to review your Pull Request as quickly as possible. In the meantime, please take a look at the contribution guidelines if you have not done so already. |
|
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
|
this is really code that @qiwzhang was already looking at. The issue of missing retries was encountered during load tests on services proxied behind Google Cloud Platform's ESPv2 |
|
/lgtm api |
test/extensions/filters/http/jwt_authn/jwks_async_fetcher_test.cc
Outdated
Show resolved
Hide resolved
test/extensions/filters/http/jwt_authn/jwks_async_fetcher_test.cc
Outdated
Show resolved
Hide resolved
qiwzhang
left a comment
There was a problem hiding this comment.
Look good. Thank you very much!
lizan
left a comment
There was a problem hiding this comment.
Sorry for being late on this.
While this shares same config from router's RetryPolicy, but we're not on same implementations. The HTTP Async Client specifies a NullRetryPolicy here, the optimal way should be allow setting a RetryPolicy in HTTP Async Client, instead of having another implementation and test.
Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
6d19fcf to
0d297b1
Compare
|
I force-pushed into this PR the new branch implementing this PR the way @lizan and @qiwzhang suggested. can you please advise? |
Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
…amespace as per code style guidelines Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
the last requested changes have been pushed on top of the same branch after the forced update, and the azure pipeline still fails for similar reasons ( most likely the ci scripts can't figure out where to rebase because a force-push occurred? ) Please advise. |
lizan
left a comment
There was a problem hiding this comment.
Thanks! This LGTM with just one nit
Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
|
@alichnewsky The CI failure is real, can you try merge main and see if it fails locally? It might be another merged PR affect it. |
…ies-via-async-client-route-retry-policy Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
you are indeed correct. my bad. correction is trivial, but a some code outside the scope of this PR does not pass spellchecking, formatting, ?clang-tidy? pre-push checks. |
it may take me a couple of days to figure out how to fix these ... |
Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
|
at this point, I have pushed all the changes I intended to make, and the azure pipeline still fails ( various timeouts, after 3h). I am not authorized to re-run the failed jobs... The only thing I can do is add a comment somewhere push that and rebuild everything again, which hardly sounds correct. Please advise. |
|
/retest |
|
Retrying Azure Pipelines: |
|
still the same issue it takes more than 3h just to pass the unit tests on mac.. so the tests get cancelled. Alternatively, I could just try to retest as you did every now and then and just hope some ci agent host gets less busy at some point ? |
…nvoyproxy#16924) Commit Message: jwt_authn: RemoteJwks to support RetryPolicy config envoyproxy#16319 ( only for background fetches failing ) Additional Description: following up on comments and code pruned from background jwks refresh mechanism from envoyproxy#16912 Risk Level: Low, default number of retries set to zero. truncated exponential backoff requires explicit configuration. Testing: Only mock-based unit tests so far. Haven't been able to get it ( or the background jwks fetch option, for that matter ) built in [esp-v2](https://github.com/GoogleCloudPlatform/espv-2) so far. Docs Changes: Release Notes: Platform Specific Features: Fixes envoyproxy#16319 Signed-off-by: Anthony Lichnewsky <alichnewsky@users.noreply.github.com>
Signed-off-by: Anthony Lichnewsky alichnewsky@users.noreply.github.com
Commit Message: jwt_authn: RemoteJwks to support RetryPolicy config #16319 ( only for background fetches failing )
Additional Description: following up on comments and code pruned from background jwks refresh mechanism from #16298.
Risk Level: Low, default number of retries set to zero. truncated exponential backoff requires explicit configuration.
Testing: Only mock-based unit tests so far. Haven't been able to get it ( or the background jwks fetch option, for that matter ) built in esp-v2 so far.
Docs Changes:
Release Notes:
Platform Specific Features:
Fixes #16319