RKE2 on Linux restarts with previous state

[nadenf]

Environmental Info:
RKE2 Version:
v1.25.11+rke2r1

Node(s) CPU architecture, OS, and Version:
Linux harana-server 5.15.0-75-generic #82-Ubuntu SMP Tue Jun 6 23:10:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:
1 server, 2 agents (Linux and Windows)

Describe the bug:
When restarting RKE2 it loads with the previous state e.g. the uptime on Pods, Containers, Nodes are not reset back to zero.

Steps To Reproduce:
Installed RKE2 using Quick Start.

Previous State:

Stopped RKE2:

systemctl stop rke2-server.service

But RKE2 is not stopped:

Manually kill all RKE2 processes:

pkill -f rke2

RKE2 is now stopped so we restart it with:

systemctl start rke2-server.service

New State:

Expected behavior:
Uptime should be zero. IP address should change etc.

[brandond]

You appear to be a little confused - stopping the RKE2 service does not stop the pods. They continue running in the background, and should be unaffected as long as they can tolerate an outage of the local apiserver. This is why the pod uptime and IPs do not reset. If you want to kill the pods, use the rke2-killall.sh script.

[nadenf]

So I have run the systemctl stop and rke2-killall scripts and it is still showing the nodes as being up for 2d as opposed to zero.

Is there another script to stop the server node itself ?

[brandond]

I suspect you're looking at the age field on the node? That is how long it has been in the cluster. It is not uptime.

[nadenf]

Bit odd but sure.

So then I have modified /etc/rancher/rke2/config.yaml .. how do I update an existing cluster to reload it.

[brandond]

Bit odd but sure.

This is not RKE2 specific, this is just how Kubernetes works.

how do I update an existing cluster to reload it.

Just restart the rke2 service on the node where you changed the config.