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
I have searched in the issues and found no similar issues.
What would you like to be improved?
In the current design, the AMS standby node does not have any liveness port. Therefore, it is not possible to configure liveness probe when deploying in K8S.
@baiyangtx After thinking about it, I believe that this function should be related to the integration of AMS in K8S high availability operation, and the subsequent support for ETCD high availability will be completed
This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.
Search before asking
What would you like to be improved?
In the current design, the AMS standby node does not have any liveness port. Therefore, it is not possible to configure liveness probe when deploying in K8S.
This is related to the integration with K8S #1917
How should we improve?
Make the standby node listen to a port to support liveness port probe.
Are you willing to submit PR?
Subtasks
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: