 Hello, my name is Wasim Swali and I am a cloud solution architect working with Mirantes and today we will be talking on how we could use Lens in order to collaborate on managed Kubernetes clusters like for example EKS and AKS. But first you have this scavenger hunt so just collect these QR codes and then you can come to the big garden to collect your prices. So don't worry I will display again this slide at the end of the talk. So yeah, this is Lens. It's basically a Kubernetes IDE that you could download and install on your laptop. It could work on MacBook, Linux, Windows, here for example I'm using MacBook and this is the main actually where we could see all the Kubernetes clusters that I have added. We could see for example K0S, the zero-friction Kubernetes from Mirantes. We could see like I have here mini-cube for example. We could see Rancher and of course we could see EKS. So Kubernetes cluster from AWS. So in order to add a new cluster it is very easy. So here for example I will show you how to add a cluster. I just need to add the cube config. Yeah and that's it. And then I could for example customize it a bit very quickly. For example let's call it MKE. This is another distribution from Mirantes. Here we go. We have our Kubernetes cluster that we could start using it. So now let's go to EKS. So this is basically EKS. So this is the main display where we could see the telemetry. So by default Lens would leverage the Prometheus stack if there is any already installed. Otherwise it's very easy to ask Lens to install this Prometheus stack for you. For example here I could go to settings, Lens metrics and then I just need to activate this stack and in a couple of minutes so Lens would install the Prometheus and start to pull this metrics. So here for example we could see the CPU usage, memory and the ports. So let's dig deeper. For example if we click on notes we could see of course here we have only the workers because the masters are handled by AWS. So here if I click on one worker for example we could see of course the memory CPU disk ports. We could see for example the internal IP, the external public IP. We could see for example that it is ready. It's already in the cluster. We could see how many CPUs we are using and of course all the ports that are in this worker. We could see that are actually up and running. And of course if we have enough rights we could leverage these extra options here. We could exact to the node. We could for example coordinate. We could like drain it and we could do a lot of things. Of course this is a class cluster so it's not recommended like doing it from here. So let's go now to the workload. We could have a very good knowledge about what's in there. We could see the ports, deployments, demon sets. It's like one single panel view and this is a little extension in order to show you how it is deployed. So I will come back to the extensions later on. The same way we could have here the ports. I can see for example in the default namespace I have these ports here. I could go a click on one of them. Again here we could have a very good knowledge about the pod and we could for example exact into the pod. We could for example get all the logs of this pod and we have a lot of features and functionalities. So the same way with deployments, demon sets, stateful sets, replica sets, etc. So here for example let's click on this deployment. We could see that we have a lot of deployments that are already here and if I want I could just have a terminal session. So this terminal session would put me directly into the context of this ECAS cluster. It means if I deploy something in this terminal session, let's say I would like to deploy WordPress. So very easily we could see that it's deployed into this context. If I click here in this mini cube and I deploy something it would be it will automatically switch context. So as you could see it's very easy to handle like different Kubernetes clusters. Again if I take this WordPress for example so I could leverage these extra options. I could for example scale it. Here it's only one pod with a few clicks. I could have like multiple pods. We could see here the new desired states and now we have three pods which are already so up and running. So same way we could have like the configs. We have the config maps, secrets. So the resource quota which is related to namespaces. So same thing with the networking. We could have for example the services. Here for example I deployed Apache and I would like to know whether it is working or not. So it's very easy. I just click here in Apache and then I make some port for what. Yeah you could see that I could find very easily what's happening with my cluster and all the deployments on my cluster. So same with the storage. Here we could see for example the storage class on AWS and here we could see all the events that are happening with my clusters within a click as well. And this is for a certain time. I could go down. There is one more interesting feature. It's a Helm charts. So as you can see here I could see all the Helm charts that I already deployed. So for example I have this Apache that has been deployed and by default with this we have some actually we have some repositories which are already added like Bitnami for example or I have my own repositories that I add to myself. And of course these are the default length features but in order to make it grow easily we have the next extensions. So if I go here I could see that I'm having different extensions. We have some extensions which are developed by Mirantis, some extensions which are developed by some of our partners like for example Aqua Security, this starboard extension that is able to analyze and give the CVs. We have the cube cost extension for example or you could like develop your own extension in order to really fit your needs. So this is a very interesting extension for example it's called resource map. So this would give you a very good idea about all your cluster and how applications are developed. For example if I take the Apache that I already deployed with Helm charts so let's zoom in. We could see here that it's so deployed by Helm charts here. We could see for example we have this deployment and then we have the pod and we have the service. We could see that thanks to the right colors the pod is up and running and my application is up and running. Yeah. And there is one more functionality that I wanted to show you today. So okay so now I can handle my cluster it is fine but how can I share it with the colleague? So one way would be to share the cube config but the thing is it's not very secure. So we developed with the lens the so lens spaces. So it's very easy to create a new space. Here for example I have multiple spaces and I have already created one for OpenMFRA for example. So there is my colleague Robert who just joined the company and actually this is so Robert VM he just actually freshly installed lens so he doesn't have anything. You see that the cluster is empty. So here within a few clicks so I just need to actually right click here and then I add this cluster to team space and then I would select the team space and the region and I just apply. So actually I already did this for ICAS because it may take like a few minutes but let's do it again for this mini cube so I will show you how to share for example this mini cube. So here I add cluster to lens spaces. I select the space. So let's select this OpenMFRA space. I select the region. It should be the closest like between myself and my colleague right. Let's say like Europe for example. I just hit so add cluster to team space. Yeah and I could see that it was added successfully and then I could just go to this space here and check what was added to this space. So here I could see that we have this ICAS and then after a couple of minutes so depending on the network we will have as well this mini cube added there and so if I go to my colleagues VM here so he would be invited through message to actually join this space and so he will join the space and then he would go to his space and then he could find that we have this mini cube and ICAS. He just need to click here and to add it to the hot bar for example to make it easier and then he could start to leverage this cluster and to work on it. Yeah so this is all I had for you today so thank you for joining this session and yes I have also a few hats so please feel free to take a few ones if you want. Thanks a lot.