This message was deleted.
# generala
adamant-kite-43734
04/30/2023, 4:28 PMThis message was deleted.
f
future-night-17486
05/01/2023, 5:23 PMIs it the same local cluster that the Rancher is running on?
p
polite-action-59010
05/01/2023, 6:37 PMYes, basically, I accidentally ran the cluster registration on the local cluster and associated with the downstream cluster ID.
polite-action-59010
05/01/2023, 6:47 PMSo what I think is happening is that rancher is still watching resources for both clusters but I don’t know how to prove it. I don’t see the same behavior when interacting with kubectl on the cluster, only via the UI
f
future-night-17486
05/01/2023, 9:04 PMI have not heard anyone running into this scenario, and do not have the enough understanding to answer your question.
If it is possible, can you try to delete the downstream cluster from rancher and see what will happen? AFAIK, Rancher will do some cleanup on the cluster, but I am unsure how big the impact will be in this case. ( it is totally fine if you cannot delete it because the setup is important)
p
polite-action-59010
05/01/2023, 9:11 PMI was hoping to avoid that since I’d have to regenerate auth contexts
f
future-night-17486
05/01/2023, 9:15 PMUnderstood. Sorry that I do not have a good answer now. I have brought this question to the team and hopeful someone else can help.
9 Views