Hello all, we're using rancher 2.7.1 on eks. we're trying to register self hosted k3s clusters using cattle-agent. this is working like a charm on vanilla k3s. when configuring custom signing keys via k3s parameters (service-account-key-file and service-account-signing-key), the cattle registration fails. Rancher ui is stuck at cluster status "waiting for api to be available". In the rancher server, the rancher pod shows the following errors: "stopping cluster agent for the cluster abc" "failed to start cluster controllers for the cluster abc context is cancelled"