KubeCon + CloudNativeCon Europe 2024 | Mitch Connors | Aviatrix

Clips
News
More from KubeCon + CloudNativeCon Europe 2024

Mitch Connors

Senior Principal Software Engineer

Aviatrix

Revolutionizing networking and security: Aviatrix introduces Distributed Cloud Firewall for Kubernetes

Even though Kubernetes streamlines the governance of applications through container management, operational challenges arise if the workloads are not compatible. Aviatrix Systems Inc. is taming this pain point through a network security solution.The containerization journey has not been smooth sailing, since only 10% of enterprise apps have migrated to containers, and Aviatrix intends to change this narrative through the Distributed Cloud Firewall for Kubernetes, according to Mitch Connors (pictured), senior principal software engineer at Aviatrix.“KubeCon’s been going now for 8 to 10 years, and we’re still day zero,” he said

play_circle_outline Addressing the 90% Problem: Aviatrix Extends Features with Distributed Cloud Firewall for Kubernetes Services

play_circle_outline Importance of telemetry and monitoring for understanding and securing networks

play_circle_outline Integration and complementarity of Istio and Aviatrix in providing security at different layers of the stack

Info

Mitch Connors | Aviatrix

Mitch Connors

Senior Principal Software Engineer Aviatrix

search

(light upbeat music)

>> Hello and welcome back to KubeCon CloudNativeCon EU here in Paris, live all week long. We're unpacking what's going on in Cloud Native Kubernetes, and really one of the sticking points that, as somebody who was a former Amazonian, and I always knew, one of the big pitch points was always networking. And there's things like service mesh here, and we're going to jump into that with Mitch Connors from Aviatrix, who also does double duty working with Istio, and also joined by Dustin Kirkland. Thank you for coming on board and helping me unpack this because I think this stuff is just so interesting, how bringing it all together is just like, literally the service mesh brings it all together.

>> It does.

>> And I think that for Cloud Native. So what's new with Istio? I know there was an announcement this week, and there's a lot of stuff going on.

>> Yeah, so we've been working for a long time towards boringness in the project, and we've got some announcements that I think are both very exciting and very boring at the same time.

>> Boring by design.

>> And the big one, of course, is that the ambient mode, which is a sidecar-less service mesh we've been working on for the last two years, is finally moving forward to beta in our next release. We took a long time in alpha. We learned a lot of lessons as we heard from users about it. And we think at this point, that it's going to be ready for primetime use come May. So we're very excited about that development.

>> Wow, that's pretty soon, May. So how long has it been in alpha?

>> It went to alpha at KubeCon EU last year,

so it'll have been 12 months. >> One year.

>> Wow, that's excellent. I think, again, when you look at Istio and you look at, there's a number of different companies that are built on top of Istio, and they solve part of the problem, I would say, and I think it's, again, for Kubernetes, they're solving the problem. But Aviatrix, you guys had an announcement this week as well, in bringing Kubernetes to your product.

>> Yeah, we did. I think something that you don't really realize at a conference like this is that only 10% of enterprise apps have migrated to containers today. So this is, what, KubeCon's been going now for 8 to 10 years, and we're still day zero. We're only at 10% completion of what we've set out to do. And what that means is that a Kubernetes only solution for networking solves 10% of your problem as a large enterprise. So my move to Aviatrix was very strategic. I wanted to work on the 90% problem, and then also serve the 10% problem, and that's what our announcement this week is all about. Our customers have trusted us for years with their layer three networks, with VMs and VPCs. We have a great reputation in that space. And today we're announcing that our features are going to be extending to Kubernetes services with our distributed cloud firewall for Kubernetes.

>> Tell us a little bit more about that. What's a distributed cloud firewall for Kubernetes?

>> So a distributed cloud firewall is pretty cool. You get to write your firewall rules, but you don't ever think about where they're going to run because they run everywhere. Anywhere there is a gateway, moving traffic from one subnet to another will enforce that firewall rule. So we've done that for a year now. It's pretty well proven out. If you have things like auto scaling groups in your VMs, you don't need to worry about the fact that you're getting new IP addresses added all the time to that ASG. It's going to be automatically updated and forced across the board. So I got to Aviatrix and started looking at the technology and went, "Well, auto scaling groups, that's Kubernetes." Auto scaling is precisely what Kubernetes is built to solve. So it was really just a very small engineering effort to go that last mile and say, "Well, now we support it for auto scaling groups, VMs, VPCs, but also Kubernetes services and pods."

>> So let's take a step back because I think that any time that I get into this conversation, people are like, "Well, service mesh does that." And I'm like, "Well, not really." Being a networking guy from way back in the day, there's a whole... The stack that you look at, the OSI stack and all the way up to layer seven, which is really where service mesh is playing, is more at the layer seven... Help people understand what the differences are between traditional networking and service mesh.

>> So traditional layer three networks are going to be based on IP address as a form of identity. So if you want to talk about, do I have a right to get from one place to another, it's always about IP addresses. Service mesh really advanced to state of the art by saying we can make identity irrelevant to IP address. So you take your app, you move it from Amazon to Microsoft to somewhere else, the identity is actually cryptographic and moves with the application, and you don't need to worry about location. However, that problem is solved uniquely for Kubernetes, using the magic of automatically being able to control your orchestration. Because we don't have those same controls for VMs in place today, VM based applications or hybrid, which is the case for most enterprises, needs a better solution, one that can bridge the gap from those layer three centric world to those layer four and seven centric worlds.

>> Yeah. I'm guessing this is a scale problem, right? The scale of VMs multiplied how many physical machines that were out there, but now we do that exponentially more with containers, right? Give us some sense of the scale of the complexity of this problem.

>> Yeah, I had to go through this with my engineering team because of course, distributed cloud firewall was built for VMs. And so it's built to watch collections of VMs, and they'll change over time and update IP addresses. And they said, "We really built this thing for a lot of change. We're expecting a new IP address every hour." (group laughs) Okay. So now we got to talk about a new IP address every five to 10 seconds in a large enough cluster, and you've got about five seconds to propagate that change out to all the gateways that need to enforce those firewall rules. So realistically, it's not a solution you couldn't do by hand. You could have someone watch those IP addresses change over time and key them into your firewall rules and have exactly the same functionality. I think it's a little bit easier to use Aviatrix.

>> Yeah, I think automating it is... I think, again, this is one of those things. When we look at it, and you had people like Isovalent being bought by Cisco, kind of bringing the security, going into their security business unit and bringing that security in there, and you have a number of other companies actually being bought, like CloudFlare going out and buying Nefeli or NIFI or whatever.

>> Nefeli.

>> Nefli?

>> Netlefy. Netlefy?

>> I thought it was Nefli.

>> I think those might be two separate places.

>> Oh. >> Yes, it may be. But anyway, it started with an N. And when you started to look at, I hate to say it this way, but networking used to be boring before. It was difficult, but it was boring. Now it seems in a multi... And we're big believers in a multi-cloud world that's hybrid and things are living everywhere. Are you seeing that applications are actually, certain pieces of logic are in colo, certain pieces of logic are on premise, like databases tied to mainframes or something of that nature, with Kubernetes front ends up in the cloud? Is that really how people are building these applications?

>> That's not just the current state 'cause that's true currently. That's the permanent state of enterprise networking. My first engineering job was at a software, a financial services company. This was in the late 2000s. And the main thing that I was doing was tying their web applications to their mainframe applications. And those mainframes are still running today at most financial services companies. So when you talk about VMs going away, I'll say, "Well, yeah, as soon as we, as soon as the mainframe goes away, we can get to getting rid of VMs."

>> Well, I think that that's a funny thing because OpenShift actually runs on a version of z/OS.

>> Does it really?

>> On mainframe. So you can actually run Kubernetes on a mainframe.

>> Oh, I have to try that. That sounds like a lot of fun.

>> It's very interesting 'cause then you're, you can bring different components there. I think it's, again, one of these circular economy and being sustainable. It's a big server, but at the same time, it's highly redundant. It has some really good efforts to it. But to your point, just the traditional apps are not going away.

>> Yeah, a service mesh that does not address the need for VMs and VMs at scale, not just a handful here or there, is not going to be viable for the enterprise for a number of years to come.

>> And being able to treat hardware, VMs, and containers all as first class citizens within the same logical language and frameworks, that's powerful from a developer and a platform engineer's perspective.

>> We need to get back to being boring. We lost sight of it for a while, but we're working on it.

>> Yeah, no, I was saying that it's always interesting when there's, it seems like each cloud vendor is coming out with a new networking term, and then you have the colos, which have their own networking, and then you have people who are buying fiber and putting it and deploying it and having other networks. It seems like there's just so many opportunities for chaos in the network. Do you see organizations really trying to wrap their hands around it and centralize that process? Is that a big piece of it? And not only that, but to secure it. Because the securing it is the big... Oh great, I can connect it up. I put a VPC here. But how do I transit those different networks?

>> Yeah, I do think enterprises are trying to do that. I don't think that they're seeing a lot of products on the market that fit terribly well today. And so the area where that tends to land is within platform engineering. Platform engineers take on the responsibility of understanding the layer three network, the layer four network, the layer seven. They'll bring in some SecOps people who understand the security tooling, both from a network perspective and from a software supply chain perspective. They put all that together into one package so that the rest of the enterprise doesn't need to be actively aware of which service mesh am I using, which region am I running in. They can just get back to writing software that works well, while the platform engineers solve that problem. But I do see these platform engineering teams, they're being really constrained. They're quite small compared to the number of developers that they serve, and the number of technologies that they need deep expertise in is quite long. So I think the market is ripe for a solution that, instead of requiring them to learn their network twice and to build their network twice, allows them to define it once for everywhere that they run. And that's the bet that Aviatrix is making.

>> Yeah, can you talk just a little bit about some of the security concerns there, the threat and the risk management that goes into... We started with firewalls, but firewalls plus plus, how are we thinking about that today?

>> Yeah, I think it's important to remember that you cannot secure what you do not understand. And the state of the art today in most enterprises is that they do not understand which services they own, what their dependencies are, which direction those dependencies flow in. And so while I want to get to talking about security, and certainly distributed cloud firewall is all about security, at Aviatrix, we like to start with telemetry and monitoring. How do you know what policies to write if you have no idea what services are running or where they are? So our customers will come to us for security, but they wind up using the monitoring features first to get an idea of overall what they own, what it's doing, which of these pieces of traffic looks appropriate, are there any that maybe stand out as concerning to us? And then from there, they're able to iterate towards a default deny security posture where all traffic is explicitly permitted before it can go through. So I think that's the journey that they're on.

>> We've talked a lot about SBOMs here, software bill of materials. It sounds like translating that concept to networks.

>> NBOMs, yeah. (Rob laughs)

>> We're going to be dropping NBOMs now. I don't know that I want to go down that road. I really don't. But it was Nefeli. I got it right once out of the 13 times I tried to remember their name. But I think, again, there seems to be consolidation, and people are trying really to understand and make this simpler. And I think to your point, it seems like you're right in the eye of the storm here. 'Cause Istio is and service mesh is really about making container communications for those applications easy. And Aviatrix really aims to do that at the multi-cloud networking perspective and security perspective. How do you see the next year playing out for this? Do you see Istio going further into that, and service mesh coming up as it meets things like Aviatrix?

>> Yeah, I do think you're going to see a lot more integrations as these technologies meet in the middle. For a long time, we thought about these technologies as competing with one another. And I think really what we're doing now is we're thinking of them as complimentary. They each serve their own purpose. They work together really well. And solutions that address security at every layer in the stack are what customers should be expecting. You should never answer the question, what do you want to secure, layer seven or layer three? That's a sucker's choice. You should have those sorts of security policies at all layers of the stack. And that's going to be accomplished through technologies that work as well at layer three as they do at layer seven.

>> Yeah, it was amusing 'cause somebody was like, "Okay, well if you just do layer seven encryption up at layer seven, you're all set, or layer four." And I'm like, "Ah, you really want to do it below there and really have that because you want encryption on encryption." Are you seeing more threats now as organizations build out these applications, especially with gen AI being turned on everywhere? They're putting, "Hey, we're going to put our LLM. We're going to build it in Bedrock or something like that, or in Google on Gemini or wherever." Are you seeing people really trying to delve into the security aspects of how their data gets between these different places, these different clouds? 'Cause a lot of the data's on prem still.

>> Yeah, I think that what the LLM trend and the AI trend has really done for us is that now the key value... Companies have come to understand their key value is the data that they can train their models on. It's not the models themselves. It's the data that trains the models. And that data, in order to train on it, has to be perpetually moving across the network, not just locally on prem, but from on prem to cloud to edge. They've got to be transferring data almost constantly. And so there's a whole new level of security that they need to apply to that because it's no longer, well, we'll lose a little bit of customer trust if we lose this data. It's, if we lose this data, we've lost the company's entire value statement.

>> Yeah, I totally agree. And I think that's actually a really good place for us to end, I think, because again, if we hadn't talked about AI, I think we would have gotten pushed off stage.

>> That's required.

>> Thank you for coming on, Mitch, and giving us the update on Istio. Again, I think that it's technology that I love. It's definitely bringing together... I agree with you wholeheartedly that it's complimentary with what Aviatrix is doing and others out there and really bringing that together. So thank you for coming on board today.

>> Rob, Dustin, thanks a lot.

>> And thank you Dustin as well.

>> You got it, Rob. >> Awesome. Back at the bar.

>> Back at the bar. >> Back at the bar. Well, thank you for watching this episode. Stay tuned for more from KubeCon CloudNativeCon EU here in Paris. We'll be back shortly. (light upbeat music)

Mitch Connors | Aviatrix

search

(light upbeat music)

>> Hello and welcome back to KubeCon CloudNativeCon EU here in Paris, live all week long. We're unpacking what's going on in Cloud Native Kubernetes, and really one of the sticking points that, as somebody who was a former Amazonian, and I always knew, one of the big pitch points was always networking. And there's things like service mesh here, and we're going to jump into that with Mitch Connors from Aviatrix, who also does double duty working with Istio, and also joined by Dustin Kirkland. Thank you for coming on board and helping me unpack this because I think this stuff is just so interesting, how bringing it all together is just like, literally the service mesh brings it all together.

>> It does.

>> And I think that for Cloud Native. So what's new with Istio? I know there was an announcement this week, and there's a lot of stuff going on.

>> Yeah, so we've been working for a long time towards boringness in the project, and we've got some announcements that I think are both very exciting and very boring at the same time.

>> Boring by design.

>> And the big one, of course, is that the ambient mode, which is a sidecar-less service mesh we've been working on for the last two years, is finally moving forward to beta in our next release. We took a long time in alpha. We learned a lot of lessons as we heard from users about it. And we think at this point, that it's going to be ready for primetime use come May. So we're very excited about that development.

>> Wow, that's pretty soon, May. So how long has it been in alpha?

>> It went to alpha at KubeCon EU last year,

so it'll have been 12 months. >> One year.

>> Wow, that's excellent. I think, again, when you look at Istio and you look at, there's a number of different companies that are built on top of Istio, and they solve part of the problem, I would say, and I think it's, again, for Kubernetes, they're solving the problem. But Aviatrix, you guys had an announcement this week as well, in bringing Kubernetes to your product.

>> Yeah, we did. I think something that you don't really realize at a conference like this is that only 10% of enterprise apps have migrated to containers today. So this is, what, KubeCon's been going now for 8 to 10 years, and we're still day zero. We're only at 10% completion of what we've set out to do. And what that means is that a Kubernetes only solution for networking solves 10% of your problem as a large enterprise. So my move to Aviatrix was very strategic. I wanted to work on the 90% problem, and then also serve the 10% problem, and that's what our announcement this week is all about. Our customers have trusted us for years with their layer three networks, with VMs and VPCs. We have a great reputation in that space. And today we're announcing that our features are going to be extending to Kubernetes services with our distributed cloud firewall for Kubernetes.

>> Tell us a little bit more about that. What's a distributed cloud firewall for Kubernetes?

>> So a distributed cloud firewall is pretty cool. You get to write your firewall rules, but you don't ever think about where they're going to run because they run everywhere. Anywhere there is a gateway, moving traffic from one subnet to another will enforce that firewall rule. So we've done that for a year now. It's pretty well proven out. If you have things like auto scaling groups in your VMs, you don't need to worry about the fact that you're getting new IP addresses added all the time to that ASG. It's going to be automatically updated and forced across the board. So I got to Aviatrix and started looking at the technology and went, "Well, auto scaling groups, that's Kubernetes." Auto scaling is precisely what Kubernetes is built to solve. So it was really just a very small engineering effort to go that last mile and say, "Well, now we support it for auto scaling groups, VMs, VPCs, but also Kubernetes services and pods."

>> So let's take a step back because I think that any time that I get into this conversation, people are like, "Well, service mesh does that." And I'm like, "Well, not really." Being a networking guy from way back in the day, there's a whole... The stack that you look at, the OSI stack and all the way up to layer seven, which is really where service mesh is playing, is more at the layer seven... Help people understand what the differences are between traditional networking and service mesh.

>> So traditional layer three networks are going to be based on IP address as a form of identity. So if you want to talk about, do I have a right to get from one place to another, it's always about IP addresses. Service mesh really advanced to state of the art by saying we can make identity irrelevant to IP address. So you take your app, you move it from Amazon to Microsoft to somewhere else, the identity is actually cryptographic and moves with the application, and you don't need to worry about location. However, that problem is solved uniquely for Kubernetes, using the magic of automatically being able to control your orchestration. Because we don't have those same controls for VMs in place today, VM based applications or hybrid, which is the case for most enterprises, needs a better solution, one that can bridge the gap from those layer three centric world to those layer four and seven centric worlds.

>> Yeah. I'm guessing this is a scale problem, right? The scale of VMs multiplied how many physical machines that were out there, but now we do that exponentially more with containers, right? Give us some sense of the scale of the complexity of this problem.

>> Yeah, I had to go through this with my engineering team because of course, distributed cloud firewall was built for VMs. And so it's built to watch collections of VMs, and they'll change over time and update IP addresses. And they said, "We really built this thing for a lot of change. We're expecting a new IP address every hour." (group laughs) Okay. So now we got to talk about a new IP address every five to 10 seconds in a large enough cluster, and you've got about five seconds to propagate that change out to all the gateways that need to enforce those firewall rules. So realistically, it's not a solution you couldn't do by hand. You could have someone watch those IP addresses change over time and key them into your firewall rules and have exactly the same functionality. I think it's a little bit easier to use Aviatrix.

>> Yeah, I think automating it is... I think, again, this is one of those things. When we look at it, and you had people like Isovalent being bought by Cisco, kind of bringing the security, going into their security business unit and bringing that security in there, and you have a number of other companies actually being bought, like CloudFlare going out and buying Nefeli or NIFI or whatever.

>> Nefeli.

>> Nefli?

>> Netlefy. Netlefy?

>> I thought it was Nefli.

>> I think those might be two separate places.

>> Oh. >> Yes, it may be. But anyway, it started with an N. And when you started to look at, I hate to say it this way, but networking used to be boring before. It was difficult, but it was boring. Now it seems in a multi... And we're big believers in a multi-cloud world that's hybrid and things are living everywhere. Are you seeing that applications are actually, certain pieces of logic are in colo, certain pieces of logic are on premise, like databases tied to mainframes or something of that nature, with Kubernetes front ends up in the cloud? Is that really how people are building these applications?

>> That's not just the current state 'cause that's true currently. That's the permanent state of enterprise networking. My first engineering job was at a software, a financial services company. This was in the late 2000s. And the main thing that I was doing was tying their web applications to their mainframe applications. And those mainframes are still running today at most financial services companies. So when you talk about VMs going away, I'll say, "Well, yeah, as soon as we, as soon as the mainframe goes away, we can get to getting rid of VMs."

>> Well, I think that that's a funny thing because OpenShift actually runs on a version of z/OS.

>> Does it really?

>> On mainframe. So you can actually run Kubernetes on a mainframe.

>> Oh, I have to try that. That sounds like a lot of fun.

>> It's very interesting 'cause then you're, you can bring different components there. I think it's, again, one of these circular economy and being sustainable. It's a big server, but at the same time, it's highly redundant. It has some really good efforts to it. But to your point, just the traditional apps are not going away.

>> Yeah, a service mesh that does not address the need for VMs and VMs at scale, not just a handful here or there, is not going to be viable for the enterprise for a number of years to come.

>> And being able to treat hardware, VMs, and containers all as first class citizens within the same logical language and frameworks, that's powerful from a developer and a platform engineer's perspective.

>> We need to get back to being boring. We lost sight of it for a while, but we're working on it.

>> Yeah, no, I was saying that it's always interesting when there's, it seems like each cloud vendor is coming out with a new networking term, and then you have the colos, which have their own networking, and then you have people who are buying fiber and putting it and deploying it and having other networks. It seems like there's just so many opportunities for chaos in the network. Do you see organizations really trying to wrap their hands around it and centralize that process? Is that a big piece of it? And not only that, but to secure it. Because the securing it is the big... Oh great, I can connect it up. I put a VPC here. But how do I transit those different networks?

>> Yeah, I do think enterprises are trying to do that. I don't think that they're seeing a lot of products on the market that fit terribly well today. And so the area where that tends to land is within platform engineering. Platform engineers take on the responsibility of understanding the layer three network, the layer four network, the layer seven. They'll bring in some SecOps people who understand the security tooling, both from a network perspective and from a software supply chain perspective. They put all that together into one package so that the rest of the enterprise doesn't need to be actively aware of which service mesh am I using, which region am I running in. They can just get back to writing software that works well, while the platform engineers solve that problem. But I do see these platform engineering teams, they're being really constrained. They're quite small compared to the number of developers that they serve, and the number of technologies that they need deep expertise in is quite long. So I think the market is ripe for a solution that, instead of requiring them to learn their network twice and to build their network twice, allows them to define it once for everywhere that they run. And that's the bet that Aviatrix is making.

>> Yeah, can you talk just a little bit about some of the security concerns there, the threat and the risk management that goes into... We started with firewalls, but firewalls plus plus, how are we thinking about that today?

>> Yeah, I think it's important to remember that you cannot secure what you do not understand. And the state of the art today in most enterprises is that they do not understand which services they own, what their dependencies are, which direction those dependencies flow in. And so while I want to get to talking about security, and certainly distributed cloud firewall is all about security, at Aviatrix, we like to start with telemetry and monitoring. How do you know what policies to write if you have no idea what services are running or where they are? So our customers will come to us for security, but they wind up using the monitoring features first to get an idea of overall what they own, what it's doing, which of these pieces of traffic looks appropriate, are there any that maybe stand out as concerning to us? And then from there, they're able to iterate towards a default deny security posture where all traffic is explicitly permitted before it can go through. So I think that's the journey that they're on.

>> We've talked a lot about SBOMs here, software bill of materials. It sounds like translating that concept to networks.

>> NBOMs, yeah. (Rob laughs)

>> We're going to be dropping NBOMs now. I don't know that I want to go down that road. I really don't. But it was Nefeli. I got it right once out of the 13 times I tried to remember their name. But I think, again, there seems to be consolidation, and people are trying really to understand and make this simpler. And I think to your point, it seems like you're right in the eye of the storm here. 'Cause Istio is and service mesh is really about making container communications for those applications easy. And Aviatrix really aims to do that at the multi-cloud networking perspective and security perspective. How do you see the next year playing out for this? Do you see Istio going further into that, and service mesh coming up as it meets things like Aviatrix?

>> Yeah, I do think you're going to see a lot more integrations as these technologies meet in the middle. For a long time, we thought about these technologies as competing with one another. And I think really what we're doing now is we're thinking of them as complimentary. They each serve their own purpose. They work together really well. And solutions that address security at every layer in the stack are what customers should be expecting. You should never answer the question, what do you want to secure, layer seven or layer three? That's a sucker's choice. You should have those sorts of security policies at all layers of the stack. And that's going to be accomplished through technologies that work as well at layer three as they do at layer seven.

>> Yeah, it was amusing 'cause somebody was like, "Okay, well if you just do layer seven encryption up at layer seven, you're all set, or layer four." And I'm like, "Ah, you really want to do it below there and really have that because you want encryption on encryption." Are you seeing more threats now as organizations build out these applications, especially with gen AI being turned on everywhere? They're putting, "Hey, we're going to put our LLM. We're going to build it in Bedrock or something like that, or in Google on Gemini or wherever." Are you seeing people really trying to delve into the security aspects of how their data gets between these different places, these different clouds? 'Cause a lot of the data's on prem still.

>> Yeah, I think that what the LLM trend and the AI trend has really done for us is that now the key value... Companies have come to understand their key value is the data that they can train their models on. It's not the models themselves. It's the data that trains the models. And that data, in order to train on it, has to be perpetually moving across the network, not just locally on prem, but from on prem to cloud to edge. They've got to be transferring data almost constantly. And so there's a whole new level of security that they need to apply to that because it's no longer, well, we'll lose a little bit of customer trust if we lose this data. It's, if we lose this data, we've lost the company's entire value statement.

>> Yeah, I totally agree. And I think that's actually a really good place for us to end, I think, because again, if we hadn't talked about AI, I think we would have gotten pushed off stage.

>> That's required.

>> Thank you for coming on, Mitch, and giving us the update on Istio. Again, I think that it's technology that I love. It's definitely bringing together... I agree with you wholeheartedly that it's complimentary with what Aviatrix is doing and others out there and really bringing that together. So thank you for coming on board today.

>> Rob, Dustin, thanks a lot.

>> And thank you Dustin as well.

>> You got it, Rob. >> Awesome. Back at the bar.

>> Back at the bar. >> Back at the bar. Well, thank you for watching this episode. Stay tuned for more from KubeCon CloudNativeCon EU here in Paris. We'll be back shortly. (light upbeat music)