Welcome! Your environment makes up so much of who you are in real life. I often wonder if your work environment reflects how your infrastructure will look. If you’re okay with satisfying that 80% use case, does your infra look like AWS with hundreds of services some of which are quite stable and others not so much? Or if you the perfect be the enemy of the good and be like a lot of companies and spend a lot of time spinning their wheels waiting for the right thing to happen. I’ve seen countless examples of this. But, what about when your environment is resilient, scalable, and cloud-enabled. What about when psychological safety is achieved AND the idea of cost per minute to the business during an outage is established? We see so many examples of bad ways and maybe a few good ways of building. I would love to see more use cases around the things that are possible when the business value is known down to the individual and the organization is a high-performer. Highlighting more of the good, I hope, would engrain “the why” behind the need for change way more than features and individual capabilities. ...

Welcome! It would appear the clock has run out for all the Heptio folks to get their payouts from the VMware acquisition. A few Kubernetes contributors are jumping ship from VMware. Four in a little over a week is nothing short of a sign, though. These aren’t the kinds of folks who like to hang out in big corporate orgs and feel like cogs in the machine. They want to feel like they’re making an impact and see the value in their work. They, like Deming, appreciate and take pride in their work. There is nothing at all wrong with this. I 100% understand, given that Red Hat is the biggest organization I’ve ever been a part of outside the Air Force. I can understand the appeal of the late-stage startup life too. But, there is comfort in working for a 25-year-old organization inside a much larger organization that probably won’t muck with us too much given the current global situation. VMware completely sucked all the Heptio out of Heptio the second they started renaming and rebranding Heptio projects to VMware products. I have to hand it to Red Hat. Realizing that the CoreOS name meant something and keeping some of its projects active and incorporating the CoreOS name into products shows that at the very least, Red Hat appreciated CoreOS’s work. I don’t know if the same can be said for VMware of Heptio. Perception is often reality in these instances because we’ll never know otherwise unless folks speak up (which they are often not allowed to). ...

Welcome! What a week it was. KubeCon EU 2020 was this past week. And amongst all the announcements there was a lot of activity and interaction too. Two things I realized this week were, first, y’all are really bubble gumming and duct taping clusters together into production like it’s no big deal just waiting to be bit by something. Second, the Kubernetes community is really an amazing bunch of people, in general. I asked what some folks thought were the highlights of the week’s festivities and I’d like to share those here: Alexis “Horgix” Chotard said, “The openness and transparency of Case Studies, especially the one from @milesbxf and @suhailpatel here Joshua Bezaleel said, “Holly Cummins keynote on climate. That was amazing.” There was a ton of praise for Ian Coldwater and Brad Geesaman’s talk, Advanced Persistence Threats: The Future of Kubernetes Attacks. Ian Coldwater was the talk of the conference pretty much. I have no idea when any of these talks are going to be publicly available. But, you can log back into the terrible platform and watch the talks and keynotes on-demand at the moment. ...

Welcome! This week I move a bunch of web sites off the .io top-level domain. Kubernetes News is one such site. Why should you move off your .io domains. Well, newly minted AWS Developer Advocated, Justin Garrison beat me to it (buy his book). But regardless, there’s enough reason and evidence out there, that we as an industry should no longer condone the use and of a top level domain for the abuse of a people. Here is a list of the articles referenced in the discussion: No to .io, yes to .xyz! How the IO Top Level Domain is mired with outages and injustice The dark side of .io: How the U.K. is making web domain profits from a shady Cold War land deal It’s time for change. It’s time for consciousness. It’s time for our consciences to get the better of us. Note: DevOps’ish may earn compensation for sales from links on this post through affiliate programs. DevOps’ish is brought to you by Accurics. ...

Welcome! DevOps’ish is back. What did the hiatus look like? Why did it need to happen at all? Like fixing an airplane while it’s in-flight, It’s hard assessing a problem while you’re in the middle of creating it. COVID-19 is just the sort of thing that the world turned upside down enough that I needed to take a break to reassess how to do the newsletter, in general. Meanwhile, sponsorships wholly dried up (for five weeks). The incentive I created for myself to write the newsletter when things were hard was gone two weeks after my family started sheltering. The world was in chaos, my processes weren’t aligned to the new state of things, and incentives were gone. When you couple that with a massive project that I was undertaking at work (and spending all my free time researching), the newsletter had to “fall off the plate” as it were. My medical world got turned upside down, too, because of COVID-19. I was rightfully put on hold for routine treatment so the medical infrastructure could adjust also. If my doctors take a break from my treatments, I don’t stand a chance at functioning at 100%. ...