Moving Repos & flux-system

[mbaronpp]

I inherited a flux 2.4.0 installation that had, say, 30 kustomizations deployed. When it was bootstrapped, a GitRepository called flux-system was created, as well as a Kustomization called flux-system. All of the Kustomizations we created referenced the GitRepository named flux-system.

We needed to move off of the original GitHub repo, so we added a 2nd GitRepository and corresponding Kustomization, both called fluxcd and began slowly moving them. In each one, we updated spec.sourceRef.name and spec.path to reference the new GitRepository.

The flux-system GitRepository that we bootstrapped flux against now only has one Kustomization, which is the original flux-system Kustomization from the bootstrap process.

How can we safely migrate that to the new fluxcd GitRepository and get off of original flux-system GitRepository altogether?

[zakariamanssouri]

Hello ,

I have migrated a whole repo without doing the kustomization by kustomization method , by doing these steps:

1. disable prune on all kustomizations (.spec.prune: false) ( otherwise you'll delete all the things !!)
2. Create New Repository and copy all the files to it
3. Run the bootstrap process with the new repo url and token ( flux boostrap) => this will update the original GitRepository and the secret used for it.
4. trigger reconciliation by executing :
   flux reconcile ks flux-system -n flux-system --with-source

I hope it will help you with your issue !

[mbaronpp]

Thanks for the feedback @zakariamanssouri . I updated my original post to indicate the flux installation is version 2.4.0. I think this fact may complicate things, as if I re-bootstrap it, I think it will try and upgrade to the latest and we will have issues with old API versions.

[marouane-zerhouni]

Hi @mbaronpp,

You can specify the toolkit version in your bootstrap process. For example, if you're using the flux CLI, flux bootstrap takes a --version (or -v) flag to specify the version. In your case, I believe it would be --version=v2.4.0
You can apply the same logic to other bootstrap methods such as the flux Terraform provider or the Flux Operator.

I do want to highlight 2 points however:

• You want your CLI to match your toolkit version to ensure your commands don't fail, since API versions have evolved. For example, calling flux get source oci using flux v2.6.x or higher will fail, since it'll query the apis/source.toolkit.fluxcd.io/v1 version rather than the apis/source.toolkit.fluxcd.io/v1beta2 one.
• According to the Flux documentation, only the last 3 minor releases are supported, which means you're running an out-of-date version.