How do Helm charts and operators interact with Kubernetes? Today we have a fascinating discussion about the interesting components of Kubernetes including Helm charts, admission controllers and things that are changing and being revised and updated.
We discuss potential topics in anticipation for Kubecon, and if you’re at all interested in Kubernetes, whether you’re attending the conference or not, you will find this to be a must follow list of topics related to Kubernetes.
What happens in the age of cloud scarcity, and are the major public clouds going to become our next OPEC, where they regulate and control prices to such a degree that they can float things up and down?
In doing that, does that mean that cloud computing has become a commodity that can be traded and bought from different providers with a marketplace? All of these questions and more are on our minds as we think about how the market for compute will evolve in the future. Is there a coming compute scarcity based on greenhouse gas or silicon limitations or the ability to generate power? All of these things could have major impacts on how we make choices to consume compute.
In our discussions, a lack of resources is not the driving factor that we see – it’s more about the market power of providers.
Our discussion about development methodologies quickly turns into one about product management methodology.
Those things are interlinked, and we spend a lot of time talking about how product management and the influence on user and operational experience has been transformed by the forces of the market. We also discuss how difficult it is to then organize team development processes to fit these quickly evolving, targeted product delivery challenges.
It’s a fascinating conversation about just how interlinked our development process is to the way we consume products in general.
In the September 29th Cloud 2030 Podcast, Rob Hirschfeld delves into the challenges of product management and its intricate connection with the development process. Emphasizing the difficulty of product management, he notes the impact of compartmentalization and siloed activities on collaboration and integration across teams. The conversation explores the critical need for cross-team discipline and collaboration, highlighting its absence in current practices and its impact on what is built and how it is built. Hirschfeld invites listeners to engage in the ongoing discussions at the2030.cloud and share their perspectives on these challenges in product design and development processes.
We talk about understanding analyst reports and engaging with analysts. How do analysts shape the industry and the industry shapes the analysts?
Today we discuss how every part of this ecosystem has to work together in order for us to build serviceable technology, because fundamentally, we count on the analysts to help understand what’s ready, what the problems are, and what’s working or not working in the enterprise.
It’s easy to pitch stuff, it’s much harder to use stuff and sell tech, and the analysts are a reasonable filter for that, and we break down how and why.
In the September 27th Cloud 2030 Podcast, Rob Hirschfeld provides insights into the dynamics of reading analyst reports. The discussion highlights the bi-directional nature of communication between analysts and enterprise customers, emphasizing a feedback loop where analysts absorb insights from the market while customers are influenced by market buzz and marketing efforts. Hirschfeld encourages participation in these conversations at the2030.cloud, urging listeners to join roundtable discussions and make their voices heard in this collaborative space.
Special guest Bill Mulligan (twitter.com/breakawaybilly/) talks to us about the use cases for BPF and how it works.
We discuss eBPF, the kernel extensions that allow you to write small programs that work inside of kernel space in a safe sandbox way. These have a lot of applications, and they’ve been creating a lot of hype inside of the Kubernetes community as a way to address networking shortfalls.
Our conversation starts broad, but eventually zeros in on eBPF. I know that you will learn a lot about how eBPF can enhance and improve your infrastructure operations environment.
How do you build, manage and fund your systems? Today’s episode is about talent, staffing and hiring the right people to do the job for you.
How you make hiring decisions is inexorably linked to how you think about solving, funding, and structuring solutions around those problems. You cannot hire people without also having straightforward answers for those questions.
We have a fantastic conversation about staffing, that we find to actually be about building the foundations for your hiring.
How do we help junior people build the right skills to do advanced automation system administration, and actually build systems that are resilient and robust? Then, after understanding that that is a learned skill that’s predominantly learned by doing the work, troubleshooting.
We started the conversation talking through how to teach troubleshooting and find opportunities for that. But we transformed the discussion into the challenge of teaching people skills that they then walk away with, that, as you’re mentoring people, you’re increasing their value, and potentially giving them the keys to leave and find a better job.
We talked about this as an industry trend, and some expectations on what you can do about it, and how you can approach that situation. Overall a very robust conversation about building great teams, through junior engineers, and what it takes to be thorough and complete in a process like that. Both from what you can do, and what you have to watch out for.
In the September 13th Cloud2030 Podcast, Rob Hirschfeld shares insights on mentoring junior DevOps engineers, emphasizing the importance of troubleshooting for their learning process. He highlights the hands-on nature of operations and admin work, where individuals encounter challenging problems, learn on the job, and understand solutions by fixing issues. Hirschfeld stresses the need for a supportive environment that allows junior team members to learn without time pressure, fostering a culture that encourages experimentation and learning through doing.
VMware Explore is a show at the end of August where VMware brings together its community, its vendors and tells what’s going on. VMware is dominating in their market, they are making the right moves, and doing a good job for their customers and their partners. This is a surprising summary of the conversation, because this conclusion is certainly not where we started out.
In this conversation, we start from the position of VMware not doing what it needs to do. It’s fumbling its message, it’s not doing the right things. Then we talk through all of the things that contribute to VMware’s position in the market.
If you listen through, the conversation follows a fascinating path to our concluding position.
In the August 23rd DevOps Lunch and Learn, Rob Hirschfeld discusses the evolving concept of platform teams as centers of excellence for corporate governance and controls in IT and operational environments. He notes the current diversity in approaches to solving problems in infrastructure but anticipates a consolidation phase where standardization becomes more prominent. Hirschfeld emphasizes the cyclical nature of IT innovation, suggesting that platform teams will play a crucial role in advocating for standards, processes, and best practices, ultimately contributing to the industry’s progress.
How do supply chain, ecologic, capital, and political issues limit our ability to continue to build big data centers? Today we expand on this continued conversation.
We’re already seeing this in the news, and we need to rethink how we are building a lot of the core infrastructure we depend on. That includes power, data centers, networking and connectivity. Potentially even human logic, which we get into.
The purpose of this conversation was to look at the bigger picture, and then pull it back into how we build IT systems.
Rob Hirschfeld, CEO of RackN and host of the Cloud 2030 podcast, discusses the shift from availability to scarcity in the IT landscape, highlighting the need to find synergies and connections between systems. He emphasizes the necessity of coupling components and integrating systems efficiently, especially as resources like power, data centers, and supply chains become limited. Hirschfeld encourages listeners to engage in the conversation at 2030.cloud, emphasizing the importance of diverse insights for shaping future discussions.
