https://rancher.com/ logo
Title
f

fast-agency-28891

05/31/2022, 12:09 PM
I have a running local k3s cluster with a Fleet manager that is working, I now wish to add a new cluster to this so I generated the token, used the oneliner to get it into values.yaml and copied it + ca.pem over to the new node. Then I use Helm to install the fleet-agent with values.yaml input file (The value.yaml was originally blank on apiserverCA and URL so I filled that manually.
root@k3s-04-b:~# helm -n fleet-system install --create-namespace --wait \
>     --values values.yaml \
>     fleet-agent <https://github.com/rancher/fleet/releases/download/v0.3.9/fleet-agent-0.3.9.tgz>
NAME: fleet-agent
LAST DEPLOYED: Tue May 31 12:51:02 2022
NAMESPACE: fleet-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
No new clusters showed up on the Fleet manager and the logs states this, I cannot understand why it is complaining or how to fix it. Anyone knows?
root@k3s-04-b:~# kubectl -n fleet-system logs -l app=fleet-agent
time="2022-05-31T10:51:19Z" level=error msg="Failed to register agent: looking up secret fleet-system/fleet-agent-bootstrap: Post \"<https://192.168.20.251:6443/apis/fleet.cattle.io/v1alpha1/namespaces/fleet-clusters-system/clusterregistrations>\": x509: certificate signed by unknown authority"
the fleet-manager:
root@k3s-01:~# kubectl get clusters -A
NAMESPACE     NAME    BUNDLES-READY   NODES-READY   SAMPLE-NODE   LAST-SEEN              STATUS
fleet-local   local   2/2             3/3           k3s-01        2022-05-31T11:55:36Z