Datasets:
willtheorangeguy
/
2021-Ship-It-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.8k
[776.42 --> 776.76] Yes.
[777.02 --> 782.62] The difference is that in the pull-based deployment, there's an operator that observes the image registry.
[783.38 --> 783.66] Right.
[783.66 --> 786.46] And then updates the environment repository.
[786.46 --> 793.52] The environment repository is basically which stores the config for everything that's running in an environment.
[793.94 --> 795.76] So basically those will be our YAML manifests.
[797.30 --> 798.64] Currently that doesn't happen.
[799.62 --> 808.24] And the reason why this flow is prescribed is to prevent things like calling on latest when latest is broken.
[809.24 --> 809.28] Okay.
[809.48 --> 810.52] Or latest changes, right?
[810.52 --> 811.72] Because you don't know what you're running.
[811.72 --> 812.16] Right.
[812.16 --> 815.74] So you're trying to capture your production as much as you can.
[815.98 --> 818.16] Like not actually like not as much like fully, right?
[818.22 --> 819.80] Like to the SHA, not even to the version.
[819.92 --> 828.46] Because when you tag an image with a version like v1.1.0, you can update the tag to point to a different SHA.
[828.80 --> 831.76] So you want to point to a specific SHA, which will not change.
[831.80 --> 835.70] It's like a get SHA, but it's equivalent in container images.
[835.70 --> 838.28] Which is what we would want.
[838.90 --> 844.94] Which is important for, I suppose, like recovery from a disaster.
[845.14 --> 848.16] Like so in this case, a disaster happened.
[848.78 --> 848.88] Yeah.
[849.24 --> 849.66] Implication failed.
[849.76 --> 850.52] You needed to reboot.
[850.66 --> 852.08] You rebooted, but you called upon latest.
[852.20 --> 853.12] Latest wasn't right.
[853.28 --> 853.58] And so.
[853.94 --> 854.24] Yes.
[854.40 --> 860.86] If you'd have had continuity in place, the operator would have told the environment repository which version was or which SHA to point to essentially.
[860.86 --> 864.50] So that when you reboot, you don't pull from a broken latest.
[864.50 --> 869.56] So a couple of things had to go wrong in our case, right?
[869.64 --> 870.54] When incident two.
[871.06 --> 872.90] It's the version that was running.
[873.18 --> 874.76] That one came down as well.
[875.12 --> 877.02] So the version that was running came down.
[877.10 --> 878.08] It had to be rebooted.
[878.50 --> 879.28] The pod.
[879.70 --> 881.84] And when the pod was like restarted.
[882.44 --> 884.06] Because it was pointing to latest.
[884.38 --> 886.12] It pulled the broken version.
[887.18 --> 888.70] So that happened as well.
[889.30 --> 891.68] On top of latest being broken.
[891.68 --> 896.48] So it needs to be like a sequence of events for this to happen.
[896.74 --> 898.98] Which is what happened in our case.
[899.02 --> 900.00] And that's why those are rare.
[900.60 --> 904.26] So as I mentioned, like in the years since I had this set up, it only happened once.
[905.38 --> 907.02] It was enough for us to have an incident.
[907.32 --> 908.46] It wasn't a major one.
[908.54 --> 911.44] It was just a minor one because production was up.
[911.90 --> 912.18] Right?
[912.18 --> 913.14] Everything was cached.
[913.54 --> 914.68] We served from the CDN.
[914.82 --> 916.46] We are serving from CDN everything.
[917.04 --> 918.54] Except the authenticated users.
[918.76 --> 923.00] Except the, how do you call them, the dynamic requests.
[923.44 --> 924.38] So not like the gets.
[924.86 --> 926.52] This was like a post, a patch.
[926.56 --> 927.54] And we have quite a few of those.
[927.62 --> 929.74] I didn't actually realize how many of those we have.
[929.74 --> 936.42] Because whenever we visit a link, like news in press, that's the most popular one.
[936.50 --> 937.04] We keep hitting.
[937.82 --> 939.42] We keep doing a lot of posts.
[940.42 --> 942.08] So there's that.
[943.58 --> 948.10] But anyways, it was like up for anyone that like was casually browsing it.
[948.20 --> 949.54] People could listen to podcasts.
[949.54 --> 954.28] Only like a few URLs that were not in the CDN were not available.
[955.52 --> 959.08] That's a good, to your point, Jared, the unsolved mysteries.
[959.08 --> 961.84] If you listen to Kaizen 20, we solve some more mysteries for you.
[961.86 --> 966.14] So if you left that conversation thinking like Gerhardt, what actually happened behind the scenes?
[966.22 --> 967.52] Well, we've kind of recapped some of that.
[967.76 --> 971.32] So the mystery is solved for those unsolved mysteries of Kaizen 20.
[971.56 --> 971.84] You're welcome.
[973.68 --> 976.78] But I do have a very exciting news.
[977.48 --> 980.74] So not only we solve that mystery, we did something even better.
[981.06 --> 986.02] And I think we discussed about this also in episode 20 about a tighter honeycomb integration.
[986.02 --> 993.00] So one of the things which we did since, we integrated Honeycomb with Fastly with our CDN.
[993.38 --> 1001.96] So we can see a lot more details about how the CDN behaves, which are the cache hits, which are the misses.
[1003.42 --> 1006.22] When I say, I don't mean misses like the misses.
[1006.58 --> 1008.50] I mean like M-I-S-S-E-S.
[1009.02 --> 1009.18] Yeah.
[1009.34 --> 1010.22] There's no U there.
[1011.04 --> 1011.80] Solid clarification.
[1011.80 --> 1012.28] Yeah.
[1013.72 --> 1017.54] And we can just like drill down, observe a lot of stuff.
[1017.64 --> 1018.38] That's amazing.
[1018.48 --> 1025.60] Like the level of visibility which we have right now, we can answer so many questions, including the pull request, which we had to open.
[1026.30 --> 1029.76] I'm going to find it up now because I forgot the exact number.
[1029.88 --> 1032.06] There were some new pull requests since.
[1032.74 --> 1034.04] This is pull request.
[1034.04 --> 1035.42] No, sorry.
[1035.54 --> 1035.90] Issue.
[1036.50 --> 1037.28] Not a pull request.
[1037.58 --> 1040.36] Issue 383.
[1041.38 --> 1047.30] Why do some MP3 requests take 60 seconds or more while others complete quicker?
[1047.30 --> 1062.54] So we have an answer to this question as well as full visibility into how the CDN behaves, the app behaves, the ingress nginx, how it behaves and how they interact among one another.
[1062.98 --> 1065.94] And some of the details which we get are fascinating.
[1065.94 --> 1072.86] Like I can finally be properly curious in prod and I didn't know what it meant until I did this integration.
[1073.32 --> 1075.76] And some of the level of detail is just amazing.
[1077.20 --> 1090.80] So we can, for example, see the top URLs, the top episodes by browser, by user agent, by data center, by country, by city.
[1091.00 --> 1093.20] It's just like so much insight.