►
From YouTube: Meshery Development Meeting (March 24th, 2021)
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
B
Yeah,
definitely
it's
yeah,
it's
exactly
the
same
as
it
is
in
america.
Yeah.
A
Okay,
good
good,
I
thought
for
a
minute.
People
were
going
to
be
thinking.
I
was
talking
about
something
else.
A
No
I'll
tell
all
right
very
good,
we're
about
about
four.
After
it's
about
time
to
get
going
couple
of
items,
one
it
is
and
to
use
my
my
least
british
accent,
it
is
lovely
to
see
people
on
webcams,
so
very
nice
to
see
very
nice.
To
literally
see
you
you
all
hey.
What
today
is
the
24th?
It's
a
home
day.
A
We
record
our
meeting
minutes.
We
post
them
on
youtube,
don't
say
anything!
You
wouldn't
want
your
mom
to
hear.
I
suppose,
if
you're
seeing
the
meeting
minutes,
the
venue
put
the
link
to
the
meeting
minutes
in
the
chat
so
jump
on
in
put
your
name
down.
A
If
you
don't
fair
warning,
we've
been
known
to
just
make
up
names
and
put
them
in
there
in
the
past,
so
you'll
get
a
nickname
quickly.
If
you
don't
now
is
also
the
right
time
to
lay
down
any
topics
that
you
might
have
questions
things
to
demo
work
in
progress
designs
to
cover,
what's
happening
with
the
release
that
just
went
out
last
night.
You
know
whatever
those
topics
are
put
just
put
them
at
the
the
bottom.
If
you
would
and.
A
Yep
and
today
we
have
a
lucky
winner
and
that
winner
is
sakshi.
A
If
this
is
your
first
time
on
this
call,
you
must
go
through
the
rite
of
passage
of
introducing
yourself
and
saying
hi,
it's
nice
to
have
you
and
do
you
want
to
tell
everybody
a
little
bit
about.
A
A
It
comes
in
two
tones
but
but
you're
forgiven,
you're
freedom,
which
and
by
the
way,
there's
a
lot
of
sarcasm
that
flows
around
the
community,
so
you'll
you'll
be
dishing
it
out
soon.
I'm
sure
nice
to
have
you
sakshi
and
by
the
way,
is
that
enunciation
of
your
first
name
anywhere
near
what
it's
supposed
to
be.
A
Because
now
would
be
a
good
time
to
train
my
tongue
on
how
to
say
that.
But
adida
will
correct
me
if
I'm
getting
it
wrong,
so
sure,
good,
okay,
enough
of
harassing
sakshi
nice
to
have
you.
We've
got
a
couple
of
topics
lined
up
today
and
so,
let's
dig
in
mr
kumar.
You
know
you're
you're.
First
at
bat,.
D
Sure
I'll
take
it
up
right,
so
I'll
be
showing
you
the
new
feature
that
got
released,
which
is
I'll,
give
you
an
overview
of
it.
Basically,
it's
it.
We've
designed
a
new
operator,
a
custom
kubernetes
operator
for
machine
which,
which
runs
a
couple
of
controllers,
to
keep
the
cluster
data
or
the
cluster,
stayed
in
sync
with
meshri.
D
D
I
already
have
gotten
stu
installed,
but
it's
fine.
So
this
is.
These
are
all
the
number
of
pods
that
are
available
in
my
cluster
right
now,
I'm
going
to
go
ahead
and
start
machinery
by
using
mishra's
heater,
so
it's
just
before
we
do
that
we
will
need
to
ensure
we
are
in
the
stable
channel.
D
We
kind
of
maintain
two
channels
which
are
stable
and
edge
edge
being
the
release
that
is
of
the
master
branch
and
stable
as
being
for
every
version
all
right,
so
we've
got
the
stable
version.
Now,
let's
start
measuring.
A
A
D
D
Yeah,
we
are
in
our
dashboard,
so
I'm
gonna
go:
go
ahead
quickly,
configure
my
queue
config,
so
it
says
config
variation
successfully,
and
now
we
have
this
right
side
panel,
which
which
displays
your
state
of
operator
that
that
can
be
manually
invoked
installed
and
uninstalled
like
it
can
be
controlled
manually.
D
But
the
default
behavior
is
that
when
meshri
gets
installed,
the
operator
gets
installed
automatically.
So
this
this
particular
page
is
the
control
plane
page
right
now
it
doesn't
show
anything
the
operator.
Currently
it
takes
a
bit
of
time
to
get
started
in
the
cluster.
So
let's
go
ahead
and
then
I
I've
I've
displayed
the
list
of
ports
to
ensure
that
we
can
like
basically
drive
real
time
the
state
of
the
operator,
if
it
as
and
when
it
gets
installed.
D
So
we
can
see
that
when
mastery
got
started,
I
did
not
click
anything
anywhere,
so
operate
got
installed
automatically
and
it's
installing
its
respective
custom
controllers.
So
right
now
we
have
two
custom
controllers,
which
are
a
broker
which
is
used
for
which
is
used
as
a
message.
D
Bus
between
for
transfer
of
messages
between
measuring
and
anything
that
is
that
is
inside
the
kubernetes
cluster
and
the
second
controller
is
nothing
but
a
mesh
sync
messaging
is
the
the
backbone
that
that
make
sure
that
the
cluster
state
is
in
sync
with
the
mesh
trees
in
sync,
with
the
machine
dashboard.
D
So
right
now
I've
got
my
operator
installed.
So
if
you
refresh
the
page,
it
will
show
you
the
status
of
the
operator
and
its
respective
controllers.
It
says
active,
active
and
the
name
of
the
other
version
of
each
and
every
component
that
has
been
update.
That
has
been
running.
D
So
if
we
come
to
the
dashboard
initially
there
were.
There
was
nothing
that
was
getting
displayed
in
here,
but
as
soon
as
the
operator
was
up,
it
shows
you
it.
It
automatically
detected
my
hto
parts
and
it
is
showing
me
the
list
of
histo
parts
in
here.
It
will
also,
basically,
if
I
had
some
linkade
or
comb
or
any
other
service,
meshes
parts,
it
would
list
them
as
well
in
a
separate
view.
D
I
can
come
back
to
that
later,
so
the
other
part
I
wanted
to
show
you
guys
was
let's
say,
for
example,
we
are
installing
a
couple
of
add-ons
for
this
view
right
now,
I'm
installing
rafana
and
from
this,
which
we
can
make
sure
that
the
parts
are
getting
created
here
so.
D
So
I'm
just
going
to
show
you
guys
that
if
mescheri
was
if,
if
measuring,
was
not
running
and
someone
installed
this
or
someone
deleted
these
pods
from
from
the
cluster
manually,
the
measuring
would
sink
state
with
that
as
well
and
before
we
move
to
that.
D
D
D
Does
it?
Oh?
Okay?
Yes,
I
think
I
just
removed
the
queue
config.
I
guess
that's
the
reason
the
raptors
got
detached.
Probably
so
I'm
just
I'm
gonna
go
ahead
and
do
system
start
or
probably
not
wait.
A
D
Yeah,
I
did
not
reconfigure
it,
so
basically,
this
is
the
thing
that
it
finds
from
a
default
path
and
it's
not
reachable.
D
Right
yeah
that
was
interesting
so
right
now
I'm
able
to
bring
your
adapter
and
yeah
I'm
getting
the
dashboard
here.
This
is
something
that
that
can
be
noted.
I
guess
one
of
the
issues
anyhow.
So
as
I
have
uploaded
the
new
config
again,
the
operator
got
installed
again
it's
getting
installed
again
and
now
what
I'm
gonna
do
is
I'm
gonna
manually
remove
this
graphana
with
the
manifest
that
way
that
we're
using?
So
that
would
be,
I
guess
so.
D
A
Okay,
but
the
the
add-on,
though,
by
the
way
your
microphone
went
out
like
a
couple
yeah
a
couple
of
minutes
back,
I
don't
know
if
it's
just
proximity
to
the
mic
or
what
but
the
do.
You
know
why
it
is
that,
so
you
were
able
to
install
grafana
through
the
customize
add-ons
switcher,
but
uninstalling
it.
No!
No.
D
A
D
E
A
Sorry,
actually,
your
mic
is
probably
like
part
of
the
question
is
whether
or
not
the
database
has
you
know
whether
or
not
mesh
sync
has
you
know
done
its
discovery
and
then
whether
or
not
the
database
is
up
to
date
and
then
whether
or
not
the
control
in
the
ui
is
yeah,
so
the
database.
D
Is
up
to
date
because
in
my
control
plane
it's
gone
like
when,
as
soon
as
I
deleted
the
funnel
it
went
away,
so
it
shows
only
promises
in
here,
which
means
this.
There
should
be
some
minor
bug
with
the
switches.
A
By
the
way
for
bart
and
vijay
and
austin
and
everyone
else,
but
but
particularly
those
that
are
focused
on
the
configuration
wizard,
this
sequence
that
abhishek
is
going
through
is
a
healthy
review
of
sort
of
the
the
sequence
of
dependencies
that
are
needed
to
complete
in
order
for
meshri
to
be
healthy
and
connected
to
things.
So
this
is
kind
of
a
nice
review.
D
D
D
Oh
sorry
for
that,
so
if
I
refresh-
and
this
is
basically
my
graphql
playground
in
which
I
can
write
some
queries
and
I
can
basically
get
output
of
it-
so
let's
say,
for
example,
I've
got
this
query
in
which
I
get
the
response
of
whatever
is
the
line
data
inside
the
cluster.
A
D
A
A
D
Uninstall,
ideally
because
yeah,
because
cubeconfig
does
not
get
rid
of
it,
the
machine
does
not
get
rid
of
the
queue
until
unless
the
page
is
refreshed
and
the
distance.
A
Makes
sense
good
from
a
user
experience.
This
is
okay,
good!
All
right!
Thanks
for
that,
I've
got
some
feedback
for
you.
A
G
Actually,
I
have
some
questions
so
in
main.gov
there
was.
There
was
some
logic
after
getting
the
from
this,
you
know
from
the
environment
variables
you
get
the
cube,
config
file,
then
you
get
the
context
and
then
you
so
all
that
has
been
replaced
right.
G
So
the
you
you
now
have
the
code,
that's
in
mesh
sync
that
you
have
something
like
attach
adapters
or
something
like
that,
and
so
that
has
been
taken
out
and
put
in
that
has
been
replaced
with
this
new
code.
D
No,
the
answer
is
no,
because
we
have
not
replaced
the
cube
conflict
flow.
Yet
we
just
we
just
replaced
the
way
it
discovers
elements
from
inside
the
cluster.
D
Basically,
whatever
the
resources
that
are
inside
the
cluster
has
been,
it's
been
brought
up
as
a
state
inside
our
database,
instead
of
actually
these
local
areas,
but
we
haven't
touched
with
the
kubernetes
or
q
conflict
flow.
Yet.
G
Okay,
this
one,
the
other
thing,
is
so
based
upon
what
the
what
the
config
file
is
in
that
that
cube
config
file
is
you're
you're.
Getting
the
service
mesh
adapters
right.
Is
that
correct?
I
mean
you're
getting
you're
getting
the
measuring
operator
right.
D
Based
on
what
yeah,
based
on
whatever
the
cube
config
that
has
been
configured
it,
it
basically
installs
the
operator
in
that
cluster.
G
Okay,
so
are
there
any
config
configuration
issues
for
the
measuring
operator?
The
machine
operator
is,
is
determined,
it's
confliction
or
existence,
or
whatever
it
is,
is,
is
determined
completely
by
the
cube
config
file
right,
is
it
true
or
not
you
say
is:
is
there
anything
that
you
can
is
any
any
such
thing
as
configuring?
G
An
machine
offered?
Is
this
such
a
thing.
D
Yes,
in
terms
of
confirming
their
controllers,
whatever
the
controllers
that
measury
operator
would
manage,
we
would
be
able
to
configure
them,
but
the
cube
config
is
just
used
when
you
wanted
to
use
when
you
wanted
to
install
the
operator-
and
it's
not
used
anywhere
else.
G
Okay,
that's
fine!
So
when
you,
when
you
say
that
you're
when
you're,
when
you
say
that
you're
configuring,
the
the
controllers,
what
what
exactly
are
you
doing?
Are
you
choosing
between
available
controllers
or
are
you?
Are
you
changing
the
settings
for
for
for
the
controllers
for
the
available
controllers
for
the
exact
right?
It's.
G
All
right
and
and
that
and
that
setting
determines
determines
what
machinery
adapters
are
are
are
discovered.
Is
that
true.
D
G
Okay,
so
when,
when
you
the
the
the
the
controllers
they
are
sinking
they're
sinking
measuring
with
kubernetes
right.
Is
that
true,
so.
D
G
Okay,
so
in
in
doing
that,
they're
they're
being
able
to
discover
what
is
available
on
kubernetes
is
that
is
that,
true
or
not
so,
in
order
to
connect
to
the
service
mesh,
you
you
have
to
have
these
service
mesh
adapters
right?
Is
it
true
or
no
okay,
so,
in
order
to
do
some
operations
in
them?
Yes,
okay!
So
how
are
these
service
mesh
adapters
being
discovered?
Is
it
through?
D
The
discovery
of
adapters
doesn't
actually
depend
on
it's.
It's
not
related
to
the
operator
flow
at
all.
It's
it's
done
by
the
machine
so,
like
basically
adapters
in
general,
are
discovered
by
misti
and
not.
D
Yeah
we
actually
pass
in
the
list
of
environment
variables,
listing
the
list
of
adapters
that
can
be
used
for
measuring.
A
Questions
pictures
always
really
help
me
help
me,
I
should
say,
and
in
slide
12
13
14
mostly
slide.
A
Is
this
one?
This
is
a
data
flow.
It's
like
if
mesh
sync
is
running
interrogating,
kubernetes
looking
at
looking
for
service
meshes,
what's
it,
how
is
it
funneling
that
data
back?
How
does
the
user?
That's
in
a
client,
a
visual
client?
How
is
it
you
know,
so
these
are
good.
This
gets
even
more
detailed,
probably
a
little
bit
of
cleanup
that
we
need,
but
this
was
mostly
us.
I
think
tracking
completion
of
the
effort
here,
but
so
the
deal
is
of
what
you
just
walked
through
by
the
way.
A
This
should
be
green
now
right
what
you
just
walked
through
abhishek,
but
it
seems
like
it
seems
like
we're
kind
of
missing
something
like
a.
I
don't
know
like
a
like
a
installer
like
a
step
through
thing.
You
know,
like
kind
of
like
a
configuration
wizard
or
something
really,
and
so
I
don't
know
well,
maybe
maybe
someday
so
what
what's
what's
next?
What's
our
next
topic.
A
Oh,
it's
the
configuration
wizard,
okay,
all
right,
yeah,
bad
bad
joke,
but
who?
Who
wants
to?
Who
wants
to
take
it
away?
Who
wants
to
talk
about
configuration
wizard
and
where?
Where
we're
at.
G
But
if
you
want
to
demonstrate
that
you
know.
B
That
you
have
yeah
I'll,
show
you
the
prototype.
Now
give
me
two.
B
B
So
this
is
where
we're
up
to
now
just
move
that,
so
this
will
be
the
measuring
home
screen.
Basically,
I've
we've
done
it
this
way,
because
I
don't
know,
maybe
there
is
a
better
way
of
doing
it.
But
when
I
was
running
the
development
server
server
and
mesherie
it
was,
the
reloading
was
really
slow.
So
I
thought
I'll
create
a
react
app
to
make.
B
So
this
will
the
icons
not
completely
decided
on
yet.
So
this
is
just
there
we
go
and
then
I've
got
a
little
pop
up
here
and
then
you
can
either
skip
it.
Don't
show
it
again
or
get
started.
B
And
then
you've
got
four
different
screens:
first,
one's
kubernetes.
Basically,
if
you
don't
connect
to
kubernetes,
you
can't
proceed
so
that
will
be
disabled
until
until
you've
connected
and
then
next
are
optional.
So
you
can
skip
through
them.
B
You
can
also
navigate
through
the
icons.
So
if
you
wanted
to
go
back,
you
could
go
there
or
if
you
wanted
to
go
here,
you
go
here
and
then
the
last
two
are
prometheus
and
grafana.
B
And
then
you
finish
so
that's
where
we're
up
to
suit
for
well,
that's
where
I'm
at
so
far
like
I
said
I
think
the
next
step
will
be
within
that
and
measure
itself
and
seeing
how
that
works.
G
Lee
can
I
see
a
few
things
here.
Please
go
ahead
and.
A
Do
you
have
any
oh
yeah,
the
there's
some
a
couple
of
minor
tweaks
in
the
you
know
the
visual
styling
that
I
think
that
bart
you're,
probably
you're,
already
aware
of
that
and
yeah
pulling
it
into
a
meshery,
will
is
a
great
next
step,
because
you
inevitably
something
will
get,
go
you'll,
learn
a
few
new
things
or
you
get
more
familiar
with
the
code
base.
A
Take
a
look
like
that's
fantastic
as
you
build
it
in
as
you
you
know,
like
start
to
put
that
into
the
master
ui,
you
might
end
up
wanting
to
open
up
a
an
early
pull
request
so
that
others
can
build
it,
compile
it
locally
and
build
it
and
sort
of
poke
at
it
and
kind
of
you
guys.
You
all
can
test
it
out.
As
you
go.
One
item
that
vj
will
be
working
on
is
like
what
what
are
the
actual
endpoints?
A
It,
I
think,
there's
I
think
largely
architecturally
or
like
largely
the
flow,
is
the
more
that
vijay
sinks
his
teeth
in
the
more
it's
just
congealing
like.
I
think
I
think
the
from
my
perspective.
I
don't
see
us
necessarily
deviating
that
much
from
what
we
have
currently
and
if
we
do
or
if
it
did
go
deeper
and
when
was
more
complex,
that
there's
always
v2
for
that
or
v3
for
there's
always
kind
of
a
you
can
bring
it
out
in
phases.
It
is
intentionally
simple
intentionally
constrained
in
functionality.
A
It's
not
powerful
one
of
the
things
that
I've
yet
to
see
in
the
yeah
drew
from
mastery
ui
one
of
the
things
I've
yet
to
see
in
the.
A
Mockups
is
well,
I
think,
a
couple
of
things
that
I've
yet
to
see
so
actually
austin
or
vijay
or
bart
anybody
who's
got
figma
up.
If
you
can
bring
up
the
mock-ups
a
couple
of
items
to
point
out
that
one
I've
yet
I
haven't,
I
don't
know
that
I've
seen
how
we
are
consistently,
where
we
have
the
area
that,
where
we're
gonna
have
confirmation
information
like
details
of
the
fact
that
kubernetes
is
connected,
here's
a
chip,
here's
some
server
name,
here's
a
version
number
or
whatever
that
details
are
so
then
the
next
step.
A
A
Okay,
this
is
an
unconnected
memory
operator.
If
you
keep
going
get
a
connected
measuring
operator,
so
we
got
details
over
there,
so
we're
getting
consistency
with
almost
consistency
with
where
we're
showing
the
details.
If
you
keep
going,
we
support,
you
know
10
different
service
meshes.
So
there's
no
design
here
for
how
something
would
scroll.
A
So
you
know
the
designs
look
incomplete
to
me.
Austin.
If
you
keep
going,
we've
also
got
confirmation
data
in
the
lower
half
of
this
card.
Well,
that's
I
guess
this
is
the
old
design
or-
and
this
is
going
away-
that's
confusing
though
austin
like
that
needs
cleaned
up.
If
you
keep
going
so
I
don't
see
where
the
confirmation
data
is
for
the
service
meshes,
so
that's
incomplete
as
well
in
the
so
grafana
here
this
looks
you
know,
incomplete
we've
got
it.
A
A
The
chip
for
all
of
you
that
are
unfamiliar
is
measure
uses
material
ui
as
its
design
system
and
there's
a
ui
component
called
a
chip,
and
it's
it's
the
oval
shaped
it's
the
horizontally
oval
shaped
button
that
we
were
seeing
kubernetes
in
in
habit
xdemo,
so
I
think
we're
behind
on
the
design
that
needs
to
improve
and
get
clarified
that
really
helps
drive
a
lot
of
clarity.
A
Vj
requests
you
to
use
this
for
the
like.
These
are
about
to
change,
so
the
screenshots
that
you've
exported
they're
they're
expired
as
of
30
seconds
ago
vijay.
One
of
the
things
we've
got
in
here
is
it's
great
that
we've
got
a
google
doc.
That's
perfect!
That's
the
normal
way.
We
would
do
a
design
spec.
We
also
captured
a
number
of
notes
in
here
about
particulars.
With
respect
to
each
step.
A
We
might
want
to
de-duplicate
that
and
maybe
just
extract
all
these
notes
either
finish
off
the
notes
and
define
all
the
behavior
here
or
extract
them
out
and
put
them
into
the
dock
either
way,
just
so
that
we're
quite
clear
that,
like
there's
one
place
that
describes
the
behavior
of
the
steps,
so
another
piece
of
feedback-
oh
yeah,
so
I
think
there's
one
I
mean
vj's
gonna
bring
up
a
few
different
questions,
but
but
one
of
those
maybe
open
questions
is
it.
This
is
a
four-step
thing.
A
It's
supposed
to
be
really
simple:
it's
not
supposed
to
let
you
do
advanced
things.
One
of
the
things
I've
yet
to
see
is
okay.
Well,
so
if
I
do
want
to
do
advanced
things,
where
do
I
do
that,
I
don't
see
any
links
to
the
advanced
there's,
no,
the
proverbial
advance
button
or
the
the
the
link
out
to
the
settings
page.
So
so
I've
talked
about
this
a
bunch
of
times
with
austin
austin.
I
still
don't
see
it
so
bart.
Let
me
let
me
talk
to
you.
Do.
A
For
barton,
yeah,
clearly
bart,
you
do
see
the
gear
in
the
upper
right
hand
corner,
but
next
to
the
well
to
the
bell
of
the
notification
center,
so
the
advanced
like
basically
the
answer
for
where
does
someone
go
to
do,
connect
potentially
multiple
kubernetes
systems
or
multiple
grafana
or
prometheus
systems?
A
Well,
first
of
all,
today
we
don't
support
that.
We
only
support
being
connected
to
what
I
say.
We
me
measuring.
It
only
supports
being
connected
to
one
instance
of
any
of
those
three
things
at
a
time.
So
one
graffana
one
prometheus
one
kubernetes,
that's
it.
We
want
to
change
that
very
soon,
even
when
we
do
change
that
this
is
supposed
to
be
the
simple
interface.
So
I
wouldn't
necessarily-
I
wouldn't
advocate
for
having
multiple
connections
here.
A
But
my
point
is
that
if
someone
does
need
to
have
multiple
connections
or
do
something
advanced
or
see
more
confirmation
details
than
they
are
here
that
that
gear
icon
in
the
upper
right
hand
corner
is
that's
the
settings
area
in
measuring.
That's
basically,
there's
it's
a
multi-tabbed
interface,
so
there's
a
tab
for
service.
You
know
we
would
want
to
just
point
them
to
the
specific
tab
with
a
an
anchor
tag
on
the
url
or
whatever.
It
is
okay,
good.
A
There
was
one
other
item,
and
that
is
for
me,
and
that
is:
is
there
a
step
zero
or
like?
Is
there?
Is
there
a
fifth
step
in
here?
I
I
don't
know
that
there
is
the.
If
there
was
so
vijay
is
openly
contemplating
this,
and
that
is
well
and
by
the
way
is
it
barthold,
sharing
or
yeah
bart?
If
you
end
up
going
back
to
your
to
step,
one
or
if
you
go
back
to
your
prototype
or
what
whatever.
A
A
A
Okay,
there
are
only
like
two
other
components
to
measure
that
they
would
need
to
be
concerned
with
one
of
the
components
is
the
meshri
operator
which
they're
going
to
deal
with
in
step
two,
so
okay,
so
that
eliminates
that
concern,
there's
only
one
other
measuring
component
for
them
to
be
concerned
with,
and
it's
the
adapters
and
the
question
is
really.
The
real
question
is
it's
kind
of
two
questions?
A
It's
like
do
you
have
an
adapter
or
multiple
adapters
running
you
know,
deployed,
can
mesh
reserver
talk
to
them
and
usually
that's
the
only
question
is
just
can
mesh
reserver
talk
to
those
the
vast
fast
vast,
vast,
vast
majority
of
time
will
be
that
mastery
server
can
talk
to
those
containers
like
the
way
that
meshi
gets
deployed
either
to
docker
as
a
platform
or
to
kubernetes
as
a
platform
is,
is
that
the
mastery
server
and
the
adapters
are
I'm
missing
the
right
word?
A
They
are
co,
they're
right
next
to
each
other
they're
on
the
same
network.
They
rarely
cannot
talk
to
each
other,
the
the
times
that
they
can't
talk
to
each
other.
A
That's
because
we
have
a
bad
design
with
respect
to
this
is
a
separate
note,
maybe
for
abhishek
or
husseina
or
novendu
or
or
all
of
you,
but,
and
that
is
that
there's
this
funky
dependency
that
the
adapters
have
on
having
a
healthy
kubernetes
connection
that
needs
to
stop,
and
that
needs
to
be
broken,
and
so
I
don't
know
how
many
of
you
kind
of
followed
all
that.
But
my
perspective
is
with
respect
to
step
zero.
A
We
don't
need
it
like
or
let's
go
prove
that
we
need
it
like
and
and
have
people
reporting
that
they
they're
unsuccessful
and
they
can't
be
because
otherwise,
the
majority
of
the
time
they're
going
to
be
successful,
they
can
get
the
message
server.
They
can
get
to
the
adapters.
A
G
Actually,
I
I
put
a
couple
of
notes
regarding
this.
Oh
whatever
it's
worth,
you
know
in
that
the
document
they
they
well,
I
mean
there's
some
minor
things.
You
know
like
like,
like
the
ships
of
the
at
the
top
you
you
use
it
for
use
for
navigation,
so
I
think
we
have
to
be
careful
there
because
you
know
there
are
precedence
requirements.
G
So
if
you
you
don't
get
things
like
going
forwards
and
going
backwards
and
whether
you
have
visited
a
particular
place
anyway.
Those
are
little
things
and
I
was
thinking
as
far
as
the
I'm,
not
at
all
a
ui
expert.
You
know
not
all
the
product
designer,
but
when
I
look
at
the
ui
it
is
everything.
Has
everything
been
shifted
to
the
left?
Did
we
have
a
space
or
too
much
space
on
the
right
and
we
had
the
information
below
below
that
icon?
G
That
shows
where
that
you
can
use
to
to
upload
the
say,
the
config
file
or
any
of
the
other
things
that
that
particular
thing
is
at
the
bottom,
and
I
feel
that
that
is
not
getting.
G
The
amount
of
you
know
prominence
because
you
know
that
should
be
the
first
thing
that
you
know
somebody
said:
hey
listen,
so
they
should
when
they
see
that
you
know
that
browse
button
or
something
like
that
they
should
get.
The
idea
looks
like
I
need
to
upload
something
out
here.
You
know
or
looks
like.
I
need
to
type
something
out
here
or
yeah.
G
I
mean,
like
I
said
you
know,
a
lot
of
these
things
are
dependent
upon.
I'm
sure
there
is
a
there
is
a
style
guide
for
for
measuring,
so
maybe
something
that
you
follow
there
and
it's
personal
taste
and
things
like
that.
But
I
have
a
few
thoughts
there.
B
On
no,
I
agree.
A
I
agree
as
well
right:
yeah,
yep,
hey,
it's
gotta
hit
you
on
the
head,
like
what's
the
point
of
the
configuration
wizard
to
help
me,
it's
like
to
make
people
successful
with
starting
to
like
starting
to
use
mystery
to
like
getting
to
the
point
where
they
can
really
use
the
the
power
of
what
it
was
designed
for
and
so
there'll
be
a
number
of
users.
That'll
be
like
they'll.
See
that
message
hey!
A
Do
you
want
to
use
the
con
config,
wizard
and
they're
like
no,
you
know,
skip
no
and
then
they're
going
off
and
doing
whatever,
but
there'll
be
many
others
that
are
like.
Oh
yeah.
I
should
probably
walk
through
that,
and
this
helps
me
and
to
vj's
point.
It
should
probably
smack
them
in
the
face
with
what
they're
supposed
to
do.
A
I
have
specific
thoughts,
but
I'll
withhold
them,
because
it
could
be
done.
A
number
of
a
lot
of
different
ways
to
vj's
point
like
and
the
way
that
it
should
be
done
is
like
in
in
context
of
meshri's
design,
language
like
in
context
of
its
design
system
and
and
the
paradigms
by
which
the
user
experience
has
been
created
and
defined.
A
We're
lacking
a
lot
of
that.
There
is
much
consistency
between
the
the
interactions
and
that's
just
been
enforced
as
the
community,
as
all
of
us
have
kind
of
created
it,
but
we
haven't
really
written
that
down,
and
so
actually
one
of
the
new
joiners
had
asked
about
the
ui
and
what
it's
all
made
of
and
how
you
know
how
it
works,
and
we
actually
don't
have
a
design
spec
called
measure
ui.
So
I
created
one
quickly.
I
don't
know
dave
yesterday
the
day
before
anyway.
A
I'll
point
it
out
to
each
of
you
because
it
needs
to
be
filled
in
and
part
of
filling
it
in
is
design
language.
I
mean
yeah,
so
I
should
say
like
we're
using
material
ui,
we
should
be
leaning
into
its
design
language
and
it
has
it,
and
it's
really
helped
us,
but
the
other
aspect
of
design
language.
What
I
mean
is
system
flow
is,
is
you
know
the
consistency
and
purpose
by
which
we're
using
a
given
react
component
like
if
we're
using
a
chip
that
we
were
just
talking
about
like?
A
A
A
A
Vijay.
I
agree
you're
right,
like
hey
you,
the
some
of
the
finer
points
need
to
be
called
out.
Like
should.
Are
people
going
to
be
expecting
to
see
confirmation
detail
why,
when
you
load
up
the
screen,
why
is
it
showing
on
the
left?
I
don't
know,
maybe
if
we
were
showing
you
a
preview
of
confirmation,
details
on
the
right
like
you'd,
be
okay
with
that,
because
it
would
feel
symmetric
to
you
then,
but
it
doesn't
if
the
yeah.
A
Maybe
if
you
don't
have
a
kubernetes
connection
and
that's
a
mandatory
step
and
you're
going
to
have
to
do
that
before
you
can
pass,
go
then
maybe
the
but
that
slider
the
expander
part.
Maybe
it
should
sort
of
slide
out,
and
maybe
there
should
be
a
little
like.
We
don't
have
this
in
our
design
language
today,
but
like
maybe
there's
a
little
bouncing
arrow
or
maybe
just
the
input
field
is
sort
of
pulsating
in
your
brain.
A
Like
you
know,
you
know,
like
the
just
a
super
thin
outline,
that's
just
sort
of
very
subtly
lights
up
or
something
I
don't
know
whatever
those
are,
but
to
vijay's
point
like
yeah.
It's
a
highly
curated
experience,
a
highly
guided
like
that.
There
are
guardrails
and
you
and
people
cannot
go
off
those
and
you're,
forcing
them
to
go
through
a
step,
sequentially
and
stuff,
and
so
as
such
yeah.
A
Forcing
them
to
do
particular
interactions
is
fine,
because
that's
what
we
want
them
to
do.
They
have
to
do
a
dd.
There's,
like
you,
know,
seven
whole
minutes
to
get
to
your
top.
There's,
probably
more
I'll,
try
to
I'll
be
responsive
to
the
comments
and
anyone
else
that
has
opinions
here
and
stuff.
Please
see
bart
and
austin
vijay.
G
A
A
And
and
then
adidas.
H
So,
the
last
few
days,
actually,
the
last
couple
of
days,
I
have
been
working
on
my
second
measuring
ctl
pr,
and
so
I
wanted
to
end
this
meeting
with
what
I
call
a
beginner's
look
into
measuring.
H
So
apart
from
the
documentation
peers,
the
first
ctl
pr
I
contributed
to
was
pretty
simple,
but
it
involved
adding
the
adapters
flag
to
context.
But
to
me
it
solved
like
a
significant
okay,
not
a
significant,
like
a
visible
pain
point,
a
visible
problem.
H
H
So
the
approach
involves
checking
if
the
version
adheres
to
a
specific,
regular
expression
which
was
formulated
based
on
past
release,
tags
or
it
could
be
latest,
and
this
involves
using
the
go
regexp
library,
along
with
the
stand
along
with
standard
go
as
as
used
in
measuring
ctl,
and
I'm
still
trying
to
figure
out
the
semantics
of
the
final
error
being
displayed.
And
I
will
try
to
demo
to
the
next
meeting.
If
I
can.
H
So
this
pr
process
included
like
a
lot
of
back
and
forth,
and
it
pulled
me
to
higher
standards
with
just
10
lines
of
code
and
and
of
course
it
was
due
to
the
senior
community
members
who
helped
me
a
lot
with
it
like
seriously
a
lot
and
initially
my
errors
included
some
rather
obvious
oversight,
such
as
misreading,
suggestions
for
naming
conventions
and
I'm
still
figuring
out,
and
I'm
still
ironing
out
a
bug
in
my
code
with
the
by
figuring
out
some
details
for
the
regex
regex
library
and
go,
and
all
of
this
in
one
pr
was
very
enlightening
for
a
beginner.
H
If
there's
a
pull
request
open
currently,
if
y'all
have
anything
to
say
about
it.
After
reviewing,
that
would
be
helpful.
Thank.
F
F
A
Today,
I
don't
know
that
we
do,
I
think,
that's
about
it.
The
adidas,
that's
fantastic.
I
heard
all
of
what
you
had
said
as
well.
It
takes
two
to
tango
or
hey
it's
not
it's.
Not
all
hussain
is
pretty
good,
but
it's
not
all
on
her
you're
you're
you're,
bringing
in
two.
So
I
was
just
chatting
with
some
of
the
maintainers
about
your
activities.
So
I'm
very
nice
to
see
you
presenting
some
of
those
there's.
You
know.
A
Maybe
the
last
thought
for
for
on
measuring
ctl
is
well
that
the
dot
the
the
measuring
release
just
went
out
so
so
we're
into
v060
and
it's
a
healthy
time
to
go.
Take
a
look
at
the
roadmap.md,
the
it's
in
the
mesherie
repos
root!
Folder,
it
outlines
what
we
think
you
know
are
the
features
and
functions
to
go
into
both
mesherie
upcoming
and
mesh
ctl
upcoming
as
well,
so
so
design
specs
are
in
our
future.
I
think
all
right.
A
Yeah,
okay,
who's
saying
it
yeah.
Do
you
have
anything
else
by
chance.
A
Got
you
okay,
yeah,
oh
yep,
yeah
yep.
I
did
see
that
or
I
saw
the
fact
that
you
would
put
something,
but
I
didn't
get
a
chance
to
read
it
in
part,
because
what
I
was
trying
to
say
before
is
really
true
is
like
it's
a
great
suggestion.
It's
distracting
from
trying
to
get
the
kubernetes
platform
done.
A
F
A
Yeah
hussein,
that's
a
great
point
I'll
leave
that
thought
in
your
capable
hands
with
adidi.
Okay.
I
think
I
think
you
could
I'll
let
you
make
that
call.
C
A
Yeah
now
the
one
of
the
things
that
that
I
don't
know
that
all
of
you
have
realized
about
adding
those
particular
flags.
That's
quite
helpful,
like
really
important,
is,
is
when
people
want
to
script
around
meshri
ctl
people
can
script
around
or
integrate
with
meshri
through
the
rest
api
that
meshrey
ctl
as
a
client
uses.
A
That's
just
harder,
like
people
have
to
write
code,
then
it's
a
lot
easier
for
the
majority
of
the
rest
of
us
to
just
write
a
bash
script
or
write
a
couple
of
command
statements
about
that
use.
Mastery,
ctl,
and
so,
but
if
there's
human
interaction
interactive
prompts
that
happen,
then
that
messes
up
those
scripts
or
can
get
in
the
way
of
those
scripts
so
having
a
silent
flag
or
a
force
or
whatever
you
guys
ended
up,
I'm
creating
those
really
help.
A
So,
as
a
matter
of
fact,
microsoft,
the
the
topic
that
we're
not
going
to
get
to
today
is
drew
was
going
to
give
an
update
on
smi
and
microsoft
is
asking
to
engage
with
mesheri
and
they
want
to
take
on
some
of
the
work
or
not
they
want
to.
They
want
to
use
measuring
and
we're
going
to
suggest
that
they
use
meshri
in
a
programmatic
way
and
and
actually
using
mastery
ctl.
It
would
be
mestre
ctl
mesh
validate.
A
So
we
need
to
make
sure
that
that's
that
particular
experimental
command
gets
some
focus
soon.
A
So
we'll
I'll
message
about
that
in
slack.
What
what
that
command
is
on
drew's
on
so
yeah
drew
hussaina
and
adidi
are
here
that
command
runs
smi
conformance
tests,
it's
good
a
good
time
for
you
to
begin
to
work
with
these
folks
on
advancing
that
command,
because
it's
been,
it
was
only
done
experimentally
and
it's
going
to
need
some
help.
Things
have
changed.
A
Very
good
all
right.
We
started
three
minutes
after
we're
ending
three
minutes
after
it's
nice
work
on
the
config
wizard,
it's
nice
to
see
it's
good
to
see
some
stuff,
austin
you're
behind
you
will
catch
up,
no
doubt
and
then
yeah
bart
can't
wait
to
see
the
stuff
merged
into
you
know
the
prototype
going
into
it's
good.
It's
good!