►
From YouTube: Meshery Development Meeting (July 14th, 2021)
Description
Meshery Development Meeting - July 14th, 2021
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/
A
Welcome
everybody:
this
is
the
measuring
development
card.
Today
is
14th
july
and
we
are
phi
after
and
we
can
get
started
and
if
anita
is,
has
not
yet
joined,
we
can
move
the
announcement
a
bit
down,
and
I
don't
know
if
there
are
any
newcomers
on
this
call.
A
B
B
Meeting
in
this
particular
topic,
I'm
glad
to
be
here.
D
You're
on
the
the
website's
call,
if
you
would
just
refresh
those
that
haven't
gotten
well
or
tell
those
that
haven't
gotten
to
meet
you,
you
know
a
little
bit
about
yourself,
you
you!
What?
Where
are
you
calling
in
from?
What
are
you?
What
are
you.
B
Currently
doing
I'm
currently
in
my
third
year
in
college,
I've
I've
taken
up
interest
in
web
development
and
for
for
quite
some
time
actually
and
I've
come
a.
B
I
mean
it's
a
huge
subject
like
knowing
knowing
about
it.
It
takes
a
lot
a
lot
of
time,
but
I've
enjoyed
every
bit
and
I
just
hope
I
learn
I
get
to
learn
more.
I
I
know
I
will
get
to
learn
more
here
with
all
those
with
everyone.
Here
I
mean
it's,
it's
kind
of
overwhelming
for
me,
but
it's
it's
fun
to
be
here
as
well.
D
D
D
Just
joined
so
anand
welcome
and
surprise.
We
ask
every
newcomer
to
say,
hi
and
introduce
themselves.
Do
you
mind
just
saying
a
couple
words.
E
Hello,
hello,
yeah,
so
hi.
How
are
you
good
good
good
good
morning,
good
evening?
Where
are
you
calling
in
from
what.
D
E
D
D
Get
in
line
buddy,
I
don't
know,
no,
that's
actually.
Actually
that's
a
good
topic
to
say
is
that
I
don't
know
if
anyone
is
no
so
annonned
very
nice
to
talk
to
you
nice
to
meet
you,
but
also
on
that
subject.
I
don't
know
if
anyone
has
noticed,
but
we've
had
like
up
on
average
30
open
pull
requests
for
the
last
three
weeks
or
so
that's
that's
like
one
of
those
problems.
That's
a
really
nice
problem
to
have
kind
of
a
thing
like
awesome.
D
D
A
question
even
like
you
know,
provide
a
review
like
I
think
you
know
it
only
takes
thinking
about
this
for
about
two
seconds
and-
and
you
know
it's
pretty
much
universally
true
people
like
to
get
feedback
on
things
that
they've
done
like
it
feels
you
know
if
no
one
says
anything
it's
sort
of
like
well,
either
everyone's
extremely
busy
or
no
one
cares,
and
that's
not
the
case.
It's
it's
that
people
are
either
a
busy
or
not.
All
of
us
recognize
that
you
might
have
something
to
say.
D
D
Let's
see
how
many
we
can
open
and
merge
how
quickly
that
that's
the
right
metric,
I
think,
but
I
feel
knowing
that
occasionally
people
are
waiting
on
me
and
they're
waiting
on
a
litany
of
other
others
that
are
on
the
call
that
are
either
maintainers
or
other
regular
contributors.
D
D
A
My
thoughts,
anyone
else
who
is
new
on
this
call
and
would
like
to
introduce
themselves.
D
A
A
Sure
so
anita
had
an
announcement
which
was
like
we
have
many
different
meetings
in
the
layer,
5
community
and
if
you
head
on
to
me
dot,
therefore
dot
you
can
see
the
community
calendar
and,
as
you
can
see,
we
have
meetings
almost
every
day.
So
one
of
the
meetings
is
a
community
meeting
which
happens
on
fridays
so
and
anita
had
a.
A
A
call
for
participation
in
creating
this
week's
agenda,
so
there
is
a
topic
opened
on
discuss,
which
is
our
community
facing
forum,
so
you
can
discuss
on
that
to
set
up
a
meeting
a
meeting
agenda
for
this
friday.
A
I
don't
think
abhishek
has
joined
yet
he
is
having
some
network
issues
lee.
Would
you
like
to
talk
about
this.
D
Yeah
sure
I'll
jump
in
real,
quick
one
I'll
say
it's
nice
to
see
drew
like
dhruv
wow
wow
dhruv
is
the
only
other
brave
soul
to
have
his
webcam
on,
like
that's
so,
oh
so
home
joining
the
ranks
very
good
neck
and
neck,
so
I
mean
drove
there.
We
go
okay
so
anyway,
I
think
you
all
get
my
point,
which
is
it's
really
nice
to
see
people.
D
So
even
if
your
hair
isn't
done,
if
you
have
a
covid
cut,
if
you're
20
pounds
overweight,
like
I
am
from
from
last
year,
from
colvin
and
refrigerator
being
within
reach,
then
you
know
it's
fine
turn
your
webcams
on.
So
there
was
a
release
of
mesherie
that
was
done
just
45
minutes
an
hour.
You
know
45
minutes
ago,
abhishek
kumar
he's
a
main
maintainer
of
mashery
and
a
couple
of
the
other
projects
he
made
a
release
of
measuring.
D
I
think
the
thing
that
probably
and
so
yeah,
if
you
don't
mind
to
bring
up
the
yeah,
the
docs
the
release,
notes
real
quick.
This
release
the
the
the
release
prior
to
zero.
Five.
Thirty
seven
was
done
just
a
couple
of
days
ago.
So
this
one's
pretty
you're
pretty.
E
D
And
I
think,
and
as
I
go
to
mute
owner,
please
don't
take
offense,
but
if
you
do
have
something
to
say,
please
come
off
mute
anyway.
This
is
a
point
release.
I
think
the
thing
that
probably
propelled
it
forward
in
terms
of
making
the
release
today
well
in
large
part,
I
think
pu
sha,
maybe
novendi,
will
talk
about
some
things
that
are
happening
inside
of
mesherie's
command
line
client.
D
There
were
a
couple
of
key
fixes
that
needed
to
get
out
and
into
this
stable
release.
So
it's
good
we'll
also
see
some
things
from
jean
gene.
Tiston
she's
joined
us
any
number
of
times
from
the
philippines
and
has
been
doing
some
work
in
measuring
ui
some
popular
work
actually
so
we'll
we'll
see
that
in
the
stable
release
as
well,
it's
good.
D
By
the
way,
this
is
another
area
of,
like
I
think,
on,
measuring
this
particular
project.
I'm
not
sure
if
there
have
been
about
five
or
six
different
individuals
who
have
made
a
release.
I
think
there's
about
six
and
that
doesn't
need
to
be
the
case
like
making
the
act
of
making
the
release
is
really
simple:
it's
actually
a
button
click,
and
so
we
need
to.
We
need
other
other
people
to
do
such
a
thing.
D
A
Thank
you,
lee
yeah.
I
have
shared
all
the
details
in
the
chat
below,
so
you
can
join
the
community
meeting.
The
ci
meeting
that's
happening
tomorrow
and
it
can
be
found
in
the
community
calendar.
A
F
Yeah,
of
course,
hello
everyone.
This
is
my
first
time
in
this
meeting.
I
forgot
to
introduce
myself
I'm
a
third
year-
computer
science
undergraduate
based
in
delhi,
so
I
recently
started
contributing
to
mexico,
and
this
was
the
issue
that
I
saw
he
created
and
it
was
basically
to
add
just
an
token
location
inside
of
that
context
truck
while
we
are
printing
out
from
mystery,
ctl
system
context
view,
so
I'm
just
simply
sharing
a
screen.
F
A
F
Okay,
so
yeah
so
right
now
this
is
the
config.yaml.
So
we
have
the
tokens
here
and
the
context
here
so
right
now,
as
you
can
see
in
the
config.jml,
I
haven't
specified
the
token
for
the
default.
I
haven't
specified
the
default
token
inside
of
the
tube
inside.
So
if
I,
if
I
do
the
mystery
ctl
system
context
view
all
it
gives
out
a
warning
that
open
default
could
not
be
found
for
context
local,
so
the
format
is
simple.
It
just
says
the
token.
F
Then
token
name
could
not
be
found
for
context
in
the
context
name
and
here
for
the
context.
It
found
the
token
it
prints
out
the
token
location
and
for
the
politics
that
it
didn't
find
the
location
it
just
it
did.
It
does
not
so
now,
if
I
quickly,
if
I
just
if
I
log
in
and
create
open.
F
It's
flickering
for
me
too:
okay,
is
it
flickering
right
now,
yeah
still
is
still
flipping,
yeah.
Okay,
so
shall
I
stop
this
screenshot
and
then
do
it
again?
Okay,.
F
Is
it?
Is
it
visible
right
now,
I
think
we're
good.
Oh
yeah,
you
know
what
it's
tolerable,
okay!
Thank
you
so
now,
as
I
have
authenticated.
So
if
I
will
see
this
new
token
has
been
added
here,
the
default
token,
with
this
with
its
location.
So
if
I
do
ctl.
F
Now
there
is
some
other
warning
also,
for
example,
for
example.
If
I
comment
out
the
token
completely
and
now
I
run
the
mctl
system
context
view
now,
the
warning
wait.
I
actually
take.
F
Yeah
so
inside
of
here,
as
you
can
see
right
now,
I
have
my
both
the
tokens
for
both
the
context.
So
if
I
comment
out
the
default
token-
and
if
I
save
it-
and
I
do
now
this
time-
the
token
is
empty-
there
is
no
token
location,
of
course,
and
the
warning
differs
that
people
not
specified
empty
for
context
in
the
context
name.
So
there
are
two
different
warnings
for
two
different
use
cases,
and
that's
it
that
that's
all
I
added
in
that
issue.
F
The
issue
was
basically
to
print
out
the
token
location
it
was
like.
It
was
less
official
more
like
a
feature
you
want
to
want
to
display
to
enhance
the
context
view,
so
it
was
less
like
a
nation.
F
D
Makes
sense
yeah
well,
so
she
think
you
might
have
broken
a
record
so
not
not
to
give
you
a
big
ego
or
anything
but
like
at
first
you
weren't
going
to
do
it
like
hey
other
people
have
joined,
introduce
themselves
for
the
first
time
and
then
like
demo
to
pr
which
is
like
you
know,
not
typical,
which
is
you
know,
fan
you
know
fantastic,
but
then
you
know
you
had
to
take
it
a
little
bit
further.
D
You've
already
got
an
alias
set
up
for
measuring
ctl,
like
it's
like
you've,
been
here
for
three
months,
so.
F
D
Yeah
totally,
I
I'm
waiting
for
you
to
reduce
it
down
to
m.
I
mean
I
don't
know
what
I
don't
know,
what
we're
doing
with
those
other
three
letters,
but
that's.
D
It's
good
to
see
that
you
know
one
of
the
things
that
I'm
gonna,
that
that
you've
done
here,
and
that
is
good
for
others
to
digest
is
well,
is,
is
test
cases
and
ideally
done
in
the
form
of
unit
tests
or
integration
tests,
but
for
nothing
else,
just
test
cases,
so
ashish
has
is
demonstrating
a
great
practice
of
of
an
understanding
that
even
like,
if
you
consider
this
the
scope
of
the
ask
for
this
particular
pr,
it
is,
you
know
like
to
put
it
as
simply
as
possible,
it's
doing
nothing
other
than
just
reading
from
a
text
file
and
printing
out
some
info
from
that
text
file
and
while
that
sounds
extraordinarily
simple
and
like
there
couldn't
be
edge
cases
there.
D
No,
there
are
and
there's
more
than
you
know,
than
a
water
written
here,
and
so
they
almost
always
come
back
to
bite
you
in
the
butt
and
they
almost
like
bite
you
in
the
rear
end
immediately.
D
It's
like,
if
you
and
it's
all
the
common
stuff,
it's
stuff
like
well,
what
happens
if
you
gave
a
null
value?
For
that
token,
what
happens
if
the
token
is
malformed?
What
happens
is
if
you
give
two
tokens?
What
happens
if
the
token
is
expired,
what
oh
geez
and
then
and
then
you
just
the
list,
goes
on
like
what
happens
if
I
have
a
really
weird
name
for
the
token,
what
happens
if
I
don't
have
a
location
for
this
it
just
it
just
goes
on
so
ashish
like,
I
think
we're
going
to
be
friends.
G
A
A
So
inside
a
context,
why
do
we
have
to
specify
the
location
to
the
token.
A
D
Yeah
yeah,
maybe
I'll
regurgitate
it
just
so
that
you
know
well,
I'm
trying
to
think
of
a
different
way.
So
the
goal
of
the
issue,
the
issue
that
was
raised
is
really
in
acknowledgment
of
what
navendu
is
saying,
which
is
when
you
deal
with
a
when
you
deal
with
mesh
config,
which
is
the
the
name
that
we
use
to
refer
to.
D
Config.Yaml
you'll
find
if
you've
installed,
meshrectl
you'll
find
config.yaml
this
mesh
config
that
she
is
showing
you'll,
find
it
under
your
your
local,
user's,
hidden,
folder
or
hidden
folder.
Under
your
user's
home
directory
dot.
Meshery
is
the
name
of
the
folder
and
then
there's
a
config.yaml,
and
when
you
run
mastery
ctl,
oh
man.
D
V-Mesh,
when
you
run
measuring
ctl
system
context
view,
you
will
see
your
current
context
that
configuration
file
config.yaml,
it
may
very
well
have
more
than
one
context.
A
context
represents
a
meshery
deployment
you
might
deploy
measurey
to
aks
or
to
locally
on
kubernetes
or
locally
on
docker
or
and
just
like
you.
If
you've
used
cube,
ctl
the
command
line,
client
for
kubernetes
you
might
want
to,
you
might
have
different
kubernetes
environments.
D
You
want
to
connect
to
so
you
want
to
switch
between
them,
and
so
that's
what
these
contacts
are
like
provides
people
the
ability
to
switch
between
measuring
deployments
well
great
and
then
the
I
the
credentials
that
you
use
to
connect
to
each
of
those
different
measuring
deployments.
D
D
D
When
you,
the
ask
in
the
issue,
is
when
someone
runs,
this
command
mastery,
ctl
system
context
view
previously
and-
and
I
guess
currently,
since
this
pr
hasn't
merged.
What
you
would
be
seeing
is,
I
think,
just
the
name
of
the
token
and
that's
helpful
like
oh,
it's
using
the
default
token.
Oh
yeah
where's
that
default
token.
Again,
I
don't
know
what
command
do
I
run
to
figure
that
out?
D
Mastery
ctl
system
token
such
and
such,
but
the
ask
was
like
to
just
circumvent
part
of
the
need
to
run
a
separate
command
and
just
show
some
details
since,
since
that's
the
token
that's
being
used
for
this
context,
go
ahead
and
retrieve
the
additional
details
like
in
this
case,
it
would
be
location
and
spit
that
out
now
that
in
some
respects,
that's
like
a
user
experience
thing,
and
so
that's
you
know,
user
experience
items
are
almost
they're,
not
endlessly
debatable,
but
people
have
different
perspectives
and
so,
for
the
most
part,
we've
talked
about
this
any
number
of
times.
D
So
if
we're
going
to
consistently
show
all
the
details-
and
you
know
like
in
this
example-
we
should
consistently
do
that
elsewhere
and
there
are
enough
commands,
as
a
matter
of
fact,
we're
going
to
talk
about
two
new
emergent
commands,
and
I
just
mentioned
one,
which
would
be
a
third
one
is
token
one
is
a
sub
command
called
mesh.
Another
one
is.
D
Another
one
is
just
a
recap
of
the
perf
command:
they
all
have
sub
commands,
they
all
have
flags
and
they
all
have
parameters,
and
they
all
have
global
flags
and
like,
and
they
all
have
a
lot
of
the
same
verbs
and
like
so.
We
want
to
be
consistent
with
the
use
of
the
the
terms
that
we're
using,
so
we
can
help
people
feel
really
confident
when
they
execute
a
mastery,
ctl
command
that
when
they
said
apply
over
here,
that
apply
means
the
same
thing
over
here
as
an
example.
A
A
Anybody
else
have
any
other
comments
too.
Oh.
H
Yeah
I
do
like
oh
do.
We
need
to
specify
that
many
things
for
defining
a
token
like
in
in
cube
ctl
conflict.
They
basically
have
a
instead
of
defining
multiple
tokens
like
we
are
in
our
conflict.
They
define
multiple
users
and
they
only
have
one
field
called
token
in
which
either
it
will
have
the
name
of
the
file,
which
has
a
token
or
the
token
itself,
and
they
define
multiple
user
users
instead
of
name
of
multiple
difference.
H
D
Anybody
you
know
yeah
yeah,
yeah,
it's
a
good,
that's
it
put
a
pin
in
that
question
like
like.
We
should
circle
back
to
that
as
and
when
more
than
just
jots
are
supported,
like
you
know
so
right
now,
the
a
token
in
measuring,
like
the
only
way
to
authenticate
to
measure,
is
using
a
token
and.
D
I'm
I'm
saying
things
that
dhruv
already
knows,
but
but
that's
the
provider
and
there's
a
built-in
local
provider,
and
then
there
are
any
number
of
remote
providers
that
anyone
can
write
and
plug
into
meshary
and
those
remote
providers.
D
And
what
and
then
that's
unknowns
to
measuring
all
meshry
says
is
when
you're
done
identifying
this
user,
you
need
to
return
back
a
a
valid
jwt,
a
valid
jot
to
access
token,
and
that
and
so
currently
like
it's
that's
why
we
deal
with
tokens
and
not
users
and
it's,
but
it's
something
to
openly
reflect
on
like
right
now,
they're
you
know
I
would.
D
I
would
make
the
analogy
between.
I
would
say
that
tokens
are
too
messy,
as
users
are
to
kubernetes
like,
and
so
maybe
in
the
future.
We
need
to
have
a
higher
level
construct
like
a
user
in
mesheri
and
then
underneath
the
user.
There
would
be
tokens
and
certificates.
Another
thing
you
like
and
that's
why
I
say
to
maybe
put
a
pin
in
that
question
because
it's
we
should
come
back
to.
A
It
all
right,
thank
you,
drew,
and
so
anyway,
anyone
else
have
anything
to
add
comments
for
ashish.
A
A
Okay
hi,
so
we
had
it
on
last
saturday,
we
tested
out
a
lot
of
commands
and
we
found
some
of
the
like
some
of
the
major
bugs
that
were
related
to
mexico
version
and
the
issues
with
kubernetes
requirement,
even
when
the
platform
is
docker,
so
some
of
them
has
been
like
35
and
you
might
not
see
them
in
the
latest
release
that
was
made
today
and
if
you
was
not
able
to
like
contribute
in
this
meeting,
so
you
can
head
to
this
excel
and
check
out
the
commands
here
and
test
them
out
on
your
local
machine.
A
A
A
So
it
basically
has
some
actions
and
test
scenarios,
and
any
one
of
you
can
test
this
out
and
report
if
there
are
any
bugs.
So
this
is
in
relation
to
the
next
release,
which
is
happening
soon.
So
most
of
this
box
needs
to
be
fixed
before
that
and
for
measuring
ctl.
We
have
a
measuring
ctl
command
tracker,
which
basically
tracks
the
progress
of
each
commands.
A
So
if
there
are
any
any
cells
which
are
not
green,
then
that
is
an
area
that
needs
to
be
worked
upon.
So
there
are
a
lot
of
open
issues
in
the
machine
repo
regarding
this,
and
anyone
can
jump
in
and
fix
those
and
the
we
also
have
a
couple
of
issues
open
with
the
for
the
next
release
for
the
next
milestone-
and
these
are
also
some
of
these
are
not
yet
assigned
and
yeah.
A
You
can
work
on
it
and
I'll
share
the
links
in
the
chat,
yeah
anybody
else.
Anybody
have
any
questions
I'll
just
share
the
links
in
the
chat,
and
so
let's
move
on.
I
hope
abhishek
is
on
the
call
I
wish.
Would
you
like
to
talk
about
your
new?
Some
of
your
new
comments.
A
Yeah
yeah,
so
the
items
I've
been
working
on
today
was
two
commands
in
mystery
city.
One
is
perf
command
which
I'll
be
talking
about
first,
so,
as
we
all
know
that
we
have
a
command
called
mischievous
apply
which
which
currently
is
used
for
running
performance
test
with
measuring
cdo.
A
A
So
when
you
run
our
performance
as
a
performance
test
with
the
flag,
this
is
what
you
get
back
and
the
feature
that
I've
added
now
is
basically
to
run
a
performance
test
with
a
performance
profile,
a
performance
test
config,
and
this
config
is
basically
come
in
compatible
with
service
mesh
specification.
A
So
I
have
already
also
created
a
topic
on
discus
which
basically
has
a
sample
of
what
the
test
config
would
look
like.
So
this
is
exactly
what
I'm
using
currently
and
in
this
country.
As
you
can
see,
I
passed
in
the
test
profile
id
the
name
of
the
test
and
all
the
other
parameters
I
needed
for
running.
The
test,
like
the
number
of
connections
appears
and
what
are
the
list
of
endpoints.
I
need
to
hear
that
etcetera.
A
So
when
you
so
this,
basically
you
have
a
flag
called
hyphenated
file,
which
you
can
use
to
pass
in
a
test
conflict
and
run
a
performance
test,
and
currently
it
behaves
exactly
the
same
as
how
the
other
command
does.
So.
A
This
is
something
that
I've
added
I'll
wait
for
the
feedback
first
and
then
I'll
proceed
for
the
next
item.
D
If
it's
possible
to
let
the
user
know
the
either
the
id
of
the
result,
the
test
results,
so
they
can
go,
look
it
up
or
something.
A
Yes,
I
did
look
up
for
that
and
having
that
will
be
a
little
bit
of
complication,
because
the
result
id
is
being
generated
when,
after
the
after
we
push
the
result
to
the
provider,
so
we
need
a
stream
connection
in
order
to
get
the
result,
id
back,
which
will
be
asynchronous,
so
we
can
implement
it.
It's
just
not
a
single
step
process,
whatever
the
second
challenge
here
is
that
we
have
an
api
called
slash
api.
A
A
Basically,
the
issue
with
this
is
that
it
does
not
post
your
results
to
the
provider,
and
this
is
what
is
being
used
in
the
file
when
you
perform
a
do
a
performance
test
with
a
file.
This
is
the
api
is
what
is
being
used.
So
that
is
something
that
needs
to
be
looked
at.
The
next
like
after
this
feature,
so
just
an
example.
A
Cool
I'll
just
move
on
to
the
next
item.
In
that
case,.
D
If
a
user
is
going
to
do
this,
maybe
all
bets
are
off,
but
it
seems
to
me
that
you
know
for
for
an
earnest
user,
someone
who's.
You
know
pretty
serious
about
a
programmatic.
You
know
using
measuring
programmatically,
to
run
performance
tests
and
then
kind
of
examine
their
results
and
et
cetera
that
you
know
that
they
may
they're
most
likely
to
manage
the
performance
profiles
in
a
file
like
you're
just
showing
they
might
also
like.
D
They
might
also
run
multiple
slightly
tweaked
versions
of
that
same
performance
profile,
and
they
might
want
to
do
it
without
literally
without
having
a
second
profile.
D
Maybe
like
most
of
the
time,
people
are
going
to
just
create
another
profile
and
it'll
be
very
similar
to
the
first
one
and
they'll
they'll
change,
one
from
running
from
30
minutes
to
an
hour
or
or
whatever
they're
changing,
but
that
that
begs
the
question:
if
someone
provides
the
they
do,
mesh
ctl
perf
apply
dash
f.
They
give
the
file
if
they
also
give
a
another
argument
that
is
duplicative
of
details
found
in
the
file.
D
D
A
D
What
do
you
want
to
include
that
could
could
be
something
for
an
interested
volunt.
You
know
contributor,
like
a
good
way
for
someone
to
get
into
measuring.
Ctl
is
to
just
sort
of
add
that
kind
of
it's
kind
of
a
freebie
like
if
anyone's
paying
attention
it's
under
perf
apply.go
a
lot
like
line
70
3ish
somewhere
in
there.
A
A
All
right
so
so
yeah!
So
that's
I'll
move
on
to
my
next
item,
which
basically
involves
meshi
ctl
mesh
command
and
for
this
purpose,
and
I'm
just
starting
to
adapters,
to
connect
to
machine
so
that
we
can
do
some
operations
with
service
meshes.
So
what
measures
ctl
mesh
command
does
is
basically
manages
life
cycle
of
service
members
inside
a
cluster
with
a
clr.
I
A
Cool
so
I've
connected
a
nested
adapter
and
a
kuma
adapter
for
now,
for
this
demo
and
just
go
and
I'll
also
display
what
okay
cluster
is
or
in
fact.
A
So
I'm
going
to
use
mini
cube
as
quite
as
I'm
gonna
focus
later.
A
So
what
my
command
would
do
is
basically
I'll
I'll,
just
give
the
command
saying,
which
is
deploy
and
the
name
of
the
server
mesh
and
pass
in
the
token
as
well.
So
it
should
go.
Install
sql
in
my
cluster
and
I'll
just
wait
for
my
cluster
to
start
up
to
show
this
particular.
A
A
A
So
when
I
go
ahead
and
execute
this
command,
it
first
asks
me
which
adapter
to
use-
and
it
only
shows
me
the
option
for
hq
adapter,
because
I
specified
history
as
a
machine
and
right
now,
I'm
cancelling
this.
You
can
I'm
canceling
this
because
I'll,
I
need
to
show
one
more
flag
that
is
available,
which
is
international
adapter.
D
A
Yeah,
so
basically,
this
command
executes,
so
there's
an
issue
with
adapter,
probably
so
I'll
just
go
ahead
and
talk
about
the
command
first,
so
this
command,
basically,
what
it
does
is
it
installs,
whatever
the
service
mesh
that
you
specify
here
in
your
cluster
and
in
order
to
remove
it,
you
have
a
measuring
cdl
mesh
remove
command,
and
these
are
the
two
commands
that
are
available
right
now.
D
Yeah,
that's
fantastic,
and
I
I
hate
to
do
to
do
this.
I
just
I
want
to
urge
if
we
can
urgently
get
to
gibril
and
rudraksha's
github
action.
This
is
this
is
fantastic.
I
think
with
the
this
the
demo
that
you've,
given
you
know
like
it's
okay,
if
we
it
it
that
you
conveyed
the
concept
and
it's
good
and
people
that-
and
I
expect
some
people
do-
have
questions
as
to
what
else
mastery
ctl
mesh
might
do
in
the
future.
So
please
see
abhishek.
A
G
G
G
G
This
is
a
workflow
using
that
action
and
you
can
see
there
are
various
fields,
one
for
provider
token,
one
for
platform
to
deployment
screen,
one
specifying
respect
to
validate
in
case
we
land
in
future
to
expand
it
to
perform
other
tests
as
well-
and
this
is
where
we
specify
the
service
mesh
corresponding
fields
here
and
yeah.
Basically,
it
would
call
a
main.js
file
just
to
call
a
cell
script.
This
is
a
very
dirty
way,
but
a
better
way
to
avoid
javascript
and
typescript
dependencies.
G
G
In
turn,
in
turn
would
set
up
measuring
on
a
kx
cluster,
and
if
it's
not
present,
the
cluster
is
not
present
for
the
purpose
of
the
test,
it
could
create
one,
but
right
now
we
need
a
cluster
is
present
with
the
service
mesh
installed.
This
is
where
we
are
validating
the
token
and
all
stuff
related
to
deploying
misery
and.
G
This
is
where
the
sma
conformance
tests
happen
right
now.
This
is
hard
coded
to
depend
only
on
a
mini
cube
cluster
with
docker
drivers,
because
this
is
still
a
mvp
and
we'll
expand
to
other
clusters
and
providers
like
eks
aks
in
the
future
in
very
near
future.
I
suppose
also.
This
is
right
now
using
a
binary
that
I
released
on
my
own
with
mesh
validate
patched,
but
I
guess
now,
after
the
latest
release
and
my
pull
request
watch,
we
will
update
it
to
fetch
the
latest
binary
from
mystery.
G
Using
that
I
mean
we
don't
need
this
at
all
and
yeah.
So
basically,
this
is
where
all
the
stuff
happens-
and
this
is
a
sample
workflow
for
it
you're
using
a
action
to
deploy
a
mini,
cube
cluster
and
with
docker
driver,
because,
right
now
the
action
depends
on
it,
install
osm
on
that
cluster
and
then
performing
a
semi,
conformance
validation
on
this
mesh
validate
needs.
Another
thing
I'll
I'll,
just
show
a
run
of
the
action
to
demonstrate
it.
Basically,
this
is
the
run.
G
So
yeah,
this
is
the
run
of
the
action,
and
this
is
where
mesh
validate
happens
and
right
now
we
don't
have
a
way
to
I
mean
we
don't
tell
them.
If
the
test
completed
successfully
or
not,
it
would
be
once
a
mesh
validate,
has
some
sort
of
blocking
code
so
that
it
blocks
the
terminal
here
and
doesn't
let
it
proceed,
and
this
is
just
a
simple
check
that
this
is
not
a
part
of
the
action.
G
This
is
a
strip
sheet
that
I
created
to
see
if
proper,
namespaces
and
the
clusters
are
getting
deployed,
which
then
will
get
deployed
when
performing
a
smi
confirmation.
So
basically
this
was
it
now.
The
next
and
very
important
step
in
this
should
be
authenticating
with
the
token,
and
we
have
not
been
able
to
do
so
because
I'm
not
sure
if
I
can
use
that
token.
G
In
this
action
I
mean
I
generated
one.
I
generated
one
by
signing
into
twitter
on
my
local
system,
the
remote
provider,
but
when
I
try
to
use
this
token
here,
I
get
this
error
same
on
my
local
system,
and
I
have
created
a
thread
here
so
yeah.
Let's,
let's
discuss
it
there
and
save
time
on
this
call.
D
G
D
G
G
D
Taking
mental
notes
yeah,
I
don't
I
couldn't
we'll
have
to-
I
don't
know
by
the
way-
hey
just
for
everybody's,
like
that's
just
another
thing
to
call
out
since
there's
a
lot
of
us
on
the
call.
I
just
said.
I
don't
know.
D
D
D
Let
me
say
this
really
briefly,
because
I
want
to
highlight
the
work
that
jubril
and
rubrock
are
doing.
First
of
all,.
D
We
do-
maybe
maybe
you.
D
Person,
maybe
that'd
be
great,
so
thanks
for
that
redrock,
but
the
second.
So
so
I
guess
my
point
of
saying
that
is
like
hey.
If
you're
doing
things
here,
let's
go
talk
about
it.
I'd
love
to
like
you
can
go
talk
about
it
by
yourself.
Go
go
grab
one
of
the
slides
and
there's
a
bunch
of
slides
in
our
community
drive
vijay
just
made
a
deck.
Actually
two
other
people
just
made
a
deck
and
presented
them
on
monday's
filters.
D
Call
and
go
go
talk
about
them,
but
if
you
want
to
talk
about
them
at
a
conference
as
well-
and
you
want
help
writing
that
thing,
let's
you
know
writing
the
proposal.
Let's
do
that.
The
second
thing
I
wanted
to
call
out
here
is
the
importance
of
the
work
with
respect
to
service.
D
Well,
how
does
someone
know
if
a
service
mesh
has
implemented
according
to
the
specifications
like
there
need
to
be
conformance
test
validation
tests?
Well,
mesherie
is
the
tool
for
that
and
on
this
particular
site.
D
If
you
go
to
the
its
latest
blog,
you
would
see
that
mescheri
is
listed
there
and
so
what
okay,
and
so
what
jubril
and
are
creating
here
with
this
github
action,
is
a
way
of
empowering
not
only
each
of
the
service
mesh
service
meshes
those
projects
to
easily
integrate
mesher's
conformance
testing
into
their
build
pipelines,
because
they
can
take
that
github
action,
just
add
it
as
a
workflow,
and
then
they
can
start
self
validate,
self-validating
and
self-reporting.
D
So
it's
really
neat.
There's
a
new
smi
controller,
sdk,
that's
being
written,
and
I
know
some
of
this
is
confusing
for
some
of
you,
but
anyway
the
or
is
new
turf
for
some
of
you
and
anyway
point
is
this
particular
github
action?
Could
then
it
we
will
likely
create
a
template,
a
github
repository
template
that
goes
into
the
service
mesh
interface
project.
D
So
so
that
project
is,
you
know
close
to
mesheri,
so
there's
smi
and
by
the
way
on
this
topic,
I'm
gonna
send
a
link,
real,
quick
and
probably
we'll
go
get
this
published
somewhere,
but
smi
smp
service
mesh
performance
service,
mesh
interface.
These
are
two
specifications
they're
just
api
specifications.
Basically,
that's
technically
incorrect,
not
api,
but
what
are
anyway,
two
specifications
that
say:
here's
how
you
use
a
mesh,
here's,
how
you
manage
its
performance
and
then
mesherie
implements
both
of
them
and
it
provides
validation
for
smi.
D
At
some
point,
it
should
provide
validation
for
s
p
as
well,
and
so
hopefully
that
gives
context
as
to
what
the
tools
that
are
being
worked
on
are
doing
I'll,
send
a
link
to
a
horrifically
ugly
venn
diagram
that
shows
how
these
projects
overlap
and
that's
why
I'm
doing
this
because
there's
a
venn
diagram
that
shows
how
they
overlap.
So
with
that
redrock
and
gibral.
Thank
thank
you
guys.
We'll
get
this
token
thing
figured
out
so.
A
Yeah,
thank
you,
the
introduction,
thank
you
gibral.
We
are
there
time.
So
I
guess
we
will
keep
some
of
these
items
to
the
next
meeting.
So
before
we
go,
we
have
a
couple
of
call
for
participation,
one
of
which
is
a
measuring
ctl
unit
testing.
A
So
I
had
a
link
to
linkedin
chat
to
yeah
to
it's
an
epic
issue,
so
the
pew
is
just
looking
for
volunteers
to
participate
and
I
think
pierce
will
share
a
doc
in
slack.
That
explains
how
you
can
write
unit
test
and
we
also
have
a.
A
We
are
also
in
need
of
a
volunteer
to
move
the
faq
session
under
the
contributing
docs,
so
we
have
a
contributing
session
in
in
measuring.
So
if
you
are
looking
to
start
somewhere,
so
you
can
start
with
moving
this
faq
dock
under
the
contributing
session.
A
Okay,
then,
so
thank
you,
everyone
for
joining.
I
hope
I
will
see
you
on
friday
on
the
minute
call
or
next
week
for
newcomers.
We
have
a
newcomers
meeting
tomorrow
and
we
also
have
a
ci
working
group
meeting
so
check
out
the
community
calendar
for
that
and
thank
you
I'll.