Releases: flux-subsystem-argo/flamingo
v2.7.2-fl.6-main-b1742696
add external links Signed-off-by: Chanwit Kaewkasi <[email protected]>
v2.6.7-fl.4-main-c4ce7dcc
update images on readme Signed-off-by: Chanwit Kaewkasi <[email protected]>
v2.6.6-fl.4-main-0d5eae51
first cut with v2.6 Signed-off-by: Chanwit Kaewkasi <[email protected]>
v2.2.8-fl.1-main-305be5e6
Technology Preview of Flux Subsystem for Argo
Replace images of existing installations
Drop-in FSA to the existing ArgoCD system. Only Deployment and StatefulSet will be replaced.
kustomize build https://github.com/flux-subsystem-argo/flamingo//release?ref=v2.2.8-fl.1-main-305be5e6 \
| 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/flux-subsystem-argo/flamingo//release?ref=v2.2.8-fl.1-main-305be5e6
Install container image from Flux Subsystem for Argo
kubectl create ns argocd
kubectl -n argocd apply -k https://github.com/flux-subsystem-argo/flamingo//release?ref=v2.2.8-fl.1-main-305be5e6
# 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
v2.2.8-fl.1-main-0fb0615a
Technology Preview of Flux Subsystem for Argo
Replace images of existing installations
Drop-in FSA to the existing ArgoCD system. Only Deployment and StatefulSet will be replaced.
kustomize build https://github.com/flux-subsystem-argo/flamingo//release?ref=v2.2.8-fl.1-main-0fb0615a \
| 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/flux-subsystem-argo/flamingo//release?ref=v2.2.8-fl.1-main-0fb0615a
Install container image from Flux Subsystem for Argo
kubectl create ns argocd
kubectl -n argocd apply -k https://github.com/flux-subsystem-argo/flamingo//release?ref=v2.2.8-fl.1-main-0fb0615a
# 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
v2.2.8-fl.0-main-3cefc21e
Technology Preview of Flux Subsystem for Argo
Replace images of existing installations
Drop-in FSA to the existing ArgoCD system. Only Deployment and StatefulSet will be replaced.
kustomize build https://github.com/flux-subsystem-argo/flamingo//release?ref=v2.2.8-fl.0-main-3cefc21e \
| 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/flux-subsystem-argo/flamingo//release?ref=v2.2.8-fl.0-main-3cefc21e
Install container image from Flux Subsystem for Argo
kubectl create ns argocd
kubectl -n argocd apply -k https://github.com/flux-subsystem-argo/flamingo//release?ref=v2.2.8-fl.0-main-3cefc21e
# 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 ArgoCD UI
In case you already deployed Flux with flux bootstrap
command, you could visualize the whole "flux-system" by:
- New Application, name it as
flux-system
- Set URL to be
flux://loopback
with Path ./ (You can also specify your real URL and Path - the same ones you used for the Flux bootstrap) - Check Sync Option: "Apply Out Of Sync Only"
- Check Sync Option: "Use Flux Subsystem"
- 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.
v2.2.5-fl.0
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.