Cloud: AWS EKS
Responsibility: Project Delivery
1. The switch from EC2 to EKS was a substantial challenge.
2. We begin the implementation process with mapping out the application landscape.
3. After that, differentiating which application could be consolidated and which required special handling.
4. Finally, we set up the EKS clusters, applied network policies and implemented private subnets to keep systems secure.
5. To scale efficiently, we used Karpenter with custom node pools to optimize CPU and memory usage according to application needs.
1. One of the major challenges was ensuring stable computer resources for critical applications.
2. Using node affinity, we ensured critical applications always scheduled on the right nodes.
3. In case of non-critical applications, Spot Instances were used to reduce costs.
4. CI/CD was challenging, but integrating Jenkins, AWS CodePipeline and ArgoCD automated the entire deployment process.
A 50-60% reduction in costs were visible after six months. Moving to EKS saved money along with improving both scalability and reliability. With costs under control, clients were satisfied and the team focused on innovations.
Ready To Take The Next Step In Your Digital Transformation Journey? Firecaat Is Here To Provide Tailored Solutions That Empower Your Business And Drive Growth.
Let's Get Started