►
From YouTube: Meshery CI Meeting (May 27th, 2021)
Description
Meshery CI Meeting (May 27th, 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
A
B
Guys,
hey,
hey,
it's
been
wow.
I've
had
a
half
an
hour
over
the
last
seven
hours
that
weren't
on
a
call
so
good
a
lot
of
stuff
getting
done,
though,
lots
of
people
here
making
stuff
happen.
One
of
those
things
that's
happening
is
dhruv,
pyush
and
abhishek
will
be
joining
here
momentarily.
I'm
sure
it'll
be
good
for
them
to
hear
part
of
this
on
code
cov
as
you're
teeing
up
agenda.
B
B
There
are
two
other
other
auto
documentation,
there's
three
other
auto
documentation
items,
so
one
is
for
graphql
api,
docs,
rest,
api,
docs
and
then
there's
an
error
codes
utility
that
generates
error
code,
documentation
as
well,
so
we've
got
a
lot
of
auto
documentation
things
going
on.
B
And
then
you
know,
maybe
we
well,
since
those
other
guys
are
just
joining.
Maybe
if
we
start
with
the
auto,
we
start
with
something
other
than
those
three
which
kind
of
involve.
B
B
I
don't
know
piyush
can't
speak
at
the
moment,
but
he
is
going
to
answer
that
question
in
chat.
I
don't
know
if
he
could.
I
think
he
might
have
created
an
issue
for
code
cove.
B
You
should
link
to
it
in
the
chat
if
so,
so,
so,
okay,
since
you
know
since
we're
talking
about
it,
maybe
by
the
way-
I
know
rodolfo
would
have
said
this
already,
but
for
the
other
12
people
that
are
on
the
call
record
your
name
down,
if
you
would
it's
good
to
good
to
get
credit
for
being.
A
A
Back
to
the
wheel,
okay,
great,
so
I
think
we
can
start
with
the
first
topic
to
for
today,
and
there
is
an
issue
for
releasing
the
reduced
notes
in
measuring,
and
this
issue
has
been
a
face
for
for
a
couple
of
months.
I
think-
and
we
cannot
fix
that-
and
the
issue
is
here
and
this
week
I
will
give
another
try
in
order
to
to
fix
this
one.
A
B
A
Also
I
have
pending
this
issue
that
is,
have
a
measured
development
environment
on
aws.
Here
we
I
think
we
have
a
like
two
options.
One
is
a
use,
easy
tools
to
deploy
their
kubernetes
and
or
we
can
use
eks
that
is
aws
service
for
kubernetes,
that
we
already
have
their
acquaintance
runner
and
we
can.
A
We
only
need
to
install
measure
either,
and,
I
think
is
eks
uses
ec2
instances
also,
so
I
think
it's
a
good
option
but
yeah
I
I
will
continue
with
this.
After
fixing
the
the
release
notes,
nice
yeah.
As
a
matter
of
fact,
sorry,
I
only
want
to
say
that
it's
important
to
have
measuring
in
a
development
environment.
B
Yeah
agreed
the
that
particular
request
was
to
in
part
to
help
out
austin
who
just
couldn't
get
mashri
running
locally
austin,
his
internship
ended,
and
so
he
hung
out
for
some
time
I
mean-
and
it
isn't
here
at
the
moment,
so
it's
probably
a
lesser
priority.
Actually
one
of
the
things
that's
of
higher
priority
is
helm,
chart
publishing.
B
We
are
we're
yet
to
successfully
automate
the
building
of
the
helm,
charts
and
their
publishing,
and
that's
something
we
could
talk
about
next,
like
that's,
and
that
would
be
for
abhishek
to
speak
to.
C
Here,
okay,
so
the
issue
here
is
that
we've
got
hem
charts
for
meshri
and
its
components.
Example
adapters
and
in
the
future,
we'll
be
having
it
for
the
conference
as
well
like
machine
operator
and
basic.
So
the
idea
is
to
auto
publish
head
chats
for
these
and
let
me
just
quickly
share
my
screen.
C
So
so
the
charts
are
present
in
here,
basically
under
install
inside
chromatic
measuring,
so
the
chart
is
currently
present
here
for
all
the
health
charts
and
we
will
need
our
ci
constructed
or
get
up
action
that
would
basically
package
these
head
charts
and
then
publish
it
to
our
helm
hub,
which
is
hosted
in
machine
dot.
Io
inside
charts,
charts
folder.
So
this
is
where
the
list
of
search
and
charts
are
being
published,
versioned
and
published.
So
we
need
an
automation
system
which
would
auto
version
auto
increment
version
and
publish
it
in
here.
C
D
A
B
Yeah,
obviously
I
do
too
much
and
avishak
you
want
to
talk
to
him.
C
B
Yeah
so
yeah,
it's
been
an
outstanding
item
for
a
while,
like
asuko
has
originally
been
the
person
to
author
here,
authored
the
original
helm
chart
and
its
publishing
has
been
manual
ever
since
we've
never
had
all
of
our
adapters
covered
in
the
home
charts.
Each
adapter
is
supposed
to
have
its
own
home
chart
and
I
don't
think
to
date.
We
don't
have
all
adapters
covered
so
we're
in
a
bad
situation.
There
we're
in
a
bad
situation
where
the
helm
charts
are
not
being
auto
released,
I
mean
they
should
be.
B
They
don't
need
a
version
number
auto,
incremented
or
auto
generated
no,
not
at
all.
All
they
need
is
the
release.
The
same
version
number
the
same
release
number
that
comes
from
a
meshery
depo
release,
so
that
version
number
where
it
says
like
that
chart
was
version.
2.1.2.
That's
forget
about
that.
Let's,
let's
make
them
the
same
as
measuring
itself.
There's
no
need
for
us
to
track
a
different
version
number
for
the
charts.
While
that's
possible,
we
don't
need
to
do
it.
B
The
charts
can
have
the
same
version
number
as
the
measure
release
that
contain
them.
So
we've
been
through.
It's
been
months
of
people
on
and
off
actually
abhishek.
If
you
could
continue
to
share
your
screen
and
maybe
point
out
some
of
the
things
that
I'm
highlighting,
which
is
like
right
now,
there's
three
open
pr's
for
testing
out
the
auto
automated
publishing
of
helm,
charts,
which
is
just
to
show
like
various
people,
have
tried
to
advance
this
and
get
it
get
it
done.
B
There
are
a
number
of
pre-existing
github
actions
that
are
readily
available
for
people
to
for
you
for
us
to
integrate
into
our
workflows
and
we've
tried.
I've
personally
tried
four
of
them.
I
think
three
or
four
of
them
and
each
one
ends
up.
I
end
up
getting
snagged
on
a
couple
of
things.
One
is
either
the
action
doesn't
like
the
way
in
which
we've
laid
out
our
charts,
so
that
url,
that
is
being
highlighted
right
now.
B
B
B
Some
of
so
one
of
the
actions
doesn't
like
how
the
charts
are
laid
out.
The
charts
are
laid
out
such
that
there's,
a
folder
called
charts
and
in
that
well
so
meshrie
has
an
application.
Server
doesn't
really
it
has
its
own
chart
kind
of
but
kind
of
not.
There
are
sub
charts
measuring
adapters
that
are
sub
charts,
that
one
of
the
actions
doesn't
like.
Unfortunately,
that
action
is
the
only
one.
B
That's
been
successful
in
terms
of
building
the
source
charts
from
the
measure
repo
and
then
pushing
them
to
the
remote
published
repo
in
measuring
io.
It
successfully
does
that
it
just
doesn't
do
it
right
now
for
the
mesh
reservoir
chart,
because
it
doesn't
like
the
fact
that
there
are
embedded
charts.
B
The
other
actions
that
we've
tried
don't
seem
to
mind
that,
but
they
don't
have.
We
don't
have
success
with
them
in
writing.
Out
to
a
remote
repo,
asuko
had
started
writing
a
custom
action
which
you
know
suffers
various
issues,
so
it
just
continues
to
be
an
open
item
and
on
this
we're
not
so
much
looking
for
a
volunteer
abhishek,
this
is
on
your
plate.
You're,
I'm
looking
to
you
to
get
this
done.
B
Okay,
so
having
described
all
that,
hopefully
that
makes
sense
to
everybody.
That's
what
almost
abhishek
is
going
to
be
doing
it's
too
important
to
leave
for
open
for
volunteers
for
months
and
months
and
months
and
months.
We
have
users
that
come
by
who
try
to
use
helm
and
it
just
falls
over
and
have
a
bad
interaction
with
mastery
to
start
with.
B
B
Yeah
and
I
hate
to
say
it,
but
this
is
one
that
I'll
speak
to.
I
think,
because
piyush
isn't
able
to
use
his
mic
at
the
moment,
but
but
p,
one
of
the
things
that
push
is
focused
on
is
bringing
forth
unit
tests
to
mastery
ctl
very
much
so
needed
every
time
that
someone
does
a
change
in
measuring
ctl.
B
B
We
have
unit
integration
and
functional
tests,
and
so
push
is
well
beginning
to
outline
kind
of
the
the
approach
to
measuring
ctl
unit
testing,
how
we
write
those
and
what
tests
we
should
write
and
there's
just
ends
up
being
kind
of
there'll,
be
a
nice
standard
set
as
we
do
that
whenever
we
build
mastery
ctl,
we
should
probably
invoke
those
unit
tests
as
well
and
that's
you
know
extremely
common
practice,
not
not
a
challenge
to
do.
B
B
C
It's
it's
basically,
that
you
can
run
your
unit
like
it.
It
integrates
with
your
repository
and
it
gives
you
the
result.
It
runs
code
coverage
every
time
you
do
some
changes.
B
So
for
github
they
have
a
marketplace
app
that
we
have
authorized
already
at
the
organizational
level
for
layer,
five
io,
which
means
that
we're
ready
to
start
to
try
to
use.
You
know
integrate
this
thing
start
to
use
it.
B
Uploader
oh
zero
percent
code
coverage
is
that
what
it
is.
B
And
so
I
don't
know
if
there's
geez
other
than
just
turning
on
code
cup
like
that,
does
anybody
know?
Is
there
anything
else
to
configure
for
code
cov
total
coverage,
total
coverage
29
something
something
what's
that
about.
A
A
B
So,
okay,
good,
so
push
is
open
for
business,
meaning
that
those
that
might
want
to
jump
in
to
measure
ctl
into
getting
some
of
the
to
taking
us
from
zero
to
hopefully
past
50
percent,
hopefully
more
toward
a
hundred.
Now
is
your
chance
to
start
from
ground
zero
ground,
zero
percent.
A
I
think
there
is
no
github
action
like
that,
and
we
only
need
to
er
to
link
the
the
repo
here
but
yeah.
I
don't
remember
well,
I
have
to
to
review
this.
C
A
A
A
B
B
B
You
can
like
a
good
example,
is
dependabot
used
to
be
configured
through
github
app
and
now
they've
transitioned
it
to
being
configured
through
yaml
file
in
your
dot,
github
folder.
So
I
think
different
apps
different
things,
but
both
abhishek
and
rodolfo
should
have
an
email,
probably
sitting
in
your
inboxes
like
as
of
30
seconds
ago,
about
the
permission
to
be
able
to
configure
this
thing,
the
github
app
so
hopefully.
B
A
C
I
I
don't
have
insight
on
this,
but
basically
this
is
to
document
all
the
rest.
Apis
of
meshri.
C
And
we
are
working
towards
having
a
open
api
style
documentation,
basically
something
called
swagger
which,
which
is
a
documentation,
format
or
spec
for
rest,
apis
and
yeah
like
basically,
it
looks
something
like
this,
where
I
think
it's
interactive,
but
currently
the
one
that
you're
seeing
isn't
or
is
it
okay.
C
So
basically
it
describes
each
and
every
routes
and
all
of
the
parameters
that
that
are
allowed
and
etc.
So
it
gives
you
the
whole
information
about
each
and
every
endpoint
that
are
available
in
meshri
server.
C
C
C
A
B
Right,
yeah
there's
a
couple
of
things
to
call
to
action
for
here,
so
just
for
context,
because
because
jubril
and
hina,
and
beneath
and
ayush
and
gautam
and
anshu
and
mert
and
vishal
and
every
everybody
it's
not
supposed
to
be
this
way.
Well,
the
maintainers,
rudolfo
and
abhishek.
You
would
imagine
that
they
would
be
speaking
a
lot
because
they're
doing
a
lot
and
so
great,
but
also
the
reason
that
you're
not
all
sitting
here,
just
to
be
spoken
at.
B
Rather
there
are
many
things
for
you
to
all
do,
some
of
which
might
be
more
interesting
to
you
than
the
next,
so
only
volunteer
for
stuff.
That
you
know
is
of
interest
on
this
topic.
It's
kind
of
a
well,
it's
really
important,
it's
an
important
topic,
and,
and
it's
one
that
we've
been
missing
for
a
while.
B
It
actually
affects
and
like
gibril
I'll
call
him
out
as
an
example
he's
trying
to
make
well
he's
like
he,
like
others,
have
tried
to
add
new
functionality
in
mesh
rectl
mastery
ctl
internally,
it's
a
it's
a
rest
client
of
mesh
reserver
and
when
he
goes
to
do
that,
you
know
his
natural
question
is
okay,
great,
so
so
where's,
the
meshery
servers
rest
api
documentation,
so
I
can
get
familiar
with
the
apis
and
which
ones
I
should
call
and
kind
of
what
their
behavior
is.
B
What
what
should
I
expect
that
they
do
and
it's
like
well
gosh,
there's
not
a
great
answer
for
that
or
there
hasn't
been,
but
piyush
and
davindu
and
dhruv
and
abhishek,
and
some
others
have
been
working
on
changing
that
answer.
For
both
measures
measuring
servers,
rest
api
and
its
graphql
api
and
mesh
reserver
has
both
and
will
continue
to
have
both
graphql.
B
B
Again,
so
each
of
them
dhruv
and
push
in
specific
have
gone
about
well
trying
to
get
a
frameworks
for
documenting
the
apis
and
so
for
the
rest
api.
That
framework
is
called
open,
api
specification
and
it's
better
known
as
swagger.
It's
kind
of
what
it's
sort
of
the
older
name
for
that
specification,
and
so
there's
some
swagger,
tooling
and
framework,
the
the
rest,
api
and
mesh
reserver
is
written
in,
go
so
the
tooling
for
documenting
this
api,
the
framework
it's
swagger,
it's
a
golang
framework
library,
it's
sitting
here.
B
You
can
see
it
on
the
screen
and
there's
a
couple
of
make
commands
that
will
generate
you
know
so
so
the
the
api
itself
and
its
docs
it
gets
described
in
the
code
in
the
rest
server
code,
what
each
endpoint
is
and
what
it
does,
and
we
were
just
seeing
an
example
of
the
initial.
B
B
There's
any
number
of
opportunities
for
any
of
you
to
jump
in
either
in
creating
workflow
to
help
run
this
to
generate
these
docs
jumping
into
jekyll
the
mesh
redox,
so
whoever's
sharing
the
screen.
If
you
can,
if
you
go
back
to
mesh
redox,
let
me
let
me
share
for
a
moment
just
to
so
so.
Here's
the
pull
request
that
we
had
had
that
was
just
being
shared.
E
But
I
I
would
like
to
say
my
progression
about
the
weapons
software
engineering
day
by
day,
I'm
learning
how
to
write
make
files,
how
to
build
a
project
whether
this
is
go
or
love,
ruby
or
any
other,
I'm
just
learning
or
remembering,
maybe
the
stuff
that
I
need
to
contribute
to
the
open
source
in
here
or
and
also
near
layer.
Five,
it's
getting
better.
In
short,.
E
No,
I
couldn't
be
able
to
run
my
computer
day
by
day,
because
I
was
having
health
issues.
B
E
B
Very
good,
all
right
so
back
to
the
topic
at
hand
and
mer,
if
you
don't
mind,
if
you'll
mute,
just
because
there's
a
feedback
on
your
line.
B
Oh,
thank
you
good,
so
just
to
see
this
in
action,
so
push
has
done
something
that,
like
four
or
five
people
before
him
didn't
either
couldn't
or
didn't
find
time
to
do,
and
that
is
to
finally
go
get
the
project
set
up
with
swagger
and
this
works
beautifully.
So
so
I
was
just
I
don't.
I
don't.
B
I
don't
know
swagger
from
a
hole
in
the
wall,
but
because
he
wrote
a
good
issue
and
some
descriptions
about
make
make
commands
and
things
I'm
able
to
go.
Do
this
briefly,
I
check
out
his
pr.
I
did
a
make
swagger
spec,
I'm
just
guessing
at
the
order,
make
swagger
docs
looks
like
great.
The
specs
are
being
made.
The
docs
are
being
made
as
well
by
the
docs
being
made.
That
looks
like
that's
a
single
yaml
file
that
falls
into
the
data
folder
under
the
docs
yeah.
B
So
if
I
go
to
docs
data,
there's
a
data
file
swagger.yaml
in
here
just
a
long
yaml
file
that
that
is
the
documentation.
This
is
this:
is
the
api
documentation.
So
then,
this
data
file
gets
picked
up
by
something
else
that
pierce
did,
which
is.
He
went
into
the
pages
section.
He
went
into
the
reference
section
and
created
well.
B
He
did
a
couple
of
things
more
than
what
I'm
just
saying,
but
but
he
created
created
a
new
layout
for
swagger
to
basically
go
through
and
read
the
ingest
that
yaml
file
read
through
it
and
then
to
generate
html
around
the,
and
you
know
like
when
I
say
he
did
it.
I
mean
he
used
an
open
source
project
to
do
that
and
that's
the
most
intelligent
thing
to
do
and
then
so
he
created
this
this
page,
it's
called
reference.
B
Hyphen
reference,
slash
rest
apis,
so
over
here,
oh
reference,
slash
rest
api,
so
I
get
to
the
page
it's
reading
in
part
of
the
yaml
file,
and
you
know,
because
this
is
borrowed
from
an
open
source
project.
It
it's
coloring
and
some
of
its
css
needs
just
a
little
bit
of
tweaking,
which
you
know
we
will
talk
about
on
monday
and
the
websites
call
or
we'll
talk
about
now.
If
any
one
of
you
want
to
take
this
as
a
challenge,
there's
css
to
be
done.
That's
one
challenge!
B
The
other
challenge
is:
there's
a
workflow
to
be
updated
that
incorporates
those
commands
to
build.
You
know
to
produce
that
documentation
each
time
and
then
I
think
piyush
would
tell
us
and
he'll
chat
chat
us
if
this
is
true
that
there's
probably
some
of
these
endpoints
that
are
still
in
need
of
a
little
bit
of
documentation
about
what
they
do
that
lends
itself,
and
so
that's
probably
the
third
area
of
like
where
you
can
go,
get
involved.
B
There's
a
spreadsheet.
That's
in
the
community
drive
it's
called
meshi
api
endpoints,
it's
very
auspicious
in
that
way.
It
lists
out
the
current
endpoints
and
the
fact
that
some
of
those
are
being
changed
to
being
restructured
reorganized
both
for
get
the
get
endpoints
and
the
graphql
endpoints
and
so
dhruv
patel's
name
is
all
over
this.
Please
go
see
dhruv,
let's
go
see,
gotham
go
see
adi
krishna,
if
you're
interested
in
graphql
and
what's
happening
here,
go
see
piyush
and
nevendoo.
B
If
you're
interested
in
what's
going
on
here
in
the
rest
server
or
are
you
the
rest
api?
These
changes
are
gonna
affect
mastery
ctl
and
mastery.
Ui
yeah
adi
go
ahead.
B
Them
good
audi
and
gautam
in
particular,
are
likely
to
be
helping
ensure
that
a
these
gra
that
the
graphql
relay
client
that
we're
using
in
measure
ui
is
being
incorporated
into
various
components
and
these
subscriptions
are
being
managed
and
are
being
used.
B
They're
also
like
there'll,
be
some
areas
where
we
will
just
continue
to
use
the
rest
api
in
meshrey's,
ui
and
but
there
may
need
to
be
some
updates
in
mesh
for
ui
as
the
endpoints
change.
As
this
one
shifts
from
slash
config
sync
to
slash
system,
slash
config,
like
there's
a
change
that
needs
to
be
done
so
both
on
mesh
for
ui
and
then
in
mesherie
ctl.
B
It
only
uses
the
rest
api
today,
but
any
of
the
changes
to
the
rest
api
need.
That
means
code
in
measuring
ctl
needs
to
be
updated
as
well,
so
so
tons
of
opportunity
in
graphql
and
go
and
react
and
in
clients
and
in
servers
to
get
involved
also
in
the
workflows.
So
there's
a
workflow
for
automating,
swagger
and
building
out
the
docs
that
we
were
just
looking
at
that
were
generated
around
swagger,
go,
go
swagger
and
then
there's
also
the
automation.
There's
also
a
similar
framework
for
auto
documenting
the
graphql
apis.
B
Graphql,
api
docs,
and
so
I
don't
think
this
is
done
either
it's
it's
in
flight,
but
now
these
are
being
auto
generated,
so
good
get
involved,
go
see
those
two
names
that
that
was
like
the
biggest
call
to
action.
I
think
in
this
meeting
was
the
fact
that
both
of
those
the
rest,
api,
mastery,
ctl
needs
code,
cov,
configured
and
etc,
and
it's
not
just
for
mastery
ctl,
but
then
all
of
meshri
that
the
rest
api
needs
incorporated,
the
swagger
stuff
needs
incorporated
into
ci
and
then
the
graphql.
B
Well,
I
don't
think
we
have
it
called
out
separately
here
like
this.
Is.
C
B
So
for
anybody
that
yeah
so
there
needs
there
needs
to
be
an
open
issue
for
incorporating
the
swagger
into
a
ci
workflow,
and
I
think
push
is
opening
one.
There
needs
to
be
an
open
issue
for
incorporating
whatever
builds
the
graphql
documentation,
incorporating
that
into
workflow
as
well.
Hence
the
volunteer
needed
peace.
A
Sure,
thanks
a
so,
the
next
topic
is,
I
think,
rest
api,
and
we
already
talked
about
this.
I
think
the
last
one
is
to
document
the
error
codes
from
the
initial
so
from
the
command
line.
C
C
Okay,
so
to
brief
what
this
is.
This
is
basically
the
task
where
we
are
creating
a
list
of
error
codes
for
each
and
every
error
that
we
have
in
any
of
the
components
in
meshley
architecture,
so
be
it
measurey
or
adapters
or
any
other
components.
So
each
of
them
will
have
a
set
of
error
codes
that
will
correspond
to
some
particular
error
with
a
suggested
remediation
and
so
the
status,
remediation
and
or
probable
cause.
C
Oh,
you
got
okay,
oh
yeah.
This
is
the
one.
So
michael
is
the
one
who's
working
on
it
and
he's
he's
basically
drafted
what
are
the?
What?
What
is
the
progress
that
is
done
in
this
in
this
utility
tool?
Basically,
we'll
need
to
automate
this
part
in
each
and
every
component
to
to
basically
so
so
right
now,
this
utility
would
produce
a
list
of
error
codes
along
with
their
metadata.
B
There,
so
a
quick
recap
is
there's
a
utility
that
auto
documents
error
codes,
those
error
codes,
get
published
into
the
troubleshooting
guide
on
docs.mestre.io.
Did
you
show
that
already.
D
B
B
It
looks
like
there
was
one
that
was
done,
or
was
it
the
masteries
there's
a
couple
that
were
done
under
measures
ctr?
Oh,
oh,
that's,
nice!
Oh
wow!
I
wonder
who
did
that?
That's
that's
great
yeah!
This
was
done
by
the
league,
all
right.
B
It's
just
that
I
have
to
harass
abhishek,
because
he
and
I
have
been
just
trying
desperately
trying
to
figure
out
how
to
get
us
to
a
point
where,
where
he's
doing
what
he's
doing
today,
which
is
he's
calling
for
for
assistance,
he's
saying
that
there's
a
this
utility
that
will
read
it
actually
reads
through
the
code
and
the
code
classes
in
golang,
which
is
kind
of
cool.
What
michael
has
done?
B
It
will
look
for
any
place
that
the
code
is
saying
that
there's
an
error
and
because
those
errors
are
using
the
same
framework
that
utility
will
auto-generate
these
code
number.
I
am
repeating
what
abhishek
said
to
generate
these
code
numbers
and
basically
it
it
auto-generates
code
numbers
and
then
auto
publishes
a
data
file
just
like
what
we
were
just
looking
at
for
the
rest,
api
stuff,
so
it'll,
auto
document
as
well,
which
is
awesome,
and
so
many
of
us.
B
What's
the
probable
cause
of
the
issue,
that's
being
faced
and
even
more
importantly,
like.
What's
the
suggested
remediation
to
fix
the
issue?
Like
that's
really
helpful,
you
know
because,
like
the
first
thing,
people
are
going
to
do
when
they
get
an
error
code
when
they
actually
try
to
execute
a
command
or
or
see
something
in
the
ui.
It's
like
error
code,
meshri
9002.
They
do
a
google
search
and
like
boom.
Like
here's,
the
answer
like
you're
disconnected
from
kubernetes
or
whatever
the
answer
is:
that's
that's.
B
What
a
great
experience
the
reality
is
eventually,
those
the
we'll
have
hyperlinks
right
from
measuring
ctl
when
some
issue
occurs
and
there's
error
code
9000,
the
hyperlink
is
like
right
there
or
in
measure
ui.
It's
like
yup
error
code,
9001,
there's
the
hyperlink
right
there
and
in
mesh
ui.
It
could
actually
I
frame
it
or
it
could
actually
read
from
source
and
show
it
to
you
right
that
you
doesn't
actually
have
to
redirect.
You
can
just
show
it
to
you
in
the
notification
center
the
notification
center.
B
You
say
yes,
there's
a
design
for
an
enhanced
notification
center,
which
is
a
design
spec
that
you
know
if
you're
interested
in
go
see
michael
gefeller,
one
of
the
maintainers
it'll
be
pretty
cool
actually,
so
the
call
to
action
is
what
it
is
to
someone
to
volunteer
to
create
the
workflow.
That
runs
this
error
code
utility
since
we're
in
the
ci
meeting
any.
B
And
if
you
think
about
it-
and
you
want
to
explore
it,
you
know-
go
see
michael
goodfeller
he's
the
guy
that
wrote
this.
So
he'll
have
lots
of
insight
as
to
you
know
what
the
workflow
would
need
to
do.
A
A
B
A
A
A
B
Yeah
mini
cube,
oh
yeah,
gibral,
yeah
chebril.
That's
what
happens
when
you
don't
add
to
the
meeting
agenda
dubai.
We
got
three
minutes
left
like
that.
Wouldn't
make
sense
to
even
start
that
topic
yeah.
I
don't
know
what
to
say
other
than
in
two
weeks
time.
This
meeting
will
happen
again
and
like,
but
I
don't
know.
B
Yeah
mini
cube,
tunneling,
like
yeah,
that
I
mean
keep
tiling
will
work
it's
good
to
do
anything
that,
like
you,
can
always
refactor
you
know,
and
so
right
now
it.
D
B
Try
kind,
you
know,
try
to
use
kind.
If
you
cannot
use
mini
cube,
it
might
even
be
smaller.
I
don't
know
I
mean
that's
another
thing
to
throw
in.
There
is
like
kind
or
mini
cube.
I
think
those
two
will
work
for
a
github
hosted
runner
that
includes
kubernetes.
There's
a
lot
of
prior
art
out
there,
lots
and
lots
of
other
projects,
running
kubernetes
and
github
actions,
and
so
get
up
workflows
so
go
see
what
they're
doing
some
that
are
right
inside
the
scenes.
Write
neighbors
cncf
projects.
A
Great
and
also
I
use
say
that
I
want
to
want
to
contribute
with
the
fixing
css
issues
in
the
rest
api
documentation.
So
I
wrote
here
your
name
and
please
start
reading
the
issue,
the
pull
request,
and
if
you
have
questions,
please
make
them
in
slack,
and
I
think
lee
abby
me
michael.
I
will
reply
you
if
you.
A
B
Nice
cool,
I'm
I'm
totally
pumped
about
I
used
jumping
in
I
said,
but
jumping
into
the
css
on
in
the
docks
like
based
on
the
work
that
you've
been
doing,
that's
great
and
then
jubril.
I'm
sorry
that
we
didn't
make
it
to
the
that
topic.
I
just
yeah
because
it
wasn't
listed.
B
But
maybe
we
could
have
another
session
in
between
now
and
two
weeks
from
now
or
something
like
you've
had
to
work
through
a
few
different
hard
things
in
github
actions
like
are
you?
Do
you
have
a
solution
for
running
your
github
actions?
Locally,
a
self-hosted
runner
locally,
because
the
gh
you,
you
know
command
line
utility
for
github.
It
lets
you
interact
with
github,
hosted,
workflows
and
get
hosted
actions
unless
you
list
them
and
invoke
them
and
stuff
like
that.
But.
B
B
I
guess
you
will's
connection
drop,
so
all
right,
never
mind.
E
I'm
just
listening
and
be
careful.
F
A
Think,
yes,
sure,
I
think
this
is
all
for
this
meeting
and
remember
that
we
have
this
meeting
every
other
week
or
every
two
weeks.