You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@amoro.apache.org by "Marvel-Gu (via GitHub)" <gi...@apache.org> on 2025/03/06 03:23:27 UTC

Re: [I] [Bug]: Amoro pod liveness check failed due to authenticate error [amoro]

Marvel-Gu commented on issue #3446:
URL: https://github.com/apache/amoro/issues/3446#issuecomment-2702693562

   I have some ideas:
   1. Modify the preHandleRequest method or needApiKeyCheck method in DashboardServer.java to ensure that the health check endpoint completely bypasses authentication
   2. Modify amoro-deployment.yaml and add a request header with name: X-Request-Source, value: Web to bypass authentication (but it is unreasonable from a design logic point of view)
   3. Modify amoro-deployment.yaml and add query parameters to provide API key and signature, but signature will change over time, so it is more difficult to handle.
   So the first solution is simple and practical, do you think there is any problem?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@amoro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org