migrate to fluxv2

[billimek]

See https://toolkit.fluxcd.io/guides/flux-v1-migration/

[billimek]

Steps suggested by @bjw-s:

• [x] scale down flux v1 and memcached deployment to 0
• [x] scale down helm-operator deployment to 0
• [x] run flux bootstrap in the repo root folder
• [x] slowly start migrating existing HelmReleases to the new structure(s)
• [x] helm uninstall flux

[onedr0p]

Step 6: migrate to new notifications for flux2 :)

Works great with Discord!

[bjw-s]

Steps suggested by @bjw-s:

• [ ] scale down flux v1 and memcached deployment to 0
• [ ] scale down helm-operator deployment to 0
• [ ] run flux bootstrap in the repo root folder
• [ ] slowly start migrating existing HelmReleases to the new structure(s)
• [ ] helm uninstall flux

This pretty much sums up my steps. The "migrating" step consisted of k uninstall <old helmrelease.yaml> (this will keep all the resources intact because Flux v1 is scaled down), and then applying/pushing the new HelmRelease manifest. The only thing you need to be careful about is that you have the same release name in v1 as in v2, so that the new HelmRelease will manage the existing resources.

[billimek]

Checklist for HelmRelease migrations:

• [x] unifi
• [x] cert-manager
• [x] blocky
• [x] flood
• [x] frigate
• [x] home-assistant
• [ ] hubot
• [x] jackett
• [x] lazylibrarian
• [x] mc
• [x] mc-skyblock
• [x] mcsv
• [x] minio
• [x] node-red
• [x] nzbget
• [x] plex
• [x] radarr
• [x] ser2sock
• [x] sonarr
• [x] teslamate
• [x] unifi
• [x] vernemq
• [x] zwave2mqtt
• [x] coredns
• [x] descheduler
• [x] ingress-nginx
• [x] kured
• [x] metallb
• [x] nfs-client-provisioner
• [x] node-feature-discovery
• [x] oauth2-proxy
• [x] reloader
• [x] vault
• [x] vault-secrets-operator
• [x] loki
• [x] botkube
• [x] influxdb
• [x] kube-prometheus-stack
• [x] modem-stats
• [x] speedtest-prometheus
• [x] thanos
• [x] uptimerobot-prometheus
• [x] rook-ceph
• [x] velero