Replies: 3 comments 12 replies
-
I'm not sure what you mean by
That just resets the etcd cluster to a single node; did you want to restore from a snapshot? Do you have any etcd snapshots available to restore from? |
Beta Was this translation helpful? Give feedback.
-
The problem is, i used k9s and must have selected the wrong namespace for termination. I think it was called something like local.
Now I see these logs in journalctl for rke2-server
|
Beta Was this translation helpful? Give feedback.
-
I restarted rke2-server on another node and that has these logs now:
It seems it's not coming up |
Beta Was this translation helpful? Give feedback.
-
I am glad for any help, I know I really messed up 😥
I don't know how to continue and the services and the data on the cluster are important.
Environmental Info:
RKE2 Version:
rke2 version v1.26.10+rke2r1 (9b01c8e)
go version go1.20.10 X:boringcrypto
Node(s) CPU architecture, OS, and Version:
3 nodes, all the same:
Linux node-01 5.4.0-166-generic #183-Ubuntu SMP Mon Oct 2 11:28:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
3 servers running as worker nodes as well as the control plane
Describe the bug:
I accidentally removed the namespace "local" or something like that and the cluster went offline and I can't fix it.
Tried to do a rke2 server --cluster-reset on one of the nodes but to no avail.
Steps To Reproduce:
Remove the local namespace on an rke2 cluster.
Expected behavior:
This should not simply destroy the cluster.
Actual behavior:
Destroyed the cluster.
Additional context / logs:
Beta Was this translation helpful? Give feedback.
All reactions