Introduction Welcome to the first part of our Kubernetes tutorial. We would like it to cover some day-to-day challenges that every DevOps engineer working with Kubernetes might encounter. That’s why we will assume that you, dear reader, are already familiar with Kubernetes and its basic concepts. In this particular part of tutorial we will focus on managing high availability Kubernetes cluster on AWS infrastructure. We will use kops - Production Grade K8s Installation, Upgrades, and Management tool.
Introduction There is a saying that every single year a couple of small businesses or growing startups are going to die around the same time. The carnage happens close to the end of the November each year. Amazon Web Services organize an event called re:Invent, where they announce significant changes in their ecosystem and platform - including new services and extensions for existing ones. Jokes aside, keeping up with the pace of the changes across the year is incredibly hard.
Introduction and Problem definition If you have worked with containers and AWS for sure you have heard about Amazon Elastic Container Service, called in short ECS. It is a workhorse for your AWS infrastructure, mainly if you use containers and do not use Kubernetes. Operating this service in most cases is an enjoyable experience. However, there is one caveat which you need to be aware. The problem surfaces when you would like to downsize your cluster, but you want to preserve certain machines from being removed.
We don’t need expressive language, except when we need it By the end of August AWS released a developer preview of the Cloud Development Kit (aws-cdk in short), which allows you to codify infrastructure code in your language of choice. A real programming language. You may ask: why is it a big deal? Imagine that you have to prepare 30 IAM user accounts and S3 buckets with the following permissions:
Introduction At the beginning of June, we have participated in an AWS Summit event in Berlin. A two-day, free event that started at 6th is an excellent opportunity to network, hear about novelties in AWS world. Personally, we seek such occasions, because In the past year AWS itself provided more than 450 updates and announcements regarding their services. Participating in such intensive event is a great way to catch up.