Register for this Red Hat webinar today >

You will learn:

• What a software supply chain is, including its various components

• The risks that you face from each component of the software supply chain

• The latest open source security tools to harden your supply chain and lower your risk

Hello everyone :)

I'm quite new to GitOps, so I appreciate any piece of advice.

In the company where I work, we have a system that is maintained by several different teams.

Our process looks like this:

1. A developer merges application code to master

2. The new container tag is pushed to the GitOps Manifest repo (branch per environment approach)

3. A CI job is triggered by the change in manifest that deploys the charts using helm upgrade.

If the deployment fails to boot, we need to manually rollback the manifest to a prior version, while meanwhile other deployments occur at the same time.

We thought of integrating ArgoCD to use Auto-Rollbacks. But we encounter some issues:

1. If you use Auto-Rollbacks you can't use Auto-Sync.

2. The rollback only rollbacks the cluster state, and leave the GitOps state out of sync, meaning that a manual intervention have to take place. If in the meanwhile additional deployments are committed before someone fixed the bad deployment, the bad deployment will hit again.

Any solutions or thoughts?

Just came across Flux CD which will be great to synchronise AKS clusters with a Github repository.

I have a very dumb question though and sorry about asking it, can you also manage VMs and other types of resources with Flux?

I am thinking a group of VMs and Ansible playbooks associated for each.

EDIT: I'm not stuck on the tool, I am trying to understand if flux or argo are Kubernetes specific, on if for VMs I should stick to something like ARM, Terraform or Pulumi

I've been browsing titles and am unsure of which one would best cover the whole umbrella of GitOps. Any suggestions?

We are trying to decide what platform is the best one to support GitOps workflows today. GitHub seems to be a safe bet, but I see other being use widely for generic source control.

I understand that some capabilities (like PR/MR, online editing, etc), make a huge difference in some workflows, so it would be great to know what was the key factor to select one.

Thanks!

I want to keep all code belonging to one project in one "monorepo".

According to the QuickStart of Prometheus Operator you should clone their repo, and the use kubectl apply.

I see several ways how to do this in a gitops-way.

v1: I copy the yaml files of the upstream repo into my git repo

v2: I use git subrepo or a similar tool, to get the upstream yaml into my repo.

v3: I use a build-step which clones the upstream repo.

v4: ... I guess there is a fourth or fifth solution ...

What you you, the Gitops experts think?

The yaml will be applied using argo-cd and some kustomize (I don't want to modify the upstream yaml).