Some important partners to improve CI and CD leveraging Cloud Native concepts

1. CICD Patterns for
Cloud Native Apps

2. Helder Klemp
● Brazilian
● CMD Senior Devops Consultant
● AWS Fully Certified Professional
● + 15 years on Software Industry
● Focused on Cloud Native, DevOps, Continuous Delivery and Kubernetes
$ whoami

3. Agenda
● Cloud Native
● Basic Pipeline
● Pipeline as Code
● Dockerising Your Pipeline
● Branch Strategies
● The Slice model
● Kubernetes improving CICD
● Deployment Strategies
● Tips for CICD Projects

4. Cloud-native is an approach to build & run applications that can leverage the advantages of the
cloud computing model
Source: https://pivotal.io/cloud-native

6. Basic Pipeline
Build -> Test -> Publish -> Deploy stage -> Regression -> Deploy Prod -> Regression

7. Typical benefits of traditional software development
paradigms
● Version control
● Code review
● Branching strategies
● Immutable CI Server
Putting your pipeline in a code repository and having it
created and run automatically by your CI tool is much
preferred to having to manually navigate through a
confusing UI.
Pipeline as Code

8. Docker
Docker Compose
Make
Creates an abstraction and independence from the CI
tooling
Tooling

9. Tooling

10. https://3musketeers.io/
Tooling

11. Trunk Based (short lived feature branches)
GitFlow
No one-size-fits-all
Decide a Branch Strategy and leverage multi branch pipelines!!
Branch Strategies

12. Every feature branch deploys an independent app on dev environment
- Devs can work locally and on non-prod envs
- Dynamic DNS provisioning ( kubernetes external-dns + route53)
- Application dns naming:
- From master branch: app-name.yourdomain
- From feature branch: feature-name.app-name.yourdomain
- Same concepts can be applied for infrastructure
- Buckets
- ELBs
- IAM
- Cleanups for feature branches
Slice Model

13. Kubernetes can improve your CI/CD Pipeline

14. Kubernetes Pipeline

15. Default Rolling Updates
Rainbow Deployments
Canary Deployments
Kubernetes Deployment Strategies

17. Allow a fast feedback when a compromised commit occurs
Kubernetes Deployment + Probes

20. ● Cloud native systems are complex and constantly evolving, and so testing in
pre-production typically cannot provide complete validation of functionality and
interactions with what is currently running in production
● initially routing only a small fraction of production traffic against the new service
observing behaviour and other KPIs
● incrementally increasing the percentage of traffic this until the new service is taking all
of the traffic.
Canary Releases

21. Canary Releases
Source: https://dzone.com/articles/gitops-workflows-for-istio-canary-deployments

22. Canary Releases
Source: https://docs.microsoft.com/en-us/azure/devops/articles/phase-rollout-with-rings

23. Not only apps
Cloud Native Infrastructure
- Ansible
- Terraform
- Kubernetes configurations
- From commit to production :)
Pipelinefy Everything

24. Avoid premature optimisation
Avoid making decisions too early
Ingress x regular service load balance
Helm as package manager
Service Mesh
TLS services
Pipelines to the rescue!!!!
Final Tips for Cloud Native projects

25. Share knowledge
Run brown bags about CI/CD / Containers / Cloud Native
Empower the technical team
Open Source
Bring CICD to Ops
GitOps
Database Changes
Server Configuration
Final Tips for Cloud Native projects

27. 27
We are Hiring: !!!!
www.cmdsolutions.com.au