Stupid logo and stupid reasoning behind it https://www.docker.com/blog/meet-the-new-docker-built-to-run-on-trust
Also if you flip the logo 90° it kinda looks like an angry dude with a tied up beard.
Stupid logo and stupid reasoning behind it https://www.docker.com/blog/meet-the-new-docker-built-to-run-on-trust
Also if you flip the logo 90° it kinda looks like an angry dude with a tied up beard.
k8s has amazing features and can be quite nice to work with. but it also comes with quite some overhead and added complexity. ask yourself what you want from your pipelines.
we have a bit of k8s and standalone docker. hell some of our customers even have full on laptops in a basement as jenkins slave. it highly depends, what your needs are. but (if in a corpo environment) don’t just go with one solution, because you already know it. the employer literally pays you to learn something new.
This is my take as well
Truth be told, we have kubernetes running in our fleet for some deployments and we also run openshift for a lot of enterprise deployments, but for almost all of the things for which we deploy via docker, it’s overkill.
I always push back on people that push k8s as the default deploy for all the things. It’s complex, it’s a lot of maintenance and ots going to be overkill for most of the things you’re deploying.
It has its use case, but it isn’t everything. Sometimes, a simple docker container or, in the case of something like AWS, a server less fargate container, is going to be enough