text stringlengths 0 1.8k |
|---|
• Providers in Crossplane interacting with IASs |
• Dagger and Q: data language, block-based, and query APIs |
• Dagger's ability to move beyond infrastructure provisioning |
• Boundary as a continuous delivery component for applications |
• Constraints of Crossplane still being defined by YAML |
• Continuous reconciliation in Crossplane vs Pulumi |
• Control over actual reconciliation in Crossplane vs client-side in Pulumi |
• Dagger making infrastructure provisioning easy with minimal boilerplate |
• Comparison to Pulumi and CDK from Amazon for similar approaches |
• CDK having advantages over YAML alternatives |
• Similarities between Pulumi and CDK for TypeScript support |
• Benefits of using TypeScript for infrastructure as code due to its strict typing and ecosystem |
• Differences in experience between using Go versus TypeScript with Pulumi |
• Convenience factors of the TypeScript ecosystem compared to Go |
• Inventing tools that were half-working and often caused more pain than they solved |
• Switching from vendor-managed repositories to GoMod |
• Difficulty in choosing between multiple GitOps tools and CNI options |
• Raw Code Live's transition to use-case specific content instead of just introductory material |
• Importance of having breadth of knowledge about available tools, but also needing to apply them in real-world scenarios |
• Onboarding process and its importance for a smooth job transition |
• Acceleration and lack of time to appreciate the present |
• Future plans for Clustered, Raw Code Live, and Pulumi |
• Alignment of personal interests with new role at Pulumi |
• Wrap-up and thank yous from host and guests |
• Promotion of changelog.com podcasts and community |
[0.16 --> 5.90] I'm your host, Gerhard Lazu, and you're listening to Shibit, a podcast about getting your best |
[5.90 --> 8.48] ideas into the world and seeing what happens. |
[8.84 --> 13.82] We talk about code, ops, infrastructure, and the people that make it happen. |
[14.42 --> 18.56] Yes, we focus on the people, because they drive everything else. |
[19.10 --> 23.74] This is my first set of interviews from KubeCon Cloud Native Con North America 2021. |
[24.50 --> 27.36] Thank you, Katie Minders, for our changelog invite. |
[27.36 --> 32.82] I spoke with William Morgan, and he shares with us some of the finer Linkerd details, |
[33.36 --> 39.30] such as the underlying security theme, why native Kubernetes objects instead of more CRDs, |
[39.66 --> 41.26] and meeting team members in person. |
[41.82 --> 49.04] Frederik Bransik speaks about PARCA, a new continuous system profiling tool that uses eBPF to help |
[49.04 --> 51.94] you understand what is happening on your hosts. |
[51.94 --> 58.16] Andrew Reinhardt gives us a great TalosOS and KubeSpan perspective and shares some follow-up |
[58.16 --> 59.70] videos on these topics. |
[60.18 --> 64.92] The last conversation was with David Flanagan, you know him as RawCode, about new beginnings. |
[65.44 --> 71.02] It's only been less than two months since we've had him in episode 18, and he kept really busy. |
[71.48 --> 77.08] Caleb, his three weeks old baby boy, was the youngest attendee at this conference, and some |
[77.08 --> 79.64] talks made him sleepy, so good job everyone. |
[80.00 --> 83.68] Big thanks to our partners Fastly, LaunchDarkly, and Linode. |
[84.04 --> 85.94] Thank you for the great bandwidth, Fastly. |
[86.12 --> 91.68] You can learn more at Fastly.com, ship new features with confidence by getting your feature |
[91.68 --> 98.10] flags powered by LaunchDarkly.com, and thank you Linode for keeping our Kubernetes fast and |
[98.10 --> 98.46] simple. |
[98.46 --> 104.72] You too can run our infrastructure as we do via lino.com forward slash changelog. |
[110.92 --> 111.80] What's up shippers? |
[111.94 --> 115.36] This episode is brought to you by our friends at Fly. |
[115.72 --> 119.74] Fly lets you deploy your apps and databases close to your users in minutes. |
[120.00 --> 127.50] You can run your Ruby, Go, Node, Dino, Python, or Elixir app and databases all over the world. |
[127.50 --> 128.58] No ops required. |
[129.02 --> 131.48] Fly's vision is that all apps should run close to their users. |
[131.94 --> 136.12] They have generous free tiers for most services, so you can easily prove to yourself and your |
[136.12 --> 139.72] team that the Fly platform has everything you need to run your app globally. |
[140.14 --> 144.78] Learn more at fly.io slash changelog, and check out the speedrun and their excellent docs. |
[145.20 --> 148.52] Again, fly.io slash changelog, or check the show notes for links. |
[151.72 --> 155.62] We are going to ship in three, two, one. |
[157.50 --> 174.36] One of my favorite talks from KubeCon in May, the European one, was overview and state of |
[174.36 --> 174.68] Linkerd. |
[174.68 --> 177.04] And you, Will, did a fabulous job. |
[177.36 --> 182.38] But I have to say, between you and Mate, I'm not sure who was the better one, because it |
[182.38 --> 183.62] was a great, great talk. |
[184.02 --> 185.36] No, seriously, how is Mate doing? |
[185.66 --> 186.46] He's doing great. |
[186.74 --> 189.04] He's doing really fantastic. |
[189.56 --> 193.26] You know, he's kind of a rising star in the CNCF. |
[193.34 --> 198.90] He was a community bridge participant, you know, as a student just, I think, a year ago, |
[198.90 --> 203.30] and then has already risen to the levels of Linkerd maintainer. |
[203.50 --> 204.76] So yeah, he's really fantastic. |
[205.24 --> 206.08] I really love that story. |
[206.16 --> 209.52] Like him shipping code, going from nothing to shipping code for Linkerd. |
[209.74 --> 210.84] That was amazing to see. |
[211.06 --> 214.82] And the enthusiasm and the fresh perspective, all that's been great. |
[215.22 --> 220.24] So in May, we heard many good things, many great things about Linkerd 2.10. |
[220.50 --> 222.40] I know that Linkerd 2.11 is out. |
[222.54 --> 223.98] So what is new in the new version? |
[223.98 --> 225.72] Yeah, yeah, great question. |
[225.84 --> 229.64] So 2.11 is actually, 2.10 was a big step, but 2.11 is even bigger. |
[230.10 --> 234.98] This is the first time where we have introduced policy into Linkerd, which means that you can |
[234.98 --> 240.56] now control which services are allowed to connect and to communicate with each other. |
[240.84 --> 245.82] So prior to 2.11, you know, whenever you've told Linkerd, hey, I'm service A, and I want |
[245.82 --> 249.36] to talk to service B, Linkerd has done its best to make that happen, right? |
[249.40 --> 251.78] It'll do retries if there's a transient failure. |
[252.10 --> 253.10] It'll do load balancing. |
[253.10 --> 254.12] It'll do all this stuff. |
[254.72 --> 258.36] And now with 2.11, for the first time, you can say, no, A is not allowed to talk to B |
[258.36 --> 260.36] unless these conditions are met. |
[260.80 --> 265.32] So that's a big, you know, for anyone who's in the security world, this is the idea of |
[265.32 --> 268.68] micro segmentation, you know, and this sort of thing becomes very important. |
[268.96 --> 269.74] How do you declare that? |
[269.84 --> 270.70] Do you have a UI? |
[270.88 --> 271.72] Do you have a configuration? |
[271.96 --> 272.58] How does that work? |
[272.84 --> 278.82] Yeah, so we, a lot of our design principles in Linkerd are to allow you to do powerful things |
[278.82 --> 280.88] with as little configuration as possible. |
[280.88 --> 285.88] And the way we do that typically is by sticking as close as we can to Kubernetes primitives. |
[285.88 --> 289.98] So, you know, rather than inventing some new version of the service, well, we just use |
[289.98 --> 294.68] regular Kubernetes services rather than inventing abstraction layer on top of these other things. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.