Help developers better understand Amazon EKS integration with GitLab's QA series Q: After using Amazon EKS, how to configure the number of Worker Node machines more efficiently or optimize resources, and how to effectively control the cost of development and maintenance? A: In addition to its own HPA (Horizontal Pod Autoscaling), Kubernetes can automatically adjust the resource flow according to the usage level. In addition, it can also extend the AWS Auto Scaling solution to set automatic scaling management for scalable resources. In addition, in cost control, although Amazon EKS will charge additional management fees, the price of each EKS can be calculated through the Calculator of the AWS platform.
You will find that the cost of automated deployment and management is cheaper than the cost of engineer labor. Q: More and more customers are considering turning existing applications into container deployments, mostly to speed up the deployment efficiency. So after changing to container mode, will it have any impact on the CI/CD workflow? A: The most direct effect of using container technology can make the application environment more consistent, such whatsapp list as testing and stage production, so that containers can avoid some differences. As for the CD part, when some usages are not the same, the container will help with the configuration, so the benefits of CI/CD to the container are complementary. Q: Customers gradually turn infrastructure into code or documents during the development process.
Is it possible to integrate the code with the existing application CI/CD pipeline to achieve a complete CI/CD deployment process? A: Observing the current market practice, it is mainly divided into two stages for overall deployment. If the team is relatively small, the infrastructure code will be separated from the app code, which will be more flexible in management; if the enterprise scale is relatively large, there will be another infrastructure team to control the deployment. In this case, the APP project will be Generate an APP package, mainly until the delivery stage. Infrastructure projects will specify the required version of the document to deploy to their Kubernetes Cluster.