Kubernetes

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.

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. Overall, 2018 was great for me professionally. I’d like to share some things I picked up on this most recent journey around the sun we call 2018. I’ll make some predictions about 2019 in the process too. Kubernetes Will Get Easier Last year, I mentioned that Kubernetes Will Find Its Way in 2018. I do believe that came to fruition this year. Pretty much every major IT company has a range of ways to consume Kubernetes. They’re all Cloud Native Computing Foundation members at the very least. Operationalizing Kubernetes is getting easier as more people gain experience with Kubernetes. Even lab or cloud-only experience might be enough to get a job at the moment. ...

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: ...

I spoke at Detroit Kubernetes, Docker & all related things about Kubernetes Cron Jobs. The talk was more like an explanation with a demo. My demo skills are non-existent so I needed to build those a little. Overall, the demo went well. But, I feel like the zoom feature in Visual Studio Code needs some work. I ended up in iTerm2 using vim to make up for the oddities VSCode threw at me. All the code for the demo is available here: chrisshort/k8s-cron-job-demo ...