Apply trunk based development and canary deployment to VinID Platform - Intro to trunk based development - Intro to deployment strategies - Canary deployment with Kubernetes and Istio - Acceptance testing and load testing with Postman and K6 - Safe and automation friendly canary deployments with Flagger - Next year challenge: Multi-cloud canary deployment with Spinnaker

1. VinID Platform
Trunk based development and Canary deployment

2. Agenda
• Intro to trunk based development
• Intro to deployment strategies
• Canary deployment with Kubernetes and Istio
• Safe and automation friendly canary deployments with
Flagger
• Acceptance testing and load testing with Postman and K6
• Next year challenge: Multi-cloud canary deployment with
Spinnaker

3. Trunk Based Development

4. TBD vs Gitflow

5. TBD vs Gitflow
• When you are just starting
up
• When you need to iterate
quickly
• When you work mostly
with senior developers
• When you run an open-
source project
• When you have an
established product
• When you have a lot of
junior developers

6. Deployment Strategies
• Recreate
• Ramped
• Blue / Green
• A/B Testing
• Shadow
• Canary

7. Recreate
Pros Cons
• Easy to setup.
• Application state entirely renewed.
• High impact on the user, expect downtime
that depends on both shutdown and boot
duration of the application.

8. Ramped
Pros Cons
• Easy to set up.
• Version is slowly released across instances.
• Convenient for stateful applications that can
handle rebalancing of the data.
• Rollout/rollback can take time.
• Supporting multiple APIs is hard.
• No control over traffic.

9. Blue / Green
Pros Cons
• Instant rollout/rollback.
• Avoid versioning issue, the entire application
state is changed in one go.
• Expensive as it requires double the
resources.
• Handling stateful applications can be hard.

10. A / B testing
Pros Cons
• Several versions run in parallel.
• Full control over the traffic distribution.
• Requires intelligent load balancer.
• Hard to troubleshoot errors for a given
session, distributed tracing becomes
mandatory.

11. Shadow
Pros Cons
• Performance testing of the application with
production traffic.
• No impact on the user.
• No rollout until the stability and performance
of the application meet the requirements.
• Expensive as it requires double the
resources.
• Not a true user test and can be misleading.
• Complex to setup.
• Requires mocking service for certain cases.

12. Canary
Pros Cons
• Version released for a subset of users.
• Convenient for error rate and performance
monitoring.
• Fast rollback.
• Slow rollout.

13. Canary release by Service

14. Canary release by Service

15. Canary release by Istio

16. Canary release by Istio

17. Canary release by Istio

18. Flagger

19. Flagger

20. detect new revision
scale from zero the
canary deployment
check canary pods
health
run the acceptance
tests
start the load tests
mirror traffic from
primary to canary
check request
success rate
stop traffic
mirroring
route live traffic to
the canary pods
promote the canary
wait for the primary
deployment rollout
to finish
check primary pods
health
switch live traffic
back to primary
scale to zero the
canary
send notification
with the result
END

21. Flagger

22. Flagger
Tester
postman-to-k6

23. Postman and K6
postman-to-k6

24. Multi Cloud

25. Cons
• No baseline
• No UI
• No support multi cloud
Pros
• Lightweight
• Simple
• Automation friendly

26. Spinnaker

27. https://ask.vinid.dev
#ask
#vinid
#dev
#question
#answer