In our previous post, we talked about why we chose Kubernetes at Thyme Care to deploy and scale our applications. We emphasized the importance of managing the complexity of Kubernetes. In this post, we hope to share just one aspect of how we’re doing that, through the automation of our deploy process.

When launching Thyme Care, we deployed our MVP to AWS Elastic Beanstalk (EBS). While it helped us hit the ground running, we quickly outgrew this solution. Just three months in, we found ourselves facing slow deployments, jumping through hoops to debug errors, and lacking the ability to implement more advanced configurations. Our plans for the future required a more robust platform – one that was highly observable, general enough for any number of workloads, and able to support our scale well into the future.