This message was deleted.
# fleeta
adamant-kite-43734
03/27/2026, 3:52 PMThis message was deleted.
m
mammoth-pencil-43427
03/30/2026, 10:39 AMHi André, those are ancient versions of Fleet and Rancher. We have done work in more recent versions to enable Fleet to use Rancher-provisioned CA bundles, in particular this in Rancher v2.11.0 / Fleet v0.12.0.
mammoth-pencil-43427
03/30/2026, 10:44 AMAlso, is this inside your management cluster, or a downstream cluster?
To answer your questions:
• agent and controller versions should match to be on the safe side
• we recommend upgrading to supported versions, minor by minor and latest patch to latest patch, e.g. latest 2.7.x to latest 2.8.y in your case, and so on, until reaching a supported version, i.e. currently at least 2.10.z.
h
hundreds-hospital-60917
03/30/2026, 10:53 AM@high-soccer-790 also see here for lifecycles of Rancher. You need to be prepared to upgrade regularly.
h
high-soccer-790
04/09/2026, 1:30 PMThank you for your responses. I updated the rancher from 2.7.x to 2.8.5 to check if the issue would be corrected but now a new problem is occurring.
The fleet agent when is initiated has the following logs
I0409 132458.899567 1 leaderelection.go:250] attempting to acquire leader lease cattle-fleet-local-system/fleet-agent-lock... 2026-04-09T132546.149564492Z I0409 132546.149359 1 leaderelection.go:260] successfully acquired lease cattle-fleet-local-system/fleet-agent-lock 2026-04-09T132546.160292913Z time="2026-04-09T132546Z" level=warning msg="Cannot find fleet-agent secret, running registration"
time="2026-04-09T132546Z" level=info msg="Creating clusterregistration with id 'hv77z96b67lmnn2grfbh8nlnhjkkc8cn2v54n4j5jphf7fdxgvkdpt' for new token"
time="2026-04-09T132548Z" level=info msg="Waiting for secret 'cattle-fleet-clusters-system/c-eacffa5140c8cca34a1c454df674a40cbf6203a353169090323a4eeaeddee' on management cluster for request 'fleet-local/request-gqkdv': secrets \"c-eacffa5140c8cca34a1c454df674a40cbf6203a353169090323a4eeaeddee\" not found"
time="2026-04-09T132550Z" level=info msg="Starting /v1, Kind=ConfigMap controller"
time="2026-04-09T132550Z" level=info msg="Starting /v1, Kind=Node controller"
time="2026-04-09T132550Z" level=info msg="Starting /v1, Kind=ServiceAccount controller" 2026-04-09T132550.766858636Z time="2026-04-09T132550Z" level=info msg="Starting /v1, Kind=Secret controller"
time="2026-04-09T132550Z" level=info msg="Starting fleet.cattle.io/v1alpha1, Kind=BundleDeployment controller" 2026-04-09T132551.167009175Z time="2026-04-09T132551Z" level=info msg="Deleting orphan bundle ID k3s, release kube-system/traefik"
and when In the continuous delivery I force update the cluster (that right now is paused)
the following logs are printed
2026-04-09T132551.167009175Z time="2026-04-09T132551Z" level=info msg="Deleting orphan bundle ID k3s, release kube-system/traefik"
time="2026-04-09T133217Z" level=info msg="Shutting down /v1, Kind=ServiceAccount workers" 2026-04-09T133217.824743574Z time="2026-04-09T133217Z" level=info msg="Shutting down /v1, Kind=ConfigMap workers" 2026-04-09T133217.824752895Z time="2026-04-09T133217Z" level=info msg="Shutting down /v1, Kind=Secret workers" 2026-04-09T133217.824760538Z time="2026-04-09T133217Z" level=info msg="Shutting down /v1, Kind=Node workers" 2026-04-09T133217.824783545Z time="2026-04-09T133217Z" level=info msg="Shutting down fleet.cattle.io/v1alpha1, Kind=BundleDeployment workers"
time="2026-04-09T133217Z" level=info msg="requested to terminate, exiting"
where then the fleet pod is killed and new one appears.
Is this something someone has ever experienced?
7 Views