Cloud Native Computing Foundation CNCF Webinars, 4 Dec 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Take the pain out of multi-cluster Kubernetes with Lens

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

Okay, hi everyone, uh as I said good morning good afternoon good evening, depending on where you are in the world. uh Welcome to today's cncf webinar, uh take the pain out of multi-cluster kubernetes with lens I'm christy, tan and I'll, be moderating today's webinar. We would like to welcome our presenter today, edward I don't know. uh Hopefully I didn't butcher that edward developer relations at mirantis a few housekeeping items before we get started during the webinar. You are not able to talk as an attendee. There's a q, a box at the bottom of your screen.

A

Please feel free to drop your questions in there and we'll get to as many as we can. At the end. This is an official webinar of the cncf and, as such is subject to the cncf code of conduct. Please do not add anything to the chat or questions that would be in violation of that code of conduct. Basically, please be respectful of all your fellow participants and presenters.

A

Please also note that the recording and slides will be hosted later today to the cncf webinars page at cncf, dot, io webinars with that I'll kick or I'll hand it over to edward to kick off today's presentation. Take it away.

B

Thank you thank you, christy, and I would like to thank everybody here for actually having me participate in this cncf webinar. I'm very excited to show you guys how we can take the pain out of multi-cluster kubernetes within open source technology called lens, as christy mentioned, I'm edward enl and I'll be walking you guys through a demo today. So I'm looking forward to sharing with you guys my tips and tricks for taking out the pain of multi-cluster kubernetes with lens. Let's get.

B

C

B

Just gone the wrong way: sorry guys.

B

So about me, I'm responsible for developer relations here at marantis and my day-to-day responsibilities is to really seek out the pain points within kubernetes to help streamline developer and operator initiatives. I'm by no means an experienced kubernetes hacker, but I do have above average, understanding of kubernetes and all of the objects that relate to.

D

B

Cool sorry about that guys, so the kubernetes challenge, people and organizations invest in kubernetes, but developers may think it is too complicated and adoption is slow. With other kubernetes focused tools, you have to know what you're looking for in order for kubernetes to be effective. Users traditionally need a quite a bit of training and understanding of all kubernetes objects and how they relate with each other, thus causing somewhat of a complication between organizations and teams. So you may not be seeing the return on investment that you should, with your container.

C

Initiatives, oh.

B

So this is lens lens. Is a developer friendly, desktop application for all of your kubernetes platforms? It's a hundred percent open source and it works with any kubernetes distribution from gke to eks, rancher and mirantis container cloud.

B

It allows developers and operators to easily onboard and operate their applications in kubernetes, thus improving productivity and increasing overall return of investment on their container initiatives.

B

Wow that actually worked sorry guys. So this is a quick stat sheet of where we stand with glenn's. Today, it's the world's most popular kubernetes, integrated development environment. We are actually self-proclaiming that, but we have some stats to back us up, as you guys can see. We currently have over 9 300 github stargazers, I think, actually, as of today, it's more like 9500 github stargazers.

B

We currently have 92 000 users that are currently using the application and we have over 1.2 million downloads. Currently, our goal is to increase this number significantly and we really want to allow developers and operators to work much more efficiently, while working with kubernetes and their container.

B

B

It does not want to work today.

B

So what are we going to be reviewing today today? We're going to be doing a demo, rich webinar, where I'll be sharing my tips and tricks and best practices for working with multiple clusters from multi-cluster management through lenses, smart console or context-aware terminal which matches to the correct endpoint of the cluster, deploying the application with helm directly into lens and your cluster via one or two clicks, and our newest functionality that should be releasing tomorrow is our lens extension api.

B

So since our slides don't want to work too much, I think it's a good idea to just jump into the demo itself and towards the end. I will also be sharing with you guys how to actually find the lens repo within github and our contact information. If you have any further questions post webinar without further ado guys, let's jump into the webinar.

B

B

So first thing we traditionally like to do is obviously add our cluster to lens lens utilizes, your rollbase access control from your cluster and your cubeconfig file.

B

There's two ways to add a cluster to lens. You can select the cubeconfig file on your operating system or you have the ability to paste it as text here for demonstration purposes. I will find my cluster.

C

B

Looks like the correct one use configuration.

B

And very simply, we just add our cluster to lens.

B

Before jumping into the demo rich webinar itself, I do want to highlight our cluster settings. Currently, our cluster is online, but this the distribution says unknown, and the reason for that is. This is currently a release candidate prior to our launch of 4.0 tomorrow.

B

So the correct distribution is actually vanilla, but for now it says unknown our kernel version, as you guys can see our api address, the node count within our cluster, our cube config file and where it sits on a laptop or desktop, and we have some functionalities that we can change here within our settings.

B

We can give our cluster a.

B

Name create additional workspaces within our cluster and the way I would think of this, as these are folders within your cluster itself itself, for maybe staging admin and production clusters, you can think of it as a separation of matter matter of concern and we'll add a workspace today.

B

In order to add a workspace, you'll hit add workspace and you guys can see. I have other testing workspaces that I did this morning.

B

And, very simply, you click this file file, icon that says save from here, we'll jump back to our settings scroll further down, and we have another neat neat functionality within lens as well, and I actually like this a lot you guys can see on the left hand side my smart console. I have several different icons to allow me to understand which cluster I'm currently working with for my admin cluster to my raspberry pi cluster, my mini cube, cluster and so forth simply add an icon.

B

um What kind of icon shall we add today?

B

Let's just add a helm, chart icon, might not be the prettiest, but that's all right and you can see- we immediately add this icon to our specific cluster, to be able to navigate through our cluster selector and our smart console very, very efficiently.

B

Lens also has a pre built in auto, detect prometheus and you have the functionality and the ability to bring your own prometheus to lens.

B

If you choose to do so, okay enough about the settings, let's actually jump in to the demo itself, and why you would want to utilize lens for your kubernetes initiatives clicking into our cluster I'll, give you guys a second to digest some of this information, but, as you guys can see, we are immediately brought into our cluster overview screen where we can see how our cluster is performing in the last hour, through the pre-built in prometheus, from our master to our worker, our cpu and memory as well.

B

Let me just move this down. We can also see how many pods are being currently used within our cluster and the capacity as well.

B

At the bottom, we have real-time events and messages that tell us what is currently going on within our cluster. This is extremely useful when you try to troubleshoot particular things within your applications. Maybe your deployments, your pods or your notes.

B

It really lens really tells you the source of the error or warning, and the message associated to help you troubleshoot very, very quickly, we'll come back to the events in a bit towards the end, but for now we're going to walk into our notes.

B

B

As you all can see, we currently have five nodes running and we can filter by cpu memory, disk and so forth, all in real time.

B

Another very, very interesting functionality within lens is being able to get a much more granular look into a particular kubernetes object. For example, a node clicking into this node brings us into this very unique user interface screen. That shows us how our node is performing in the last hour from our cpu to our memory to the disk and the pods itself at the top left.

B

Let's have this go away? That's fine! At the top left. You guys can usually see the kubernetes object here, as well as the name.

B

On the right, depending on your role, based access control that we leverage from your cubeconfig file, you can do specific actions to this object itself. For example, you can shell into the node, you can cordon the node drain and you have the ability to jump into the kubernetes resource. Manifest of this particular object clicking into here.

B

We are immediately brought into the kubernetes resource, manifest.

B

As you guys can see which allows us to test and debug and change all in real time, if we click save and close, we'll cancel this jump back into our note, and we have some other very interesting things happening here as well. We can see all the settings associated to this kubernetes object, all in one place from when it was created all the way down to the operating system, the image, the kernel version, container, runtime, the kublet version and, of course, very importantly, our labels.

B

We can see all of the pods that are also running within our node, all in one place, and we have the ability to click through each and every single object within lens as well.

B

So, for example, if I want to take a look at this fluent td pod itself, I can click here and we're immediately brought into a granular view. In of the last hour of how our particular pod is performing once again from cpu to memory network and file system.

C

We'll close this for now.

B

So this is a very unique screen as well. This is our workloads overview screen where you can see different kubernetes objects and how they're currently performing so, maybe, if I'm an operator or an application owner- and I want to see how my application is currently running or how my cluster is performing. I can come here and immediately get real-time insights to my application or my cluster all at once.

B

As you guys can see, we have our pods our deployments. Our stateful sets our damien sets jobs and cron jobs again at the bottom. We have our real-time events that tell us what is currently happening. As you guys can see. I have a warning message here and that warning message actually occurred roughly eight minutes ago from here we'll jump into pods there's several ways: you can do this, as you guys can imagine you. Can click pause under the overview?

B

Click pods here and also click pods in the top right clicking into pods, brings us into a very unique screen.

B

We immediately can see all the pods that are running within our kubernetes cluster, from the name to the namespace. The amount of containers what the pot is being controlled by and the status of the pot itself.

B

So what makes this unique and fascinating for us? Well, one of the very cool things that lens provides for us is the ability.

C

B

B

Another very very important thing I want to mention here is that lens has a pre-built in context aware terminal. What does this mean? That means that lens auto-magically, yes, I did say auto-magically- connects to the correct endpoint of your cluster itself.

B

So to show that lens does this, I will perform a little bit of cube ctl to show that we are matching to the correct endpoint of the.

B

B

So, as you guys can see, here's our endpoint and the version- and if I minimize this screen jump back to our nodes, we can see that lens auto-magically has matched to the correct endpoint of the cluster itself, lens also downloads. In the background, the most latest and greatest cube ctl that you guys can perform within the terminal.

B

Another quick thing I like to run all within our terminal.

B

Is matching our nodes and you guys can see our notes are matched to the correct cluster. So lens performs this for us without having to write any command line, to make sure that we are reducing user error, while working within our clusters themselves.

B

Jumping back over to workloads and the overview screen will jump into pods.

B

And move forward lens also allows us to filter and search, as mentioned previously, for a particular pod or other kubernetes object that we are looking for.

B

We can select a namespace and it immediately highlights all of the pods associated to the cube system namespace.

B

I do want to mention here that this carries on through every single section within lens as well.

B

So if I move to our deployments, as you guys can see, it is currently filtering or not filtering, but matching to the correct namespace, which is the cube system in order to remove this it's very similar to excel. If any of you have used excel just uncheck this box.

B

Now that we are in deployments, we will open up a deployment to view what is currently happening. The deployment that I will be opening up is the nginx.

B

We can view when it was created, the name, the namespace it's associated with and various other settings here as well.

B

Another very neat functionality that lens does is: it provides us a user interface to be able to utilize kubernetes to scale our deployments up and down with a click.

B

Let me show you how we do this scrolling to the right. We can see the scale icon. Currently we have three replicas deployed for the nginx deployment and we want to scale this up to, let's say.

B

B

Clicking scale jumping into our pods and scrolling down, we can immediately see the containers being created without running any command line. Everything that happens within lens is near real time as well.

B

Let these deploy.

B

And just with a simple click lens has utilized kubernetes to scale our deployments.

B

I find this extremely useful and I think you guys will too going back to our deployments and our engine x. We can see immediately that we have 45 pods currently running from here. We also have the functionality and the ability to utilize kubernetes to scale them down to do so. We do the same thing.

B

And we'll scale them back down to four all in real time lens begins to terminate these pods.

B

As you can see here,.

B

We'll let this run.

C

B

Going back to our deployments again, we have the functionality here and the ability to filter and search through a click of a button or typing a particular thing. For example,.

B

And you guys can see we get a much more granular view into our search.

B

And why is this beneficial? I mean technically up until now or depending what tools you're using you would have to write some type of cube ctl to be able to understand all the objects that are currently running so to demonstrate.

B

B

Do a quick command line.

B

Open this up and you guys, can immediately see all of the objects with the specific details associated.

B

I'm not sure about you guys, but this is quite a bit of an eyesore for myself and to be able to filter and search here. You would have to perform other compliment, complicated command lines to be able to find this information lens. Does this for us simply by clicking and filtering and searching thus creating a much more.

B

Efficient use of our time.

B

Clicking into another pod, we get another another very useful functionality within lens which is being able to view all of the logs associated to this particular kubernetes object.

B

Opening opening this up, we can see all of the logs that are.

B

Associated to this particular pod.

B

Lens also gives us the ability to save this log.

C

B

Save and we can choose to save this to our desktop our downloads or wherever we choose to do.

C

So we'll close this for now and move along.

B

Let's open up another deployment, let's see what deployment we want to open up. Maybe we will open up our core dns and again, you guys can see. We get a much more granular view into this deployment and how it's performing in the last hour, through the pre-built in prometheus.

B

With all the settings associated, another thing I want to highlight here is the ability to walk through each and every single kubernetes object through a simple click scrolling down to our pods. We can see the two pods I can click into them and immediately once again get a granular view into these pods.

B

Anything that you see that is hyperlinked is clickable.

B

We can show our tolerations.

B

We can see our containers, the ports associated to the containers, our volumes, our config volume and much more so if I was working in this pod and I wanted to see what it's being controlled by and how that particular kubernetes object is performing.

B

I can click directly into this core dns and view this replica set in a granular fashion.

B

This creates a much more efficient environment for all kubernetes hackers that are utilizing lens. The ability to click and walk through each and every single object is very, very useful.

C

B

Move along so we're almost at the halfway point, and I want to talk to you guys all about what we've already reviewed and where we are going with the demo itself now, so we reviewed how to add a cluster, how to create a workspace, how to add an icon to our cluster to create a much more efficient environment within our smart console. So if I wanted to jump to my admin cluster, I can do so.

B

If I wanted to jump to my raspberry pi, I can do so. I wanted to jump to mini cube. I can do so my staging cluster and so forth.

B

Coming back to our lens demo, we've also reviewed the context aware terminal which allows us to auto magically. Yes, once again, auto magically connect to the correct endpoint of our cluster.

B

This reduces any human error that could be happening.

B

We've also reviewed the pre-built in prometheus that lends leverages from your cubeconfig file and we talked about how lens is leveraging your role-based access control from your yaml file. We do not build a new construct. We are leveraging once again your role based access control from your yaml file.

B

I think that's extremely important to note, as well as again the context aware terminal where we are automagically matching to the correct end point of the cluster so from here we're going to walk through a couple other things within lens, but I do want to show you guys how we can deploy and install a helm chart directly into our cluster with lens and also how we can port forward into that particular application.

B

After we do this, we will get a sneak peek within our lens extension api, which allows users and organizations to build extensions on top of lens to one harness our user user base and, as you guys know, it's over 93 000 and to increase the lens functionality, but also again harnessing our user base for your particular tool. Product open source technology that can sit on top of lens. As an extension.

B

Okay, so let's move along, we have our damien sets.

B

Our stateful sets our jobs and our cron jobs again. Lens allows us to filter.

B

And search in every single section and with every single kubernetes object within our cluster itself from here we'll jump into our config.

B

Take a look at our config maps.

B

And scroll and of course we can take a look at them on the top, you can see the kubernetes object, config map and on the right you can see the name of that particular config map when it was created, the name space it's associated with and, of course, very importantly, our labels.

B

Scrolling down.

B

We can see the data associated as well to this config map all in one place. I won't scroll through this whole thing, as you guys can see it's very very long, but we do have this functionality within.

B

Lens the next thing I want to show you guys is our secrets, which is very important or your secrets, and again you can only view these particular things based off of your role based access control, that lens leverages from your yaml file.

B

Is all of our secrets associated the name, space they're associated with the labels, the keys the type and, of course, the age filtering for a specific namespace? We'll do stack light and immediately, we can see we have filtered for the specific namespace and we have 27 out of 85 highlighted here.

B

Clicking into a secret, you get very you get much of the same functionality as you did in the other: kubernetes objects when viewing them, you get the name and it was created, the namespace, the labels associated and, of course, the secrets.

B

Opening this again is based off of your our back that we leverage from your yaml file and show it real, quick and we can hide it, and we can close this, I'm pretty sure within this cluster we don't have any resource quotas, hbas or pod distribution budgets, but we can take a.

B

B

We are filtered so, let's unfilter.

B

And, as you can see, we do not have any of these.

B

Moving down to network, we can see all the services associated our endpoints, our ingresses and our network policies as.

B

B

So if you guys haven't caught on yet lens allows us to filter and search within any section, creating a much more efficient environment for whoever is utilizing this tool and working within their cluster.

B

From being able to click and view and jump into kubernetes resource, manifest all without having to write any command line,.

B

B

Close this, let's actually exit that leave that there's our endpoints. I don't think we have any ingresses and our network policies.

B

You can take a look at our storage, our persistent volume claims and once again you guys can see that there are some things hyperlinked here, which immediately gives us the ability to walk to that kubernetes object through a simple click.

B

We've opened this pod, it's a jenkins pod. You can see when it was created. The labels associated the annotations, what it's being controlled by and the nodes.

B

You can always view the logs as well, and we can see various other details while scrolling.

B

Okay, so let's actually move towards deploying a helm chart within our cluster through lens, so lens leverages artifact hub a public repo online to pull hundreds, if not thousands, of different helm packages that we can choose from and yes, you definitely can bring your own home package. If you choose to do so today. For this example, we'll download wordpress.

B

We'll use bitnami.

B

We'll open the helm chart package- and this is provided to us through once again artifact hub and all of the details associated to this helm chart is packaged for us from the introduction to the prerequisites installing the chart. The parameters of the chart and various other details, as you guys can see again. Anything that is hyperlinked is clickable.

B

So, for example, if we wanted to jump to our kubernetes documentation, we can do.

C

B

Here we'll install it's a little smaller.

B

Actually, let's just scroll through this for a second, you can see everything associated to this helm.

B

And we can click install immediately lens begins to install this helm chart in the package directly to our cluster and, as you guys can see, it was successful.

B

So there's three places where this lives lives under our charts or releases view our ham release and our release is here clicking into here. You can see that we deployed and installed our helm chart 24 seconds ago.

B

And, of course, you get various other details here as well.

B

You can see the secrets associated the service account the config map, the persistent volume claim the deployment and the stateful set as well and again. Anything that is currently highlighted or hyperlinked is clickable, so I can click into my deployment and immediately get a granular view in the last hour of our wordpress deployment, with the labels associated the annotations when it was created and so forth again, we can scale through lens. Well, excuse me, while it leverages kubernetes or uses kubernetes.

B

If we choose to do so so now, I want to show you how we can port forward directly into this application for demonstration purposes. I will move to my local cluster. This cluster is not a local cluster, so we will jump to our mini queue, which is my desktop cluster and, as you can see, I have my icon associated. So I know immediately where this cluster is within our cluster selector or a smart console.

B

To port forward, we would go to our network find the particular application.

C

Click, our port.

B

And it immediately opens up, as you guys can.

B

See, as you guys can probably tell I had this work, this helm chart already deployed within my mini cube, so we did not have to install and deploy it. All. I did was move to my network to my services and clicked our particular port and again lens immediately launches.

B

As you guys can see,.

B

So we're at 41 over the hour, so the last thing I do want to highlight for each and every single one of us is our lens extensions. This is set to be released tomorrow. Currently, you can play with this um through a release candidate that you can find on github, but for now let's see how we can add an extension and which extension we're going to add and the value of that extension.

B

Scrolling to lens at the top left, we'll click extensions and you can see. I currently have an extension already installed, but we can find another extension.

B

Yep use config and immediately lens installs. This extension on top of lens all in real time.

B

So today I will be demonstrating the mirantis lens extension to container cloud.

B

And what's useful about this extension itself is being able to add clusters to lens from mirantis container cloud immediately so I'll sign here in real quick and what we're signing into. Obviously, you guys can see the end point at the top. That's the url and then we're signing into our mirantis container cloud instance to view which clusters we can grab from mirantis container cloud.

B

As you guys can see, we have several different clusters here from our default to our demo in our demo, 2. so for demonstration purposes. I will grab two of these clusters add selected clusters.

B

They were skipped because they're already in lens cool and to view these clusters we'll jump to our workspaces, and we can see that we have added the demo2 cluster directly to lens through the mirantis container cloud extension.

B

Voila, so this is one of the first extensions there's many more currently out and available, and we really do hope that everyone begins to think about extensions that we can leverage on top of lens to harness our user base for your particular technology tool or open source activity.

B

Okay, guys we're coming up to the witching hour and there's one last thing I do want to highlight. I will jump back to my workspace for default and this is our custom resources.

B

Let's go back to my demo and within our crds.

B

We can take a look at istio, envoy and other custom resources on top of kubernetes. If we choose to do so, I don't think I currently have any, but if you choose to do so, you have that functionality within lens as.

B

Well, so to bring it all home if you're an application owner a developer, an operator lens gives you a much more granular view into your cluster. How your application is performing.

B

You can cordon you can shell into a node. You can scale up and down different deployments all in real time, without having to write any command line.

B

Awesome thanks guys from here. I do want to jump into a quick slide. Let's see if it actually, let me scroll.

B

And what we can do instead is we can just open it up. This.

C

B

So here's our contact information where you can find the github repo or you can download lens my email, the lens email and please, please, please join our slack community for posting issues with lens troubleshooting.

B

um Maybe ideas that you would like to see that would come to lens anything of that particular nature. We are more than willing to listen to the community and get your feedback. This would be greatly appreciated. We want to listen to everybody. We want to build this together and we want to make this the greatest kubernetes ide.

B

E

uh I am nick chase also from mirantis. I'm gonna go ahead and facilitate the questions here. Thank you very much edward. That was very informative.

E

uh If you have questions, please go ahead and drop them in the chat or the q a, and we will try and.

C

E

So uh let's go ahead and look at this list here. um Let's stop, but there seems to be a bit of excitement about these extensions somebody wants to know. Can I create my own extensions.

B

Yes, yes, you can absolutely create your own extensions, so our documentation is posted on github currently and we were we were. We are more than willing to work with you to actually help you build it build the extensions itself.

B

So let me once again share. We always have this issue share our contact information and I can also provide the documentation if you email me where you can build a lens extension and if you go to our website, kateslends.dev.

B

Click partners: you can request to become a partner really what that means is that you want to build an extension, become part of the lens extension community.

B

Fill out this form and we will provide you guys with documentation, potentially a discovery, call with the technical team that built lens as well and um anything else. You guys need to help onboard you guys to build your extension. So the answer to that is yes,.

E

Okay: let's go ahead and look back at this list.

E

How does lens handle access control to your kubernetes cluster so how to secure.

B

Got it got it yeah, so lens will automatically inherit the access control from your cube config file through the roll based access control of that yaml file itself.

E

So, basically, whatever um so, whatever security uh the user has, if they were accessing kubernetes through any other means uh lens, will honor that.

B

Correct, I see another question here from and I apologize if I butcher it from centos, I couldn't see clusters or nodes um in lens ide, as shown what could be the reason currently showing empty cpu or memory or other details, though it's ready so lens, auto detects your metrics and your prometheus from your yaml file, and if you do not have that currently within your yaml file, you can still install prometheus directly to through lens. So the way you would do this is in settings of your cluster.

B

You have this metric stack and you can install it.

E

Here, what different flavors of kubernetes clusters does lenses work with? Oh.

B

That's a fantastic question, so lens works with any kubernetes distribution from gke to eks, to rancher, mirantis container cloud and any approved cncf certified kubernetes.

E

B

uh It does that does include k, zeros.

D

Just for those of you who haven't heard of it, we we uh also were involved in the whole.

E

um K zeros launch a couple days ago, so, uh okay, so let's see here, I.

B

See another question nick: um is it possible to set up the default shell, fish or zsh and use these features? It's not currently possible lens will default. The terminal lens will default and use the terminal in the current environment.

B

So please feel free to open up a request on lenses github, and hopefully we can build that very very soon. That's an excellent question.

E

Available as a web version, something that I can run in cluster for all my end, users.

B

No, no, it is not lens, is a desktop application, um so un, unfortunately it is not a web web application. It's a desktop application and you can download it at our github repository lens app.

E

E

Oh, let's see yeah.

E

uh What is this, uh what is the mirantis container cloud tool you used in the demo? It seems like it manages multiple kubernetes clusters.

B

Yes, yes, so miranda's container cloud. What I highlighted in the demo was the extension to marantus container cloud. Mirantis container cloud provides a single pane of glass to help developers and operators stand up and maintain their kubernetes clusters anywhere, so think of it as a managed kubernetes offering that's the way. I would explain.

B

It yeah, I don't see any other questions. It looks like jose, asked a question that was already answered. um I can. I can answer it again. So.

B

If you don't have prometheus set up within your yaml file, you can install it here within lens. uh Where did it go here? All right? Sorry, let me go back to my settings. Yeah and our metric stack. You can install it here and lens will automatically install a prometheus onto um lens, so you can get the cpu and the memory to show up um as we've shown.

B

If I go jump to my demo cluster like this, but currently this is leveraging um the auto detect feature within lens and it's leveraging the metrics that are built within my cluster file itself. My yaml all.

E

Right well, um if we don't have any other questions. Oh it looks like something just popped up. No.

E

I know that was the duplicate, okay, so uh yeah. So I suppose if we have no other questions and uh going once going twice sold uh so edward, um oh no, wait a minute. We do have one more question. Is there.

B

A way to log into pod to see its content and internals through that's an excellent question. um You can, I believe you can so you can take a look at your pods. You can select a pod and you can view the logs associated to see what is currently happening within the pot itself.

B

Does that answer your question.

B

Yeah you can exact directly into the pod or, as I'm, showing here, the logs itself. This will help you view exactly what is currently happening and again you can save your logs directly to your desktop. If you choose to do so, you can also search within your logs as well so um index.html.

B

It highlights everything here. So the answer to your question is yes, excellent.

E

Okay, all right any other questions before we before we take our leave.

B

And once again, I do want to mention um and show you guys where you guys can find lens currently, so, as you guys can see, you can find it github and we are currently releasing or planning on releasing our ga version of lens 4.0 tomorrow or the next day. Currently there is a release candidate that is that is out, and you guys can play with that as of right now, um and that is currently what I'm working off of for this particular demo itself.

B

So, if I jump into about lens, you guys can see it's a release, candidate, 4.0 and that's once again why we were unable to highlight the distribution version of your of your kubernetes, but for this particular cluster I know it's vanilla and um once ga is out, you guys will also be able to see that uh your distribution version.

E

All right: well, you want to take us home, edward.

B

Yeah um sure guys, so thanks for sitting through the entire demo, I know it was packed with a ton of different things from walking our kubernetes objects through clicks and filtering.

B

Also highlighting that lens has a pre-built in context, aware terminal which auto magically yes once again, auto magically matches to the correct endpoint of the cluster lens has pre-built in prometheus, auto detect as well to bring you metrics all in real time for the last hour to see how your cluster's performing lens also allows you to install and deploy a helm chart all in real time, as we highlight it here through our apps. This is the repo we're utilizing artifact hub, you can search for your particular helm, chart grab it.

B

B

All through several clicks- and we also walk through our lens extensions feature where I really suggest- and I push each and every single one of you to begin thinking about what kind of extensions can sit on top of lens.

B

If you choose to do so so with that, I want to thank each and every single one of you for joining our webinar today of how to take the pain out of multi-cluster kubernetes with lens, and I hope each and every single one of you go ahead and downloads it, and I also hope that it creates a much more efficient use of your time when working with kubernetes and the current clusters.

B

Thank you all. It was very, very exciting and I hope you guys enjoy the rest of your day from wherever you are in the world, stay safe to your family and your friends.

A

Awesome thanks so much edward for the great presentation and thank you nick for supporting today um and thank you michelle for being on the back end and helping as well um as edward, said, hope. Everybody has a great day stay safe out there, a reminder that you can find the recording and the slides from this presentation uh posted later today to the cncf webinars page. We hope to see you at a future cncf webinar thanks. Everybody.

B

Thanks everyone.