Today we dive deep into the mystery of Kubernetes installation, specifically OpenShift installation. We help explain why Kubernetes installs look so weird compared to traditional operations, install processes, and where are the playbooks? Where are the scripts? Are the runbooks describing all the steps you need to take? All of it seems to be missing, and in this podcast, we explain why.
DevOps Lunch and Learn focuses on home labbing versus enterprise use cases and why it is so tricky to satisfy the home user with enterprise products. This really is a dilemma because we love to see more crossover and we’re going to talk about why.
This episode of the TechOps series goes into high availability troubleshooting. Not just high availability, not just troubleshooting, but actually talking through what it takes to manage and maintain and fix HA systems. This is part of a longer discussion we’ve been having and so there’s some really interesting ideas in the middle of these discussions that I hope will shape your thinking as you build high availability systems, diagnostics and troubleshooting for people who are in high availability very complex environments.
We step back in this episode of our Tech Ops series and talk about cloud self managed infrastructure and how you balance the competing concerns. We started from a report that RackN had commissioned talking about on premises Kubernetes, and mixing that into your IT infrastructure.
Can you have a cloud broker? Can you do multi cloud, some sort of tried and true topics for cloud consideration, but through a new filter and through this repatriation idea of mixing and matching your IT Infrastructure?
We deep dive into something seemingly very small, but with a lot of repercussions for how you manage and run a data center, and that is test scripts for servers.
As you’re going through a production cycle or a provisioning cycle, how do you test? What do you test? This topic was from a Reddit thread that we answered and then had a whole hour conversation about just how important and impactful this type of script is.
Today we dive into RackN high availability technology and what we did to build consensus based raft HA capabilities directly into Digital Rebar. This is one of those episodes where we are talking specifically and only about Digital Rebar, so it is a vendored conversation from that perspective.
If you are building HA systems, or are interested in how HA systems work, this is a great session to learn firsthand from our experience!
This is one of those fun conversations where we’re really diving not just into the tech but the enterprise consumption of the tech and how people are thinking about it. How does technology like Kubernetes evolve and get used in ways that the community is not thinking about and find a whole new path for adoption and commercialization?
If this is going on in your organization, we want to hear from you. We want you to be part of the conversation, because this is a really important transition point for the industry, for people questioning their VMware consumption, and for people looking to expand their Kubernetes footprints.
We talk about current events, the acquisition of data stacks and the closing of the HashiCorp acquisition by IBM. Later, we dive into the productivity of AI and what’s going on – are companies really getting the benefits that they expect from AI chat bot integrations and what the challenges are?
We touch base on a little bit of something more infrastructure focused, where I give a preview of work I’ve been doing on separating Kubernetes virtualization from Kubernetes development use cases, which is something that we will be talking about more in the future.
The cloud2030 Tech Ops series is an ongoing discussion for us to create what I think of as 200 level content for tech and operations leaders, exploring really complex, deep topics in a thoughtful way to really extend your knowledge base and capabilities in the data center and infrastructure space.
Today’s episode talks about gitops and immutability, and what we’re doing here is connecting together the operational concepts between controls and desired state communications and how that gets executed in infrastructure in an operations sense. Rather than a developer approach, this takes an operations approach. So if you are interested in how to manage immutability and what that means in infrastructure, this discussion is for you.
We dive deep into the technical details of BootC – a Red Hat-led technology that uses container-like definitions to describe machine boot processes. BootC is an important development, especially as companies embrace containers and seek a unified approach to machine configuration.
RackN CTO, Greg Althaus, provides an in-depth overview of how BootC works, its key capabilities, and the potential benefits and challenges for operations teams. They explore topics like BootC’s relationship to containers, the concept of immutability, different deployment methods, and the operational considerations around managing BootC at scale.
This conversation offers a balanced, non-Red Hat perspective on BootC, highlighting both its technical merits and the significant operational work required to successfully adopt and integrate it. Listeners will come away with a nuanced understanding of this emerging technology and the factors organizations should weigh as they evaluate BootC for their infrastructure.