GitOps with ArgoCD and Flux
A two-day GitOps workshop focused on the ArgoCD vs. Flux decision and an enterprise-grade environment-promotion workflow — a side-by-side implementation of the same pipeline in both tools, selection criteria, multi-cluster, and progressive delivery.
Comparison instead of assumption
Most GitOps material assumes a single tool or presents ArgoCD and Flux as a complementary toolset. This workshop starts from a different premise: participants deploy the same reference application separately in ArgoCD and in Flux, to see the differences in the operating model firsthand before making a decision for their organization.
ArgoCD dominates, but doesn’t always win
ArgoCD accounts for 78% of GitOps adoption per CNCF data, but that does not mean it is the right choice in every context — Flux, being more CLI-first and deeply integrated with the Flagger ecosystem, is sometimes the better choice for teams that prioritize automation over a graphical interface. The course teaches documented selection criteria, not just popularity.
From tool choice to production rollout
Once the tool is chosen, the workshop moves to enterprise practice: environment promotion, managing multiple clusters from a single repository, progressive delivery with Argo Rollouts, and secure secrets management — a complete workflow ready for organizational rollout.
Benefits
- Implement the same deployment pipeline in ArgoCD and in Flux to make an informed comparison
- Apply documented selection criteria between ArgoCD and Flux for a specific organizational context
- Design environment promotion (dev → staging → prod) under the GitOps model
- Implement progressive delivery (Argo Rollouts) and secure secrets management (SOPS, Sealed Secrets)
Who is this training for?
Prerequisites
- Hands-on Kubernetes knowledge (deployments, namespaces, basic Helm)
- Familiarity with Git and core CI/CD concepts
Training program
GitOps — principles and the starting point for comparison
- Single source of truth, declarativeness, automatic reconciliation — GitOps fundamentals
- Pull-based vs. push-based deployment architecture
- Preparing a shared repository and reference application for tool comparison
ArgoCD and Flux — a side-by-side implementation of the same pipeline
- Deploying the reference application in ArgoCD: Application, ApplicationSet, UI
- Deploying the same application in Flux: GitRepository, Kustomization, HelmRelease
- Selection criteria: operating model, UI vs. CLI-first, integration ecosystem, learning curve
- When to use ArgoCD, when to use Flux, and when to use both in one organization (different teams/clusters)
Environment promotion and multi-cluster
- Promotion patterns for dev → staging → prod under GitOps (branch-based, folder-based, ApplicationSets)
- Managing multiple clusters from a single configuration repository
- Helm and Kustomize as an environment parameterization layer
Progressive delivery and secrets management
- Progressive delivery with Argo Rollouts: canary, blue-green, metric analysis
- Secrets management in GitOps: SOPS, Sealed Secrets, External Secrets Operator
- Rollback and disaster recovery under a declarative model
Delivery Methods
Online
- Convenience of participating from anywhere
- Interactive live sessions with trainer
- Materials available for 30 days
- No travel costs
On-site
- Direct contact with trainer and group
- Intensive hands-on workshops
- Networking with other participants
- Full focus on learning
Frequently asked questions
How is this different from GitOps with ArgoCD and Flux — Continuous Deployment in Kubernetes in our catalog?
Both courses teach the same tools, but with a different structure. The existing course presents ArgoCD and Flux as a complementary toolset for deployment. This course has a different learning goal: participants deploy the same reference application separately in each tool, to make an informed comparison of the operating model and choose one for their organization — the starting point is the "which tool" decision, not "how to configure both".
Will I know which tool to choose — ArgoCD or Flux — by the end of the course?
Yes, that is the workshop's main goal. Participants learn documented selection criteria (operating model, UI availability, integration ecosystem, team learning curve) and apply them to their own context — everyone leaves with a well-reasoned recommendation, not just a feature list of both tools.
Can you use ArgoCD and Flux at the same time in one organization?
Yes, and the course shows when that makes sense — for example, different teams with different operating preferences, or different clusters with different requirements. The key is a consistent configuration repository structure, regardless of which tool reads a given directory.
What does environment promotion look like in practice under GitOps?
The course shows three patterns: branch-based (separate branches per environment), folder-based (separate folders in one branch), and ApplicationSets/generators that automate promotion based on variables. Participants implement a chosen pattern for a dev → staging → prod example.
Request a quote
Funding Options
Check funding options for your company
Development Services Database
An instrument for micro, small and medium-sized companies — check whether it applies to your organisation
Check availabilityNational Training Fund
An instrument for employers — we help you check whether it can be applied
Learn moreTrusted by
We train teams at Poland's largest companies
Interested in this training?
Contact us - we'll prepare an offer tailored to your organization's needs.