This document discusses using ArgoCD and Helm together to provide a unified process for infrastructure changes and application deployments. It introduces ArgoCD for continuous delivery using GitOps and Helm as a package manager. Abstract Helm charts are proposed to reduce the learning curve and standardize infrastructure components. The unified process leverages ArgoCD and Helm with CI/CD to provide a trusted, versioned process for all changes. Knowledge sharing initiatives like training and pairing are recommended to support developers in using these tools.
2. ABOUT ME
• Software developer for 10+ years in various teams
• 6 years at Riskified
• 2 years as a cloud platform developer
• Design of the developers experience
• Leads the DevOps Culture
• Argo community member
4. DEPLOYMENT VS INFRASTRUCTURE
DEPLOY INFRASTRUCTURE
Owner Developers Operations
DEPLOY INFRASTRUCTURE
Owner Developers Operations
Process GitOps ClickOps, ScriptOps
Versions Supported -
Rollback Supported ?
DEPLOY INFRASTRUCTURE
Owner Developers Operations
Process GitOps ClickOps, ScriptOps
Versions Supported -
Rollback Supported ?
Trusted process Untrusted process
5. FROM
UNTRUSTED
TO TRUSTED
PROCESS
Better Process
● Understand the changes
● Monitor
● Versioned
● Rollback
Knowledge
● Reduce the learning curve
● Provide resources for advance learning
● A sharing process (training, paring)
31. A MORE
COMPLICATED
EXAMPLE
Vault is a secrete manger
● Environment variables
● Files
● In-cluster service with admission
webhook
HashiCorp
vaultproject.io
34. For The user - 2 lines
VAULT - A MORE COMPLICATED EXAMPLE
values.yaml
35. • Semantic versioning
• Change Log
1 . 2 . 3
● One every quarter
● Change Instructions
ABSTRACT
CHARTS IS THE
PLATFORM API
Major
incompatible API changes
Minor
New features
Patch
Bug fix
36. • Semantic versioning
• Change Log
01 New objects should be added only when absolutely
necessary by more than one consumer
02 Variable name should be in camelCase
ABSTRACT
CHARTS IS THE
PLATFORM API
• Guidelines
42. THE UNIFIED PROCESS
CI
Merge code
to main
CI
Trigger Build & Publish
Force Sync02
Pull
View Diff &
Sync
02
Apply
Unified
Process
03
Update the
tag value
Infrastructure
Change
Merge code
to main
01
01
44. Knowledge
sharing process
Workshop
Create and deploy a new
service
101 Sessions
First training for all teams
Communication
New features and releases,
and how developers can use
them
Paring
1X1 time. Answer questions,
help make the application
cloud native
Slack
Create community with
dedicated channels
45. DEPLOYMENT VS INFRASTRUCTURE
DEPLOY INFRASTRUCTURE
Owner Developers Developers
Process GitOps GitOps
Versions Supported Supported
Rollback Supported Supported
Trusted process Trusted process
46. Thank you
for your time!
Omer Kahani
Twitter: @OmerKahani
Email: omer@riskified.com
DevOps World (September 23)
https://tinyurl.com/yxl2xwpx
Find out more
https://medium.com/@kahaniomer
https://medium.com/riskified-technology