Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Improvement]: Support liveness port testing for standby instance #1957

Closed
2 of 3 tasks
Tracked by #2806
baiyangtx opened this issue Sep 12, 2023 · 3 comments
Closed
2 of 3 tasks
Tracked by #2806

[Improvement]: Support liveness port testing for standby instance #1957

baiyangtx opened this issue Sep 12, 2023 · 3 comments

Comments

@baiyangtx
Copy link
Contributor

Search before asking

  • 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.

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?

  • Yes I am willing to submit a PR!

Subtasks

No response

Code of Conduct

@czy006
Copy link
Contributor

czy006 commented Apr 11, 2024

@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

Copy link

github-actions bot commented Oct 9, 2024

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.

@github-actions github-actions bot added the stale label Oct 9, 2024
Copy link

This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants