You should olive oil to cook your eggs with. I was visiting with some friends of our several years ago, one of them from a Houstonian Greek family. He was making fried eggs for us, and poured a big pool of olive oil into the skillet. “What the hell?!” I said in my head, “you’re cooking that in olive oil?” I asked him. Sure, why not? he said, I always do.
For whatever reason, this was mind-blowing. I’d been cooking eggs in spray-bottle oil and butter when I wanted to treat myself - if I was going really crazy and wanted to Arkansas it I’d use left over bacon grease like my grandma.
But, since then, I’ve cooked eggs and just about everything else in olive oil.
Next week, on Thursday March 19th there’s a big online conference we’re doing. Check out the agenda: It’s chock full of developer, DevOps, Spring, & kubernetes. We’ll also spend a small amount of time explaining what all this Tanzu stuff is, of course.
It’ll be better than real work!
I wrote up an analysis of the State of Kubernetes 2020 survey that VMware did.
This week it’s just Brandon and me - I get a little crazy in the opening monolog, then we get down to business:
Most of our time is spent discussing the joys of eating half-baked bread. We also discuss what a Tanzu is, kubernetes konspiracy theories, and Oxide the new private cloud hardware startup…wait, wut?
As a thanks for subscribing, I setup a discount code for my book Digital WTF: you can get a copy for free! I also put this link on the “thanks for signing up” email, so if you wanted to help out with my ego-boosting, tell your friends and enemies to subscribe if they want to get a copy of the book for free too.
VMware (where I work) had a big announcement on this past Tuesday. To sum it up, you can use kubernetes in VMware-land now, built into the VMware’s virtualization infrastructure. I haven’t (ever?) spent the time to understand all the components and layers of the VMware stack, so you’ll pardon me just referring to the large, enterprise stack of software as “VMware.” The point is: if you’re organization uses VMware (which is likely the case) kubernetes is available to you.
This is a big deal in the ongoing “make kubernetes boring” throught-train. Building kubernetes into VMware makes it widely available and, indeed, “boring” in that it’s ubiquitous and available - at least the VMware distro. If you’re a developer using kubernetes in a large enterprise, you should ask the ops people about this. In my experience, ops people are very interested in giving developers what they want - with some tricky word-play there: what developers want, but also what operators want. I think this is one of those time when the two wants are the same.
The next step, after kubernetes is “boring,” is to go back to focusing on developer and DevOps tools: getting your organization to focus on product development and driving the business with software, making developers more productive, ensuring that real CI/CD is in place, and so forth.
With VMware, IT operators can provision Kubernetes clusters just as easily as they provision virtual machines. Developers are able to access conformant Kubernetes clusters through the native Kubernetes API. And the CIO now has the flexibility of a next-generation platform that can support both virtual machines and containers, the mixed workloads that make up modern applications.
Tanzu Kubernetes Grid is embedded into vSphere 7 with Kubernetes as part of VMware Cloud Foundation 4 to deliver Kubernetes clusters as a service to developers.
The headline news is that vSphere now has native support for Kubernetes, so you can run containers and virtual machines on the same platform, with a simple upgrade of the system that you’ve currently standardized on and adopting VMware Cloud Foundation.
Helping out operations people:
This also addresses another key constraint of Kubernetes success: the skills gap. With minimal additional training, your vSphere administrators are now able to support Kubernetes and the modern applications run in containers.
And, included in general coverage a summary of and take on the previous container and kubernetes portfolio at VMware/Pivotal.
Often, governance and rules turn out to be folklore, their origins long forgotten, even non-existent. Here’s a technique to expose that, and then start building up more helpful governance.
For example, we ran a leadership program with a set of senior leaders in a large, private-sector organization. They felt frustrated about the ways the organization constrained them from innovation, from collaboration, and from having the time and space to focus more on creating what they want for the future rather than reacting to what they have now. As they discussed these limitations together, they realized they each had a different sense of what, exactly, the limitations were. Each person had created in her mind a set of the limitations that came from outside, and all of them had been acting to ensure that their own staff lived inside those boundaries. Upon collective reflection, though, they discovered that none of them had a really clear sense of what the actual limitations were in the organization. Listening to their different perspectives on this day was boundary shattering for them; they discovered that most of what they were railing against was a phantom, a rumor, or other ghostly sense of what was allowed or not. They realized that they, too, had been unconsciously creating these boundaries for their people, even as they disliked them for themselves. Collectively, they began to play with creating new boundaries—with their eyes open and on purpose—that would enable some of the things they had previously experienced as constrained.
— Simple Habits for Complex Times: by Jennifer Garvey Berger, Keith Johnston
If you’re interested in seeing these links daily, I post them as I find them on my blog. There’s also some longer commentary for many of them that I add there that I don’t include below, for example here and here.