Hey, friends, did you know that you can work with your Azure
Kubernetes Service clusters or AKS clusters from Visual Studio code?
Rong Zhang and Tats Mishra are here to show me the latest VS code extension
that adds your favorite AKS tools and diagnostics
today on Azure Friday.
Hey friends, it's Azure Friday. I'm Scott Hanselman.
I'm going to learn all about AKS today.
Rong Zhang is here. How are you?
Good. How are you?
I'm always happy to learn.
And I'm happy that you're here to teach me.
So talk to me about this extension and what it adds to my Visual Studio code.
Yeah, sure. Yeah.
So first of all, I'm wrong.
I'm the PM working for access operability.
We aim to provide the best customer support, experiencing all aspects work.
Yes. So now like the feature we're going to introduce today is within the VS code.
You can download the extension then leverage a tools there
to do a lot of things.
For example, you're able to provisioned Agora resources for you to fast
accrued clusters, the actual portal to check your castle
property server and also navigate all your customers really quick.
And besides that,
you can also create a good help workflow to make your deployment easier.
The diagnosis, the diagnostic and the troubleshooting tools in the CAS
extension also provides you a very quick access to all the guys
in the resources and documentation that can help you to resolve the issue.
If that happens, all your kids classroom.
So now this provides you like a very good convenience, support
and to save your time.
So yeah,
these are the bulk cool features we're trying to introduce today.
And I wanted to have Tats Mishra for to give you
like a very cool experience on the demo, to walk you through in details.
That'll be great.
Let's bring Tats in
Hi, Scott. Hi, Rong. Hey.
Welcome, welcome.
This is great. So you know what? I do my Kubernetes stuff.
I spend a lot of time at the command line.
Is this going to be more visual or is this going to be more more obscure commands?
I think you're going to love it.
It is going to be more visual.
And what will happen is I will be have done all the heavy lifting upfront.
So for the user, it has just one click features,
but there's a lot of things going on.
So for people who want to download,
they will go to the Visual Studio, a visual code,
and then go to a managed extension
and type as your community services.
That's where you will find this extension because I have already installed it.
There would be an install a button here and once usable, install it usable.
See this icon up period for their visual
visual studio code.
You will see
two windows, three windows prima facie, but two are very important for this.
One is Cluster Explorer, another one is Cloud Explorer.
It's extension is
Cloud Explorer functionalities.
So for day zero user,
there will be a log in here and it'll be your normal portal.
And once you log in you will see your subscription
and the clusters within that subscription appearing for them.
So let's go and see what are the features.
There are some basic features like merge into cube config, save,
save cube conflicts, but we have now introduced things like running
cancer diagnostics and now you can run diagnostics on your cluster
by leveraging detectors which run when you are in the portal.
So for example, for best practices
like best practices under the hood, it'll go
to the right resource, get the data and populated for the user.
So without leaving VS code, experience user can do all this
well. So is that typing commands
that I could be typing for me or is that calling into Azure itself
and pulling stuff that I couldn't get from Q Curl?
So it's calling arm API for Container Services.
So it is like you are typing commands for the territory,
but you are basically and there are many of these.
So create update, bleed knowing issues,
network and connectivity and node help.
Now the another one click feature
which is more heavy lifting is the running scope.
So one basic problem some people have
is they have clusters which have bad nodes
and they want to see logs of their cluster.
So essentially the idea is to simplify it case scope tool,
which is an open source tool and run it by just one click.
So users will go and select behind the scenes.
It will take over the identity, generate 2 minutes pass, start collecting the log
out of your nodes within the cluster and then start populating
the data
into your storage which it will past deploying the history as well.
So now user just need to sit back and don't need to leave their squad
ecosystem.
Very cool.
So this,
this thing that's created on the right hand side
that that diagnostics view is an example that's come down and that's
telling you that your stuff is healthy and everything is, is great.
And would there be a recommendation if it was not healthy?
Exactly.
So there will be a recommendation
if it is not healthy and it gets linked to other help helping links
where you can go and find out how to make it healthy.
So now we have just run the pretty scope
and in there it will have a generate link.
I'll go and generate the link.
So under the hood
your tool has just run and it'll tell you what it has collected for you.
This is all user usually can
type in a command prompt,
but now it's all in one click and user doesn't have to set up anything.
It's just a preset up of diagnostic settings and off you go.
Okay.
Net link it's going to send is something that I can share
and then will that link expire or that link live forever?
So the link which it is going to create is two links.
One is 2 minutes, six expiring, another one is seven days expiry link.
So you can share that seven day expiry link.
So this is a seven day shareable link.
So you can just paste it in the in your email,
send it to CSR if you want to download it, you click on there.
I will go and download this free.
Okay.
So I see that you just clicked on that and then we saw just briefly there it hopped
because you're on a mac and it put it into the downloads folder.
So that was a drive by download and you got that link available to you now.
Absolutely.
And then we have the navigational feature which is I have actually found out
that a lot of time people who find it hard to actually find exactly their cluster.
So usually what I do, I go to my portal and then I search for my cluster
from resources and it appears now you can directly go to like
if I want to go to this cluster, I'll just go showing that your portal
and it'll often goes and it'll open in your browser
so it doesn't need to now tell you don't need to go to portal
and search for your cluster, it will open your cluster to the model for you.
So it's a deep navigation link right there.
And it
and there's some
more usability and developer experience updates
which is say you are in your code ecosystem and you're working in a project
and you are looking for certain properties, but you are usually
your developers usually do.
For example, what is my provision state it success or failure
is my cluster running on the old version or your version?
How many nodes do I have which always type in my running or what's my website?
So what size regions are and what is a provision state
and this this size of that?
VM So ordinarily I would have to, as I mentioned before,
go down to the command line, open up a terminal,
remember the right cube cuttle for that, or maybe use the Azure Command line.
There's lots of different ways to collect this information
depending on how you want to do it, depending on whether it's the node itself
and you'd use cube cuttle or whether it's the host around the outside of it.
And then I would use Azure CGI, right?
Absolutely. Absolutely. Right. Right.
And this is just and usability for the developers.
Like I'm about to introduce another feature which we did
for the developer is creating workflows.
So usually when I created up against my cluster
and I will have a starter workflow, I will need to populate certain things,
for example, environment variables and so on and so forth.
And I'll go to a GitHub through their GitHub workflows
and make this scaffolding file, which I need to carefully go and change it.
So we have simplified that.
So on your cluster in your right click and you create GitHub workflow,
let's say I'll choose starter workflow for cats.
One, two, three.
It will automatically populate resource groups and custom name for you.
So all user need to do is save it on your project
and provide the container name what they want to provide
a deployment plan that's ready to go
and it's
just adding it to get into your project
and you are ready for development against your cluster.
You know, this really fills the gap because you've got access tools,
you've got the voice code
editor where we spend our time, you've got the Azure portal,
and ordinarily you find yourself jumping around and jumping around.
And this is automating a lot of those common tasks that one does
when they are diagnosing the health of an X cluster, doesn't it?
Absolutely. And we are we will continue to grow this.
There's one last thing which I have pre run for you,
which is an installation or service operator, which is
deploying a lot of resources within this, your Kubernetes clusters.
So essentially when you if user need to download
and deploy as your service operator
under the hood, there are
about 5 to 6 deployments they have to do, but we have simplified it.
So now users just have to provide their app by the end service principle
because these are passwords.
We are asking the user upfront about it and we do give them enough help
so that they can actually find out how to generate these.
Once they have this and they deploy it through their cluster,
all they have to do is click submit and this is one of the run
I've done previously that it will show you what all under different heavy lifting
it does for you, and in the end it will deploy the service
operators resources and then all user need to do is barge it to their
mast occupancy.
And then in the Cluster Explorer
they will go and they will have your services available
with every single resource they want to create against the cluster.
Hence the real orchestration which is in case
provides is
clear here.
So I think that's the demo I have for you
for today, if you have any question.
No, that's great.
This definitely is going to save a lot of people a lot of time.
I appreciate you and Ron coming by to show that to me so wrong.
Where would I go to learn more
about about this extension and these improvements for diagnostics?
Yeah.
So definitely we have all this documentation
shared under the voice code site.
Yeah.
So you can go to this documentation and then kind of like
I learned through the entire process, the entire process as I wrote you,
you can install the apps extension the beginning and then like these are like
a very simple intuitive like instructions, pretty much like a bullet
listed out all the steps you need to do for like a goal through this experience.
And then we also provide,
you know, the screenshots to guide you like what exactly that look like.
Yeah. So that's definitely a resource could like
learn more about like these features and how to use it.
Very cool.
Well, thanks.
Both of you are in touch for hanging out with me today on Azure Friday.
Just thank your families.
But yeah.
All right.
I'm learning all about how batch code and the access extension makes Kubernetes
just that much more fun and easy here on Azure Friday.
Hey, thanks for watching this episode of Azure Friday.
Now I need you to like it.
Comment on it, tell your friends retweeted watch more
Azure Friday.