Description

When setting up their management cluster, Rancher users start by installing... Rancher. This can quickly result in complex sets of config files, not to mention that upgrading Rancher itself is a manual process.

What if... Rancher itself could be configured through Fleet, harnessing the power of GitOps and/or HelmOps?

Goals

• Find a way for Rancher, at install time, to adopt an existing Fleet release instead of installing a new one, provided that the Rancher and Fleet releases are compatible with one another
• Check what happens in Rancher upgrade cases, and improve what can/should be

Stretch goals

• Establish best practices for configuring Rancher through Fleet (e.g. fleet.yaml or equivalent files, repository structure, etc)

Resources

• Rancher Docs
• Rancher repo
• Fleet Docs
• Fleet repo
• Curiosity!