►
From YouTube: Meshery Development Meeting (Jan 5th, 2022)
Description
Meshery Development Meeting - January 5th 2022
Agenda:
- [Lee] Confirmation of v0.7.0 feature champions.
- [Piyush] New UX with `system start`.
- [Nithish Karthik] Progress update: Refactoring Meshery UI in v0.7.0
- [Gaurav] Enhancements + features in Meshery UI
- [Aditya] Updates on Service pattern catalog.
- [Aaditya Subedy] Updates and issues on service-mesh labs.
- [Hussaina] UX improvement for mesheryctl token.
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/meshery
Twitter: https://twitter.com/mesheryio
LinkedIn: https://www.linkedin.com/showcase/meshery/
Docker Hub: https://hub.docker.com/u/layer5/
A
Okay,
let's
get
rolling,
hey,
welcome
everybody!
This
is
the
mastery
development
meeting,
the
first
one
of
2022
and
surprise
we're
live
on
youtube.
We're
actually
not
live
on
youtube.
It's
a
private
feed,
but
we're
trying
to
streamline
part
of
the
processes
as
we
head
into
the
new
year.
So
so
don't
be
alarmed
if
you
try
to
see
yourself
on
youtube,
but
you
can't
at
the
moment
don't
worry.
You'll
be
internet
famous
in
about
an
hour.
So,
okay.
A
Well,
we've
got
a
healthy
set
of
topics
lined
up
last
time
we
met
wasn't
very
long
ago.
I
think
we
met
just
before
just
before
christmas,
and
so
for
those
that
are
well.
We
have
a
couple
of
housekeeping
items.
I
guess
first,
a
quick
check.
Is
anyone
new
on
the
call
today,
like
first
time
on
the
measuring
dev
call?
A
B
A
B
A
That's
great,
that's
perfect
good
to
have
you
there's
a
lot
of
things
outside
of
straight
up
coding
to
be
done
in
the
projects.
One
of
them
is
really
critical
and
we're
going
to
find
a
lot
of
people,
a
lot
of
people
in
cloud
native
land,
paying
attention
to
service
mesh
performance
in
the
upcoming
months,
and
so
one
of
mesherie's
sibling
projects
service,
mesh
performance
smp
it
needs
people
oriented
toward
devops
like
like.
A
C
A
C
A
B
A
If
you
will,
if
you
want
to
use
more
of
an
agile
nomenclature,
and
so
there
had
been
an
email
or
two,
there
have
been
a
few
emails
about
the
roadmap
and
the
most
recent
one
was
sent
out
to
each
of
the
individuals
that
are
on
this
list.
Hopefully,
hopefully
all
of
them
got
it,
and
so
what
we're
asking
people
to
do
is
reflect
on
their
ability
to
their
ability,
willingness
to
take
on
and
champion
that
area
and
drive
it
forward
for
the
dot
seven
release.
E
All
right,
thank
you.
Moving
on
push
would
you
like
to
speak
to
your
topic?
Okay,
hi,
hello.
Let
me
share
my
screen.
Okay,
so
I'm
using
latest
messaging
version.
This
is
release
candidate,
3
and
in
just
a
second
okay.
So
right
here
we
are
looking
on
the
pods
that
are
running
right
now.
This
is
really
like.
I
created
this
cluster
very
recently
we
can
see.
Five
minutes
has
been
passed,
so
this
is
a
new
mini
cube
cluster
and
I
am
going
to
start
measuring
with
our
latest
release.
A
E
E
Let's
hit
it,
it
says
that
it's
not
working
right
and
very
recently,
someone
in
slack
like
said
that
he
was
not
able
to
access
machine
ui.
It
was
stuck,
it
was
not
working.
So
how
do
we
improve
this?
I
came
with
something
new.
I
won't
run
it
because
it
will
take
time
I'll
show
you
a
video
that
I
already
recorded.
E
Yeah
this
one
so
I'll
start
here
yeah.
So
this
is
this
is
starting
machine
ui
like
messaging,
and
that
now
the
status
of
the
pod
is
container
creating
it
will
keep
waiting
to
get
necessary
to
the
running
state
like
as
it
is
just
trying
and
wait.
Till
machu
reaches
the
running
state
and
after
like
around
three
minutes,
two
minute
and
thirty.
Second
yeah
it
switched.
Okay
measure
is
running
and
that
started
measuring
with
a
correct
endpoint
and
it
is
accessible
the
moment
here.
The
pod
status
changes
we
are
like
on
the
screen.
E
A
E
This
will
actually
also
help
in
a
messy
ctl
mesh
command,
because
whenever
we
deploy
the
service
meshes
like
link
id
is
getting
started.
We
do
not
know
it
actually
started
or
not,
because
we
have
no
idea
of
the
the
pods
changing
their
state.
So
these
functions,
these
readiness
functions,
readiness,
health
checks
can
be
generalized
for
any
pods
and
we
can
like
send
back
some
new
data
that
it
has
been
actually
started.
Not
just
operation
was
executed.
F
Status
at
regular
intervals
right
there
is
some
logic
to
do
it
in
an
exponential
manner
right.
So
maybe,
instead
of
calling
the
cube
api
at
regular
intervals,
maybe
we
could
double
the
timeout
right
if
the
card
is
not
ready.
Yet
we
could,
let's
say
we
queried
at
a
second
a
second
and
then
maybe
fourth,
second
and
eight
second
kind
of
thing
exponential.
E
Yeah,
okay,
yeah,
that's
a
really
good
question.
Actually
I
was
trying
to
do
that
when
I
tried
like
I,
I
started
with
this
problem,
but
then
I
found
that
there
is
a
command
in
tube
ctl
known
as
acute
ctl
weight,
and
you
can
pass
conditions
to
check
that
whenever
you
like,
you
are
just
deploying
some
head
chart
or
manifest,
then
you
can
run
cube,
ctrl
wait
and
it
will
wait
till
the
pod
gets
started
or
whatever
the
condition
you
have
passed
as
the
argument.
E
E
Okay,
so
I
checked
it
how
that
works
and
tried
to
replicate
it
in
here,
so
I
thought
we
can
like
query
it
on
in
intervals
after
10
seconds
after
10
seconds
again,
but
that
was
not
not
being
implemented
by
cube
ctl.
So
I
thought,
if
cube
ctl
is
doing
it,
but
at
each
second.
Maybe
we
can
do
that
also
like
the
timeout
set
and
the
default
type
timeout
is
for
five
minutes,
and
I
think
five
minutes
is
enough
for
any
system
to
start
measuring
and
measuring
image.
F
Hook
it
up
that
also,
as
one
of
the
query
like
I
mean,
have
you
considered
all
the
speeds
of
getting
the
mystery
pod
right,
though
it
is
like
200
mb,
there
could
be
like
very
slow
connections.
In
that
case
also,
it
should
be
enough
for
pulling
the
mystery
image
and
starting
it
right.
So
I
I
believe
you
would
have
considered
all
that
right.
So.
E
Okay,
oh
okay,
I'm
not
sure
if
I
like,
I
haven't
considered
that
fact
that
it
might
take
more
than
five
minutes,
but
if,
if
it
takes
more
than
five
minutes,
we
will
return
just
an
error
that
the
pods
haven't
the
running
state
yet,
but
you
can
check
them
with
necessity
system
status
and
to
get
the
url
of
measuring.
You
can
run
necessity
system
dashboard,
so
we
are
like
telling
them
the
information
that
they
can
to
which
they
can
access
measure
ui.
E
F
E
Yeah
that
that
is
shown
by
cube,
ctl
commands
that
image
is
being
pulled
and
then
it
is
getting
started.
Container
is
being
created
and
things
like
that,
but
we
I'm
not
sure
if
we
should
show
them
in
this
here
like
this,
the
command
is
the
like.
The
only
purpose
of
command
is
to
get
started
with,
let's
start
and
the
lack
of
the
the
errors
was
that
we
had
no
idea
when
machinery
was
coming
up,
so
we
were
using
some
times
sleep
times.
E
We
were
sleeping
for
some
time,
maybe
10
seconds
20
seconds
30
seconds,
but
that
might
that
was
like
that
was
simply
not
enough.
30
seconds
is
not
enough
to
get
the
pot
started.
So
that's
how
I
came
up
with
something
that
can
fall
till
she
changes
it
straight
to
running
and
yeah
yeah
and
that's
what
I
have.
E
H
B
E
A
H
A
A
Hussein
is
initial.
Suggestion
was
that
you
know
we
might
be
able
to
sort
of
do
something,
slightly
more
intelligent
or
slightly
more
efficient,
with
exponential
backup
and
retry,
rather
than
every
10
seconds
the
overhead.
There
is
probably
negligible.
That
said,
it's
to
push's
sort
of
final
point
on
his
initial
presentation.
A
This
isn't
the
only
area
that
the
air,
the
only
area
of
measuring
that
such
logic,
such
assertion,
like
like
verifying
an
assertion
like
measuring,
is
running.
That's
an
assertion
that
you
want
to
verify.
It's
like
wow.
Those
assertions
go
right
back
into
some.
Some
integration
tests
that
we're
going
to
talk
about
later
in
the
call
those
assertions
go
right
back
into
what
meshri
does,
as
in
its
orchestration
role
as
it's
orchestrating
and
re,
deploying
and
reconfiguring
service
meshes
that
it
need.
You
know
when
it's
done
with
the
operation
it
needs
to.
A
It
would
have
an
assertion
that
the
configuration
that
was
applied
to
the
mesh
is,
in
fact
you
know
was
successful,
is
in
fact
applied
and
so
piyusha's
example.
There
is,
like
you
know,
thinking
forward
toward
the
command
mesh
ctl
mesh,
which
deploys
service
meshes
and
configures
them,
particularly
as
you
think,
toward
measuring
ctl
pattern,
which
may
incorporate
any
number
of
configurations
that
you
would
send
to
a
mesh
like
the
assertion,
the
the
verification
that
that
particular
operation
was
successful.
A
A
A
We
have
to
hussaina's
point.
We
have
little
to
no
idea
how
long
that
might
take.
It
shouldn't
be
less
than
five
minutes,
but
you
know
slower
connections.
It
might
take
longer
and
so
yeah.
So
anyway,
there
there's
potential
enhancements
to
do
it's.
I
think
pu,
you
demoed
both
responses
right,
you
demoed
the
timeout
response
and
what
the
ux
would
be,
and
then
you
demo
the
successful
response
as
well
right,
yeah.
Okay,
does
anyone
want
to
re-characterize
or
suggest
something
different
than
how
I
summarized.
H
E
It
actually
checks
like
if
your
cluster
is
ready
to
deploy
measuring
and
it
is
connected
and
all
of
all
kind
of
checks,
even
after
deploying
measuring.
If
you
want
to
check
that
your
system
is
fully
configured
or
not,
there
are
there's
like
there
are
two
or
three
checks
that
will
confirm
that
your
system
is
coming
like
completely
computer
adapters
are
connected,
measuring
is
connected
to
adapters.
Machine
is
connected
to
the
kubernetes
server
and
you
can
do
all
the
operations.
G
G
So
basically
like
right
now
we
have
a
proposal,
for
you
know,
making
huge
changes
in
the
machine
architecture
and
yeah,
so
you
can
actually
go
to
the
links
and
see.
What's
the
reason
behind
you
know,
we
are
actually
introducing
some
new
parts
into
measure.
Ui
such
as
redux
and
redux
tank
credits
observable
and
the
reason
for
why
we
are
doing
that
can
be
is
actually
explained
pretty
well
over
in
this
particular
spec.
G
So
I
can
actually
look
at
that
and
you
know
understand
why
and
also
yeah
currently,
as
a
part
of
that,
like
the
implementation
process
is
currently
going
on
and
it's
so
if
you
want
to
get
started
or
you
can
actually
go
to
the
branch
over
there,
that's
called
measure
your
restructuring,
the
results
we
have
that
link
in
the
dot
castle
and
in
the
readme
file.
You
can
it's.
G
It's
pretty
well
explained
as
to
how
you
can
get
started
with
contributing
to
this
particular
initiative
that
is
yeah
this
overall
of
architecture
and
measuring
ui
yep,
so
actually
like
yeah.
The
point
here
is
that
if
you
are
someone
who's
looking
to
contribute
to
ui
or
front-end,
it's
so
currently,
like
the
tech
stack
that
they're
using
is
that
is
also
listed
over
there,
but
yeah
it's
next
days
and
mostly
based
on
react.
G
Also,
we
have
a
implementation
tracker,
so
one
issue-
okay,
actually
like
these
are
the
so
one
part
of
that
implementation
is
to
you
know,
create
some
globally
reusable
components
that
we
can
actually
use
to
that.
We
can
actually
use
all
over
ui.
So
that's
basically
kind
of
like
a
component
library
for
measuring
ui,
so
yeah
that
that's
that's.
Basically,
the
kind
of
intention
behind
you
know
creating
globally
reusable
components.
G
We
would
actually
have
to
come
up
with
some
designs
and
if
you
are
someone
who
who
is
into
design
as
well,
then
also
yeah.
There's
a
lot
to
be
done
in
that
area
as
well,
so
yeah,
so
yeah
just
go,
go
over
the
code
base
and
see
how
things
are
being
implemented,
and
if
you,
if
you
think,
there's
something
that
we
can
improve
or
you
feel
different,
then
yeah.
Just
now,
let
let's
just
you,
know,
get
engaged
and
make
it
better.
A
G
So
right
now,
as
you
can
see,
like
most
of
the
components
are
being
taken
up
and
so
yeah.
We
are
actually
kind
of
waiting
on
the
designs
and
actually
like
there.
There
are
some
yeah.
There
are
some.
You
know:
implementation
like
back
and
integration
things
that
are
still
left
out,
but
we
are
actually
waiting
on
some
decisions
to
be
made
before
we
start
implementing
that
so
yeah
we
kind
of
hold
up
with
some
designs
right
now.
So
that's
that's.
Basically
the
situation
right
now,
but
nevertheless
there
are.
G
H
G
Yeah,
we
are
actually
using
it
if
you,
if
you
can
look
in
the
so
actually
like,
we
have
not
yet
started
writing
tests.
Okay,
that's
probably
something
that
we
can
yeah.
Okay,
that's
probably
something
that
we
can.
Actually
you
know,
keep
it
as
a
next
task.
We're
able
to
get
started
with
that
is
to
start
writing
tests
for
the
ui
components
that
we
have
already
written
yeah.
That's
actually
a
great
point.
I
don't
know
what
they
have.
H
B
H
It's
not
is
it,
you
know
any
kind
of
things
yeah
and
I
really
like
the
the
like
the
vision
of
these
libraries
or
this
ecosystem
of
react.
Testing
libraries
is
that
you
know
the
it
helps
you
test,
less
implementation,
details
and
more
external
of
how
your
component
works
at
the
user
perspective,
even
though
it's
at
the
component
level.
Yes,
I'm
sure
you
guys
are
a
little
bit.
Maybe
someone
else
not
all
is
not
stuff.
G
G
G
Yeah
actually,
regarding
that
regarding
types
so,
ideally
like,
we
should
be
using
typescript,
because
obviously
it's
a
lot
better
than
javascript.
That
there's
no
other
reason
for
that.
But
the
reason
why
we're
not
doing
it
right
now
is
so,
if
you
think
about
it
like
if
someone
who's
new
and
he
wants
to
contribute
to
measuring
ui,
there
are
a
lot
of
so,
let's
say
like
if,
if
he
comes
and
sees
mr
ui
architecture
or
dexter,
you
would
want
to
learn.
G
Yeah,
okay,
it
kind
of
it
already
kind
of
feels
intimidating
for
some
people
and
if
we
also
introduce
typescript.
Obviously
after
some
time
I
mean
like,
let's
say
obviously
like
we
would
be
there.
We
would
want
to
go
there
after
quite
some
time,
but
then
yeah
just
waiting
for
that
people
to
catch
up.
So.
B
G
G
G
H
H
A
I
H
I
A
If
you
would
have
started
with
those
from
the
very
beginning,
most
of
them
would
just
they
would
have
been
so
much
overhead.
It
would
have
been
ridiculous,
like
you
would
never
get
anywhere
because
you're
just
doing
process,
but
by
the
time
that
you've
got
so
and
that's
in
part,
why
there
will
probably
perpetually
be
a
theme
of
refac.
Some
component
somewhere
will
always
be
in
a
process
of
being
refactored
because
in
part,
because
of
that
so
but
gar
of
you're
up
next,
do
you
want
to
yes
you're?
I'm
sharing
my
screen
all
right.
K
Let
me
just
yeah
so,
like
most
of
us
know
that
this
pattern,
configurator,
is
used
for
configuring.
Our
patterns
based
on
the
service
and
application
that
we
have
so
the
library
we
are
using
over
here
is
the
rjsf
react,
json
schema
form
and
this
code
mirror
over
here.
So
I
have
made
a
couple
of
changes
in
this
ui
of
this
pattern.
Configurator.
So
previously
it
was
a
tab
component
that
was
overlapping
with
some
of
the
style
issues
and
all
so
I
re-enhanced
this
tab
with.
K
As
you
can
see,
and
next
item
is
a
call
for
volunteers
for
designing
and
asking
like,
as
he
said,
that
we
need
to
have
like
much
of
ux
stuff
needs
to
be
done
in
the
mystery
ui
after
the
refracting
is
done
or
parallely.
We
can
have
many
stuffs
and
I
guess
there
are
a
couple
of
issues
related
to
ux
and
designing
over
figma
and
the
machine.
K
Ui
components
are
also
open,
so
you
can
have
a
look
at
the
this
figma
file
is
of
the
machine
by
all
components
that
we
are
using,
and
I
guess
one
question
to
mario's
answer.
He
asked
me
yesterday
on
the
immersion
app
called
that
this
rjsf
component
that
we
are
using
in
this
mesh
map
also
so
mario.
This
is
the
component
that
I
was
talking
yesterday.
G
Okay,
you
gotta,
can
you
scroll
a
little
bit
yeah
sure
yeah?
Okay,
I
was
just
worried
about
like,
where
does
question
mark
go
like
in
replicas
another
thing
another
thing
is
like
so
so
this
looks
really
great.
Getting
the
icon
like
settings
right
in
front
that
depicts
like
what
is
we
are
doing
visually
too.
G
K
I
guess
we
don't
have
much,
so
let
me
move
to
the
next
item,
that
is
the
github
import
for
patterns.
So
let
me
give
a
brief
intro
about
what
we
have
currently
in
the
pattern
ui.
So
currently
we
have
the
functionality
of
uploading
patterns
locally
from
our
file
system
and
from
our
url
directly.
That
is
the
raw
url
from
service
mesh
pattern
repository
and
next
we
are
planning
to
have
a
github
import
facility
that
will
allow
the
user
to
import
multiple
patterns
with
a
single
click
using
this
github
import
approach.
K
K
I
have
discussed
this
thing
with
early
and
like
on
the
slack
that
why
to
have
this
two
different
kind
of
uploads,
a
url
or
github,
we
can
have
a
single
upload
that
will
can
have
that
will
have
one
url
and
the
all
this
github
id
path,
repository
and
branch
will
be
fetched
automatically
through
the
github.
What
and
all
the
credentials.
So
the
user
can
import
multiple
patterns
at
a
single
time.
K
A
So
we're
sort
of
kind
of
I
think
to
neticia's
point
is
that
gaurav
is
answering
true,
I
think,
with
respect
to
the
confines
of
patterns,
applications
and
filters,
but
then
sort
of
with
respect
to
maybe
the
rest
of
measuring
those.
You
know
the
the
like.
The
buttons
are
a
bit
there's
some
differences
and
they're,
probably
not
worth
fixing
in
6.0,
but
just
a
good
reminder
about
how
we
want
to
drive,
reuse
and
through
reuse.
A
A
A
G
On
we
have
my
topic
regarding
to
the
service
mesh
catalog,
so
to
give
context
here
so
we've
been,
it
has
been
an
upcoming
effort
to
create
a
service
mesh
catalog
where
people
would
be
able
to
download
or
copy
the
url
to
existing
patterns.
Last
time,
jared
had
suggested
to
include
a
download
button.
So
now
we
have
incorporated
a
download
option
to
download
your
yaml
files,
so
the
problem
that
was
going
on
here
was
we
were
not
being.
I
was
not
being
able
to
filter
these
patterns.
F
D
J
I
do
not
find
the
option
to
share
my
screen
all
right,
so
I
guess
there's
some
issue
but
yeah.
So
almost
all
of
the
labs
have
been
updated,
like
I've,
updated
the
instructions
and
screenshots
of
of
all
the
labs
like
and
console
and
istio
are
been
working
by
karin
and
branch
you
right
other
than
that
all
the
lab
instructions
and
the
screenshots
has
been
updated,
but
I
have
run
into
some
some
issues
regarding
the
instructions
and
commands
on
the
lab.
J
So
yeah
I
talked
to
lee
about
that,
also
in
the
slack
but
yeah.
I
could
not
find
any
solutions
for
that
too,
like
after
you
install
the
traffic
mesh
with
the
install
command
the
mesh,
and
when
you
go
to
the
ui
tab,
the
chip
for
traffic
mesh
does
not.
You
know,
light
up
and
it
says,
like
adapter
could
not
be
configured.
A
Naming,
maybe
maybe
not
but
it'd,
be
great
if
we
could
get
if,
if
a
single
person
on
the
call
might
volunteer
to
check
this
out
like
the
what
you'd
have
to
do
is
just
go
run.
This
lab
the
one
for
traffic
mesh
and
then
explore
the
kubernetes
environment
a
little
bit
to
understand
why
it
is
that
the
the
mesh
readapter
for
traffic
mesh
is
not
registering,
or
maybe
it
is
but
but
why
mesh
reservoir
is
not
able
to
talk
back
to
it.
So
there's
some.
A
E
J
J
A
They're
pro,
I
think,
it'll
look
like
I.
I
honestly
don't
remember
off
the
top
of
my
head,
like
it
does,
follow
that
same
process
as
a
service
mesh,
that's
how
it
works,
but
I
don't,
for
my
part,
I
don't
recall
like
where
they
have
their
injector
or
how
what
mechanism
they're
using
to
do
that.
I
can
tell
you
for
sure
that
the
lab
that
is
for
meshri
and
kuma
shouldn't
have
any
mention
of
console
in
it.
So,
like
yeah,
that
section
yeah
yeah.
J
J
J
E
A
Come
on
guys,
I'm
gonna,
be
I'm
gonna,
be
so
bold
as
to
say
what
a
beautiful
question
to
like
take
it.
Take
it
to
slack
yeah,
okay,
nice
who's,
saying
it
by
the
way.
Aditya
is
well
he's
just
asking
for
some
assistance,
but
but
he's
also
looking
to
have
a
few
more
labs
created,
so
so
mohit
or
rohit,
there's
like
if
you're
into
devops.
Those
labs
are
a
great
thing
to
work
on
you'll
learn
as
you
go
so
over
to
husseina.
F
F
We
pick
it
up
from
the
default
location
and
if
the
token
is
not
present,
so
we
used
to
throw
some
errors
saying
that
the
file
is
not
present
or
something
like
that
which
does
not
help
the
user
to
do
what
exactly
is
missing
kind
of
thing
so
right
now,
what
I
have
done
is
whenever
this
error,
wherever
this
error
is
thrown,
I
have
added
a
meaningful
error
in
that
one
needs
to
run
mystery.
Ctl
system
login.
If
the
token
is
not
found
and
then
retry
whatever
operation,
they
were
doing
so.
F
F
So-
and
I
have
also
refactored
some
code
here
in
the
add
auth
details
where
they
were
doing
a
read
file
and
then
unmarsh
link
to
get
the
token
and
all
that
it's
already
been
handled
in
the
read
token
function
initials
package.
So
I
am
directly
calling
read
token
here
in
the
add
earth
details
and
if
that
phase,
for
example,
let's
say
someone
called
machine
ctl
system
config
with
a
token
path
which
is
not
correct,
so
we
we
try
to
read
the
token
from
that
part
or
if
it
is
a
empty
file.
F
Also
users
can
just
try
that
right.
So
in
that
case,
if
it
fails,
we
will
check
whether
for
a
given
for
the
current
context,
if
there
is
any
token
already
present
right,
so
we
try
to
keep
that
up
so
line.
Number
50
is
about
that.
So
this
is
a
new
function
that
I
have
written
so
where
we
get
the
current
context
and
from
that
we
try
to
get
the
token
location,
I
mean
the
token
get
location
is
nothing
but
the
path
from
there.
We
try
to
read
the
token.
F
A
F
E
F
Yes,
yes,
yeah
actually
yeah,
that
was,
it
would
be
useless
if
it
eventually
comes
and
fails
right.
So
I
thought
through
this,
but
the
thing
is
that
the
common
code
in
system
config,
is
in
the
set
token
function,
so
I
I
I
could
try
to
move
it,
so
I
could
try
to
have
like
a
predict
check
before
we
call
any
of
this
aks
related,
I
mean
from
the
user,
for
aks
inputs
are
eks
inputs
right
like
what
is
you
want
to
create
the
config
now
and
all
that
right?
F
So
we
can
avoid
this.
Maybe
I
I'll
try
to
do
that.
I
mean
like
a
prereq
prerequisite
check
before
even
getting
into
any
of
this
user
input
right.
So
I
thought
I
mean
I
added
it
in
the
add
auth
details,
because
for
for
the
other
comments
it
would
be
only
add
or
details
right.
So
that
is
where
actually
you,
you
need
the
tokens,
so
I
thought
it
would
be
better
there,
but
we
could
have
one
more
period
check.
E
F
A
Yeah
nice,
I'm
just
trying
to
we
have
to
finish
off
that
thought.
Well,
it's
a
great
we're
at
time.
We've
got
a
few
items
that
weren't
quite
covered
today,
but
we'll
have
this
same
call
same
time
next
week.
We
also
will
continue
to
have
the
mesh
rebuild
and
release
call
every
other
thursday,
and
I
I'm
trying
to
remember
if
that's
this
coming,
there's
tomorrow,
oops,
that's
not
what
I
need
meet
dot
layer.
Five
that
I
have
so
today
is
the
fifth
okay.