You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During last months I used many times rancher-cleanup to unregister cluster from a Rancher.
I saw during this time a lit bit files and config regarding from Rancher in the cluster.
Examples:
In the config.yaml still got many config from files only uses from Rancher, like this:
I understand this files are not more necessary, so is the case, maybe is good idea the rancher-cleanup delete that config.
Another Example:
A cluster delete from Rancher and cleaned with rancher-cleanup still got files and folder like
That folder contain files only uses from Rancher, and only created from Cluster created via Rancher, not cluster imported. But in the case you want to register the cluster again in another Rancher or the same Rancher was created, that files conflicts with Rancher, for example the cluster-agent.yaml and this result a problem when that deployment is redeploy.
Maybe it will be better to delete all config only need it from Rancher
The text was updated successfully, but these errors were encountered:
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.
Good morning everyone,
During last months I used many times rancher-cleanup to unregister cluster from a Rancher.
I saw during this time a lit bit files and config regarding from Rancher in the cluster.
Examples:
I understand this files are not more necessary, so is the case, maybe is good idea the rancher-cleanup delete that config.
Another Example:
That folder contain files only uses from Rancher, and only created from Cluster created via Rancher, not cluster imported. But in the case you want to register the cluster again in another Rancher or the same Rancher was created, that files conflicts with Rancher, for example the cluster-agent.yaml and this result a problem when that deployment is redeploy.
Maybe it will be better to delete all config only need it from Rancher
The text was updated successfully, but these errors were encountered: