Archives

The year 2019 is winding down. This is the time of year I reflect on the past 365 days. I feel a few themes that are predominant but, I’m looking forward “for the next thing” and it’s still Kubernetes and the cloud native ecosystem. This is why I think Kubernetes will become the standard cloud APIs that we all build on in the future. I look at Linux and how it has become table stakes these days. I look at Ansible and see that organizations are using either Ansible or a very similar tool. Seeing application deployment and infrastructure as code as more of the norm than the exception is great! Then there’s Kubernetes. The tool providing a consistent, repeatable, and extensible functionality to every cloud provider. While cloud providers’ lack of interoperability by design attempts to lock folks in (there’s plenty here for everyone, AWS), Kubernetes is there making hybrid solutions possible. I see organizations using it to provide the right blend of on-premises and cloud resource use. I see folks using it for data science to make sure their models run to completion. I see folks building mountains of Raspberry Pi Kubernetes clusters to learn it. Kubernetes is becoming a standard API set folks are starting to expect to exist in data centers and clouds. When I look for what’s next in technology, I generally look for pain points. Kubernetes is solving some pain points and working on improving others with every release. Linux lowered the barrier to quality operating systems. Kubernetes is pushing infrastructure to be API driven. This is what we’ve wanted for years. It’s not perfect but, the future is now. ...

I had a long week with a lot of ups and downs. But, the real downer was delivered on Friday afternoon when I learned my insurance provider had denied a trial run at a new nerve stimulator. I had been talking to friends and family about this new nerve stimulator because it was way less invasive to implant. In a nutshell, the nerve stimulator is synthesized to produce a cancellation signal that keeps the brain from feeling the pain. One friend described it as being akin to Iron Man. Instead of keeping metal out of my heart, the nerve stimulator would keep pain from my brain. It also featured technology like Bluetooth and wireless power which means that I could have a cordless device that’s inert in my body with no exposed wiring. No issue with TSA or any government facilities I might find myself in or around again someday (never know if or when a friend will call). Back to the drawing board… ...

re:Invent is easier to cover when it’s not in e-mail form. Pulumi is Focused on Community We’re looking for a passionate Developer Advocate to lead our community outreach, helping devs and ops folks build innovative cloud software together. The community is warm and welcoming, and growing organically. Join our vision to help every team program the cloud! SPONSORED X-Team is Hiring Go developers with strong AWS skills (Remote) We are looking for passionate Go developers with strong AWS skills to work with the world’s leading brands, from anywhere. We love to work with Kubernetes, Docker, Serverless, and AWS tools. Travel the world while being part of the most energizing community of developers. We provide the funding needed to help you achieve your goals and grow as a remote developer. Join X-Team! SPONSORED Commentary: Andy Jassy aims to reinvent Amazon Web Services for the cloud’s next generation — “In an exclusive one-on-one conversation, Amazon’s cloud chief reveals how he views the future of the cloud, the competition, market shifts, customer demands and controversies” ...

Editor’s Note: The newsletter passed 4,000 subscribers this week. Thank you to everyone that help spread the word. I’d love to get to 5,000 subscribers as quickly as possible though. If you don’t mind, please ask your coworkers, BFFs, family, and folks on social media to subscribe to DevOps’ish. Y’all keep being awesome! It is worth noting that the metrics-based system I use to help write DevOps’ish has broken. This week, I lost the ability to post to Twitter due to rate limiting of Tweets sent by IFTTT. Thank you in advance to all the folks that will suggest Zapier, Buffer, etc. But, this isn’t a normal use case for any of those tools. Also, I don’t want to be for a service. I’m looking for a solution but, to be honest, I’d like to build an open source tool to handle the DIY Buffer using IFTTT I’ve cobbled together (and has worked just fine for YEARS). But, I don’t have the skills to do it nor the time, even if I did. If you’re interested in working on such a project, let me know. I can provide support, full credit where it’s due, and mentions throughout all the work I do. ...

Editor’s Note: The newsletter passed 3,975 subscribers this week. I’d love to end the month at 4,000 subscribers. If you don’t mind, please ask your coworkers, BFFs, and folks on social media to subscribe to DevOps’ish. Y’all stay awesome! I’m exhausted. I tweeted midweek that I likely shortened my lifespan at KubeCon this week and I wasn’t sure why. It was a net negative experience for me. The people are great. I love meeting contributors and teaching new folks how to contribute. But, the problems that had to be solved on the ground were extreme in some cases. I sent out my unpolished report internally. I will share it when I have the energy to clean it up a lot. I can tell you for certain, I’m not the only one that feels this way. One CNCF Ambassador already hung it up. I have legitimate concerns about the long term viability of Cloud Native Computing Foundation. At this rate of disregard for the communities forming underneath it, the intent seems to get as much money as possible at all costs. It’s frustrating as hell and I’m still mulling what to do. If I end up leaving my CNCF Ambassador title behind, it would free up some time to do more in the community. I will not do a full KubeCon again. ...