“Learn Enough Docker to be Useful” is a series of articles (so far 6) that explains different parts of Docker in a very simple and straightforward way. Here are the parts so far:
“How To Build a Serverless CI/CD Pipeline On AWS” is a nice guide to some of the newer Amazon AWS services, targeted at developers and DevOps. It shows how to tie together the following:
- Amazon EC2 (server instances)
- Docker (containers)
- Amazon ECR (Elastic Container Registry)
- Amazon S3 (storage)
- Amazon IAM (Identity and Access Management)
- Amazon CodeBuild (Continuous Integration)
- Amazon CodePipeline (Continuous Delivery)
- Amazon CloudWatch (monitoring)
- Amazon CloudTail (logs)
The examples in the article are for setting up the CI/CD pipeline for .NET, but they are easily adoptable for other development stacks.
There is plenty of documentation, tutorials, and guides online, explaining Docker containers, Kubernetes container orchestration, and microservices. Here are a few that I found useful for the quick and simple introduction into these technologies and how to tie them together.
Firstly, some basic 101s:
- Docker 101: Fundamentals & The Dockerfile
- Kubernetes 101: Pods, Nodes, Containers, and Clusters
- Running Kubernetes Locally via Minikube
- Clustered computing on Fedora with Minikube
- Kubernetes Glossary
Secondly, “Introduction to Microservices, Docker, and Kubernetes” YouTube video nicely puts all the things together, with complete code and configuration examples, some glue, and extra tips.
And finally, a few bits that you might need to solve on the way, which are not necessarily related, but can throw you off:
- Some of the virtualization bits (such as VirtualBox) might fail to run properly if you have Secure Boot enabled. To solve this problem, reboot the machine, go to the BIOS, and disable Secure Boot (enable Legacy Mode).
- Additionally, while you are there, check for the Virtualization Technology settings. Enable Virtualization Technology in the BIOS to further smooth out VirtualBox and friends.
- While working on your first minikube cluster (sorting out VirtualBox and such), it helps to completely remove and start again, after sorting out any issues that prevent Kubernetes to start (proxy timeouts, etc). A quick “minikube delete && minikube start” will save you some time on troubleshooting weird issues, than just “minikube start” after a failure.
“Docker and Kubernetes in high security environments” is an interesting case-study from the Swedish Police Authority, on how to setup and maintain a high security configuration of Docker and Kubernetes.
Not something that you’d think of on a daily basis, but a very handy guide for a weekend reading, or for a priority target scenario.
Scott Lowe shares an updated setup of Kubernets on the Amazon AWS. This blog post covers some of the bits in Kubeadm, which have been updated and improved, since his previous post on the subject some time last year.
If you are working with Amazon AWS, Kubernetes, Docker, VMWare, or other related technologies, I can’t recommend his blog high enough.