text stringlengths 0 1.8k |
|---|
**Gerhard Lazu:** Yes. I love a good mystery, especially when I have an answer for it... |
**Jerod Santo:** Exactly. |
**Gerhard Lazu:** Otherwise it drives me crazy. I hate it. Like, "Oh, \*\*\*\*! What's the answer?!" |
**Jerod Santo:** It's like that show, Unsolved Mysteries, which I always avoided, because... Come on, give us the solution already. Have you guys ever watched that one? It's probably dead now, but back in the day they would show these mysteries and they're like, people who are actively being sought by FBI, or whatever.... |
**Gerhard Lazu:** Unsolved cases. |
**Jerod Santo:** And I'm always like, "I want the solution!" |
**Adam Stacoviak:** Yeah. It's those shows that don't have endings essentially that get me. It's like, "I can't watch that..." It drives me crazy. |
**Jerod Santo:** Yeah. |
**Adam Stacoviak:** Okay... So what are we doing to solve this then? If "latest" can't be used, how do we uncut that corner? |
**Gerhard Lazu:** So right now we have Keel.sh, which basically watches the Docker image updates, and when there is an update, it will just basically update itself. But what we have in the deployment, it's also "latest". So we need to use GitOps properly. What that means is commit in the manifest the version of the app... |
So basically, the infrastructure gets continuously reconciled with what is versioned in the repo, and what we version in the repo is the app updates. So when a new image is built, there will be a new push to the repo, a new commit to the repo, which has the exact version of the app that should be running, and there'll ... |
So finish GitOps... We're 90%, maybe 95% there. Because we version the manifests, but we don't update them when the app updates. And we don't apply them when the app updates. So that's what's missing. |
**Adam Stacoviak:** Is there like one place to learn exactly what the requirements are for GitOps to comply, I suppose? You could search on Google what is GitOps, and there's a lot of pages that describe what is GitOps. |
**Gerhard Lazu:** I think GitOps.org is a good resource. That's the one that I would recommend for learning what GitOps is. And in a few episodes we'll have Alexis from WeaveWorks, where we'll be talking all about GitOps. |
**Adam Stacoviak:** So GitOps.org doesn't resolve to anything for me... |
**Gerhard Lazu:** GitOps.tech. That's the one. |
**Adam Stacoviak:** So this is what you would consider the canonical resource for learning about GitOps at least... It's gonna link out to WeaveWorks, it's gonna link out to a PDF, an ePUB book... So I guess this is a book, too? |
**Gerhard Lazu:** So the last time when I've seen it -- I'm seeing this has a few updates. I wasn't aware of the book, so that must be something new... |
**Adam Stacoviak:** It does say "We've just released our short book on GitOps." |
**Gerhard Lazu:** \[11:57\] There you go. So that's the new element which I wasn't aware of. If you scroll down, you see push-based deployments, pull-based deployments, which is what we have, by the way... We have a pull-based deployment model. And WeaveWorks were the ones that coined the term of GitOps, and this is th... |
**Adam Stacoviak:** Okay. So they have this graph down there... Or, sorry, this -- what do you call this thing? Infographic, I guess... A graphic to look at, essentially outlining what -- |
**Jerod Santo:** Is there information on the graphic? |
**Adam Stacoviak:** Say again? |
**Jerod Santo:** Does the graphic have information on it? |
**Gerhard Lazu:** Yes. |
**Adam Stacoviak:** It does have information on it. |
**Jerod Santo:** Oh, that's a classic infograph then. |
**Adam Stacoviak:** That's right. It's really just a graphic of what the flow is, from application repository all the way to deployment, what should happen in there. So are you seeing that we're somewhat adhering to this push-based deployment graph here, this idea? |
**Gerhard Lazu:** Yes. The difference is that in the pull-based deployment there's an operator that observes the image registry, and then updates the environment repository. The environment repository is basically which stores the config for everything that's running in an environment. So basically, those would be our ... |
**Adam Stacoviak:** And the reason why this flow is prescribed is to prevent things like calling on "latest" when "latest" is broken. |
**Gerhard Lazu:** Yes. Or "latest" changes. Because you don't know what you're running, so you're trying to capture your production as much as you can. Not as much like fully, like to the SHA. Not even to the version, because when you tag an image with a version, like v1.0, you can update the tech to point to a differe... |
**Adam Stacoviak:** Which is important for recovery from a disaster. So in this case, a disaster happened, the application failed, you needed to reboot, you rebooted, but you called upon latest, and latest wasn't right... So if you would have had continuity in place, the operator would have told the environment reposit... |
**Gerhard Lazu:** Yeah. So a couple of things had to go wrong in our case when instant 2. The version that was running - that one came down as well. So the version that was running came down, it had to be rebooted, the pod, and when the pod was restarted, because it was pointing to the latest, it pulled the broken vers... |
So it needs to be like a sequence of events for this to happen, which is what happened in our case, and that's why those are rare. So as I mentioned, in the year since I had this set up, it only happened once. It was enough for us to have an incident. It wasn't a major one, it was just a minor one, because production w... |
But anyways, it was like up for anyone that was casually browsing it; people could listen to podcasts. Only a few URLs that were not in the CDN were not available. |
**Adam Stacoviak:** That's a good -- to your point, Jerod, the unsolved mysteries... If you listen to Kaizen 20, we solved some more mysteries for you. So if you left that conversation thinking "Gerhard, what actually happened behind the scenes?" Well, we've kind of recapped some of that, so... The mystery is solved fo... |
**Gerhard Lazu:** \[16:12\] But I do have very exciting news... So not only we solved that mystery, we did something even better. And I think we discussed about this also in episode 20, about a tighter Honeycomb integration. So one of the things which we did since - we integrated Honeycomb with Fastly, with our CDN, so... |
**Jerod Santo:** Solved clarification... |
**Gerhard Lazu:** Yeah... \[laughs\] And we can just drill down, observe a lot of stuff... That's amazing. The level of visibility which we have right now - we can answer so many questions, including the pull requests which we had open. I'm going to fire it up now, because I forgot the exact number. There were some new... |
This is issue (not pull request) 383. "Why do some mp3 requests take 60 seconds or more, while others complete quicker?" 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... And some of t... |
We can for example see the top URL's, the top episodes by browser, by user agent, by data center, by country, by city... It's just so much insight. And this is just like the content stuff. Then it comes to the CDN. As I mentioned, the cache status; how many hits versus how many misses. We can slice and dice by audio re... |
**Adam Stacoviak:** So this is the first time we've been able to have observability to this level on our CDN. So to recap, we leverage it quite well, because all requests go through Fastly first, prior to hitting our application. So it would make sense that if you make that choice and lean that heavily, trust that much... |
**Gerhard Lazu:** Correct. |
**Adam Stacoviak:** And this is thanks to the details and visibility that Honeycomb gives us. |
**Gerhard Lazu:** Correct. Yeah. That was one of the big improvements since episode 20. And we can see the slowest requests, and we understand that the XML ones, like the sitemap, or the feeds that are the slow ones, they take 5 seconds sometimes to load. The website is fairly fast; the only time when it gets slow is w... |
**Adam Stacoviak:** \[20:37\] They were waiting that long, huh? |
**Gerhard Lazu:** They were waiting that long because they had to go all the way to our data center in New York. |
**Adam Stacoviak:** It’s probably a big GIF, too. |
**Jerod Santo:** Yeah, they always are. I mean, GIFs are just large files, unfortunately. |
**Adam Stacoviak:** Yeah, they tend to be megs. At least a meg, sometimes ten. Maybe 50, but... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.