Laszlo Fogas11/08/2022, 6:33 AM
John Dietz11/08/2022, 2:56 PM
Laszlo Fogas11/08/2022, 3:22 PM
ADIL RAFIQ11/08/2022, 3:38 PM
Laszlo Fogas11/09/2022, 8:31 AM
Argo provides solutions to problems but not from argocd itself but purpose built tools like argo events, workflows, rollout. Soon your deployment workflow can get from managing one tool to multiple tools. (edited)💯 this is what I see as well. Gitops is great and all, but a bit too loose definition. You need to augment it with different workflows and the details all come down to your implementation.
ADIL RAFIQ11/09/2022, 9:00 AM
Laszlo Fogas11/09/2022, 9:03 AM
doing a hobby projectIs it a blog post, or a tool? I'm in the kubernetes for control plane camp. Cause I have the tooling in place for gitops. But then Flux has a Terraform provider.. so there is crossover between the two worlds. I am happy to team up with a blog post perhaps.
Damian Keska11/09/2022, 10:36 AM
. A step to achieve good testing could be usage of a K3s cluster locally in an automated way for example, but worst is if a prod cluster is OpenShift and the tested automation would not run on plain Kubernetes.
main branch = single source of truth
Lars W. Andersen11/10/2022, 4:35 PM
Damian Keska11/11/2022, 2:43 PM
is discovering different branches e.g. release-1.0, release-1.1, etc. in a repository, and creating versioned objects on cluster (using Helm - branch name is passed as a Helm variable, then it is stripped down to a version number). I will probably create a blog post about it soon.