TL;DR: We’re fixing the rancher-fleet Controller component’s Image repository name as rancher-fleet on console instead of rancher-fleet-controller to match upstream.
We’re changing the default repository name for rancher-fleet controller component to rancher-fleet on console instead of rancher-fleet-controller to match upstream. Once this change is implemented, all new image updates and tags will be released in console/rancher-fleet
Our FIPS offerings for rancher-fleet images already follows upstream:
- console/rancher-fleet-fips
- console/rancher-fleet-agent-fips
Image that will be affected:
| Announcement date | Planned Change date |
| 10/21/25 | 11/04/25 |
What is changing?
Chainguard is moving the rancher-fleet-controller image to rancher-fleet on console to match upstream rancher-fleet images names. All new updates and releases will be moved to the rancher-fleet repository.
| Upstream | Chainguard Console (before change) | Chainguard Console (After change) |
| rancher/fleet | rancher-fleet-controller | rancher-fleet |
| rancher/fleet-agent | rancher-fleet-agent | rancher-fleet-agent (no change) |
Why is Chainguard making this change?
We’re fixing rancher-fleet image names to match upstream names, which makes it more convenient for our customers to identify and use our images. Our FIPS versions for rancher-fleet images also follow names as per upstream.
How will this affect me?
If you use Chainguard’s rancher-fleet controller image [rancher-fleet-controller], the following updated image tags and releases will be pushed to the new repository [rancher-fleet], and the rancher-fleet-controller repository will be removed on November 4th, 2025.
No changes in rancher-fleet-agent image.
What do I need to do?
Please update your references to the new repository name for rancher-fleet controller component.
rancher-fleet-controller:latest → rancher-fleet:latest
If you’re using the latest tags, no other changes are expected.
If you’re using a specific older tag, you’re requested to move to the latest v0.13.3 of rancher-fleet-controller before we migrate to the new repository.
Need help or have questions?
We're here to help - visit our support portal at support.chainguard.dev.
- Chainguard Team
Comments
0 comments
Article is closed for comments.