text
stringlengths
0
1.8k
[3696.24 --> 3698.42] There was a lot of topics and talks to pick from.
[3698.94 --> 3700.68] So that was a very good experience.
[3701.12 --> 3701.94] Choose the variety.
[3702.08 --> 3703.16] Yes, it is a big conference.
[3703.28 --> 3703.58] You're right.
[3703.90 --> 3705.46] It's one of the biggest ones I know.
[3705.94 --> 3707.68] And it's just like so diverse.
[3707.68 --> 3709.58] I love the diversity of KubeCon.
[3709.68 --> 3713.08] I'm not aware of any conference that gets diversity better.
[3713.28 --> 3715.24] And I mean diversity from all perspectives.
[3715.54 --> 3716.44] Any favorite talks?
[3716.78 --> 3719.06] Anything that stood out that was memorable?
[3719.60 --> 3721.72] Because we spoke about memorable communication.
[3722.02 --> 3723.00] I didn't watch.
[3723.18 --> 3723.72] There were too many.
[3723.72 --> 3729.50] So for me, it was quite late since I'm in Europe.
[3729.86 --> 3734.70] So on Wednesday, my talk started at half past 11.
[3735.14 --> 3739.40] So before that, I just watched one talk to see how things are working with the platform.
[3739.40 --> 3745.04] And thereafter, I was too tired to continue watching talks like at 1 a.m. in the morning.
[3745.64 --> 3745.72] Yeah.
[3745.84 --> 3751.04] The next day, I was watching one, which was about a new generation of Nuts, just to see
[3751.04 --> 3754.24] how the Nuts messaging system works compared to RabbitMQ.
[3754.64 --> 3756.36] So I enjoyed watching that.
[3756.92 --> 3761.38] You do know that all these talks, first of all, you can watch them on demand in the platform
[3761.38 --> 3763.76] before they become available on YouTube.
[3763.76 --> 3768.64] So what I tend to do, and this is what I've done.
[3769.02 --> 3773.74] While I haven't watched the talks as they happened, only a few, what I've done, I would
[3773.74 --> 3775.92] go back to the previous day, what I've missed.
[3776.04 --> 3779.70] Because you're right, like three, four o'clock, staying up until three, four o'clock, it doesn't
[3779.70 --> 3780.40] really make sense.
[3780.76 --> 3781.94] Well, at least not to me.
[3782.42 --> 3787.02] And what I have done next day, I would go over the previous talks, go over all of them,
[3787.36 --> 3789.84] see if there's something that resonated with me.
[3789.84 --> 3793.90] And if it did, I would watch parts of it or the parts that really stood out.
[3794.28 --> 3798.90] And that was a good experience because I could consume the talks much quicker before they
[3798.90 --> 3800.00] become available on YouTube.
[3800.10 --> 3803.70] So I could consume a lot more content and content that was relevant for me.
[3803.78 --> 3808.52] That is actually one of my favorite parts of a virtual conference where all this is recorded
[3808.52 --> 3810.46] and it's available as it happens.
[3810.94 --> 3812.52] So I enjoy the platform.
[3812.66 --> 3816.92] I think the platform enables you to consume and to connect to the conference in a different
[3816.92 --> 3817.14] way.
[3817.30 --> 3818.04] I thought that was good.
[3818.04 --> 3819.94] What was the most valuable content to you?
[3820.78 --> 3823.32] I really enjoyed eBPF, I have to say.
[3823.76 --> 3827.30] It's something like the whole eBPF ecosystem, super, super interesting.
[3827.94 --> 3833.02] Liz Rice's talk, cloud native superpowers with eBPF, because I just love the kernel.
[3833.30 --> 3838.02] I just love that observability, understanding what's happening inside the kernel.
[3838.48 --> 3840.46] That's the talk that really resonated with me.
[3840.54 --> 3845.78] It's something that I picked up on at last KubeCon, but this one, I could focus a bit more
[3845.78 --> 3847.06] on the eBPF ecosystem.
[3847.06 --> 3849.94] I didn't even know that there's actually an eBPF foundation.
[3850.46 --> 3852.46] I learned about that at this conference.
[3852.96 --> 3859.06] And yeah, it's just really interesting networking and the kernel and performance and metrics
[3859.06 --> 3860.70] and that sort of thing.
[3860.92 --> 3866.30] My most important takeaway about eBPF is that it's all about kernel events.
[3866.62 --> 3868.56] And events, you know, I mean, I love eventing.
[3868.70 --> 3870.02] It's a great concept.
[3870.40 --> 3873.50] And I think the way it's implemented, like the underpinnings are really, really solid.
[3873.50 --> 3876.34] I can see some amazing things coming out of this.
[3876.84 --> 3880.08] Have you used eBPF in your projects you're working on?
[3880.64 --> 3884.60] Not yet, but all that is going to change in the next few months.
[3885.14 --> 3890.08] So parka.dev, that's one of the first things that I'll be setting up.
[3890.18 --> 3891.44] And the next one will be Cilium.
[3891.70 --> 3894.12] Cilium with Hubble and a couple more things.
[3894.12 --> 3899.04] I think the level of observability from a kernel perspective is unique.
[3899.34 --> 3901.38] I haven't seen anything like that before.
[3901.72 --> 3907.56] And now that you mentioned that, I think the only utility that I've used that uses eBPF
[3907.56 --> 3910.86] under the hood was net data, but not extensively.
[3911.02 --> 3915.10] Only, you know, like at a brief level, superficial level.
[3915.36 --> 3915.96] It's good.
[3915.96 --> 3920.86] And it's not much different than it was before with eBPF or since it added eBPF integration.
[3921.14 --> 3925.24] But that's the first one that I have used with eBPF, now that I remember.
[3925.58 --> 3926.90] What else would you like to talk about?
[3927.52 --> 3929.80] One good experience was speaker support.
[3930.06 --> 3935.30] So there was a dedicated Slack channel and support was answering with the response time
[3935.30 --> 3935.92] less than a minute.
[3936.60 --> 3941.80] So when we asked a question, it just got flagged and someone was saying they will look up the
[3941.80 --> 3943.48] answer or get in touch with us.
[3943.90 --> 3945.58] So that was really great support.
[3945.58 --> 3949.62] Well, that sounds like VIP speaker support to me.
[3950.02 --> 3951.86] And I'm glad that it worked so well in practice.
[3952.10 --> 3952.48] It was.
[3952.64 --> 3952.94] It was.
[3953.36 --> 3957.98] Yeah, I'm really happy when ideas like that work well out in practice, you know, because
[3957.98 --> 3959.56] you never know what's going to happen.
[3960.00 --> 3964.00] But it just goes to show that KubeCon is a really well-organized event.
[3964.34 --> 3967.52] And there's like so many moving parts to it.
[3967.60 --> 3971.76] It's just crazy how much happens behind the scenes.
[3971.76 --> 3976.72] And big props to all the organizers and to everyone that made it happen.
[3977.08 --> 3979.92] It was difficult because it was both in-person and virtual.
[3980.42 --> 3982.40] And I think the combination worked really well.
[3982.58 --> 3985.16] But next time, I'm also thinking of going in-person.
[3985.56 --> 3988.80] So Valencia, next year, I would very much like to be there.
[3988.86 --> 3989.30] And who knows?
[3989.44 --> 3990.08] Maybe we'll meet.
[3990.38 --> 3991.08] Wouldn't that be nice?
[3991.08 --> 3991.52] Right.
[3993.52 --> 3994.02] Okay, David.
[3994.10 --> 3995.34] Well, thank you for making the time.