Talking the Future of Tech
This episode is one of our book club episodes starring John Walpole, who wrote the Two But Rule, which is very tongue in cheek while also very serious about momentum thinking and using a negative bouncy discussion pattern.
I like to think of it as a bouncy discussion pattern to really explore ideas and drive ideation in a positive way by asking and challenging people’s ideas in a constructive way.
Transcript: otter.ai/u/2-CzhoZXo1U9URwEc3…?utm_source=copy_url
Is Kubernetes actually creating the amount of cloud portability of infrastructure agnosticism that we hope it will? If we’re using the same platform across multiple clouds, multiple infrastructures, multiple management teams, does that actually create portability?
It’s a key question for us in building cloud architectures, making decisions about the architect and about how we build architect applications, and even how we structure our teams. In this conversation, we get to the heart of answering that question, but our answers might surprise you.
Transcript: otter.ai/u/ASE9dLnP8qo2jednZB…?utm_source=copy_url
Image: www.pexels.com/photo/black-and-w…n-bucket-3908821/
What would our systems look like if we didn’t have Kubernetes?
We started this discussion with platform engineering and its associated challenges. In talking about platforms, we covered ways in which people can consume infrastructure more effectively. That segwayed directly into ways in which Kubernetes could be changed under the covers, used for virtualization use for non traditional containerized automation.
This episode is a pretty thorough review of alternatives to Kubernetes, and the ways in which Kubernetes misses the mark.
Transcript: otter.ai/u/0qX-qloVOzAQ47LgpS…?utm_source=copy_url
Image: www.pexels.com/photo/wrecked-ship-2336927/
How can you execute on a zero trust strategy and what do you need to keep in mind while building it? Today covers the 101 and 201 levels on zero trust.
We had a really good conversation about how it works, what doesn’t work, what you need to be prepared for. Even if you think you understand zero trust, you will get something out of this conversation. And if it’s a new topic for you, you can also benefit from this pragmatic discussion of zero trust, security and application architects.
Transcript: otter.ai/u/Z1SO1WuJYT3JmEctZe…?utm_source=copy_url
Image: www.pexels.com/photo/wooden-chai…ll-studio-963486/
We continue our discussion of what would the environment look like without Kubernetes? We started with the idea of what if Kubernetes went away, what if there was a copyright or a trademark or an API issue that made us have to abandon Kubernetes altogether?
In this episode we played what if scenarios, exploring what made Kubernetes unique, and if parts of Kubernetes or parts of the architectural model could exist outside of Kubernetes? What would be necessary?
We identified enough parts of Kubernetes individually where we saw how it itself is an interesting convergence of some core technologies. Nothing new except in the combination of those architectural paradigms, designs and open source models. Through this, we dig into why Kubernetes is so powerful in the market.
Transcript: otter.ai/u/L7GZRD8-wEnzLIJL5_…?utm_source=copy_url
Image: www.pexels.com/photo/wreck-of-su…-of-bay-12102304/
A conversation about platform migration turned into an interesting topic about the end of expertise and the changing of the way we think about expertise in a variety of contexts.
How can platform improvement be radically transformed by the use of AI? We discuss entering a world where the lock that we’ve had in a platform, or the longevity of a platform, is radically transformed by the ability to review, scan, test, correct, and transport the data included in that system. The expertise needed to handle platform migration might be entering a new era in which it’s radically reduced. What are the implications of those transformations?
We address a wide range of the impacts of knowledge, AI, and generative machine learning.
Transcript: otter.ai/u/4nL-a5_7dMhYBsvSFP…?utm_source=copy_url
Image: www.pexels.com/photo/shepherd-do…of-sheep-5384726/
Cloud2030PlatformArchitectureCloudDigital TransformationLift and Shift
Rob’s Hot Take:
In the May 6th episode of the Cloud 2030 podcast, the discussion revolved around the diminishing significance of expertise due to advancements in AI and ML technologies. Rob Hirschfeld, the host, emphasized how various fields, from law to data science, traditionally reliant on specialized knowledge, are being impacted by AI, challenging established barriers of expertise. The episode explored the transformative implications of AI on different sectors, suggesting that this theme will be a focal point in future podcasts and discussions on 2030.cloud.
How has Kubernetes changed our industry? Today’s discussion is part of a multi podcast conversation in which we’re going to think about ways in which Kubernetes could go away, or could influence other technologies in such a way to be transformative.
We went down the path of what we have learned from Kubernetes and how it influences other aspects of IT operations, architecture and design, and explored the impact that the expectation for declarative immutable operational constructs will play into other aspects of our system. We also discuss micro LS microkernels and how operations are staged to talk about the need for declarative OS, banking on this idea that what Kubernetes has built extends into other areas.
Chat GPT Summary:
“The conversation is part of a multi-podcast series focused on exploring ways in which Kubernetes could influence other technologies, as well as the potential consequences if it were to disappear.
During the discussion, the group delved into the lessons learned from Kubernetes and its impact on various aspects of IT operations, architecture, and design. One key takeaway was the importance of declarative immutable constructs in managing the complexities of modern IT systems. The group also explored the potential for microkernels to revolutionize system design and emphasized the need for declarative operating systems.
Overall, the discussion highlighted the transformative role that Kubernetes has played in shaping the IT industry and underscored the importance of adopting a declarative, immutable approach to managing complex IT systems.”
Transcript: otter.ai/u/7SMjDGwHTMLmfaCACk…?utm_source=copy_url
Image: www.pexels.com/photo/submarine-m…-harbor-14707646/
https://soundcloud.com/user-410091210/chick-fil-a-edge-kubernetes-deep-dive
We break down the edge compute cluster by the Chick-fil-A team, and we talk about how they use Kubernetes, specifically K3s in 2500 of their restaurants to build an IoT and restaurant management system. This system uses Intel Knucks, a commodity commercial residential grade hardware.
It’s an update on a four year old Kubernetes story with a lot of buzz, and they show how they have been successful building this system.
If you’re interested in Kubernetes, Edge DevOps and distributed systems, this episode has a lot to enjoy.
Transcript: otter.ai/u/i0lBYq9PNQevn0AIvX…?utm_source=copy_url
Image: www.pexels.com/photo/person-in-b…of-cards-6255293/
Rob’s Hot Take:
In the Cloud 2030 podcast episode on Chick-fil-A’s Kubernetes control plane, Rob Hirschfeld highlights the challenges and benefits of transitioning cloud infrastructure and applications to edge locations using commodity gear. He emphasizes the success of Chick-fil-A’s approach in bringing cloud tools and platforms to non-cloud environments, showcasing the potential for mapping cloud processes back into edge computing. Hirschfeld encourages listeners to explore the detailed discussion on Chick-fil-A’s edge clusters and engage in broader conversations on Cloud 2030 at the2030.cloud.
https://soundcloud.com/user-410091210/improving-time-to-decision
How do we improve the time to decision for CIOs? Today we talk about general business practice and how we can help.
Technical innovators and architects create value for the teams that they support. This can either be from an automation perspective, which is what RackN does, or from a data perspective, which Tyler describes in the podcast today. These are real challenges.
When we flip the script and talk about the miscommunication between how CIOs see business challenges and translate business challenges into technical delivery, however, we get into a fascinating set of discussions where Joanne brings up some key challenges for 2023. We also discuss mapping those from CIOs into implementation, followed by ultimately trying to find ways that people can make fast, valuable decisions that feel right.
This conversation is rooted in important conceptual executive level thinking. We’ll include the list of points that Joanne talks about below as well as in the show notes, and I highly recommend you check those out.
Joanne Friedman’s Key Challenges for 2023
1. Tackle inflation and margin pressure
2. Migrate supply chain disruption
3. Make sustainability a pillar
4. Calibrate talent management strategy
5, Streamline procurement and sourcing
6. Strengthen digital thread
7. Prioritize innovation initiatives
We try to name these key challenges, but in a lot of cases we are talking about the list or the graphic. You’ll need to refer to the show notes in order to see the complete one.
Transcript: otter.ai/u/sFESW3yziGOolNbiyt…?utm_source=copy_url
Image: www.pexels.com/photo/man-holding…er-board-1117132/
Rob’s Hot Take:
In the Cloud 2030 podcast episode dated February 9, CEO Rob Hirschfeld discusses the challenge of making fast, impactful decisions in a rapidly changing technological landscape. He emphasizes the importance of intuitive understanding and emotional context in decision-making, highlighting the need for clearly articulated goals and consensus building beforehand. Hirschfeld advocates for executives to rely on their intuition, grounded in a solid foundation of groundwork, and invites listeners to engage in ongoing discussions on this topic at 2030.Cloud.
https://soundcloud.com/user-410091210/pt1-devops-ll-230124
Our mini episode today is a short discussion of API delineation and abstractions for platform engineering.
This was a short intro discussion, and it is especially interesting because platform is a major topic we will be exploring in the coming year. We highlight the challenges of finding the right abstraction points as well as building front end and back end automation.
Transcript: otter.ai/u/5gzoEliQ5H7N5LnGSP6sdOFNjv8
Image: www.pexels.com/photo/white-paper…te-table-7897470/