Go to file
Adam Pickering effadb5783
Merge pull request #108 from adamkpickering/add-metadata
Add CODEOWNERS file
2025-10-15 10:44:37 -06:00
.github Add .github/CODEOWNERS 2025-10-01 11:59:30 -06:00
deploy Initial commit 2022-05-30 13:03:21 +02:00
scripts Remove unused files 2024-05-29 12:22:58 -06:00
.gitignore Add release.yaml workflow 2024-05-29 11:50:56 -06:00
Dockerfile Add pull-request.yaml workflow 2024-05-28 12:44:23 -06:00
README.md Update README.md 2024-05-29 12:32:43 -06:00
cleanup.sh Properly retrieve finalizers after patching 2023-10-18 16:50:50 +02:00
verify.sh Adding PSP condition to verify script 2023-10-18 14:54:20 -04:00

README.md

Rancher resource cleanup script

Warning

THIS WILL DELETE ALL RESOURCES CREATED BY RANCHER
MAKE SURE YOU HAVE CREATED AND TESTED YOUR BACKUPS
THIS IS A NON REVERSIBLE ACTION

This script will delete all Kubernetes resources belonging to/created by Rancher (including installed tools like logging/monitoring/opa gatekeeper/etc). Note: this does not remove any Longhorn resources.

Using the cleanup script

Run as a Kubernetes Job

  • Deploy the job using kubectl create -f deploy/rancher-cleanup.yaml
  • Watch logs using kubectl -n kube-system logs -l job-name=cleanup-job -f

Verify

  • Deploy the job using kubectl create -f deploy/verify.yaml
  • Watch logs using kubectl -n kube-system logs -l job-name=verify-job -f, output should be empty (besides deprecation warnings)
  • Check completed logs using kubectl -n kube-system logs -l job-name=verify-job -f | grep -v "is deprecated", this will exclude deprecation warnings.

Developing

How to Make a Release

Releases are done via github actions, and triggered by pushing a tag to the remote that starts with v. There are two types of releases: "pre" and "full" release. To make a prerelease, push a tag that contains the string rc or alpha (for example, v1.2.3-rc1 or v1.2.3-alpha1). To make a full release, push a tag that does not contain either of these strings (for example, v1.2.3).