Kubernetes

This Monday (2019-08-19) will be my first day as Principal Technical Marketing Manager on the Cloud Platforms team at Red Hat. What does that mean? OpenShift (a lot of OpenShift), Kubernetes, containers, Operators, and all the associated bits will be my day job. Helping folks help themselves with technology is still and always will be the name of my game. But, working full time in the Kubernetes or cloud native ecosystem was a 2020 goal. Crossing off 2020 goals in 2019. #winning ...

If you'd like to have me speak at your conference, Meetup, podcast, webinar, live stream, etc. please send me a message. Thank you! Here's a current list of ready to go CFPs and/or abstracts that I can speak to at a moments notice. Learn how Ansible can help developers (or any systems savvy person) quickly ramp up to build Operators to automate and manage the life cycle of complex Kubernetes applications. ...

At Red Hat Summit this year, I had the task of explaining Kubernetes Operators with Ansible in two, fifteen-minute talks, separated by three hours, in the middle of the busy Red Hat booth to anyone that walked up. I had to explain Kubernetes, the difference stateful and stateless apps, what a Kubernetes Operator is, how to write an operator with Ansible, and then demonstrate this capability. Use of video and sound was discouraged. Also, there wasn’t going to be an ethernet cable available, meaning only conference show floor WiFi was available for a demo. ...

I made an innocent comment on Twitter last week that led to WAY more feedback than I was expecting. The Kubernetes community showed me there are a lot of options when creating Kubernetes Secrets. I made the statement: Every single time I have to create a secret, I have to read the docs. I should have this figured out by now." Years ago, a colleague asked Albert Einstein if he knew his phone number. The rebuttal was short and rather Einsteinian, “Never memorize something that you can look up.” So when a reminder of how “Memorization is an anti-pattern.” came up during the conversation about Kubernetes Secrets, I was quite relieved. ...

I had a random thought pop into my head during a conversation one night so I tweeted it, “Christophernetes” Then Brandon Dimcheff chimed in with a very appropriate shortening, “c14s” Then Andy Randall chime in with what is now my display name on Twitter, “c14s for Short” Thank you all for this.