This document discusses improving the developer experience through GitOps and ArgoCD. It recommends building developer self-service tools for cloud resources and Kubernetes to reduce frustration. Example GitLab CI/CD pipelines are shown that handle releases, deployments to ECR, and patching apps in an ArgoCD repository to sync changes. The goal is to create faster feedback loops through Git operations and automation to motivate developers.

1. DevEx | GitOps & ArgoCD
Micro FeedBack Loops

2. DevEx
A Cloud-Native

3. why?

4. Shifting Architecture(s)

5. We tend to take
our work very
seriously

6. Faster!, Higher!,
Stronger!
- More features
- Time To Market
- When Is it ready ?

7. PUT IMAGE HERE
AND CROP AS CIRCLE
Operational Overhead
- The TCO & ROI of the entire
SDLC - is defined by its
operational cost
- More CapEx - Capital (Capability)
exp
- Less OpEx - Operational exp

8. what

9. Developer to “yak shaver”
Some days … more than others

10. Developer to “yak shaver”
Many TOIL’s
along the road
…

11. how

12. Transform
Frustration to
Motivation ?

13. 2019 - RadarCon
Greg Burrell Senior Reliability Engineer, Netflix

15. Much more than just Git !

16. Build your platform - PRODUCT THINKING
What kind of environment would you like want to work in ?
- Interfaces UI / CLI
- Logins
- Context switches …

18. Build your platform - Remote |
Offline

19. Shorter ! Feedback Loops
DOD - Definition of Done
- How do I know it’s done ?
- How does the team know it’s done ?
- How does management know it’s done ?
- How does NOC know it’s functional ?

20. - Revisit -> Re Target your CI / CD processes
- Chosen Frameworks
- Educate your teams / selfs

21. Solution Suggestion
that works
But …

22. Reduce Frustration | Micro Feedback loops ++
● Helper-tools / Utilities
● Make (my personal favorite)
● Kubectx / kubens
● Common functions
○ Set cloud provider project / profile
○ Get a secret from credentials store
● IDE -plugins
● IDE - the obvious
○ Auto lint / build / deploy

23. Developer Self-Service
Cloud Native | like ordering on amazon …

24. Self-Service Cloud Resources
cpu, ram, [ disk, network ]

25. Self-Service Kubernetes Resources
cpu, ram, [ disk, network ]

26. - selfService CI

27. Demo that (should) works
How will our Dev
Experience look
like with GitOps ?

28. If you're seeing this
slide the demo
failed miserably ;)

29. 🚀 Boosting the Developer
Experience
Crawl, Walk, Run, Fly !

30. Shorten them feedbacks !
- Not just standard pipelines
- DAG’s
- Logic which speeds up the feedback loop
- Caches
- …
- Flows based on Git Operations

31. Talk is cheap | { Show me the code }
https://gitlab.com/fsdi/devops/meetups/obca/nodejs-app

32. DISTRIBUTION - CD

33. Gitlab-ci | release-job
release-job:
image: node:latest
tags:
- npm
stage: release
variables:
GL_TOKEN: "$ACCESS_TOKEN_GITLAB_RUNNER"
script:
- npm install @semantic-release/gitlab
- NEXT_VERSION=$(npx semantic-release | grep 'Created tag' | sed -E 's/.* ([[:digit:].]+)$/1/'
| awk '{print $NF}' | sed 's/^v//g')
- echo $NEXT_VERSION
- echo "NEXT_VERSION=$NEXT_VERSION" >> build.env
except:
- merge_requests
artifacts:
reports:
dotenv:
- build.env
only:
- dev
- master
UPDATE
COMPONENT
VERSION
33

34. Gitlab-ci | deploy
deploy:
stage: deploy
tags:
- ec2
image: maven:3.6.3-jdk-8
services:
- docker:dind
script:
- aws ecr get-login-password --region eu-west-2 | docker login --username AWS
--password-stdin
139114143232.dkr.ecr.eu-west-2.amazonaws.com
- docker build -t $NEXT_VERSION -t $CI_COMMIT_SHORT_SHA -f Dockerfile .
- docker tag $NEXT_VERSION $ecr_url:$NEXT_VERSION
- docker tag $CI_COMMIT_SHORT_SHA $ecr_url:$CI_PROJECT_NAME
- docker push $ecr_url:$CI_PROJECT_NAME
UPLOAD TO
REPO
34

35. Gitlab-ci | deploy-patch
deploy-patch:
stage: patch
image: alpine/git:latest
variables:
URL_REPO: https://gitlab.seculert.com/cwp/moti-temp/argo-apps.git
tags:
- kubernetes
before_script:
- git config --global user.email "bellam@tikalk.com"
- git config --global user.name "gitlab-runner"
- wget https://github.com/mikefarah/yq/releases/download/v4.2.0/yq_linux_amd64 -O
/usr/bin/yq &&chmod +x /usr/bin/yq
script:
- echo $NEXT_VERSION
- echo $CI_COMMIT_REF_NAME
- echo $CI_PROJECT_PATH
- pwd
- git clone https://gitlab-runner:$ACCESS_TOKEN_GITLAB_RUNNER@gitlab.seculert.com/cwp/moti-temp/argo-apps.git
- git status
- git checkout $CI_COMMIT_REF_NAME
- git branch
- cd argo-apps
- LAST_VERSION=$(yq e ".image.tag" apps/panorama/values/eu-west-1/backend-threat-detection-whitelisting.yaml)
- echo "LAST_VERSION=$LAST_VERSION" >> last_version.env
- yq eval ".image.tag = "$NEXT_VERSION"" -i apps/panorama/values/eu-west-1/backend-threat-detection-whitelisting.yaml
- git commit -am '[skip ci] $CI_COMMIT_BRANCH image update'
- git remote remove origin && git remote add origin https://gitlab-runner:$ACCESS_TOKEN_GITLAB_RUNNER@$CI_SERVER_HOST/cwp/moti-temp/argo-apps.git
- git push origin HEAD:$CI_COMMIT_REF_NAME -o ci.skip
dependencies:
- release-job
artifacts:
reports:
dotenv:
- last_version.env
only:
- master
- dev
PATCH APPS
REPO
35

36. Gitlab-ci | argoscd
argocd:
stage: patch
tags:
- kubernetes
image: argoproj/argocd:latest
before_script:
- argocd login argocd.eu-west-1.dev-cwp.seculert.com --insecure --username patchuser
--password $ARGOCD_PASSWORD --grpc-web
script:
- argocd app sync backend-threat-detection-whitelisting --grpc-web
- argocd app wait backend-threat-detection-whitelisting --health --timeout uint
5 --grpc-web
- argocd app get backend-threat-detection-whitelisting --grpc-web
only:
- master
- dev
dependencies:
- deploy-patch
ENSURE
SYNC /
ROLLBACK
36

37. “The best way to
predict the future is to
create it.
Peter Drucker
Are you ready for the cloud natvie dev experience ?