Run Traefik Anywhere with Traefik Labs

Alright, so last topic. Uh, you know, it's this notion of being able to run traffic anywhere. Um, and I think you, you guys are probably seeing this theme of running anywhere more this CubeCon than I have seen in the past CubeCon.

So it's very timely topic and what I want to just kind of, uh, share with you are a, the fact that traffic can indeed run anywhere. But I wanna show you how that is possible. So first of all, traffic, you know, we talk about Kubernetes a lot, but it's the fact that we can run on Linux, we can run as a container in Docker, we can run inside of HashiCorp Nomad.

Um, and obviously we can run inside of any certified Kubernetes distro natively. This is how you install traffic. This is a helm chart install.

It's the same helm chart install for any environment. Pick your favorite distro, A-K-S-E-K-S-G-K-O-K-E or any other CNCF distro. This is pretty much it.

You know, you may not need all the parameters, but you know, you have 17 lines of code here. This is what you're using to deploy traffic. What you need is the, the license.

So, you know, you get the license key from us and then, you know, you had asked a question earlier about, okay, we wanna deploy a bunch of these. How do I do that? There's your helm chart command.

You can make this part of your CICD pipeline and off you go. Also in the edge, exact same helm chart command. If you wanna deploy traffic at the edge, pick your, take your pick.

You know, we are actually the default ingress in K three s. So if you are deploying K 3D, you know, with K three s, traffic already comes into it, uh, the open source has already baked into it and then you can just upgrade. Uh, we also work seamlessly with Digital Ocean Kubernetes and the docks.

Um, those of you that are familiar with that, we also work with canonical micro KS, uh, we also integrate, uh, seamless with ods, LKE or you know, any other certified Kubernetes for the Edge. Um, as long as they're CNC of compatible, as you see the exact same command, also you can run us in offline and air gap mode. The only thing that changes is line nine, right?

That's a new, uh, statement. You just gotta set that flag hub offline equals true and now it's completely air gapped. No call home, no, no telemetry, nothing.

It's that simple. So it's not a brand new product, it's not a whole different way of installing it. You install it exactly the same way, just one flag.

And now this is completely our gap. Oh, I have a question. This is Tony Res with TechOne.

So I'm sure I'm not alone as being new to this platform. There's a lot of VMware administrators like myself that are making that shift. Can you make some recommendations on kinda where to start learning some of this tips?

How, how simple is this? What are some of the correlations to the kinda the platform that I'm particularly used to that a lot of people out there are used to and kind of get us up and running kind of best practices kind of scenario? Great, Great question.

Uh, and that nicely segues into my my last slide here. You wanna, if you are a VMware user and you're trying to figure out like how to get into containers and then do this because you're responsible managing both, right? You need to create operational leverage first, and this is where you need a abstraction layer for that application intelligence.

So step one would be, work with us, let's deploy traffic as an application layer in your environment so that you can start to define the policy layer that you're gonna write once that will work with your VMs. And then when you introduce the containers, the same application routing layer can route to both of them. And are there sandbox type environments ways that you can try this out in a lab kind of absolutely.

On your own? Absolutely. Uh, just reach out to us and, and then we can work with you and, and then come up with something that would work.

Cool. So that's step one. You know that this is a wrap up, right?

Like the three things that I wanna leave you guys with is to achieve operational intelligence, application intelligence. It's really the objective here is for companies to create this operational leverage. This is gonna be a reality, which is the coexistence of VMs and containers.

And now you throw serverless into it and not serverless the way we know it, like, you know, with the cloud provider serverless versions. But with K native, now serverless can come on-prem into your environment. So you're gonna be dealing with these three types of workloads.

So you need the operational leverage, and that's where our unified application intelligence comes in. With ai, it's really about gaining that architectural control because without having that decoupled architecture, you're always gonna be relying on the, the cloud provider or whoever else your provider is their custom implementation of the AI runtime environment. So you wanna really decouple it.

And then the third is being able to run traffic anywhere is the only way to get true sovereignty around your deployments. Like sovereignty is there not, if you cannot leave a particular cloud, if you're tethered to one particular environment, you don't get a fully sovereign deployment. So combining all these three things should give you guys all the, you know, the, I think the, the muscle that you need and the the strategy that you need to go forward.