►
From YouTube: Meshery CI Working Group (June 29th, 2020)
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
A
So
you
guys,
hopefully
won't
have
to
suffer
and
near
as
much
good
morning
me
I
noticed
something
Neal
back
back
to
you,
yeah
there's
a
sign
of
the
box
that
is
hopefully
being
sent
today.
Your
way
is
well
I,
don't
have
any
laying
around
otherwise
I
would
spoil
the
surprise,
I
guess.
I
guess
I'll
tell
you
that
the
paper,
the
so
there's
piece
of
paper
that
there's
a
homemade
process
by
which
we
go
through
and
create.
A
Yeah,
good,
okay,
well,
people
made
oh
yeah,
you
know
I,
really,
wanna
I
really
want
to
show
a
video
about
it.
I
really
want
for
us
to
have
a
video
about
this,
but
and
when
we
took
what
a
little
while
ago-
and
we
were
gonna
kind
of
work,
it
into
a
small,
a
small
video
clip,
essentially
mejia,
my
wife
and
and
our
kids
will
have
the
ability
to
make
to
make
buttons.
They
have
a
small
like
button
press
machine.
A
So
so
we
like
okay,
we
got
the
logo
kind
of
designed
these
circles
to
go
into
buttons.
We
like
punch
them
out
using
this
large
hole,
punch
and
then
go
over
to
this
small
button,
making
machine
where
you
put
together
some
plastic
anywhere.
You
go
through
this
process
and
make
buttons
and
so
yeah
there's
a
video
of
them
doing
that
I
wanted
to
this
was
like
I.
Don't
know!
This
is
a
long
time
ago
anyway,
we've
they've
made
quite
a
few.
A
A
A
A
Now
that
doesn't
mean
that
measure
we
can
actually
get
to
them
measure
we
can.
If
you
deploy
ma
cherie
cluster
like
if
you're
deploying
measure
e
inside
of
kubernetes
and
anyway,
then
just
the
fact
that
I
just
said
that
is,
like
that's
a
whole
nother.
There's
a
lot
of
scenarios
to
this.
That
I,
don't
think,
are
really
is
really
fair
to
say
to
not
have
had
that
stuff
written
down
and
then
ask
you
to
go
yeah
anyway.
A
I
guess
what
I'm
saying
is
I
think
you're
doing
a
great
job
having
gone
through
and
understanding
the
various
aspects
of
it
without
without
much
of
a
good
description.
So
it
I'm
gonna
I'm,
taking
an
action
item
to
go
grab
the
conversation
that
we
had
had
and
and
I
get
an
actual
spec
kind
of
going.
Okay,
cuz
part
of
what
I
think
will
happen.
Vijay
is
it
you
will
be.
A
You
will
you'll
be
successful
with
facilitating
the
80%
use
case,
I,
think
or
the
the
like,
but
that
later
as
we
go
to
add
the
concept
and
the
kind
of
the
construct
of
an
environment
and
let
people
name
their
environments
or
have
multiple
connect
connections
to
multiple
different
kubernetes
clusters
at
the
same
time.
Well,
there
are
ramifications,
then,
to
what
you
would
have
done
here
that
need
to
be
taken
into
context
and
so,
and
so
in
part
were
I.
A
Think
we're
only
looking
to
achieve
part
of
the
goal
here,
acknowledging
that
like,
if
you,
if
you
achieved
all
of
the
edge
cases,
that
it
might
be
it
that
might
not
be
worth
it
because
there'd
be,
there
would
be
some
rework
later
when
we
go
to
add
environments,
and
so
okay,
yeah
I,
think
you're
tracking,
well,
I
think
that
that's
in
part,
why?
When
I
saw
your
name
on
the
list
today,
I
was
like.
Oh
boy,
we've
got
an
unfinished
or
there's
a
set
of
conversations
that
we
didn't
walk
through
and
we
should.
A
That's
been
discovered
and
one
that's
been
selected
and
persisted
as
the
users,
preference
and
then
more
than
that
persisted
as
the
users,
preference
for
that
particular
environment
and
for
like
and
so
yeah
I
think
that
the
the
project
itself
is
a
little
bit
under
equipped
at
the
moment
to
address
all
the
things
you
might
need
to
address.
If
you
were
really
really
flushing
this
out
right.
A
A
Okay,
very,
very
good,
well
in
Vijay
I.
Just
last
thought
there
is
that
I'm
excited
about
that
one,
because
because
there's
a
lot
of
power
behind
the
fact
that
we
have
a
lot
of
metrics,
charts
and
pounds
to
display
in
inside
memory
and
very
very
few
people
actually
make
it
that
far
in
Missouri
because
of
the
lack
of
kind
of
auto-discovery
happening.
So,
okay.
C
A
Okay,
fair
enough!
Well
let
me
let
me
do
this
if
I
can,
given
that
we've
got,
you
know
about
eight
eight
minutes
or
so
left.
Let
me
say
that
there
there's
one
topic
we
wanted
to
get
to
today.
That
I
I
think
that
we
talked
about
in
the
past
a
number
of
times.
As
a
matter
of
fact,
when
we
started
this
working
group
I
think
was
the
at
the
very
top
of
the
list
of
of
the
first
priority.
Well,
I
mean
one
of
the
first
priorities
was
like
versioning
massery
server.
A
Along
with
that
was
this
this
notion
of
establishing
once
we
were
able
to
version
ma
cherie,
we
can
then
establish
release
channels
and
I.
Think
to
establish
this
stable
release.
Channel
is
pretty
pretty
straightforward.
So
leader
are
you
on
the
line?
Yes,
I
am
I,
think
they'd,
say
yep.
I
think
this
is
actually
maybe
I
should
not
say
any
leader.
What
questions
do
you
have
or
how
have
you
interpreted
this
and
where
do
you
think
first.
C
If
we
should
call
it
like,
instead
of
stable
data
store,
let's
keep
it
like
latest
and
then
stable,
stable
ease
would
be
the
last
of
the
release.
I
guess
I!
Try
to
see
how
others
do
it
like
came
in
to
align
with
the
requirements
or
saw
of
other
opposes
that
I.
So
a
so
another
thing
that
bit
confuses
about
the
age
in
stable,
so
both
of
them
and
be
the
same
that
age
is
without
testing,
they
think
and
all
the
stuff,
so
I
will
shoot.
A
Briefly,
yeah
I
think
in
in
some
respects.
The
other
proposal
is
to
actually
not
use
the
actual
list,
like
the
the
one
all
by
itself,
but
is
to
potentially
use
the
latest
tag
in
combination
with
like
stable,
latest
edge
latest,
and
hopefully
as
I
say
this
next
part.
That
will
be
explained
that
the
when
we
execute
our
workflows,
we
will
produce
an
edge
release.
A
The
majority
of
the
time,
basically,
almost
any
time
that
we're
merging
to
master,
we
would
be
producing
an
edge
release
and
that
that
we
would
be
publishing
an
edge
latest,
basically
every
time
that
we
merged
to
master,
but
that
a
smaller
percentage
of
the
time
we
would
be
producing
a
stable
release
when
merging
to
master
and
a
release.
Tag
is
present
and
then
that's
what
signifies
the
notion
that
it's
a
that
is
a
stable
release.
D
A
Yep
I
think
that
we're
I
think
we're
ready
to
execute
on
the
logic
for
stable,
like
you're,
saying
for
stable
latest
for
I.
Think
that
I'm
cushy,
if
you're
on,
can
you
remind
me
I
thought
we
wanted
to
hold
off
on
edge
for
a
moment,
because
there
was
another
consideration
in
there.
But
that
might
not
be
the
case.
A
Oh
I
know
why,
because
yeah
as
we
go
to
do
this,
that
there's
some
updates
that
need
to
happen
within
mastery
CTL
we
need,
and
and
actually
there,
the
docker
compose
file
used
for
mystery
right
now
that
compose
composed
file.
Part
of
making
this
part
of
this
disk
is
update
to
the
workflow.
The
door
would
be
that
we're
not
it's
not
just
it's
not
just
about
producing
a
docker
container,
an
image
and
tagging
that
image.
A
Yes,
that's
what
needs
to
happen
here,
but
subsequent
to
that,
we
also
are
going
to
need
to
update
tags
inside
of
the
mesh.
We
yeah
mol
file,
the
docker
compose
yeah
mol
file,
yeah
and
eventually
we'll
need
to
make
an
update
to
mesh
Ricci
Thiele
as
well,
so
that
we
can
enable
users
with
control
over
switching
between
channels
should
they
want
to.
C
A
Files,
one
for
edge,
one
for
stable
I
want
you
know,
and
for
us
we
want
to
try
to
differentiate
a
little
bit.
Have
it
be
as
simple
as
possible
have
just
one
download
in
one
installer
like
we
do
today
by
default,
it
would
be
set
to
stable
and
it
would
only
be
after
someone
is
well
ended.
Basically,
after
someone
is
running
my
sri
that
they
would
be
able
to
switch
to
edge
in
advanced
user,
okay.
A
C
A
E
Leave
one
item
I
had
I
think
we
do
not
have
a
much
time
to
think
about
buttons,
I
think
put
forward
through
the
next
meter
that
look.
If
I
somebody
uses
like
kind
of
a
scaffold
engine
for
Cuban
it
is
that
automatically
building
and
deploying
production
there's
a
in
continuously
updating
the
deployment
workflow
and
enhances
dev
environment
full
at
a
tough
environment.
That's
we
can't
can
build
or
redeploy
that
image
is
again
and
again,
and
some
engines
does
for
us
so
kind
of
a
mystery.
E
A
F
If
we
have
some
time,
we
I
have
some
question
that
you
asked
me
to
delete
the
slack
apps
for
the
notification
thing,
but
I
tried
to
looking
where
I
can
delete
the
apps,
but
I
didn't
find
some
settings
regarding
that.
I
share
the
disconcert
of
that
with
you
in
the
chat,
but
I
think
you
missed
that
yeah.
A
And
so
there's
been
a
think,
it
kind
of
a
point
of
confusion,
probably
just
for
me
on
the
use
of,
like
a
legacy
token,
to
interface,
with
slack
versus
the
use
of
this.
This
github
action
slack
app,
the
github
action,
slack
app
I
think
works
a
lot
or
works
a
little
bit
better
in
that
when
you
see
the
the
avatar
of
the
user
in
slack
that
that
sends
the
notification,
the
github
action
avatars
is
this
or
that
that
logo
is
this,
which
is
great.
A
F
A
A
Okay,
kids
in
the
deal
was
is
as
we
create
new
repositories
that
we
need
to.
We
want
to
try
to
have
the
same
set
of
workflows
in
each
of
the
repos
and
so
setting
this
as
an
organizational
level
or
as
an
org
level
secret,
so
that
it's
available
to
all
the
repos
was
essentially
what
I
was
looking
to
do,
but
then,
with
the
use
of
legacy,
tokens
for
slack
or
API
tokens
and
then
the
use
of
the
github
actions,
slack
app,
I
guess
I
would
yeah
was
wasn't
quite
sure.
I
can
go.
A
We
can
go
add
this
as
an
organizational
level
secret,
and
maybe
that's
all
that
we
need
to
do
to
make
sure
that
this
workflow
works
across
all
repos.
So
I
think
one
of
the
reports-
yeah,
okay,
okay,
I'll,
do
that
and
message
the
channel
and
then
it
would
be
good
if
Shubham,
maybe
if
you
could
verify
that
I
think
the
learn
layer,
5
repo
is
probably
one
of
those
today
that
I,
don't
think,
will
notify
OnStar.
So
maybe
we
can
use
this
as
the
test.
Repo.
A
A
A
Okay,
I
mean
right
now.
Duty
in
image
hub
will
work.
If
console
is
laid
down
and
yeah
it's
a
much
smaller
app.
It
would
be
probably
easier
to
work
with.
There's
there's
one
other
app
that
is
small.
It
doesn't
really
have
a
UI
image.
Hub
has
a
UI,
maybe
that's
nice,
maybe
that's
not,
but
this
this
learn
layer
5,
is
something
that
we'll
be
integrating
into
the
SMI
surface
mesh
interface
project
as
well.
It's
a
small
sample
app
that
would
work
probably
equally
as
well
as
image
hub.
Would.
A
A
This
one
hasn't
been
built
into
the
mesh
readapted
just
yet
as
a
sample
app,
but
that
doesn't
mean
that
it
won't
run
on
any
of
the
service
meshes.
Oh.