text stringlengths 0 1.8k |
|---|
• Introduction of Polar Signals, a company offering continuous profiling solution |
• Discussion of continuous profiling, its history, and how it can be done cost-effectively in production using eBPF and Kubernetes |
• Parca (a continuous profiling tool) is being opened up to the world at KubeCon |
• The goal of Parca is to provide a way for developers to optimize their systems and reduce costs by identifying performance bottlenecks |
• Continuous profiling is still a relatively new concept, and Parca aims to democratize it and educate the community about its benefits |
• The tool uses eBPF (extended Berkeley Packet Filter) to collect data on system performance metrics such as CPU, memory, disk operations, and network operations |
• Parca's UI has undergone significant improvements over a short period of time due in part to extensive dogfooding (using the software internally) |
• The developers use Parca themselves to optimize their own tool, creating a self-reinforcing cycle of performance improvement |
• Plans to productionize eBPF-related projects |
• Advice for those who couldn't attend KubeCon in person or virtually |
• Updates on Parca's development process and community involvement |
• COSI (Cozy Operating System Initiative) progress and implementation in Talos |
• Discussion of the future of operating systems, specifically with regards to API-driven interfaces and reduced reliance on SSH |
• Talos installation methods and ease of use |
• Creating a Kubernetes cluster with minimal setup and networking complexity |
• Using COSI or PXE booting for bare metal installation |
• Cloud deployment options and image upload requirements |
• Consistency across environments, including laptops, cloud, and bare metal |
• Minimalism and lack of unnecessary packages in Talos compared to other operating systems |
• Security features, such as reproducible supply chain, read-only file system, and ephemeral storage |
• Signing and tracing code commits from development to deployment for security and audit purposes |
• Concerns about minimalist systems and security |
• Use of musl instead of glibc and its performance implications |
• Talos' use of musl and Go programming language |
• Kubernetes and containerization with glibc |
• Host and container configuration for musl and glibc |
• Linux kernel version and LTS strategy |
• KubeSpan announcement and on-demand cluster scaling |
• Discussion of Andrew Rynhard joining an AWS Graviton instance to his laptop |
• Andrew Rynhard's excitement about attending KubeCon in person and meeting his company colleagues |
• Advice from Andrew Rynhard on how people who can't attend KubeCon in person should participate, including joining the CNCF Slack and watching catch-up videos |
• David Flanagan's personal updates, including the arrival of his new baby boy Caleb and his job change to be a developer advocate for Pulumi |
• Remote participation in KubeCon and managing multiple sessions |
• Comparison of David Flanagan's and Gerhard Lazu's methods for participating in remote KubeCons |
• Interacting with other attendees during virtual events |
• Chairing the operations track at KubeCon, selecting talks, and being familiar with upcoming sessions |
• GitOps tools Argo and Flux, their use cases, and benefits |
• The failed attempt to consolidate both tools into a single "GitOps Toolkit" in 2019 |
• Interest in understanding the strengths and weaknesses of each tool and attending an upcoming GitOps summit |
• Comparison between Flux and Argo for GitOps |
• David Flanagan's new role at Pulumi and his interest in infrastructure as code and continuous integration/delivery |
• Benefits of using Pulumi over TerraForm and HCL, including support for high-level programming languages |
• Comparison with other tools such as Dagger (using CUE), Crossplane, and CUE Blocks |
• Discussion of CUE language and its use cases, particularly in comparison to HCL and Pulumi |
• Discussion of limitations and constraints in infrastructure as code tools |
• Comparison of Dagger and Boundary for providing a single interface to infrastructure management |
• Advantages of Crossplane for continuous reconciliation and control over execution |
• Similarities between Pulumi, CDK from Amazon, and other tools for infrastructure as code |
• Preference for TypeScript as a language for infrastructure as code due to its strict typing and flexibility |
• Comparison of Go and TypeScript for use with Pulumi |
• Discussion of challenges in managing dependencies in Go |
• Changing format of Rawkode Live from high-level introductions to use case-specific content |
• Focusing on real-world applications and solutions with specific tools |
• Reducing decision fatigue by providing more practical examples and inspiration |
• Exploring the cloud-native ecosystem and its many projects |
• Importance of balance between breadth of knowledge and in-depth expertise |
**Gerhard Lazu:** One of my favorite talks from KubeCon in May, the European one, was Overview and State of Linkerd, and you all did a fabulous job... But I have to say, between you and Matei, I'm not sure who was the better one. I think it was a great, great talk. No, seriously, how is Matei doing? |
**William Morgan:** He is doing great. He is doing really fantastic. He's kind of a rising start in the CNCF. He was a Community Bridge participant as a student, just (I think) a year ago... And then he has already risen to the levels of Linkerd maintainer. So yeah, he's really fantastic. |
**Gerhard Lazu:** I really love that story, like him shipping code... Going from nothing to shipping code for Linkerd - that was amazing to see. And the enthusiasm, and the fresh perspective - all that's been great. |
So in May we heard many good things, many great things about Linkerd 2.10. I know that Linkerd 2.11 is out, so what is new, in the new version? |
**William Morgan:** Yeah, great question. So 2.10 was a big step, and 2.11 is even bigger. This is the first time where we have introduced policy into Linkerd, which means that you can now control which services are allowed to connect in to communicate with each other. Prior to 2.11, whenever you told Linkerd "Hey, I'm... |
**Gerhard Lazu:** \[04:20\] Okay. |
**William Morgan:** So that's a big -- you know, for anyone who's in the security world, this is the idea of micro-segmentation, and this sort of thing becomes very important. |
**Gerhard Lazu:** How do you declare that? Do you have a UI, do you have a configuration? How does that work? |
**William Morgan:** Yeah, so a lot of our design principles in Linkerd are to allow you to do powerful things with as little configuration as possible. And the way we do that typically is by sticking as close as we can to Kubernetes primitives. So rather than inventing some new version of a service - well, we just use ... |
So we've tried to avoid introducing CRDs, and I think prior to 2.11 we had two CRDs I think in total, from two years of development, or five years of development, or however you wanna count it. But with 2.11 we introduced two new CRDs. |
The way that it works is you express policy by using a set of annotations that you can set at the cluster level, at the namespace level, at the workload level... Or, in addition to that, you can add these CRDs that basically specify the types of traffic that are allowed. And that combination together is really elegant,... |
**Gerhard Lazu:** Yeah. Okay. That makes perfect sense, especially from the Kubernetes' primitives side; I really like how you're thinking about that. But one thing which I really loved about Linkerd was the visual element - the dashboards, the graphs, all that stuff. That was amazing. So I'm wondering, from that persp... |
**William Morgan:** Yeah, so one thing we've never done, and probably never will, is allow you to create those objects through the UI. So we've always wanted the UI to be a read-only tool that allows you to understand the state of the system. But once you get into like -- you know, you're dragging a slider, or you're p... |
**Gerhard Lazu:** That sounds great to me. That is a very wise decision, and I'm sure we'll come back to this later, another time, not today... But that sounds great. So which is your Linkerd top-of-the-mind item? And this can be something that you will be working on, or something that is like a hard problem that you'v... |
**William Morgan:** Yeah, so for me I think it's a theme more than anything else... And it's a theme that we didn't really expect when we were first starting to develop Linkerd, but it's one around security, around especially security of the traffic in your cluster. |
So we came into Linkerd in the early days of the project very reliability-focused. Our background was at Twitter, and Twitter was constantly down, at least at the time... So our vision for what we were doing was we were gonna have load balancing, and retries, and blue-green deploys, and all these reliability techniques... |
\[08:09\] So that was like our foray into the world of security, and that theme has continued to develop through the policy features, the micro-segmentation, and onto other features, more types of policies... You know, there's a lot more we can do in this area of "How do you secure the traffic in your cluster?" And it'... |
So that theme has been just developing for us over the past couple of releases, and it's gratifying not just because things like that are cool, but because people are using it, and they're getting a lot of value out of it, which is kind of like the end goal of Linkerd; if no one's using it -- I don't know, to me that's... |
**Gerhard Lazu:** Yeah. I know that that is a very big, complicated, meaty problem to tackle, which you're not going to solve in a patch release, maybe not even in a major release. It'll take many, many cycles to get it right... And it's changing as well, with all the new rules and regulations. I know that this is some... |
My top-of-mind is "Can Linkerd 2.11 still do linkerd install | kubectl apply -f?" Because that was amazing. You can install Linkerd in your Kubernetes with Linkerd? That just blew my mind when I first saw it, and I'm wondering, does it still work? |
**William Morgan:** Yup, that still works. We've maintained that. That's not typically the production deployment, because people are moving into repeatable deployments, and Helm charts, and config-as-code... But yes, that still works. I think that's still really important, because a lot of people -- believe it or not, ... |
**Gerhard Lazu:** How would you recommend someone that installs Linkerd in production? So this is a very nice getting started, which I find very valuable, especially when I'm trying things... I love when tools are really easy to use, and this is in my perspective one of the ways in which Linkerd is super-easy to get st... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.