Journey through the design of a Kubernetes AWS EKS Platform
This series of articles start as a personal development project.
As the reader, I want to improve my knowledge and try to keep up with all the different options available during the design of a Kubernetes platform based on the AWS EKS product.
I can’t think a better way to verify if I totally understood the subject than having to explain it to someone else.
You will be my Kubernetes AWS EKS sparring partner.
It will be a long journey using many different services/products and I want to avoid leaving running service when not needed and at the same time avoiding bad surprises like a huge AWS bill at the end of the month because I forgot to stop some resources.
With this goal in mind, all the components will be implemented following the idea of infrastructure as code so I can create and delete resources consistently.
All the code will be available on my GitHub account in the EKS journey repository.
I will try keeping the format very simple, short, reach of diagrams and pictures something that you can read during a coffee break.
Stay tuned to start this journey together :)
Comments and feedback are welcome.
NO WARRANTIES: All of the information provided on this series is provided “AS-IS” and with NO WARRANTIES and it is a personal point of view based on personal experience.