text stringlengths 0 1.8k |
|---|
[157.20 --> 158.26] It really is insane. |
[158.44 --> 162.36] I mean, this was just, this show was just an idea recently. |
[163.36 --> 174.18] And that's, I think, I think anybody who makes things come to life from nothing is always flabbergasted by the creation, I suppose, once you sort of get into it. |
[174.20 --> 177.24] But podcasting is a little different because it really is a journey. |
[177.78 --> 181.14] It's a journey pre-production and it's a journey post-production. |
[181.14 --> 183.96] Now we're obviously post-production 30 episodes in. |
[184.32 --> 187.70] And I think it's just kind of crazy looking back thinking like this was just an idea. |
[188.34 --> 192.00] And then in particular, the podcast, the impact to us and to the audience. |
[192.00 --> 193.96] And I think that's just, that's why I love it. |
[194.08 --> 194.66] That's why I love the game. |
[195.48 --> 195.64] Yeah. |
[195.84 --> 197.76] I mean, we shipped it, right? |
[197.80 --> 198.48] It took us a while. |
[198.58 --> 201.56] It took us five months to ship the first episode, the first three episodes. |
[201.56 --> 203.44] And then it was like a roll. |
[203.44 --> 207.98] What blows my mind is that my mind is on episode 40. |
[208.52 --> 210.66] And most people don't realize this. |
[210.96 --> 213.98] Like the next five episodes are pretty much like locked in. |
[214.96 --> 217.48] The guests, the topics, the flow. |
[217.80 --> 221.86] And even the five ones after that are like, you know, nebulous. |
[222.02 --> 224.78] Nothing locked in for real, but it's coming. |
[224.78 --> 229.08] So for me, it's even like more mind-blowing because I'm already like in February. |
[229.30 --> 230.70] I'm thinking February right now. |
[231.70 --> 232.14] Yeah. |
[232.16 --> 233.04] You just live in the future. |
[233.14 --> 239.80] I think you might be the most prepared and scheduled out podcaster in the entire universe, Gerard. |
[241.42 --> 241.86] Okay. |
[242.48 --> 245.62] I'm happy that I got scheduled out through December. |
[246.12 --> 247.60] But you're, no, it is. |
[248.52 --> 249.12] Thank you. |
[249.12 --> 255.10] I mean, I don't want to like, I don't want to like leave myself open to like, you know, unique encounters and like, you know. |
[255.18 --> 255.94] Yeah, that's the challenge. |
[256.42 --> 258.56] Serendipity is taken out and when you're scheduled out. |
[259.34 --> 260.46] That is a great word. |
[260.56 --> 261.46] I haven't heard it in a while. |
[261.60 --> 263.40] I was, I thought I was the only one using it. |
[264.90 --> 265.26] Okay. |
[265.74 --> 267.06] That'd be a surprise and delight. |
[268.54 --> 268.90] Right. |
[269.06 --> 271.06] So, well, thank you very much. |
[271.10 --> 273.22] In which case, Gerard, I appreciate that. |
[273.32 --> 273.66] Thank you. |
[273.66 --> 281.36] And what I'm really excited about is, I don't think many people realize this, but there is like a theme to this. |
[281.52 --> 282.54] And there are like multiple themes. |
[282.60 --> 285.72] So like a couple of episodes, they kind of cluster together and there's a buildup. |
[286.48 --> 292.22] And a lot of the episodes that we had, like the last 10, 15 ones, they're leading to something. |
[292.36 --> 293.44] They're building to something. |
[293.74 --> 297.52] And that will be the Christmas episode, episode 33, which I'm very excited about. |
[298.24 --> 299.64] We'll come back to that a bit later. |
[299.64 --> 305.90] But one of the things which is on my mind is the incident too. |
[306.18 --> 312.12] I mean, our last episode 20, our last Kaisen episode 20 was all about incidents. |
[312.56 --> 314.20] We call it five incidents later. |
[315.20 --> 323.08] And there was something which I wanted to understand, which I didn't at the time, was why was an unhealthy pod put back into service? |
[324.10 --> 325.12] Do you remember that? |
[325.62 --> 326.32] I do remember that. |
[326.60 --> 327.64] We didn't have answers. |
[328.26 --> 328.50] Yes. |
[328.50 --> 332.02] So my answer is we're using the latest tag. |
[332.42 --> 342.20] What that means is that our, like, if something is unhealthy and it has to go back to the previous one, it will use the latest tag. |
[342.36 --> 343.44] But latest has moved on. |
[343.84 --> 347.16] So it doesn't keep the old SHA, the one that was working. |
[347.42 --> 348.96] It says always the latest. |
[349.34 --> 354.12] So if you were to go back, then you always go back to the latest. |
[354.26 --> 355.62] And by the way, the latest has already moved. |
[355.68 --> 357.02] So that's like the broken version. |
[357.02 --> 360.28] Ah, so you're pointing back to the same version, which is broken. |
[360.68 --> 361.08] Exactly. |
[361.80 --> 362.20] Exactly. |
[362.28 --> 363.08] Why are we doing that? |
[365.04 --> 366.38] Some corners have been cut. |
[366.38 --> 373.22] The honesty, I love it. |
[373.22 --> 375.44] That worked well for quite some time. |
[375.50 --> 379.72] So I have to say that even though those corners have been cut, there was like a tradeoff to be made. |
[379.86 --> 381.52] It was like a conscious tradeoff. |
[381.94 --> 382.16] Yeah. |
[382.16 --> 384.02] And it only failed once. |
[385.02 --> 385.26] Right. |
[385.30 --> 387.20] So that tradeoff is like bit us once. |
[387.82 --> 387.90] Right. |
[387.90 --> 399.62] But I think it is high time that we revisit the whole GitOps approach, the GitOps approach that we have, but not really have to how we run our infrastructure. |
[400.18 --> 410.44] So while we do version all the manifests and everything is in the repo and we apply them, some manifests reference like latest and latest can, you know, move. |
[410.44 --> 417.38] So we cannot, basically right now we don't capture everything we run at the SHA that we run. |
[418.00 --> 423.48] So Ingress Nginx, external DNS, we have versions for those, but for our app we have latest. |
[423.90 --> 427.08] The thinking goes, we always want to be running latest, right? |
[427.08 --> 428.72] Like when do you not want to run latest? |
[429.26 --> 430.76] Apparently when latest is broken. |
[431.50 --> 432.02] Exactly. |
[432.46 --> 433.92] One time when you definitely do not. |
[433.92 --> 434.56] That's when you don't want to run latest. |
[435.14 --> 440.58] So, but that's something that, yeah, we will, we will be investing in. |
[441.00 --> 445.04] I will be spending a bit, a bit of time on that among many other things. |
[445.04 --> 450.44] But that's, that explains this incident too, which I didn't have an explanation 10 episodes ago. |
[450.76 --> 452.86] How did you learn the, how did you learn of this? |
[452.86 --> 458.44] Um, I looked at the manifest and I tried to understand what happens. |
[458.58 --> 467.48] So I went through the steps of what would happen or of what happens in Kubernetes when like the, the new one gets, gets put in service. |
[467.70 --> 468.74] It fails. |
[468.98 --> 470.80] The old one crashes. |
[471.36 --> 473.98] And when it gets restored, it gets restored with latest. |
[475.02 --> 476.84] So that's what happened. |
[477.24 --> 480.98] So my developer brain sees something like this and I think infinite loop. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.