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

Control plane load balancer sends requests to unhealthy machines #516

Open
dlipovetsky opened this issue Sep 27, 2023 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@dlipovetsky
Copy link
Contributor

Describe the bug

The control plane load balancer sends requests to unhealthy machines. I have seen this cause kubeadm join to fail on machines during bootstrapping.

The cause is that CAPVCD creates a load balancer whose "Graceful Disable Timeout" is set to the default, 1 minute. The timeout should be disabled. However, vmware/cloud-provider-for-cloud-director#292 does not allow the timeout to be disabled.

Reproduction steps

  1. Create a CAPVCD cluster.
  2. Confirm that the timeout is 1 minute in the control plane load balancer configuration:
    image
  3. Remove the kube-apiserver static pod from one of the control plane nodes.
  4. Send Kubernetes API requests to the load balancer. Some request should fail.

Expected behavior

The timeout should be disabled, and the load balancer should not send requests to an unhealthy machine.

Additional context

No response

@dlipovetsky dlipovetsky added the bug Something isn't working label Sep 27, 2023
@arunmk arunmk self-assigned this Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants