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.

Sign up for GitHub

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

Jump to bottom

[Improvement] support best-effort/strict/none policy for calling switchover during component updating in cluster.spec #8769

Open
wangyelei opened this issue Jan 9, 2025 · 0 comments
Open

[Improvement] support best-effort/strict/none policy for calling switchover during component updating in cluster.spec #8769

wangyelei opened this issue Jan 9, 2025 · 0 comments
Assignees
@cjc7373
Labels
kind/enhancement New feature or request

Comments

@wangyelei
Copy link
Contributor

In special scenarios, switchover may not succeed, leading to the inability of updating to continue.

example:

  1. Created a cluster with excessive resources, pods creation failed. At this point, reduce cluster resources, due to switchover failure, blocking.
@wangyelei wangyelei added the kind/enhancement New feature or request label Jan 9, 2025
@wangyelei wangyelei changed the title [Improvement] support best-effort/strict/none policy for calling switchover during component updating [Improvement] support best-effort/strict/none policy for calling switchover during component updating in cluster.spec Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cjc7373 cjc7373

Labels
kind/enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cjc7373 @wangyelei