 Welcome to my lightning talk. My name is Christine. I work at isovalent, which is one of the founding companies of Sillium, which is an open source project and I'll talk a little bit about that But I care about the open source ecosystem a lot and I focus around service meshes and prior to isovalent I worked at Google doing service mesh stuff as well. So Get going fast with Sillium and Argo. So briefly the agenda today is Going to be touching upon what is Sillium if you're not familiar DevOps and developers how this is a kind of beneficial ecosystem here an Example we'll walk through and then lastly some takeaways and what's next? This is a lot for a slide really early in the morning on a Monday as well but Sillium in itself is a networking tool that leverages ebpf extended Berkeley packet filter and we use Sillium as a CNI in the Kubernetes landscape, but it's also so much more than that It's also the service mesh. It also has security such as tetragon. It also has Hubble as an observability tool So there's open source tool that leverages a powerful kernel module is Used in many ways across different cloud providers So I'm kind of going to go to the left field now with DevOps and developers So of course as you all know at Argo GitOps is the source of truth where you have this codified Practice of having your repo represent to what infrastructure you have So this is kind of parallel to the application being reflected in the repo and the app of apps pattern Talk earlier was talking about to this and so it's having your root app and being able to declarative declaratively Have your child apps be referenced by this root app And so kind of where does Sillium land in this something that I'm really passionate about is the Gateway API project Which is a sig networking group under Kubernetes and basically it's the ingress succession so now that the ingress is going to be maintained the Gateway API is something that is more flexible and I will talk a little bit more about that but Sillium has a very strong implementation and with Sillium and ebpf You have what metrics that you can monitor. So it pairs really nicely with Argo rollouts This is an example diagram on the side here of some of the Resources that are available with the Gateway API So now there's that clear line between your cluster operators or your platform ops and then your application developers which are empowered to You create their own HTTP routes GRPC routes, etc And so now you have the separate resources that application developers can touch and then their Kubernetes model Okay, so we're just going to walk through an example. This is a lightning talk I wish I could do a live demo, but I don't think I've made enough sacrifices to the demo gods So we're just going to talk through it So we have our devs touching their own repo for example that Maintain front-end and you have your platform ops which maintain apps and their charts within their own repo And then you have your cluster dev staging prod and it's running Argo CD and Sillium So whenever a dev makes a commit to the repo and there's like a version to a front-end for example The changes are reflected inside the infrastructure So that's where your root app is residing and then it will be able to push those changes to the cluster now something that'll be cool if you use gated Gateway API and Sillium is that you can have your devs also make commits directly to the platform ops repo as well So then if they want to have a rollout that's occurring so version 2 we want to do canary rollout they can commit and then platform ops are able to Approve any changes because it has that nice github Or a get a source of truth and so now you can declaratively manage your resources for Gateway API So of course the power of being declarative is giving the power back to the devs and the platform ops We're keeping them separate, but then they're also empowering each other There's a source management and deployment management strategy Which is still kind of developing and it's nice that Argo CD and Argo rollouts are so flexible and allows you to Create this architecture in this ecosystem. It's organized for teams now you only have you can have people who should only create Resources who have that power, but then also people who can approve such changes to your repo There's of course version control reconciliation of someone to delete something by accident or something gets rolled out by accident You can roll back and lastly again the Gateway API. I would stress that you check it out and the Argo website also has Resources on how the plug-in works with gate with Argo rollouts and I have links at the end Which are right here. So these slides are uploaded You don't have to take pictures if you don't want so if you can check them out and schedule That's cool, but I would say try out to Liam. It's so much more than a just see and I it's also service mesh and it's really powerful and Check out EBPF as well if that is something that is tickling your interest and also the Gateway API a project that I love so dearly so please get involved give feedback and With that all being said, thank you so much