The presentation discusses how Lunar bank achieved the capability of doing a failover using Githubs and moved from canary deployments to canary clusters. The main focus is on the tech stack used and the challenges faced during the process.
- Lunar bank moved from canary deployments to canary clusters to meet the needs of their customers who rely on them to move quickly and provide new features in a highly reliable manner.
- The production clusters were made truly disposable by deeply integrating with the infrastructure provider, writing new custom operators, and moving most state out of the cluster.
- The company achieved the capability of doing a failover using Githubs, which was complex and required a lot of work.
- The tech stack used included Kubernetes, Git Ups, Flux, AWS, S3 bucket, RabbitMQ, and external DNS.
- The challenges faced included merge complexity in the Github repo, stalling of new deployments during the exercise, and discomfort among employees due to the complexity of the process.
The company created a branch for the new cluster and made some edits to it, such as the cluster name and routing weights. They then spun up another Kubernetes cluster, pointed Flux to it, and federated the two clusters. They made some edits in both branches and shifted the routing weight until they stopped using the old cluster. They removed the services and federation and merged the branch into the main branch, pointing Flux to it. However, this process was complex and caused discomfort among employees.