I went to KubeCon + CloudNativeCon North America 2018 in Seattle, Washington this week. My trip was cut short due to a work meeting in Raleigh, NC. But, I definitely pushed myself to my limits in Seattle. Make no mistake, had I been staying the entire week as planned I would not have done the time on site the way I did. I wore quite a few hats on this trip: ...
One of the reasons I stood up a Kubernetes cluster on Raspberry Pis in my house was because of the savings I wanted to gain by not running high-available, redundant infrastructure in the cloud. Kubernetes provides high-availability by design. It’s pretty awesome the possibilities that exist given this capability. Need a web server to constantly run? Build a container and throw it in the Kubernetes cluster. Need a service available all the time? Package it and ship it to the Kubernetes cluster. ...
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. ...
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. ...