When we heard there was an opportunity to design a logo for Minikube we jumped right on it and won by public vote. Here’s how we came up with the logo.
In the realms of branding logo-design is one of the harder aspects to get right. The logo embodies the organisation and fosters recognition and since Minikube is part of Kubernetes — a clearly defined brand — we had to take care not to stray too far from the parent company whilst still creating an emblem that Minikube can call its own. To achieve this we kept three design tenets in mind:
Meaning can make or break a logo. Kubernetes means helmsman or pilot in Ancient Greek, and one can think of the platform as guiding your containers to stability. With this in mind, we thought we would keep the nautical theme and take it to its limits. Interestingly, we found that the logos that did not include a ship’s wheel were the least popular.
After initial feedback we had more of an idea of what we needed to include. A ship’s wheel for Kubernetes and a cube to represent containers. The final design should only represent what the user wants to know.
It can be easy to go overboard with a ship’s wheel, so we had to be very strict on ourselves and employed minimalism in order to achieve a greater effect with fewer and simpler elements. We’ll be honest, there were times when we had too much going on.
The final piece of the puzzle we considered was balance. This is achieved through the use of size, shape and colour. These factors are what give weight to an element. When they’re not correctly measured the end result will look messy and confusing. In order to keep things clean we used the existing Kubernetes logo border and colour palette.
So there you have it. That is how we created a logo for Minikube that ties it to the existing brand whilst creating its own identity. Want to know more about how we approach design? Here’s a recent post.
Why did we do this?
We did this because we love Minikube! Previously you had to set up a Kubernetes cluster yourself on a local machine — which takes a bit of time — or you could use a staging environment, which isn’t that great because you could only test at the end of the software cycle.
With Minikube you’re able to run a Kubernetes development environment on a local virtual machine before pushing your work to a production cluster, saving both time and money.
By spinning up local development clusters efficiently we’ve been able to get projects numerous projects out the door quickly and easily.
If you want to know more about Minikube or start a local cluster we suggest you start here:
Here’s the winning logo:
Earn some stickers!
As usual, if you want to stay in the loop follow us on twitter @wercker or hop on our public slack channel. If it’s your first time using wercker, be sure to tweet out your #greenbuilds and we’ll send you some swag!