Welcome back.
In this section, we are going to understand about how we are going to configure access to multiple
aqueous clusters in adjure, so accessing multiple other cluster will be our day to day requirement
and how we are going to do that and what Cube CTL commands will help us in doing that will be our core
goal of this section.
So with that said, so assume like you have a cluster one and two are three and four, whatever it is.
Right.
And as it gets admin using Cube SBL, if you if you want to access ECUs cluster, so you do the command,
Idzik is credit, get credentials and then provide all the research group name and then cluster name.
And then after that you do the cube still get nodes to see whether you have got the access so far.
But now we are going to understand about current context, use context and all these things from cube,
Syrian conflict perspective, all those things.
OK, so now if your current context is configured to a cluster one using the command eighty-six, get
credentials, come on.
So then you will be able to execute the commands related to cluster one.
If you are current context is configured to cluster two, then you will be executing the command to
the cluster.
So how you are going to set the current context and then use that context in your cube scale?
We are going to look into.
Right.
So consider you have two clusters name to configure.
It gets the demo three and four cluster access for cubes.
So you already know that EDEK is get credentials and resource group name, which is nothing but a case
kasarda the three and the name is it is the military cluster name.
So you can configure your cluster access to one cluster in the same way to access other cluster.
So you need to provide those cluster information.
So if you want to see the config information, what is present in your cube config so you can secure
ctrl config view in the same way if you want to see what to which cluster you have the current context
pointed to.
So you can say Cube, Sutil config, current context.
And finally, if you want to switch the context, okay, so your current context is pointing to X cluster
one and then if you want to switch to X Cluster two, so then how you are going to use the command use
context to switch the current context to cluster one, to cluster two.
So you are going to explore these things.
So one is get credentials, secondees, config view and config, current context and config use context.
So these are the things we are going to explore as part of this section.
So these are important for us when we move further for our other sections, which are adjure authentication
area authentication for your cluster accesses the next section which we are going to deal with.
So I'll show you a few things which you are going to do after this section.
And so before going there, we need to understand a few of the additional commands here.
So that's the reason we added this as our first section.
So just now we completed the section has two DB application routing Section 20 and we are moving to
21, which is adjure a case authentication and then are back.
So this core section is primarily about how you are going to attempt to get to your Carbonetti cluster,
adjure using adult active directly.
And you also need to understand about Kuban.
It is role based access control in combination with aju active directory groups.
So considering all those things, I have designed it section with four sections, which is nothing.
But one starts with your cluster access, with those calcitriol config use, context, view and then
the current context comments.
And then you will move on to other hédi authentication for ex admins and then you will move on to Cuba.
Nettie's are back with Adjure early on.
It is with the Cuban.
It is concepts called roll and then roll binding.
From there again you will move to the next level, which is nothing but Cuban.
It is auerback cluster rule and then cluster roll binding in combination with agility authentication.
So this is all we are going to look into step by step.
So whatever you are seeing, these things we are going to explore in each and every section.
The first one is are already attending.
It with a kiss admin's.
So how you are going to do that, you are going to see and next you are going to look into Roeland and
roll binding using that for an ex user who is in it for a specific namespace, how you are going to
give the access for that user.
There is a user and then you to you access for him for only the namespace.
So like that in the same way for the entire cluster read-only access, how you are going to provide
using cluster roll and then cluster roll binding.
Right.
So like this you are going to provide all those information and then understand better what Cubans are
back in combination with a case and also Azure active directory groups.
So all these all these things we are going to explore in it step by step manner in our Section 21 and
doing so in our next lecture will move on with the cluster access to multiple clusters.
So implementation things.
OK, so I'll see you in the next lecture.
Until then, bye bye.
Thank you.