Closed adsz closed 1 year ago
If you manually run the script, please supply the output of kubectl get nodes
as that is what is being checked before proceeding.
For running it with kubectl
, it will deploy the Job and then it will run in a pod which should use the service account but I would like to see the logs from the pod to confirm.
Also please supply output of kubectl version
.
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.
I have the same error
I'm getting this error when I run the script:
I've tried the below but still getting the same error:
Also tried
and
kubectl --kubeconfig ~/.kube/config create -f deploy/rancher-cleanup.yaml
but still no luck.