Skip to content
Discussion options

You must be logged in to vote

don’t remove the old operator first and then install the new one - that’s the path that blew up on CRDs. also don’t run two operators that both try to own the Flux controllers for long.

the supported move onto the current Flux Operator is a takeover, not a wipe (migration guide):

  1. Leave the existing Flux CRDs / CRs / sync alone (no oc delete crd, no uninstall of the toolkit).
  2. Install the new Flux Operator into the same namespace Flux already uses (usually flux-system) - alongside what you have today.
  3. Apply a FluxInstance named flux that matches your current sync (repo/url/path/branch, components, pull secret) and OpenShift:
apiVersion: fluxcd.controlplane.io/v1
kind: FluxInstance
metadata:…

Replies: 6 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@tomm1990
Comment options

Answer selected by siwyroot
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants