This post assumes technical expertise from the reader; with working knowledge on Amazon Web Services (AWS) and Kubernetes.
upday started its Kubernetes journey on two smaller product lines with very light traffic last year. Armed with the confidence of running production workloads on Kubernetes, we then worked on migrating our primary product line, the upday platform.
This post summarizes the strategies we employed to handle the specific challenges we face at our scale.
A summary of the architecture can be read here. Although the underlying systems have evolved since that post, our core value proposition remains the same, but at a high level, i.e. …
Containers provide an easy and efficient way to package and run applications. At upday, more than 60% of our workloads are containerized and orchestrated with Kubernetes.
We follow most of the best practices associated with building and running containers in production. To name a few, we build all the containers with minimal packages, run containers as non-root, and enforce runtime policies within orchestrator.
Incorporating static container scanning was something that was planned for our infrastructure and security roadmap this year. Why? Static scanning can reveal the vulnerabilities before the container gets launched. But scanning alone doesn’t suffice. …
This is the Part 2 of the our Kubernetes migration series, you can read the Part 1 on why we decided to adopt Kubernetes here.
This part assumes a technical expertise; along with some working knowledge on Amazon Web Services (AWS), Linux, Docker and Kubernetes.
If you are new to Kubernetes, it is recommended to have a working level knowledge of Kubernetes. Linux Foundation’s Introduction to Kubernetes course helps to get started. Jérôme Petazzoni’s Container Training Workshop covers it in depth.
This part consists of 3 topics — Preparation, Execution and Learnings.
We believe that it is important to take care of the following things during the implementation. …
Most of us would have read or came across a blog post or two talking about migration to Kubernetes as an infrastructure strategy.
This post is something similar, but attempts to talk about it from both, a Business and an Engineering point of view.
This is a story in 2 parts of upday’s Kubernetes Migration Journey.
Everything has a history!
No so long ago, there was an Engineering team that engineered the backend and data APIs that powered the awesome upday application. …