►
From YouTube: Meshery Build & Release Meeting (January 27th, 2022)
Description
Meeting agenda:
[Lee] Review of last meeting minutes.
Local Kubernetes Cluster troubleshooting learnings:
Quick start - https://docs.meshery.io/installation/quick-start
Suggest simplest setup for beginners somewhere? (Docker desktop Kubernetes)
Be short & dry in our documentation: “links everywhere” to avoid over-explaining 3rd party setup, unless absolutely necessary.
Add link to https://docs.meshery.io/guides/troubleshooting/installation in https://docs.meshery.io/installation/quick-start
[] Meshery Test Plan
[Aaditya] Meshery Compatibility Matrix
[Hersh] GitHub Action for Patterns
Need to evaluate the ongoing need for this Action.
[Mario] Updates on Cypress tests
A
All
right,
let's
get
rolling,
hey,
welcome
everybody!
It's
january,
27th
thursday,
it's
12
p.m.
If
you're
in
central
time
zone,
which
mario
is
steven's
with
us
he's
an
hour
later,
steven
always
feels
a
little
bit
ahead
of
the
game.
I
wonder
why
that
is,
but
aditya
is
here
and
so
deepa
young.
So
we've
got
a
number
of
things
to
cover.
A
It's
been
a
while,
since
we've
met,
I
think
all
of
you
have
been
on
the
call
before
there
might
be
a
couple
of
more
joining
in
part
because
it's
been
a
while
since
we've
met.
We
should
take
a
moment
to
review
where
we've
been
like
take
a
moment
to
review.
If
we
didn't
have
some
action
items
from
the
last
few
meetings.
A
So,
let's
do
that
I'll
drop
my
name
in
here,
so
there
were
last
time
we.
It
was
actually
a
great
use
of
the
time.
Mario,
I
think,
if
I
recall
mario,
was
running
through
some
notes
on
a
local
deployment
of
measuring
under
different
circumstances.
You
know
kind
of
using
kind
or
using
mini
cube
and
then
exposing
services
and
kind
of
load
balance.
B
So
so
yeah,
maybe
like
the
in
maybe
the
yeah
just
suggest
a
simple
setup
and
in
case
there's
other
kind
of
setups
just
like.
Maybe
we
should
try
not
to
document
everything,
because
because
we're
kind
of
like
adding
more
things,
we
need
to
keep
updated
instead,
like
just
well
maybe
reference
people
to
how
to
like
other
links
where
those
steps
are
described.
But
just
maybe.
A
Yeah,
no
yeah
actually
there's
something
that
some
of
the
some
contributors
have
had
a
little
bit
of
a
difficult
time,
drawing
a
line
on
in
the
past
of
like
hey,
we
might
say,
use
if
you're
on
windows
use
wsl
too,
and
then
some
contributors
will
want
to
describe
wsl
too
and
how
to
install
how
to
turn
it
on
it's
like
wait,
wait!
Wait.
We
should
just
put
a
link
to
like
you
know.
A
We
need
to
have
it
kind
of
like
the
dry
acronym.
We
need
to
have
another
like
put
a
pet.
You
know,
keep
dry,
do
some
padding
so,
but
just
to
reflect
on
your
experience
and
the
notion
that,
like
if,
if
the
quick
start
guide
is
draws,
it's
kind
of
you
know
called
out
onto
its
own
as
a
single
page
that
there's
probably
a
lot
of
links
pointing
to
it
to
say
this
is
how
to
quickly
get
going.
A
A
Right
that,
but
that
guide
was
entitled.
Troubleshooting
measuring
installations,
which
seems
highly
relevant,
seems
like
exactly
what
you
were
saying
is
like
hey.
If
there's
common
snafu,
you
know
common
pitfalls,
we
should
probably
list
those
and,
to
the
extent
that
there's
many
at
least
having
a
link
to
this
page
from
the
quick
start
just
makes
a
lot
of
sense.
To
me.
C
A
A
Plan
is
an
understanding
of
our
test
strategy,
and
actually
stephen
in
the
past
has
helped
provide
templated
test
plans
spreadsheets
in
the
way
that
you
attract
these
the
different,
the
way
that
you
account
for
your
different,
your
actors
and
your
systems,
the
desired
outcome,
the
actual
outcome,
all
these
things,
those
were
those
are
helpful.
Those
those
are
reflected
to
a
certain
degree
in
the
test
plan
and
the
way
that
the
test
plan
spreadsheet
is
kind
of
laid
out.
There's
a
some
of
those
same
columns.
What
component
is
under
test?
A
A
A
What's
the
current
state
of
what's
the
historical
state
of
tests
that
were
run
on
this
current
on
the
stable
release?
What's
the
current
state
of
tests
that
have
like
just
been
run
on
the
edge
release,
because
the
edge
release
is
really
like
it's
happening,
or
it's
happening
all
the
time
for
different
components,.
D
Yeah,
so
not
much
change
since
yesterday,
although
I
was
trying
to
you,
know,
apply
the
date
filter
like
for
sorting
which
you
which
you
suggested,
but
I
don't
think
that
would
be
possible.
I
tried
many
many
ways
and
finally
found
we
have
to
create
a
plugins,
but
after
creating
a
plug-in
student,
exactly
the
sort
did
not
happen
as
expected.
So
I
think
we
have
to
change
the
date
thing
in
the
actual
integration
test.
Only
okay.
A
A
D
A
C
A
D
A
A
A
A
So
maybe
hirsch
will
watch
this
later,
so
I'll.
Explain
that
a
little
bit
more
to
say
that,
like
if
we
were
to
take
a
common
pattern
like
a
pattern
that
might
describe
the
istio's
sample
app
book
info
and
its
configuration,
which
would
include
a
virtual
service
destination
rules
like
a
deeper
configuration
of
istio
and
then
since
we're
also
able
to
generate
load
and
run
a
performance
test
in
that
same
workflow.
In
that
same
github
workflow,
we
can
then
also
say
not
only
did
eco
istio's
components
deploy
so
did
it
so
did
an
application.
A
A
A
A
There's
a
third
one
or
another
one
proposed,
and
it's
a
github
action
for
service
mesh
patterns,
the
github
action.
The
reason
that
we
would
need
like
three
for
measuring
is
is
really
just
all
about
convenience.
It's,
like
is
the
user,
trying
to
verify
performance
of
their
workload
each
time
that
they're
making
a
new
release
of
their
their
app
great.
Then
then,
there's
a
curated
and
opinionated
github
action
for
doing
a
performance
test
is
the
user?
Are
they
trying
to?
B
A
The
workflow
here
this
file
is
called
workflows,
ete,
tests.camo,
so,
okay,
so
it
it
kicks
off
when,
when
people
open
a
pull
request
or
merge
to
master
set
pattern
file
for
service
mesh
install,
so
it
seems
like
it
might
be
using
mastery
ctl's
pattern
file,
so
so
there
it
does
use
this.
It
does
deploy
using
this
pattern.
File.
B
A
C
A
Cool,
so
the
so.
This
is
sorry.
This
is
kind
of
what
I
was
looking
for.
I
think
there's
a
lot
of
good
stuff
in
here
actually,
but
in
some
respects,
if
we
are
evaluating
whether
or
not
we
need
another
github
action
for
patterns,
specifically,
here's
an
exam,
an
example
of
how
someone
can
do
this
today-
okay
yeah-
I
don't
know-
maybe
that
get
up
action-
isn't
the
best
suggestion,
because
it's
such
a
short.
A
B
A
B
B
B
A
A
A
D
A
A
A
B
But
I
I
to
be
honest:
I
gave
a
bit
more
priority
to
like
getting
the
what's
it
called
and
the
the
adapter
setup.
You
know
it
was
failing,
so
I
was
really
like
worried.
It
could
be
like
that,
there's
an
actual
bug
in
there,
but
I'm
not
sure
if
we
can
go
to
the
issue
itself.
I
think
that
abby
suggested
to
just
like
try
with
a
simpler
pattern
file,
but
I
don't
know
it
was
some
of
the.
B
B
B
But
I
did
follow
the
like
updating
the
the
gold
version
it
was
causing
issues
during
the
liking,
there's
a
prior
step
in
there
to
to
just
start
the
adapter
right
and
now
it's
not
throwing
that
mesh
kit
error.
But
I
don't
know
since
the
problem
here.
Well,
maybe
not
the
problem.
The
difference
is
here
we're
starting
from
source.
B
B
I
know
we
need
to
do
this.
We
just
need
to
pass
a
flag,
so
that
measuring
knows
it's
there.
I
think,
because
yeah
or
well,
I
would
need
to
debug
this
locally
and
see
if,
like
there's
something
else
causing
the
500
again
the
file
I
took
for
those
pattern
and
application
deployments.
It's
it's
just
the
latest
from
the
examples
that
were
suggested
on
the
issue
so
and.
A
A
B
B
A
A
A
A
A
B
A
See
slightly
the
when
measuring
when
a
mesh
adapter
spins
up
it
will
attempt
to
connect
to
mesh
your
server
and
if
the
server
isn't
available,
then
it
will
skip
a
beat
it'll
back
off
and
say:
oh,
you
know
it'll
it'll.
I
think
it's
for
a
period
of
it
used
to
be
10
minutes.
I
think
we
set
it
to
30,
but
for
a
period
like
some
10
to
30
minutes
it
will
back
off
and
retry.
It
doesn't
sit
there
and
do
it
like
it
backs
off
and
retries.
A
A
It'll
it
right
like
actually
I
mean
yeah,
it's
actually
a
good
like
it's
kind
of
a
good,
a
good
proof
point.
If
I
were
to
kill
this
so
let's
say
I
so
I
killed
I'm
killing
mescheri's
server.
My
shoe
server
is
now
dead
and
then
here's
my
messagery
istio
instance
that
I
ran
it.
It
had
connected,
and
now
it's
it's
just
running
by
itself.
It's
that's
interesting.
Actually,
let's
do
two
tests,
so
the
first
one
is,
let's
just
run
the
adapter
and
it
spins
up
here
in
a
minute.
You
know
it
compiles.
A
B
A
By
the
way,
it
might
be
the
case
that
that,
like
while
that
is
technically
true,
that
those
two
commands
are
different,
it
might
be
the
case
that
the
make
run
itself
of
of
the
actual
command
executed.
That's
it
so
here
here's
the
command,
that's
executed,
is
it
turns
on
debug
or
it
sets
a
couple
of
environment
variables.
Debug
the
true
go
proxy
to
direct,
go
some
dbr.
Then
it
then
here's
the
command
that
actually
runs
or
the
just
go
run
main
go.
B
A
B
A
It's
configured
so
here
is
so.
I
just
ran
the
istio
adapter
again,
so
it's
the
adapter.
Oh
there's
another
misspelling
anyway,
the
adapter
is
listening
on
port
10000.
It
is
attempting
to.
It
is
attempting
to
register
the
latest
components,
attempting
to
register
static
workloads,
components
available
statically
for
this
version
already
like
it
already
knows
how
to
talk
to
the
latest
version
of
istio.
A
A
A
Came
back
so
so,
like
yeah.
If
the
timing
is
slightly
off,
it
shouldn't
be
an
issue
okay,
and
so
now
we
wanted
to
verify
that,
let's
just
to
take
a
quick
look
at
the
state
of
my
local
cluster,
so
I'm
running
docker
desktop,
so
I've
got
a
linker
d
instance,
that's
failing,
but
other
than
that,
it's
just
the
meshri
operator
and
a
blank
kubernetes.
A
So
we
said
that
we
want
to
verify
that
our
pattern
file
of
choice
is
working
so
we'll
upload
a
pattern
put
it
downloads
book
info
pattern
commit
okay,
so
we've
got
book
info
pattern
and
we're
just
gonna
okay.
So
assuming
that
it's
all
good
to
go,
you
know
like
the
next
action
that
you're
taking
inside
the
workflow
is
just
to
deploy
so
we'll
just
we'll
just
hit
deploy
here.
A
A
A
A
A
Adding
examples
in
swagger
docs
this
helps
document
this
set
of
apis,
because,
because
normally
what
I,
what
I
would
everyone
should
be
able
to
immediately
do
is
say
that
if
you
do
want
to
go,
interrogate
mesher's
apis,
you'd
go
to
mesh
redox
you'd
go
to
one
place
would
be
these
references,
this
reference
guide.
So
this
is
the
rest,
the
documentation
for
the
rest
apis.
A
If
I
wanted
to
look
at
those
workloads
that
have
been
registered,
then
I
should
be
able
to
get
them
and
the
what
I
was
asking
for
is
better
example
calls
that
people
can
make.
This
is
actually
really
helpful.
I
think
for
well
for
a
lot
of
people,
a
lot
of
folks
that
but
mario
and
specific,
like
hey
okay.
So
if
I
go
to
slash
api,
slash
home
and
then
I
put
a
type
it
might
so
that
either
being
a
workload.
A
B
A
A
B
C
A
A
A
A
It's
already
coming
in
right,
so
we
should
be
able
to
go,
build
the
app
ourselves
and
when
I
go
to
edit
it,
the
ui
starts
to
crunch
I'm
guessing
what's
happening
here.
Is
it's
trying
to
it's
trying
to
grab
all
the
all
the
workloads,
all
the
definition
of
all
the
workloads
and
that's
probably
causing
it
to
crash.
B
A
B
A
There
is
a
ui
bug
here
where
this
applications
interface
is
supposed
to.
Let
you
configure
your
app
just
like
you
would
configure
your
pattern.
It
is,
I
think,
it's
it's
killing
itself,
like
it's
probably
trying
to
load
up
all
the
json
descriptions
for
how
to
configure
istio,
and
it's
probably
it's
just.
B
A
A
A
Now,
okay,
so
here's
some
so
the
the
like
this.
I
have
no
idea
what's
inside
this,
okay,
oh
no
here
it
is.
This
is
another
example.
This
is
probably
the
same
sample.
This
is
probably
the
same
pattern
file
as
the
one
that
we're
getting
the
500
on
for
istio
gateway.
If
I
take
and
try
to
deploy
it
from
here.
B
A
A
And
it's
basically,
I
think
it's
another
version
yeah.
I
think
it
is
it's
basically,
I
think
it's
the
same
issue.
It's
just
that
this
one's
getting
to
a
different
object
first,
rather
than
so
yeah
the
fact
that
this
schema,
the
definitions
of
these
components
might
have
recently
changed.
This
is
something
that
we
need
to
follow
through
on
quickly.
This
is.
A
Yeah
the
thing
about
yeah,
we
should
version
the
schema.
I
also
suspect
that
won't-
or
it
would
take
a
little
while
like
that.
That
would
be
helpful.
I
think,
like
there's
some
pre
analysis,
that
that
the
system
is
capable
of
you.
We,
we
have
a
an
end
point
where
you
can
say
verify
for
before
I
click
before
I
have
a
bad
user
experience
just
verify
for
me
that
in
fact,
any
of
these
are
deployable
that
the
engine
is
capable
of.
Has
all
the
necessities.
A
B
B
A
B
A
Yeah
exactly
so,
we
have
one
issue
here:
I'll
go
file
unable
to
edit
applications
because
we're
probably
not
paging
all
of
the
component
json
that
we're
pulling
so
that's
probably
an
issue.
I
mean
that
is
an
issue
and
that's
probably
the
problem
pattern
most
available
most
previously
written
patterned.
Examples
are
running
into.
A
A
B
B
A
B
B
A
A
Yeah,
that's
a
great
there's
like
another
thing
that
we
should
be
able
to
there's
a
bunch
there's
like
three
or
four
different
ways
that
we
should
be
able
to
go
create
these
patterns
like
one
is
to
come
in
here
and
say.
I
would
like
to
build
out
this
applications
to
the
applications
book
info
and
to
and
yes
to
go
through
and
say
well,
it'll
have
a
is
to
describe
so
it'll
have
the
product
page,
basically
redescribe.
The
the
other
way
to
do
this
is
to
go.
A
Take
the
literal
book
info
pattern
manifest
import
it
here
yeah.
This
is
actually
I
mean
this
is
exactly
the
kind
of
things
that
we
need
to
be
running
through
before
we
do
the
dot
six
release,
so
this
so
actually,
mario,
if
I
could
leave
you
or
dp
on
or
anyone
else
with
this
particular
manual
test
to
do
that
would
be
to
go
grab
the
book
info
sample,
app,
the
url
or
or
download
it
to
import
it
here
and
then
and
then
try
to
deploy
it.
A
A
A
C
A
Yeah
yeah
definitely
these
first
two.
They
should
be
done
really
quick,
very
like
within
a
day
that
we
should
get
these
these
two
bugs
fixed
this
one.
It
is.
It
is
it's
an
interesting
thing
like
you
get.
We
can
just
manually
test
this
as
users,
but
the
workflow
that
we
were
looking
at
before,
where
those
integration
tests
that
are
going
on,
like
the
mesri
istio
adapter,
one
of
those
integration
tests.
A
A
A
A
A
B
A
A
A
Which
is
so,
I
think,
there's
I
think,
the
folks,
the
contributors
that
have
done
this
have
are
confused
as
to
yeah
anyway,
yeah
they're
confused.
So
this
needs
to
be
clarified
that
so
an
invalid
application
name,
okay,
invalid
application
file
name
field-
is
either
not
present
or
valid.
It's
interesting.
A
A
A
B
A
B
B
A
A
B
For
the
other
ones
right
because
they're
all
part
of
that
like
there,
it's
there's
a
hierarchy
so
but
I
might
be
wrong
not
in
this
case,
but
usually
that's
how
tools
work
yeah,
that's
how
they
parse
the
yamo.
It's
really
obnoxious.
You
know
I
hate
that,
but
that's
how
they
usually
work.
You
can
just
try
it
again.
B
A
B
B
I
think
it's
recording.
It
is
yeah,
it's
just
recording
the
requests.
So
it's
a
200,
but
let's
see
the
content,
I
think
the
front
end
isn't
even
not
a
dragon,
but
not
over
the
uh-huh.
Just
click
over
the
name,
double
twice:
what's
the
payload,
so
just
let's
go
back
the
the
payload
should
be.
Oh,
is
it
there?
No.