EKS is a service to run kubernetes, so you don’t have to install the software, or manage or patch it. Just like GKS on Google, kubernetes as a service is really the way to go if you want to build kubernetes apps on AWS.
Join 38,000 others and follow Sean Hull on twitter @hullsean.
So where do we get started? AWS docs are still coming together, so it’s not easy. I would start with Jerry Hargrove’s amazing EKS diagram. If a picture is worth a thousand words, this one is work 10,000!
1. Build your EKS cluster
I already did this in Terraform. There aren’t a lot of howtos, so I wrote one.
Basically you setup the service role, the cluster, then the worker nodes. Once you’ve done that you’re ready to run the demo app.
Related: When you have to take the fall
2. Build your app spec
These are very similar to ECS tasks. You’ll need to make slight changes. mountPoints become VolumeMounts, links get removed, and workingDirectory becomes workingDir and so on. Most of these changes are obvious, but the json syntax is obviously the biggest bear you’ll wrestle with.
When done do this:
$ kubectl apply -f my-controller.json
Related: When clients don’t pay
3. Build the service spec
The service is quite a bit different than an ECS service. I suggest starting from the guestbook service. Find it here
Edit that and add your own app name & details. Then apply:
$ kubectl apply -f my-service.json
Related: Why i ask for a deposit
4. Get the endpoint and go!
$ kubectl get service -o wide
You should see the EXTERNAL-IP display a loadbalancer endpoint. Copy that into your browser and you should see your app running.
Related: Why i ask for a deposit