Skip to content
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

Files and config, regarding Rancher #86

Closed
frit0-rb opened this issue Feb 7, 2024 · 1 comment
Closed

Files and config, regarding Rancher #86

frit0-rb opened this issue Feb 7, 2024 · 1 comment

Comments

@frit0-rb
Copy link

frit0-rb commented Feb 7, 2024

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:

  • In the config.yaml still got many config from files only uses from Rancher, like this:

image

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

image

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

Copy link

github-actions bot commented Apr 8, 2024

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant