This message was deleted.

After a while, a new node spawned additonally to the old one with the new hostname and the old become became unavailable. 😅 Well, at least I got my data back. But it's not optimal 🙂 So does anybody else experience sth. equally?

Don't change the hostname? The node name is set from the hostname by default, and Kubernetes objects can't be renamed... so yeah, you change the hostname you get a new node.

I didn't know that changing the node's hostname would break sth. whats the best way to revert it? I thought of registering a new node (with all roles) wait until the data transfers and re-register it with the final hostname?