v2.2.5-fl.0
Pre-release
Pre-release
Technology Preview of the Flux Subsystem for Argo
Replace images of existing installations
Drop-in the Flux Subsystem for Argo to the existing ArgoCD system. Only Deployment and StatefulSet will be replaced.
kustomize build https://github.com/chanwit/flamingo//release?ref=v2.2.5-fl.0 \
| yq e '. | select(.kind=="Deployment" or .kind=="StatefulSet")' - \
| kubectl -n argocd apply -f -
Update existing systems
Replace over the existing installation (non-HA deployment). All ConfigMaps will be replaced.
kubectl -n argocd apply -k https://github.com/chanwit/flamingo//release?ref=v2.2.5-fl.0
Install container image from the Flux Subsystem for Argo project
kubectl create ns argocd
kubectl -n argocd apply -k https://github.com/chanwit/flamingo//release?ref=v2.2.5-fl.0
# find init password
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d; echo
# forward port to localhost:8080
kubectl -n argocd port-forward svc/argocd-server 8080:443
How to manage Flux resources
In case you already deployed Flux with flux bootstrap
command.
- New Application, name it as
flux-system
, set URL to beflux://loopback
with Path ./ - Choose the destination namespace to
flux-system
- Create the app
Delete App
You can safely delete an ArgoCD app and let Flux continue to take care of your system by choosing to delete it with non-cascading.