Navigating Disaster Recovery in Kubernetes and CNCF Crossplane
Denunciar
Compartir
•0 recomendaciones•51 vistas
Navigating Disaster Recovery in Kubernetes and CNCF Crossplane
•0 recomendaciones•51 vistas
Denunciar
Compartir
Descargar para leer sin conexión
In Crossplane, deploying resources using GitOps (ArgoCD) is straightforward, but disaster recovery is a different ballgame. When calamity hits, you can't just spin up a new Kubernetes cluster, point it to your Git repository, and expect a 'magical' restoration. This talk will demystify the notion that disaster recovery is 'magic' by exploring various strategies tailored for different levels of disasters using Velero.
Recomendados
Más contenido relacionado
Similar a Navigating Disaster Recovery in Kubernetes and CNCF Crossplane
Similar a Navigating Disaster Recovery in Kubernetes and CNCF Crossplane (20)
![Databases - EBC on the road Brazil Edition [Portuguese]](https://cdn.slidesharecdn.com/ss_thumbnails/databases-ebc-em-sp-952db625-25b2-414c-8dcf-9019a020482d-868555694-181004192335-thumbnail.jpg?width=768&fit=bounds)
Más de Carlos Santana
Más de Carlos Santana(8)
Último
Último(20)
Navigating Disaster Recovery in Kubernetes and CNCF Crossplane
- 1. Carlos Santana (@csantanapr) Sr. EKS Specialist SA, AWS CNCF Ambassador Navigating Disaster Recovery in Kubernetes and Crossplane
- 9. © 2023, Amazon Web Services, Inc. or its affiliates. @csantanapr A model to think of resiliency Resiliency Disaster Recovery One-time Events High Availability Average over time
- 10. © 2023, Amazon Web Services, Inc. or its affiliates. @csantanapr Disaster recovery (DR) • About business continuity • Larger scale, less frequent, events: • Natural disasters • Technical failures • Human actions • Measures a one-time event: • Recovery Time • Recovery Point Natural Disaster Technical Failure Human Actions
- 11. © 2023, Amazon Web Services, Inc. or its affiliates. @csantanapr Recovery Objectives Data Loss Downtime Recovery Point (RPO) Recovery Time (RTO) Disaster How much data can you afford to recreate or lose? How quickly must you recover? What is the cost of downtime? Time
- 12. © 2023, Amazon Web Services, Inc. or its affiliates. @csantanapr Backup & Restore Pilot Light Multi-site active/active Warm standby RPO / RTO: Hours RPO / RTO: 10s of minutes RPO / RTO: Minutes RPO / RTO: Near real-time • Data backed up • No services deployed • Cost $ • Data live • Services idle • Cost: $$ • Data live • Services run reduced capacity • Cost $$$ • Data live • Live services • Cost $$$$ Strategies for disaster recovery active/passive strategies
- 13. © 2023, Amazon Web Services, Inc. or its affiliates. @csantanapr Crossplane Disaster Recovery • Crossplane Upgrades and Rollbacks New api versions added to CRD (ie 11.0 -> 1.10.2) Issue #3859 Providers upgrade and rollback – CRD ownership • Configuration Package Provider auto upgrade • Velero --features=EnableAPIGroupVersions 13
- 18. © 2023, Amazon Web Services, Inc. or its affiliates. @csantanapr Scenario 2: Backup Database 22 Crossplane east-1 ETCD Claim mutation webhooks ArgoCD AWS Cloud Crossplane ETCD restore restore west-2 Amazon RDS Amazon RDS EKS EKS Backup-RDS S3 backup Backup non-global resources Backup-EKS S3 west-2
- 19. © 2023, Amazon Web Services, Inc. or its affiliates. @csantanapr Summary • Everything fails all the time • Shortest path to Recover • Different failure domains • Crossplane rollbacks • Use auto replication (ie. s3) for faster RTO • Lower cost by recover from backup DB (high RTO) 23
- 20. © 2023, Amazon Web Services, Inc. or its affiliates. @csantanapr Resources 24 https://github.com/awslabs/crossplane-on-eks https://crossplane.io https://go.aws/3K4ue0W https://velero.io Recovery When Using Crossplane for Infrastructure Provisioning on AWS EKS Blueprints https://argoproj.github.io/cd