-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
k3s crashes if I do not start the cloud-provider #10068
Milestone
Comments
This was referenced May 29, 2024
Validated on Version:-$ k3s version v1.30.1+k3s-7a0ea3c9 (7a0ea3c9)
Environment DetailsInfrastructure Node(s) CPU architecture, OS, and Version: Cluster Configuration: config;
Steps to validate the fix
Reproduction Issue:
Validation Results:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
(Ubuntu 22.04 on x86_64)
Cluster Configuration:
Single node cluster (for simplicity of reproducing the issue)
Describe the bug:
k3s crashes every ~1:30 with the following error:
Steps To Reproduce:
Install is fine. Because I added
--disable-cloud-controller --kubelet-arg cloud-provider=external
, it reasonably expects that I will add a cloud-controller, which will remove the taints.Expected behavior:
I expect it to function. The node continues to have the taint, but k3s should not crash because of that (which, ironically, makes it harder to actually run the cloud-controller)
Actual behavior:
Crash every ~90 seconds.
Additional context / logs:
As described above. k3s is behaving correctly insofar as it expects that taint to be removed. It is causing issues in that it is crashing, rather than simply logging the issue.
As a contrast, run a full k8s (e.g. using kubeadm or "the hard way") with
--cloud-provider=external
, and it will have the taint. But the apiserver will not crash.The text was updated successfully, but these errors were encountered: