While I was in Austin for KubeCon + CloudNativeCon North America 2017 I was told about the Cloud Native Computing Foundation Ambassador program. After reading up on it and experiencing the first day of the conference I decided to apply to become a Cloud Native Ambassador. The responsibilities are right in line with what I’m trying to do in Detroit. I would love to continue my community building around cloud native and open source projects. ...
For many months, I have wanted a Kubernetes cluster of my very own. One that I can tinker with, break, rebuild, and deploy services to. In the fall of 2017, I decided to stand up a three node cluster in Google Kubernetes Engine (GKE). It was nice and shiny and Googly but it wasn’t cheap. Totaling almost $40/month to run I was envious of my friends who have virtually unlimited access to cloud compute. ...
A former co-worker and now friend used to have a tagline, “Everyday is a school day.” I remind myself of this fact nearly every time I learn something new. 2017 was arduous and mentally challenging. But, I did pull out some golden nuggets while reflecting back these past few weeks. I’d like to share some things I picked up on on this most recent journey around the sun we call 2017. ...
DISCLAIMER: The views expressed in this article are solely mine. They do not reflect the opinion of my employer, nor that of any group I am affiliated with, sponsored by, or employed by. Please read my Disclaimer before breaking out the tar and feathers. To say that Docker had a very rough 2017 is an understatement. Aside from Uber, I can’t think of a more utilized, hyped, and well funded Silicon Valley startup (still in operation) fumbling as bad as Docker did in 2017. People will look back on 2017 as the year Docker, a great piece of software, was completely ruined by bad business practices leading to its end in 2018. This is an outside facing retrospective on how and where Docker went wrong and how Docker’s efforts to fix it are far too little way too late. ...
Getting Started with Kubernetes sounds like quite a daunting feat. How do you get started with “an open-source system for automating deployment, scaling, and management of containerized applications”? Let’s examine Kubernetes’ beginning. Containers have been in use for a very long time in the Unix world. Linux containers are popular thanks to projects like Docker. Google created Process Containers in 2006 and later realized they needed a way to maintain all these containers. Borg was born as an internal Google project and many tools sprang from its users. Omega was then built iterating on Borg. Omega maintained cluster state separate from the cluster members thus breaking Borg’s monolith. Finally, Kubernetes sprung from Google. Kubernetes is now maintained by Cloud Native Computing Foundation’s members and contributors. ...