text
stringlengths
0
1.8k
\[55:39\] We've shown things where Crossplane is running and has a sidecar container which is an OCI-compliant registry. And importantly, a lot of this functionality was very easy to build, because there's a library that we depend on in Crossplane that a lot of folks are big fans of at this point called Go Container Re...
And actually kind of alluding to that hack week, myself and my co-worker Michael - we worked on a way to actually build OCI images in your browser. Since we're just putting yaml in them, you can imagine putting an editor in a web page that you receive, and using actually Rust and WebAssembly we're actually able to buil...
So lots of fun stuff around that, and lots of stuff that will help the developer loop maybe not be used in most production settings, but getting folks to the point where they can have a package that's consumable and really useful to them as an organization as quickly as possible - definitely a goal for us.
**Gerhard Lazu:** So what I've heard is pushing container images, OCIs straight into Kubernetes, with no external container registry, just using the kubectl, the Kubernetes API. That sounds amazing. I love that. And I have ten follow-up questions, especially around the WebAssembly and the web browser... But we're runni...
**Jared Watts:** I think one of the biggest things here for me is that folks are starting to buy into Kubernetes and really getting understanding and seeing the power of a control plane type of approach for many of their applications, that "Hey, you can do that for your own infrastructure as well, too", and that we hav...
**Gerhard Lazu:** That sounds amazing to me. What about you, Dan? What would you want people as a listener to take away from this discussion?
**Dan Mangum:** I would say that my ask for folks is to think a little bigger with their infrastructure. And what I mean by that is envision a future that seems impossible right now. A lot of folks think kind of like this pie-in-the-sky vision of being able to just consume these infrastructure packages and build them i...
**Gerhard Lazu:** This was too much fun. It was very difficult to contain myself and not be more excited. Thank you very much for this lovely conversation. See you next time.
**Jared Watts:** Thank you so much for having us. It's always a pleasure to talk with you.
**Dan Mangum:** Absolutely.
• Gerhard Lazu shares his personal experience of almost joining Packet in the summer of 2019 due to an email mix-up
• Marques Johansson and David Flanagan discuss what attracted them to Equinix Metal (formerly Packet), highlighting their interest in bare metal infrastructure and networking capabilities
• The impact of the Equinix acquisition on Packet's products and services, including expanded global reach and integration with Equinix's existing infrastructure
• David Flanagan shares his experience using Packet before the Equinix acquisition and notes the benefits of integrating with Equinix's extensive network
• Acquisition of Packet by Equinix
• Evolution from bare metal servers to Equinix Metal platform
• Benefits of leveraging Equinix network and infrastructure
• Trade-offs in instance size and pricing
• Importance of maintaining the "purity" of bare metal experience
• Challenges and considerations for providing managed Kubernetes on top of bare metal
• Definition of Kubernetes and its components
• Challenges of running Kubernetes on bare metal, particularly for HPC workloads
• Evolution of Kubernetes over the next five years towards more bespoke implementations
• Kubeadm as a popular tool for deploying Kubernetes
• Cluster API as an opinionated way to deploy Kubernetes clusters with automated remediation
• Tools for managing multiple clusters and visualizing cluster infrastructure
• Discussion of UI tools for Kubernetes management, including Argo CD and Flux
• Use cases for managing multiple Kubernetes clusters through a management cluster
• Introduction to Rawkode Academy, a YouTube channel focused on cloud-native technology and Kubernetes learning
• Challenges of keeping up with evolving technology and importance of sharing knowledge and expertise
• Example episode of Klustered, where hosts Thomas Stromberg and Kris Nova intentionally try to "wreck each other's clusters" in a livestream
• The hosts discuss episodes of Rawkode Academy where they fix broken Kubernetes clusters with varying levels of complexity.
• Kris Nova uses advanced techniques (LD_PRELOAD, kernel modules, eBPF) to debug a cluster, while Thomas Stromberg uses forensic analysis tools to help identify issues.
• David Flanagan recommends an episode featuring MayaData's team discussing CSI driver development and storage architecture.
• The hosts discuss the format shift of Rawkode Academy from individual fixes to more complex cluster breaks.
• They also mention the evolution of breaks in clusters over time, with participants now modifying Go code for kubelet and recompiling it.
• Gerhard Lazu suggests renaming Rawkode Academy to "Break my Kubernetes" or a similar title due to its focus on debugging and fixing issues.
• The conversation turns to the complexity of Kubernetes clusters and how each one is unique in its problems, making debugging and running them efficiently challenging.
• Challenges of managing workloads across many servers
• Kubernetes as a solution for container management
• Trade-offs between microservices architecture and operational complexity
• Declarative configuration and stateful declaration in Kubernetes
• Using Kubernetes with monolithic applications
• Benefits of using Kubernetes, including service discovery, DNS, reconciliation, and remediation
• Ecosystem and community around Kubernetes and its software extensions (controllers and CRDs)
• Crossplane as an alternative to Terraform for managing infrastructure as code
• Infrastructure deployment using Crossplane
• User data scripts for provisioning devices
• Equinix Metal provider integration with Crossplane
• Complexity of deploying Changelog's monolithic app
• Kubernetes issues with Kube-proxy, Calico, and Cilium
• Performance problems with long HTTP request tails
• Blue/green deployment methodology for upgrades and testing
• Use of bare metal for CPU-intensive tasks or stream processing to improve performance
• Virtualized setups can suffer from "noisy neighbors" issues due to shared resources
• Cloud providers' interest in maximizing costs and profits leads to resource contention
• Hybrid architectures with both virtualized and bare metal infrastructure may be necessary
• Equinix Metal's partnership with cloud services like Fly.io for building a CDN in 5 hours
• Evaluating the benefits of using bare metal versus managed Kubernetes services for specific workloads
• Benefits of using bare metal infrastructure compared to virtualized environments
• Tinkerbell project: an open-source tool for deploying and managing bare metal infrastructure
• Challenges of operating bare metal, including the need for specialized knowledge and expertise
• Equinix Metal's API and high-level abstractions (e.g. Crossplane, Kubernetes) for managing bare metal resources
• Pros and cons of using bare metal, including flexibility, performance, and visibility into system operations
• Potential use cases and applications for bare metal infrastructure
**Gerhard Lazu:** Before the episode I mentioned about my history with Packet, that neither of you are aware of. I almost joined Packet in the summer of 2019, and do you know what happened?
**David Flanagan:** No.
**Gerhard Lazu:** Okay. That's the answer which I was expecting... \[laughs\] There's two people that know what happened. It's Zach and Dizzy. Zach, "Emails got lost in the shuffle." That's exactly what happened. I didn't know what he meant at the time, because I knew nothing about Equinix Metal, so I couldn't imagine ...
**David Flanagan:** It is disbelief, because I can't believe what you're telling me, that you almost worked at a company, and the reason that you're not is because an email just was missed?
**Gerhard Lazu:** Emails got lost in the shuffle, yes. So I didn't follow up as much as I should have maybe... Actually, I think you're right, David. Maybe on paper I wasn't as good as I thought I was. So Zach, when he got my email he like replied because Bruce at the time was the head of engineering. But Bruce just le...
**David Flanagan:** \[04:16\] You should just email tomorrow and be like "Hey, can we pick this back up?" And then just come and work with us. I think that'd be great.
**Gerhard Lazu:** Okay, I'll think about that. Thank you for that. That's one idea, for sure. But the thing which I wanted us to talk about is what attracted you to Packet in the first place? I'll go last. Marques, would you like to go first? What attracted you to Equinix Metal?
**Marques Johansson:** Sure. It's interesting, your setup there, because I hadn't realized that you have a strong engineering background before we got to know each other the last time... And I'm wondering if the role that you would have been looking for would have been in engineering, or would have been, say, on our te...
I liked what I did previously at Linode, where I was pulling together an ecosystem of tools, and I guess I wanted to relive that experience a bit with the learning of Kubernetes behind me. And there was a strong use and need for that kind of tooling a Equinix Metal.
**Gerhard Lazu:** That makes sense. What about you, David? What attracted you to Equinix Metal?
**David Flanagan:** It was all one huge misunderstanding, and I'm surprised that I'm still here.
**Gerhard Lazu:** So it's basically the opposite of me, right? \[laughs\]
**David Flanagan:** I thought I was joining the Metallica fan club, and now I'm writing code and doing dev rel for a bare metal cloud company. No, I think I've found an interesting career, and I think because I've always worked directly with bare metal for the last 20 year - you know, there was no cloud back in 2001 wh...