text stringlengths 0 1.8k |
|---|
[480.98 --> 483.42] Is that going on here or does it just fail? |
[483.54 --> 485.78] Because if it runs latest, latest is broken. |
[486.14 --> 487.62] Runs latest, latest is broken. |
[487.72 --> 487.90] Yes. |
[487.96 --> 489.52] Does it just keep doing that over and over again? |
[489.84 --> 490.00] Yeah. |
[490.18 --> 495.06] So in our case, what happened was that the version that was running, that crashed. |
[496.64 --> 499.28] And because like, it's just meant to restore it, right? |
[499.34 --> 500.42] It crashes, not a problem. |
[500.50 --> 501.16] It'll come back. |
[501.62 --> 501.94] Right. |
[502.76 --> 507.00] But when it comes back, it doesn't know which version it should come back with because it has latest. |
[507.00 --> 512.68] And it resolves that when it boots and latest has moved along, which is where the problem comes from. |
[513.70 --> 519.16] So we need to capture the version of the app that we want to run. |
[519.60 --> 522.22] Often that the app, it's the app container image. |
[523.06 --> 525.86] Currently, because we use latest, that always changes. |
[527.58 --> 528.70] So, yeah. |
[530.30 --> 531.22] That's a challenge. |
[531.36 --> 533.86] It's always nice to get answers to mysteries. |
[533.86 --> 534.30] Yes. |
[535.42 --> 536.72] I love good mystery. |
[537.82 --> 539.42] Especially when I have an answer for it. |
[539.76 --> 541.06] Otherwise, it just drives me crazy. |
[541.18 --> 541.54] I hate it. |
[541.68 --> 543.14] Like, oh, what's the answer? |
[543.64 --> 549.02] It's like that show, Unsolved Mysteries, which I always avoided because, come on, give us the solution already. |
[549.14 --> 550.22] Have you guys ever watched that one? |
[550.36 --> 551.56] It was probably dead now. |
[551.68 --> 558.14] But back in the day, they would show these mysteries and they're like, people who are actively being sought by FBI or whatever. |
[558.88 --> 559.78] There's no solution. |
[559.88 --> 562.64] At the end, they're like, if you know where this person is, please let us know. |
[562.64 --> 564.50] I want the solution. |
[565.10 --> 565.22] Yeah. |
[565.30 --> 565.50] Yeah. |
[566.14 --> 568.90] It's those shows that don't have endings, essentially, that get me. |
[569.00 --> 570.28] It's like, I can't watch that. |
[570.56 --> 571.74] It just drives me crazy. |
[572.00 --> 572.24] Yeah. |
[572.82 --> 573.06] Yeah. |
[573.94 --> 574.30] Okay. |
[574.46 --> 576.22] So what are we doing to solve this then? |
[576.22 --> 580.48] If latest can't be used, how do we uncut that corner? |
[581.50 --> 588.24] So, right now, we have KeylessH, which basically watches the Docker image updates. |
[588.24 --> 591.58] And when there is an update, it will just basically update itself. |
[593.00 --> 597.06] But what we have in the deployment, it's also latest. |
[597.36 --> 601.18] So we need to use GitOps properly. |
[601.62 --> 605.28] What it means is commit in the manifest, the version of the app that should be running. |
[605.28 --> 609.68] And that should automatically be applied, which is where Argo CD comes in or something like that. |
[609.74 --> 610.64] I'm thinking Argo CD. |
[610.98 --> 612.10] Maybe there will be something else. |
[613.14 --> 619.24] So basically, the infrastructure gets continuously reconciled with what is versioned in the repo. |
[619.24 --> 623.24] And what we versioned in the repo is the app updates. |
[624.00 --> 633.52] 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. |
[634.00 --> 637.74] And there will be a reconciler, which will make sure that that is true. |
[639.44 --> 641.04] And that's currently what we don't have. |
[641.04 --> 643.56] So finish GitOps. |
[644.22 --> 646.98] We're 90%, maybe 95% there. |
[648.04 --> 652.38] Because we versioned the manifests, but we don't update them when the app updates. |
[652.68 --> 655.46] And we don't apply them when the app updates. |
[656.04 --> 657.16] So that's what's missing. |
[657.60 --> 664.46] Is there like one place to learn exactly what the requirements are for GitOps to comply, I suppose? |
[665.52 --> 667.58] You can search on Google, what is GitOps? |
[668.20 --> 670.30] And there's a lot of pages that describe. |
[670.30 --> 673.52] I think GitOps.org is a good resource. |
[674.28 --> 678.44] That's the one that I would recommend for learning what GitOps is. |
[679.22 --> 686.90] And in a few episodes, we'll have Alexis from WeWorks, where we'll be talking all about GitOps. |
[687.52 --> 690.74] So GitOps.org doesn't resolve anything for me. |
[691.24 --> 693.66] GitOps.tech, that's the one. |
[694.22 --> 698.52] So this is what you would consider the canonical resource for learning about GitOps, at least. |
[698.52 --> 701.38] It's going to link out to WeWorks. |
[701.38 --> 705.20] It's going to link out to a PDF, an EPUB book. |
[705.26 --> 707.00] So I guess this is a book, too. |
[707.94 --> 710.82] So last time when I've seen it, I've seen this has a few updates. |
[711.56 --> 712.90] I wasn't aware of the book. |
[713.00 --> 714.48] So that must be something new. |
[714.66 --> 717.32] It does say we've just released our short book on GitOps. |
[717.32 --> 717.78] There you go. |
[717.88 --> 720.62] So that's a new element, which I wasn't aware of. |
[721.08 --> 726.56] If you scroll down, you see push-based deployments, pull-based deployments, which is what we have, by the way. |
[726.62 --> 728.02] We have a pull-based deployment model. |
[729.84 --> 733.64] And WeWorks were the one that coined the term of GitOps. |
[733.64 --> 738.98] And this is the resource, like the canonical resource for me, at least, when it comes to GitOps. |
[739.72 --> 739.96] Okay. |
[740.14 --> 741.20] So they have this graph down there. |
[741.36 --> 745.40] Sorry, this, what do you call those things? |
[746.12 --> 747.26] Infographic, I guess. |
[747.80 --> 748.16] Infographic. |
[749.18 --> 752.96] A graphic to look at, essentially outlining what... |
[752.96 --> 754.32] Is there information on the graphic? |
[755.04 --> 755.52] Say again? |
[756.24 --> 757.76] Does the graphic have information on it? |
[758.10 --> 758.30] Yes. |
[758.30 --> 759.24] It does have information on it. |
[759.24 --> 760.94] So that's a classic infograph, then. |
[761.14 --> 761.54] That's right. |
[761.94 --> 767.20] It's really a graphic of what the flow is from application repository all the way to deployment. |
[767.40 --> 768.72] What should happen in there? |
[768.78 --> 774.50] So are you saying that we're somewhat adhering to this push-based deployment graph here? |
[774.68 --> 775.12] Yes. |
[775.62 --> 775.98] This idea? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.