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

Round up MaxUnavailable to 1 node instead of 0 #730

Closed

Conversation

e0ne
Copy link
Collaborator

@e0ne e0ne commented Jul 5, 2024

When MaxUnavailable is configured as percent and cluster is too small we need to roundup MaxUnavailable count to 1 instead of 0 to get draining working.

Copy link

github-actions bot commented Jul 5, 2024

Thanks for your PR,
To run vendors CIs use one of:

  • /test-all: To run all tests for all vendors.
  • /test-e2e-all: To run all E2E tests for all vendors.
  • /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

To skip the vendors CIs use one of:

  • /skip-all: To skip all tests for all vendors.
  • /skip-e2e-all: To skip all E2E tests for all vendors.
  • /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor.
    Best regards.

When MaxUnavailable is configured as percent and cluster is too
small we need to roundup MaxUnavailable count to 1 instead of 0
to get draining working.

Signed-off-by: Ivan Kolodiazhnyi <[email protected]>
@e0ne e0ne force-pushed the round-up-max-unavailable branch from 38ee3be to 262a805 Compare July 5, 2024 14:45
Copy link

github-actions bot commented Jul 5, 2024

Thanks for your PR,
To run vendors CIs use one of:

  • /test-all: To run all tests for all vendors.
  • /test-e2e-all: To run all E2E tests for all vendors.
  • /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

To skip the vendors CIs use one of:

  • /skip-all: To skip all tests for all vendors.
  • /skip-e2e-all: To skip all E2E tests for all vendors.
  • /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor.
    Best regards.

@coveralls
Copy link

coveralls commented Jul 5, 2024

Pull Request Test Coverage Report for Build 9810045968

Details

  • 4 of 4 (100.0%) changed or added relevant lines in 1 file are covered.
  • 5 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.005%) to 40.972%

Files with Coverage Reduction New Missed Lines %
controllers/generic_network_controller.go 5 75.78%
Totals Coverage Status
Change from base Build 9774956990: -0.005%
Covered Lines: 5589
Relevant Lines: 13641

💛 - Coveralls

ykulazhenkov
ykulazhenkov previously approved these changes Jul 5, 2024
Copy link
Collaborator

@ykulazhenkov ykulazhenkov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

additional discussion required

@adrianchiris adrianchiris self-requested a review July 9, 2024 13:24
@ykulazhenkov ykulazhenkov dismissed their stale review July 9, 2024 13:29

additionat discussion required

@ykulazhenkov ykulazhenkov self-requested a review July 9, 2024 13:30
@e0ne
Copy link
Collaborator Author

e0ne commented Jul 10, 2024

After discussion in the meeting we decided that it works as designed. We can't set maxUnavailable: 10% in a cluster of 2 nodes because 1 unavailable node is 50%

@e0ne e0ne closed this Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants