Just a real quick reminder: docker-compose let’s you run multiple containers at once, while you provide container images, local mount points and other configurations needed for your workload.
My config examples are neither best practice nor production environment recommendations! So please see this article just as a fun little kick-starter to your own journey. Therefore I will refrain from too complicated orchestration examples, health checks, vast deployments, ingress routing and others. Please bear in mind, I want to keep the examples short, simple and understandable. Which microservice can we use to show off the Docker to Kubernetes story? Well, how about WordPress? Why WordPress? It is a very simple microservice (mysql-database, php-webserver), which delivers a good WYSIWYG experience and shows off interconnectivity of microservices in a straightforward way. This is what we want to have a look into in this article. But when your container runs and your docker-compose is up and running, how do you continue from there? How do you translate Docker, docker-compose, docker-stacks into a Kubernetes Deployment? Isn’t Kubernetes too overwhelming to “just use”? As said, Docker is great to get started to “play with containers and microservices”.
With the latest Kubernetes announcement to drop Docker Runtime support (NOT Docker Container Support!!!) it is even more clear now, that Docker’s glory days as Runtime of choice are ticking toward an end.īut let’s keep looking on the bright side of Docker. The last attempt was Docker Enterprise Edition which is now part of MIRANTIS. Sadly, Docker never really embraced Kubernetes as the new (de-facto) Container Orchestration standard and tried everything to be its own thing. Docker was considered a great choice to run your apps in production as well, with the easy to learn, install and adapt Docker Swarm Orchestration. It did not matter if you wanted to just play around with containers or if you wanted to build up new microservices, Docker was and still is a great choice to get yourself started.
It established itself very fast as the de-facto standard to get going with your container journey.
0 kommentar(er)
