text stringlengths 0 1.8k |
|---|
[1940.64 --> 1943.40] just in terms of Kubernetes, but just across the board, right? |
[1943.86 --> 1945.10] And AWS is what it is. |
[1945.18 --> 1948.00] So if you're on AWS, you're probably forced to be on AWS and whatever. |
[1948.20 --> 1948.94] You're on EKS. |
[1949.16 --> 1952.76] And then once you've got that, as I mentioned before, there's so much other stuff that has |
[1952.76 --> 1955.10] to be configured and deployed on top of that. |
[1955.28 --> 1957.72] And our best advice is just to keep it as simple as you can. |
[1957.72 --> 1963.54] Most of our customers have already spent so many innovation points when they are adopting |
[1963.54 --> 1964.00] Kubernetes. |
[1964.40 --> 1970.18] We kind of feel it's our mission, our job to help guide them towards more conservative |
[1970.18 --> 1976.30] solutions and fewer moving parts, because it's so tempting once you've got Kubernetes, |
[1976.42 --> 1979.30] like, oh, I guess I need Istio because Istio does all these cool things. |
[1979.38 --> 1979.82] It does. |
[1980.08 --> 1982.16] And if you need those things, that's great. |
[1982.46 --> 1983.38] Jump on board. |
[1983.56 --> 1985.96] But holy crap, is Istio complicated? |
[1985.96 --> 1987.50] And it's dangerous. |
[1987.72 --> 1991.08] I mean, like, if you misconfigure Istio, like, you can really do damage to your production |
[1991.08 --> 1991.44] traffic. |
[1991.94 --> 1996.86] And, you know, avoid any tooling that you don't have an immediate pain point for. |
[1997.14 --> 2001.88] When you look at the CNCF landscape, it can often look like you're in a toy store, you |
[2001.88 --> 2002.02] know? |
[2002.12 --> 2005.42] You see all these wonderful, cool gadgets, and you just want to grab them all up into |
[2005.42 --> 2005.86] your basket. |
[2006.04 --> 2010.78] But you need to show a lot of restraint, because every one of those that you add is something |
[2010.78 --> 2012.40] else you have to manage and understand. |
[2012.90 --> 2013.26] Oh, yes. |
[2013.60 --> 2013.88] Yes. |
[2014.08 --> 2016.80] Most people forget about that, like, install it, and that's it. |
[2016.80 --> 2018.20] Well, how are you going to upgrade it? |
[2018.20 --> 2018.32] Right. |
[2018.52 --> 2021.26] And some components don't upgrade as well as others. |
[2021.64 --> 2021.80] Yep. |
[2021.98 --> 2026.02] And then that just opens, like, a whole new world of problems, like, a whole new set of |
[2026.02 --> 2026.36] problems. |
[2026.88 --> 2031.00] Like, do you upgrade in place, or do you stand up another Kubernetes cluster? |
[2031.34 --> 2034.74] And if a cluster gets too big, well, should you split in multiple clusters? |
[2034.82 --> 2038.36] And before you know it, you're, like, you're solving problems that you didn't even know |
[2038.36 --> 2040.00] existed before you chose Istio. |
[2040.00 --> 2041.02] So maybe don't. |
[2041.36 --> 2041.38] Right. |
[2041.56 --> 2042.00] Exactly. |
[2042.40 --> 2042.84] Exactly. |
[2043.28 --> 2044.44] You're, like, where am I? |
[2045.40 --> 2045.84] Exactly. |
[2046.60 --> 2048.02] I thought I understood networking. |
[2048.26 --> 2048.80] No, you don't. |
[2049.52 --> 2049.68] Right. |
[2049.80 --> 2050.00] Yeah. |
[2050.08 --> 2052.98] When you understand networking, then you see how Istio actually works. |
[2053.08 --> 2054.20] You're, like, oh, my gosh. |
[2054.74 --> 2058.12] And there are some components that are kind of table stakes for a new cluster. |
[2058.34 --> 2062.32] Like, cert manager is a great example of just, okay, everybody should have cert manager |
[2062.32 --> 2063.12] running in their cluster. |
[2063.12 --> 2068.70] But there's so many other things that are cool and interesting, but probably not something |
[2068.70 --> 2068.96] you need. |
[2069.20 --> 2070.48] Another example is Helm. |
[2070.76 --> 2077.36] Helm, as a tool, is amazing for installing third-party packages, something that somebody |
[2077.36 --> 2078.74] else has to maintain, right? |
[2078.76 --> 2079.70] You need Postgres? |
[2079.88 --> 2082.36] Then, sure, use the official Postgres Helm chart. |
[2082.42 --> 2084.56] That's the best way to do it, by far. |
[2085.06 --> 2088.42] Well, Postgres may be a bad example, because there's also operators that do an even better |
[2088.42 --> 2089.00] job, right? |
[2089.00 --> 2095.72] But what I see teams immediately doing, because they just didn't know any better, they just |
[2095.72 --> 2099.70] assume that this is how you use Kubernetes, is they start building Helm charts for their |
[2099.70 --> 2100.68] internal applications. |
[2100.94 --> 2102.66] Small teams doing this. |
[2103.08 --> 2110.80] And Helm, although it's great for package distribution and consuming third-party software, in order |
[2110.80 --> 2118.24] to author a Helm chart, you are using a Turing-complete templating language in order to generate |
[2118.24 --> 2120.98] white space-sensitive data structures. |
[2121.38 --> 2122.38] How crazy is that? |
[2122.74 --> 2123.08] Oh, my goodness. |
[2123.08 --> 2123.68] It's just crazy. |
[2123.78 --> 2124.54] It's crazy, right? |
[2124.84 --> 2126.00] I'm glad it's not just me. |
[2126.10 --> 2127.46] That thing's exactly the same way. |
[2127.58 --> 2128.68] I'm glad it's not just me. |
[2128.74 --> 2129.58] So I'm not the crazy one. |
[2129.64 --> 2130.06] Okay, good. |
[2130.86 --> 2133.44] Okay, so I have confirmation that I'm not crazy. |
[2134.90 --> 2135.26] Okay. |
[2135.50 --> 2138.68] I don't know about that, but just one aspect, you're not crazy. |
[2139.08 --> 2139.52] Damn it. |
[2139.68 --> 2140.00] Almost. |
[2140.64 --> 2141.00] Almost. |
[2143.00 --> 2143.36] Almost. |
[2143.74 --> 2145.96] And the sad thing about it is they just don't know any better. |
[2145.96 --> 2147.14] They've got very simple applications. |
[2147.14 --> 2151.84] They're a small team, and they end up spending a lot of time building these Helm charts to |
[2151.84 --> 2154.10] make them, you know, to distribute them and stuff. |
[2154.16 --> 2154.84] You don't need that. |
[2155.06 --> 2162.98] Like, Customize, for example, is a great tool for managing your YAML when it's being deployed |
[2162.98 --> 2163.90] to multiple environments. |
[2163.96 --> 2165.76] Because you can make very small changes. |
[2165.98 --> 2168.94] Customize is much easier to understand, much easier to maintain. |
[2169.36 --> 2171.64] If you're really small, you don't even need a tool like that. |
[2171.68 --> 2174.62] You could just apply the YAML and just call it a day, you know? |
[2174.62 --> 2181.22] I think when a team chooses Kubernetes, where it should focus on is automation. |
[2181.58 --> 2188.08] Building out their own internal automation system, not just for managing the cluster using |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.