Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: How to deal with existing flux installations #133

Closed
esteban1983cl opened this issue Jan 2, 2025 · 1 comment
Closed

Question: How to deal with existing flux installations #133

esteban1983cl opened this issue Jan 2, 2025 · 1 comment

Comments

@esteban1983cl
Copy link

Hi team, please help with this question:

I want use this controller, currently I have an EKS running flux, this was bootstrapped with flux cli.
How can you recommend deploy the FluxInstance manifest to manage an existing repository without enter in update loops ?
I my head pass a some things if I deploy a flux instance like this:

apiVersion: fluxcd.controlplane.io/v1
kind: FluxInstance
metadata:
  name: flux
  namespace: flux-system
  annotations:
    fluxcd.controlplane.io/reconcileEvery: "1h"
    fluxcd.controlplane.io/reconcileArtifactEvery: "10m"
    fluxcd.controlplane.io/reconcileTimeout: "5m"
spec:
  sync:
    kind: GitRepository
    url: "https://github.com/my-org/my-fleet.git"
    ref: "refs/heads/main"
    path: "clusters/my-cluster"
    pullSecret: "flux-system"
  distribution:
    version: "2.x"
    registry: "ghcr.io/fluxcd"
    artifact: "oci://ghcr.io/controlplaneio-fluxcd/flux-operator-manifests"
  components:
    - source-controller
    - kustomize-controller
    - helm-controller
    - notification-controller
    - image-reflector-controller
    - image-automation-controller
  cluster:
    type: kubernetes
    multitenant: false
    networkPolicy: true
    domain: "cluster.local"
  kustomize:
    patches:
      - target:
          kind: Deployment
          name: "(kustomize-controller|helm-controller)"
        patch: |
          - op: add
            path: /spec/template/spec/containers/0/args/-
            value: --concurrent=10
          - op: add
            path: /spec/template/spec/containers/0/args/-
            value: --requeue-dependency=5s

Currently this repo has the gotk-sync.yaml and gotk-components.yaml that deploy flux with its components and the initial gitrepository and kustomization. What happen with that files ?

Thanks for your help

@stefanprodan
Copy link
Member

Please see the migration docs here: https://fluxcd.control-plane.io/operator/flux-bootstrap-migration/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants