Latest / Nutanix Weekly / Nutanix Weekly: Nutanix and Canonical Partner to Simplify Kubernetes Deployments with NKP and Ubuntu Pro
Transcript
- <p><!--block-->WEBVTT<br><br>1<br>00:00:04.000 --> 00:00:19.699<br>Philip Sellers: Welcome to another episode of Nutanix Weekly. I'm your host, Phil Sellers. I'm also the practice director for Modern Data Center here at Zintegra and want to say thanks for spending some time with us. This is another one of those<br><br>2<br>00:00:20.280 --> 00:00:24.729<br>Philip Sellers: content with context sort of situations. We like to<br><br>3<br>00:00:24.910 --> 00:00:52.130<br>Philip Sellers: to take the content we find online from our partners and add our real world context, our experiences and anything we're hearing from our clients collectively and add that to learn together. So I want to say, Welcome and introduce my co-host for today. Jayra Cox, architect at Nutanix and all around. Good Guy.<br><br>4<br>00:00:52.400 --> 00:00:59.219<br>Jirah Cox: Phil, who's your peer? At integra? That would be the practice director for archaic Data center.<br><br>5<br>00:00:59.400 --> 00:01:01.130<br>Philip Sellers: Archaic data center.<br><br>6<br>00:01:01.130 --> 00:01:05.909<br>Jirah Cox: Your modern data center right? Then, that implies somebody else is doing the Stone Age stuff.<br><br>7<br>00:01:05.940 --> 00:01:14.669<br>Philip Sellers: Well, I was. Gonna say, I think it's that statue of Matthew we've got in the office, or something, you know, just posed over there made out of marble.<br><br>8<br>00:01:16.220 --> 00:01:19.140<br>Jirah Cox: The classic Renadon's data center. I think.<br><br>9<br>00:01:19.390 --> 00:01:20.160<br>Philip Sellers: Yeah.<br><br>10<br>00:01:20.560 --> 00:01:33.857<br>Philip Sellers: yeah. Classical data center that that's got a ring to it. Right? You know, it just seems like something you would do with a gray beard. And what do you call the little spectacle like Mr. Beanut?<br><br>11<br>00:01:34.190 --> 00:01:34.850<br>Jirah Cox: Monocle.<br><br>12<br>00:01:34.850 --> 00:01:36.629<br>Philip Sellers: A monocle. Yes, that just.<br><br>13<br>00:01:36.630 --> 00:01:37.209<br>Jirah Cox: I mean, if you.<br><br>14<br>00:01:37.210 --> 00:01:37.930<br>Philip Sellers: Yes, I mean.<br><br>15<br>00:01:38.320 --> 00:01:41.332<br>Philip Sellers: I mean, between you, me and the recording. If you launch that position, please let me know.<br><br>16<br>00:01:43.460 --> 00:01:56.780<br>Philip Sellers: Director of Classical Data center. Well, this is great. I mean, we we do talk about modern data center, modern sort of things. An awful lot. And and that's on purpose. We.<br><br>17<br>00:01:56.850 --> 00:02:16.100<br>Philip Sellers: we think that the data center has changed. And there are a lot of ways you can choose to get the job done. But we advocate for a simplistic way with lots of choice and a lot of power. So that brings our friends, like Gyra from nutanix onto the podcast to talk about<br><br>18<br>00:02:16.200 --> 00:02:18.020<br>Philip Sellers: all things going on.<br><br>19<br>00:02:19.720 --> 00:02:24.940<br>Philip Sellers: But this will be a kind of interesting conversation, because this isn't<br><br>20<br>00:02:25.290 --> 00:02:29.059<br>Philip Sellers: necessarily the traditional world of Nutanix is a gyra.<br><br>21<br>00:02:30.446 --> 00:02:40.840<br>Jirah Cox: I guess not. I mean to be to be coy and and have the audience not read into what we're talking about. Yes, it's it is, it's newer to anything, for sure.<br><br>22<br>00:02:41.030 --> 00:02:44.320<br>Philip Sellers: Yeah, but it's a good thing. I mean, it still follows<br><br>23<br>00:02:44.690 --> 00:03:13.480<br>Philip Sellers: the core tenets of choice simplicity and performance. That sort of underlie everything Nutanix does. I don't know that that's an official 3 word tag, but I think it describes what Nutanix does really? Well, so we'll pull back the suspense here and and read you into what we're talking about. We're reviewing a blog post from May 7th on nutanix.com slash blogs.<br><br>24<br>00:03:13.650 --> 00:03:26.130<br>Philip Sellers: Title of today's Post is nutanix and canonical partner to simplify Kubernetes deployments with Nkp and ubuntu. Pro wow.<br><br>25<br>00:03:26.290 --> 00:03:27.989<br>Jirah Cox: It's awesome. Yeah, it's very exciting.<br><br>26<br>00:03:27.990 --> 00:03:32.229<br>Philip Sellers: With a Linux provider, so.<br><br>27<br>00:03:32.230 --> 00:03:41.330<br>Jirah Cox: And I mean, I'll even say not. I'm not. Gonna assume. This is part of the business negotiations, but my personal favorite distro of choice for the last 15 years.<br><br>28<br>00:03:41.330 --> 00:03:52.400<br>Philip Sellers: That that it's near and dear to my heart. You know, I learned on on Red hat varieties many, many moons ago. But yeah, let's let's be honest like.<br><br>29<br>00:03:53.450 --> 00:03:57.329<br>Philip Sellers: go a little nerdy here may lose a few listeners, bear with us, but.<br><br>30<br>00:03:57.330 --> 00:03:58.579<br>Jirah Cox: On this podcast.<br><br>31<br>00:03:58.580 --> 00:03:59.982<br>Philip Sellers: I don't know.<br><br>32<br>00:04:00.760 --> 00:04:06.419<br>Philip Sellers: rpm was an amazing thing. Package management and things like that with red hat was was<br><br>33<br>00:04:07.050 --> 00:04:12.500<br>Philip Sellers: incredible to me as a young person trying to learn Linux<br><br>34<br>00:04:12.630 --> 00:04:15.850<br>Philip Sellers: and Ubuntu got all those things right, you know.<br><br>35<br>00:04:16.360 --> 00:04:24.888<br>Philip Sellers: And you know the package management is is fantastic. And so yeah, it's my preferred distribution, too.<br><br>36<br>00:04:25.650 --> 00:04:32.109<br>Philip Sellers: I think they're just also a really good community partner in general. And so I I like them for that.<br><br>37<br>00:04:32.450 --> 00:04:43.449<br>Jirah Cox: They? They definitely were, I think, in my experience, where? Yeah, early on in the community building. Well, okay. Sorry for the nerdy, pop, quiz. Phil, do you know, what do you know what ubuntu means?<br><br>38<br>00:04:44.386 --> 00:04:52.100<br>Philip Sellers: I don't specifically know what it means. I do know that it is a a term from Africa.<br><br>39<br>00:04:52.100 --> 00:04:52.840<br>Jirah Cox: True.<br><br>40<br>00:04:53.330 --> 00:04:56.940<br>Philip Sellers: Not mistaken. Remember what it means.<br><br>41<br>00:04:56.940 --> 00:05:00.660<br>Jirah Cox: It means. I am what I am, because of what we all are.<br><br>42<br>00:05:00.810 --> 00:05:01.720<br>Philip Sellers: Yeah.<br><br>43<br>00:05:01.720 --> 00:05:27.640<br>Jirah Cox: And it so the community aspect of it is, even in the naming of the distro. I used to actually send off for the free the free Dvds right? Every single new, you know, rodent named release rodent, or I guess animal animal kingdom named release and for a while I, I, you know, had them on my bookshelf. And then I realized that was really quite silly. But but yeah, they were great. So the community is right there.<br><br>44<br>00:05:27.996 --> 00:05:35.480<br>Jirah Cox: baked into even the naming of of of ubuntu, and not to get terribly inflammatory here. But yeah, it's like<br><br>45<br>00:05:35.520 --> 00:05:54.800<br>Jirah Cox: usable, friendly, Debian. Sorry. Sorry, Debian. Diehards. But what do you mean? Debian is not friendly and usable. You know. Check out our forums. Okay, we'll stop that. But but yeah, and you know the the other funny<br><br>46<br>00:05:54.800 --> 00:06:13.320<br>Jirah Cox: high in here for the this. This theming of okay, of course, the the headline announcement is, you can now use use ubuntu and really ubuntu pro right. The actual commercially supported variant, not the community supported variant as the underlying substrate OS for running the Nkp container platform.<br><br>47<br>00:06:13.470 --> 00:06:18.113<br>Jirah Cox: which is great and fantastic for all of our joint customers.<br><br>48<br>00:06:18.990 --> 00:06:33.470<br>Jirah Cox: I scroll past a meme earlier today in in other nerd circles. Right? That was like, Oh, it's serverless. But then you look on the covers and it runs on servers right? And so the the tie in here would be okay. It's containers, so I don't care about the OS.<br><br>49<br>00:06:33.950 --> 00:06:38.370<br>Jirah Cox: And underneath that is, the OS. Is an OS.<br><br>50<br>00:06:39.100 --> 00:06:48.379<br>Philip Sellers: Yeah. And and here here I'm gonna ask the stupid question, why would you want to run Nkp in an ubuntu vm on Nutanix?<br><br>51<br>00:06:49.680 --> 00:07:02.899<br>Jirah Cox: But or anywhere, right in a Vm or or anywhere. Yeah, for sure. So and I guess here's my simplistic answer back is because so the containers have to run on Kubernetes. Kubernetes has to run on an OS. Somewhere.<br><br>52<br>00:07:03.150 --> 00:07:08.360<br>Jirah Cox: You could run that on like a free, open source. Community supported Linux distro<br><br>53<br>00:07:08.830 --> 00:07:25.459<br>Jirah Cox: that option does not go away. Just because there's now this also strong partnership with canonical for vin 2 pro but folks like security teams. Right? Folks like it. Leadership. Love to be able to say there's support at every level of the stack<br><br>54<br>00:07:26.006 --> 00:07:52.269<br>Jirah Cox: or we get better than say, free, open source software. Sla's around things like Cv patching right? Vulnerability management. You know, rapid mitigation. And so that's that's to to skip a little bit ahead to some of the the F's. And B's, as they say. You know of what this brings to the to the stack. That's something that you can do pro has in spades over over something that's, you know, would be a community based distro.<br><br>55<br>00:07:53.080 --> 00:08:12.590<br>Philip Sellers: Yeah. And and 2. I I think you hit the nail on the head. 1st of all is that long term commercial support that's necessary for the enterprise, and for really any business, right security has to be at the forefront. So getting those vulnerabilities patched, not having, you know, as aggressive<br><br>56<br>00:08:12.710 --> 00:08:28.080<br>Philip Sellers: of an upgrade cycle as open source sometimes forces upon people. These are problems that ubuntu pro solves their long term releases not unlike the model that Nutanix has had with their long term leases<br><br>57<br>00:08:28.581 --> 00:08:43.860<br>Philip Sellers: releases have have always helped with that from a support, ability standpoint. But you mentioned naming to, I think briefly, there, I love the naming. 25, 0, 4. Right now is plucky puffin. I mean.<br><br>58<br>00:08:43.860 --> 00:08:45.340<br>Philip Sellers: come on like.<br><br>59<br>00:08:45.980 --> 00:08:53.440<br>Philip Sellers: if you're listening to this, podcast. Do you not need a plucky puffin in your night life, I mean like, come on like.<br><br>60<br>00:08:53.440 --> 00:08:56.969<br>Jirah Cox: My life is, my life is plucky, puff, and deficient for sure.<br><br>61<br>00:08:58.350 --> 00:09:00.818<br>Jirah Cox: which is also a tongue twister.<br><br>62<br>00:09:01.230 --> 00:09:02.978<br>Philip Sellers: It is, they all have been<br><br>63<br>00:09:03.460 --> 00:09:04.386<br>Philip Sellers: But yeah,<br><br>64<br>00:09:04.990 --> 00:09:15.209<br>Philip Sellers: you know this. This is a real thing for the enterprise, you know, and obtaining support and and keeping things up to date. That's that's a huge thing. But<br><br>65<br>00:09:15.630 --> 00:09:21.029<br>Philip Sellers: this is also an embrace of a nciless<br><br>66<br>00:09:21.300 --> 00:09:27.759<br>Philip Sellers: way to leverage in Kp, because this Linux can run on bare metal.<br><br>67<br>00:09:28.300 --> 00:09:28.690<br>Jirah Cox: Yeah, sure.<br><br>68<br>00:09:28.690 --> 00:09:30.110<br>Philip Sellers: Support. Nkp.<br><br>69<br>00:09:30.410 --> 00:09:52.239<br>Jirah Cox: Very true. In fact, I mean with all respect to our friends that have moved to not even a new capability introduced here right like Nkp, since since it's since well, since before it joins the new 10 X family, right? Has been able to be part of your fleet management running containers anywhere, including on bare metal, for sure. Now, of course, the same. I would submit. The same value. Prop exists for<br><br>70<br>00:09:52.240 --> 00:10:05.018<br>Jirah Cox: using like an ubuntu pro on bare metal as it does exist, for in a Vm. It's, you know, security doesn't really care what the substrate is. It's an OS that needs some kind of a patch or mitigation. So you know, chop, chop, get to it,<br><br>71<br>00:10:05.670 --> 00:10:09.831<br>Jirah Cox: And I like the way that you felt called out like<br><br>72<br>00:10:10.540 --> 00:10:18.224<br>Jirah Cox: aligning more closely with enterprise patching right? Because so one of the earliest things that the article calls out here that<br><br>73<br>00:10:19.428 --> 00:10:43.729<br>Jirah Cox: one of the promises right of this platform from canonical is 10 plus years of security maintenance. So it actually kind of separates out what in most like consumer OS's are are to get are together intertwined mitigation of Cbes and security vulnerabilities and patching. And now with this you get those are intentionally broken out. I can mitigate findings from my security scanners.<br><br>74<br>00:10:44.044 --> 00:10:58.489<br>Jirah Cox: Very rapidly, but not actually, Rev. The version of the software that runs my stuff which might need a new requalification or go back to the lab, or whatever. Go back through engineering. I can securely patch, but not have to not have to upgrade.<br><br>75<br>00:10:58.960 --> 00:11:18.929<br>Philip Sellers: Well and and canonical, has a feature called live patch, also helping where doesn't actually require a reboot. So you're able to do kernel vulnerability patching so very low level in the operating system while keeping the system online. And so that's a huge differentiator for<br><br>76<br>00:11:19.429 --> 00:11:38.399<br>Philip Sellers: running Nkp on a ubuntu pro system. So you know that, and a host of other security features, you know, as with any pro or enterprise release, they're really talking about security here under the open source.<br><br>77<br>00:11:39.070 --> 00:11:41.540<br>Philip Sellers: Canonical umbrella.<br><br>78<br>00:11:42.010 --> 00:12:05.990<br>Jirah Cox: Yeah, and that matters so much to to practitioners, right? Because containers can't live migrate right? So to to drain to drain the host of the containers deposits running right. They have to get restarted somewhere else, which could be a failure in one of them, or if it was like a monolithic app in my container ecosystem. Would be minimally disruptive to my user base. If I can patch the host<br><br>79<br>00:12:05.990 --> 00:12:14.250<br>Jirah Cox: with the pod staying right where they are. That's of course, way way better. I can now Patch, honestly kind of like the rest of the Nci stack non-destructively<br><br>80<br>00:12:14.320 --> 00:12:16.168<br>Jirah Cox: during the business day.<br><br>81<br>00:12:17.217 --> 00:12:26.609<br>Jirah Cox: at the at the time of my choosing, and get those nights and weekends back, and not need to be on my laptop on a Friday night on the VPN. To to to push out a patch.<br><br>82<br>00:12:26.950 --> 00:12:42.449<br>Philip Sellers: Yeah. And I think that's that's the other part of this, too, is beyond the patching. You've got choice again in ways to deploy cost mitigation things like that, you know. If you're running nkp on bare metal<br><br>83<br>00:12:42.720 --> 00:12:59.009<br>Philip Sellers: ubuntu pro, you're not gonna have some of the same features. You get on Nci, that are storage specific and and things like that. But you know, for certain workloads that may be okay. If you've got ephemeral workloads that don't necessarily need data.<br><br>84<br>00:12:59.010 --> 00:13:15.090<br>Philip Sellers: But then you've got databases. This gives you a way to to unify Nkp across all of your different operating environments while also benefiting from the unique value that you get from an nci deployed Nkp stack. So<br><br>85<br>00:13:15.120 --> 00:13:25.890<br>Philip Sellers: again, getting a high level of choice in the way that you do things while being able to benefit from common standard operational practices.<br><br>86<br>00:13:27.210 --> 00:13:28.809<br>Jirah Cox: Totally. I mean, if I picture, like.<br><br>87<br>00:13:28.870 --> 00:13:57.490<br>Jirah Cox: you know, containers running underneath like a cash register that probably doesn't really need an nci stack right. But but there's still going to be a container host, right? And that's going to need some kind of patching. So now I can. You know my my security team or my container team can now patch whether it is in the data center in the cloud under the cash register, all with one mechanism right? And and one level of service to the business of now our OS patching doesn't need to take anything down or ever be noticed.<br><br>88<br>00:13:57.800 --> 00:14:02.009<br>Philip Sellers: But and I love that you went there with your example of cash registers, because<br><br>89<br>00:14:02.930 --> 00:14:20.610<br>Philip Sellers: I hate to use fast food. But it's an approachable thing we all interact with. And every one of the restaurants now has an app, which means they're running some level of infrastructure in every one of those stores, and everyone who's doing some level of door dashing and stuff like that.<br><br>90<br>00:14:21.010 --> 00:14:46.629<br>Philip Sellers: All of our restaurants, especially Post Covid. And and during Covid they became incredibly more connected, and a lot of them chose to create and architect these mobile applications and these user experiences on containers and on Kubernetes. That's something that we see over and over and over again with our enterprise customers. They're choosing to go this route.<br><br>91<br>00:14:47.327 --> 00:15:01.779<br>Philip Sellers: And it makes for that infinite scale. When you've got hundreds or thousands of different points, presence. It's just the way that the industry has shifted. Do you think we'll see that<br><br>92<br>00:15:02.300 --> 00:15:08.220<br>Philip Sellers: experience shift? Move down to smaller businesses over the next few years.<br><br>93<br>00:15:09.250 --> 00:15:16.880<br>Jirah Cox: Absolutely. I mean the easy one to always reach. For when we're, you know, doing a thinking deep thoughts about the feature, of course, is AI right like.<br><br>94<br>00:15:16.880 --> 00:15:17.300<br>Jirah Cox: sure.<br><br>95<br>00:15:17.300 --> 00:15:29.889<br>Jirah Cox: and even, and even with even even staying on fast food for one more second, like we've all seen the screenshots right of places, ex- experimenting with voice to text for ordering right? And so do I want that to run.<br><br>96<br>00:15:29.890 --> 00:15:30.700<br>Philip Sellers: Angles.<br><br>97<br>00:15:30.700 --> 00:15:31.350<br>Jirah Cox: There you go!<br><br>98<br>00:15:31.970 --> 00:15:52.179<br>Jirah Cox: Do I want that to run? Don't want that to run the cloud and pay by the pay, by the token, or don't want that to be effectively a container sitting on a Gpu or adjacent to a Gpu that can run through. You know the latest. Whatever whisper model it is that can do voice to text reliably and generate the order in my structured data format and push that over to cash register.<br><br>99<br>00:15:52.505 --> 00:16:09.769<br>Jirah Cox: And yeah, it's easy to imagine that kind of use case not needing a whole lot of virtualization, but needing an awful lot of governance around lifecycle of the the containers and the things that run them for sure. And and at that point retail, broadly right, I think, is is.<br><br>100<br>00:16:09.920 --> 00:16:20.930<br>Jirah Cox: I think, I mean this very respectively. It's like an AI playground, right like a AI applied to retail broadly is is I think, a a very much booming already, and only going to be growing industry.<br><br>101<br>00:16:21.370 --> 00:16:25.669<br>Philip Sellers: Yeah, I can only imagine what things I was seeing<br><br>102<br>00:16:25.820 --> 00:16:39.569<br>Philip Sellers: in the retail space around video, not just surveillance, but analysis of what a traffic flows through my stores look like what attracts more attention. You know, if I redesign this end cap<br><br>103<br>00:16:39.720 --> 00:16:49.000<br>Philip Sellers: in my store, which in cap gets more attention, what brings people to that, and makes them more<br><br>104<br>00:16:49.810 --> 00:16:54.389<br>Philip Sellers: intent to buy all those kinds of things being run.<br><br>105<br>00:16:54.850 --> 00:17:15.950<br>Jirah Cox: Or even like I mean, it's it's easy to imagine a B testing across stores right with data driven, you know. Let's take the let's take the subject of analysis out of it. Right? Here's the data that this in cap in that store makes people linger more than that one in that store, therefore, next week that one becomes our new standard, you know, on our on our layout models.<br><br>106<br>00:17:16.319 --> 00:17:24.369<br>Philip Sellers: Yeah, I mean you. You look at the Amazon app. You know they A B test a lot on this in live. You know that<br><br>107<br>00:17:24.999 --> 00:17:38.249<br>Philip Sellers: transaction where the checkout looks a little different. That's not a mistake. Y'all, that's them doing live a B testing with with their audience. And so you know that that's the kind of thing that<br><br>108<br>00:17:38.724 --> 00:17:57.099<br>Philip Sellers: it's happening more and more in the physical world. Now, just like you're talking about. And we didn't have access to to some of that. I thought it was cool that a video could be used to count the number of of people foot traffic, you know. But that was 10 years ago, and<br><br>109<br>00:17:57.209 --> 00:18:01.076<br>Philip Sellers: we've come so much further beyond that today.<br><br>110<br>00:18:01.779 --> 00:18:06.659<br>Philip Sellers: sentiment, analysis, you know, of voice and of text. You know.<br><br>111<br>00:18:06.660 --> 00:18:08.100<br>Jirah Cox: Real Time inventory.<br><br>112<br>00:18:08.100 --> 00:18:13.719<br>Philip Sellers: Yeah. Oh, the inventory stuff, I mean, you know all the little robotics and and applications<br><br>113<br>00:18:14.150 --> 00:18:19.730<br>Philip Sellers: inside of warehouses. You know, we we have a large retail customer.<br><br>114<br>00:18:20.170 --> 00:18:28.539<br>Philip Sellers: The systems in their warehouses cannot go down, that is death to them, and it is an exponentially expensive<br><br>115<br>00:18:28.840 --> 00:18:43.609<br>Philip Sellers: per minute cost, and so that uptime becomes paramount. For the infrastructure that's behind the scenes. But you know, to bring that closer and full circle. Now we're talking about some of that same stuff running in a<br><br>116<br>00:18:43.900 --> 00:18:46.350<br>Philip Sellers: a chicken shack down the road.<br><br>117<br>00:18:47.390 --> 00:18:50.004<br>Jirah Cox: Yeah, well, or or even<br><br>118<br>00:18:50.921 --> 00:19:19.029<br>Jirah Cox: you know, most of these retail environments also, you know, maintain like a store lab, right? Or a test, a test store nearby. Hq. For rapid prototyping, right and development. And so how do I ensure that the way I deploy to a a science project lab also is the way I roll out at scale in prod across the actual retail edge. So that kind of standardization leads to simplicity leads to uptime as well.<br><br>119<br>00:19:19.370 --> 00:19:25.359<br>Philip Sellers: Well, and and that drives the need for consistent, reliable.<br><br>120<br>00:19:26.180 --> 00:19:34.130<br>Philip Sellers: flexible infrastructure as a basis. Then you can iterate, and then you can try all this crazy stuff on top of it, because<br><br>121<br>00:19:34.890 --> 00:19:38.680<br>Philip Sellers: the difficult complex stuff has been made simpler.<br><br>122<br>00:19:39.130 --> 00:19:41.839<br>Philip Sellers: The actual okay, fun stuff.<br><br>123<br>00:19:42.070 --> 00:19:51.019<br>Jirah Cox: With with all the respect in the world for my my container colleagues. Now who are genuinely smart people, I often<br><br>124<br>00:19:51.330 --> 00:19:58.629<br>Jirah Cox: oversimplify containerization. To this is the fashionable way to install an application right now, is it?<br><br>125<br>00:19:59.190 --> 00:20:20.489<br>Jirah Cox: It actually does have a bit more complexity and scaffolding underneath of it. Sure! But the complexity is worth it when I want to install it 100 times a day. Right is then to your point when I can automate that with guaranteed outcomes. Now I get to go to the fun part right, and spend less time automating infrastructure and more time actually driving business value on the app layer on top of that.<br><br>126<br>00:20:20.490 --> 00:20:27.990<br>Philip Sellers: Absolutely. You know. I I moonlighted as a app dev many, many years ago, so<br><br>127<br>00:20:28.160 --> 00:20:36.312<br>Philip Sellers: I feel for them, but like I never did at dev to the level that that people do today professionally.<br><br>128<br>00:20:36.970 --> 00:20:49.069<br>Philip Sellers: But even then there's something rewarding about that cycle of iterating and improving and showing your work in real time. And so that drives<br><br>129<br>00:20:49.260 --> 00:20:52.970<br>Philip Sellers: the behavior you're talking about of deploying, you know.<br><br>130<br>00:20:53.250 --> 00:21:00.160<br>Philip Sellers: 100 250 times a day as you're iterating through and making incremental progress on the<br><br>131<br>00:21:00.290 --> 00:21:02.809<br>Philip Sellers: bigger problem that you're solving.<br><br>132<br>00:21:05.050 --> 00:21:30.320<br>Philip Sellers: It's fun stuff. We may have gotten a little off topic. But, you know, underlining kind of why we're here today. Nutanix and canonical. Their partnership is strong. Nkp on ubuntu pro opens and solves some real core enterprise problems in terms of security flexibility and longevity<br><br>133<br>00:21:30.865 --> 00:21:44.379<br>Philip Sellers: but also choice, and how you choose to go to market and meet your business needs. So Jaya, I appreciate you talking with me again today and just kinda<br><br>134<br>00:21:45.070 --> 00:21:50.690<br>Philip Sellers: going back and forth around this topic of kubernetes and our favorite distro.<br><br>135<br>00:21:51.700 --> 00:21:54.149<br>Jirah Cox: Thank you for wrapping it up. I need to go find some fried chicken.<br><br>136<br>00:21:54.530 --> 00:22:00.999<br>Philip Sellers: See planet alright. Everyone have a great day, and we will see you on the next episode.<br><br><br></p>