 Hi, everyone. Thanks for the key. So today I'm going to talk about seven tip and tricks on how to make the most of your Kubernetes journey. So the first one is take it easy. So you might have used other orchestrators, like Mises or Tokuswar. But Kubernetes is just a little bit more complicated of all of them, right? And as soon as you start deploying, you realize that things aren't so easy anymore. But it's only when you move to persistent storage and networking that things are really, really complicated. And they don't stop if you go to network policies or pod disruption budget. So it's hard. So take your time and, you know, you might not learn Kubernetes in three hours or a weekend. So be aware of it. Tips number two is just pay attention to your productivity when you use the command line. So we spend a lot of time typing commands, such as kubectl get pods. So it makes a lot of difference if you have your command line optimized. So that doesn't mean just using things such as kubectl auto completion. Also means using, you know, know what to search when it comes to documentation. So kubectl explain or using tools to change context and namespace quickly, using crew to manage your plugins in kubectl or like a terminal prompt like QPS1 to just get the current status of the cluster at a glance. A couple of links if you're interested in this sort of stuff on the screen. Number three is don't drop connections. So you might be aware that Kubernetes, when you do a running upgrade, is going to create a new pod and then switch that pod for all your deployments. So that deployment is, that switching is based on something called readiness and liveness probe. So Kubernetes will wait for the liveness and readiness probe before it switches to the new version. Now, if you don't set those readiness and liveness probe, what happens is Kubernetes will not wait for your application to start. It will actually just replace immediately, which is an excellent recipe to take down your production infrastructure. Tips number four is click and play. So you might be tempted to just use Google Cloud Platform, click on the UI, select a couple of options, a couple of AZs, and create your own cluster. And then click on it and connect. You might do the same with VKS, so just go in console, couple of screens and create your cluster. Same with VKS as well. But if you do that, you should be aware that there are some challenges we're doing so. And mainly, the challenge is around keeping the configuration in scenes, the time it takes to create those configurations, always the need to go and click on stuff. Instead, what you should pay attention to is to just use something like Terraforms or infrastructure code or Pulumi, where you can have things like this where you script out the entire infrastructure and then with a command, you can just bring it up. Number five is exposing services. So you might be familiar with services in Kubernetes. You can have multiple of them, and you have a sort of external load balancer which is used, which is called Ingress. And then you could have several Ingresses. The most famous one is NGINX, but you can have as many as you want. So which one should you choose? Well, it depends, right? Just pay attention and spend the time and select the right one. Number six is automate your governance. So if you're looking at violating your YAML files or enforcing back-to-back practices when it comes to writing resources, standardizing your YAML, or just in general, being really quick and getting feedback when your YAML isn't the way you want it to be, just use the Open Policy Agent, Copper for CloudSafe 66, or QB Evolve from Instrumenta. They're all designed to basically look at your YAML and give you feedback or reject resources. The last tip I've got for you, today, is make new friends. I was lucky enough to be in KubeCon Barcelona this year where I had the opportunity to meet people that I usually only meet online. So to make the best of your Kubernetes journey, my advice to you is enjoy the next three days because it's gonna be great. That's all I wanted to say today. Thank you very much for listening to me. I'm Dan. I work for Learned Kubernetes, and this is it. Thank you very much. Thank you very much.