-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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-killall.sh
does not work if data-dir doesn't end with /k3s
#10708
Comments
TestingSteps:
Observations:Reproduction:config.yaml
Node OS:
Version:
Validation:Version:
Pod Info:
Processes:
Conclusion |
It doesn't look like you passed in the custom data-dir when running the killall script? You need to set the K3S_DATA_DIR env var when running the killall script if you're using a custom data dir. This PR did not change that requirement. See the validation here: #10471 (comment)
|
Testing StepsReproduction:
From Logs:
Validation:
|
Same problem with the grep expression as rancher/rke2#6522 - it expects the k3s data-dir to end with
/k3s
. If it does not, the pods are not killed.The text was updated successfully, but these errors were encountered: