rancher / rancher-cleanup

171 stars 43 forks source link

Cant pull image #91

Closed pwnzor11 closed 4 weeks ago

pwnzor11 commented 4 months ago

Stuck indefinitely in crashloopbackoff due to image not being available for my platform. Isn't this designed to work with k3s?

mingyard commented 4 months ago

me too：

kubectl create -f deploy/rancher-cleanup.yaml

serviceaccount/cleanup-service-account created clusterrolebinding.rbac.authorization.k8s.io/cleanup-admin created job.batch/cleanup-job created

kubectl -n kube-system logs -l job-name=cleanup-job -f

Error from server (BadRequest): container "cleanup" in pod "cleanup-job-2sq8d" is waiting to start: ContainerCreating

aadiene commented 3 months ago

Facing same issue. And I suspect the cause to be target architecture on my side. Built images not compatible with arm64/aarch64.

aadiene commented 3 months ago

Just to confirm that building the image for arm64 arch was the trick to remove rancher components from my aarch64 cluster. I got some errors on verify step though error: the server doesn't have a resource type "podsecuritypolicy" but it seems to be related to this issue 43043.

github-actions[bot] commented 1 month ago

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.