You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modify the preHandleRequest method or needApiKeyCheck method in DashboardServer.java to ensure that the health check endpoint completely bypasses authentication
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)
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?
Yes, I prefer the first solution, AMS should keep a global white list for all kinds of requests and keep an addition one for specific kinds of requests if needed.
What happened?
The liveness check for the amoro pod has failed while AMS ran normally.
Affects Versions
master
What table formats are you seeing the problem on?
No response
What engines are you seeing the problem on?
AMS
How to reproduce
Relevant log output
Anything else
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: