►
From YouTube: Layer5 Community Meeting (Jan 22nd, 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
A
I
think
we're
about
we're,
probably
about
up
sweetie.
I
know
you're
you're
tying
off
a
couple
of
things,
but
whenever
you're
ready
we're,
probably
all
set.
B
Good,
so
am
I
on
please.
B
All
right
lee:
will
you
start
us
off
or.
A
Yeah,
I'm
sure
well
by
the
way,
if
you're,
so,
if
you're
on
the
call,
hopefully
you've
got
access
to
the
meeting,
minutes
drop
your
name
in
and
now
I'm
just
realizing
that
that's
not
what
shrewdy
meant
but
drop
your
name
in
and
when
you
do,
you
know
be
sure
to
drop
your
last
name
too
else.
A
Somebody
might
make
up
your
last
name
for
you,
and
so
that
will
be
the
price
that
you
pay
good
deal
so,
who
all
do
we
have
on
yeah,
very
good?
Let's
just
get
that
the
link
shared
to
the
meeting
minutes
so
again.
A
And
good
deal,
I
suspect,
we'll
have
a
couple
of
other
folks
joining,
but
actually
shreedhi.
If
you
don't
mind
taking
us
through
some
of
the
regular
riga
prigma
roll.
If
you
would,
we've
got
a
maybe
a
newcomer
today
as
well.
B
Sure
all
right,
every
welcome
everybody
to
the
community
calls
we
take
a
day
every
week,
figure
out
what
we've
been
doing
all
week
to
call
out
everybody
working
on
projects
and
make
a
few
jokes
at
their
expense.
B
We
also
make
a
couple
of
important
announcements
that
everybody
should
know
about
and
discuss,
project
details,
issues
to
work
on
and
just
get
everything
going.
B
So
as
a
tradition,
we
introduced
newcomers
in
this
call.
So
if
you
are
attending
this
particular
call
for
the
first
time,
you
have
a
first
hand
opportunity
speak
up
and
introduce
yourself
and
tell
us
a
little
bit
about
yourself
that
can
include
your
favorite
color
abhisheks
is
purple
if
anybody
wants
to
know
or
what
you
work
with
or
what
you've
been
working
with,
or
what
projects
you
were
interested
in.
Could
change
from
anything
really.
E
So
hello,
everyone,
this
is
yosh
pandey.
I
am
a
sophomore,
a
computer
science
student
at
indian
institute
of
information
technology,
ranchi
india
and
I
love
to
make
websites
and
I've
recently
been
making
a
game
engine
which
is
sort
of
odd,
because
I'm
here-
and
I
also
love
making
websites-
and
I
want
to
you-
know-
learn
more
about
open
source.
F
Actually,
I
did,
I
think,
lily
didn't
forget
me
still
driven
by.
I
guess
I
joined
earlier
a
few
months
or
one
year
before.
A
Yeah,
oh,
oh
raj,
yeah,
that's
right,
yeah,
I'm
so
focused
on
trying
to
poke,
I
don't
know,
be
kind
and
poke
fun
at
josh,
pandey
that
I
wasn't
paying
attention
to
ross
or
raj
being
here
so
yeah,
just
raj
I'll.
Do
it
for
you?
A
If
I,
if
you
don't
mind,
raj
has
well
been
in
and
out
of
the
community
for
some
time
has
been
interested
in
the
projects
that
that
that
we're
doing
and
some
of
the
ones
we
haven't
done
yet
so
very
early
on
I
mean
all
most
of
you
are
familiar
that
hey
we,
you
know,
mesri
is
probably
our
biggest,
not
probably
it's
our
biggest
project.
There
are
other
projects,
though,
and
one
of
those
that
we
had
had
an
intention
for
a
mind
for
it's
still.
Roadmap
for
us
collectively
is
well.
A
It
was
called
mesh
monkey
earlier
on
and
I
suppose
it
still
is
it's
you
know
more
or
less
the
thought
that
service
meshes
are
powerful
and
we
can
use
them
to
do
chaos,
engineering
and
so,
as
it
so
happens,
chaos
engineering
was
a
raj.
Was
an
early
community
member
to
signal
interest
in
that
area
and
rightfully
so,
because
he's
been
well
working
with
a
chaos,
engine
litmus
chaos
and
he
and
others
have
presented
litmus
chaos
and
well
in
I
mean
he
and
others
have
been.
A
You
know
just
engaged
for
some
time,
we've
kind
of
considered
what
what
how
an
integration
between
meshary
and
miss
chaos
would
work
and
and
their
the
the
two
and
their
purpose
are
well
aligned.
It's
just
great
raj
went
off
and
rushed
it.
I'm
gonna
tell
your
whole
story.
If
I
can
you
like
one
off
and
did
I
think,
a
google
summer
code
ended
up
yeah,
I.
F
Litmus
chaos
yeah
right
now,
I'm
I'm
working
on
some
internal
projects
for
my
data,
so
I've
been
like
not
contributing
regularly
to
litmus
these
days
still
like
maintaining
some
stuff.
A
But
okay,
very
good,
but
and
then
refresh
my
memory,
did
you
end
up?
You
know
I'm
graduating
and
then
moving
into
a
role
with
my
data.
F
Yeah
I
passed
out
last
year
and
I
I
joined
military
as
a
full-time
employee.
That's
awesome,
yeah!
That's
awesome!.
A
And
then
good
and
then
you've
got
a
topic
for
us
a
little
bit
later,
we'll
talk
about
helm,
charts.
I
think
yeah.
F
I
was
looking
from
like
ken
perspective,
so
that
if
I
can
start
first
or
if
you
have
any
other
agenda,
you
can
talk.
First,
okay,
look.
A
At
a
couple
other
items,
but
yeah
good,
good,
okay,.
A
Yeah
thanks
for
saying
that
hold
that
thought.
For
one
moment
there
you.
D
A
It's
good
to
have
you,
though
there
is
there's
might
be
one
other
individual
that
I'm
not
sure
if
you've
been
on
the
call
before
but
semite
again,.
A
Good
afternoon,
good
morning,
yeah
thanks
for
coming,
do
you
want
to
introduce
yourself
real
quick,
just
say
a
few
words.
G
Yeah,
I'm
new
to
I
need
to
front-end
development,
so
I'm
going
to
contribute
to
many
open
source.
So
that's
when
I
I
get.
I
come
across
this
community,
but
I
have
not
been
able
to
contribute
to
any
of
the
any
of
the
projects
so
joining
today,
I'm
observing
of
yeah
and
how
can
I
join
how
I
cannot
contribute
to
any
of
the
community?
A
Nice,
that's
great
by
the
way,
just
to
be
so
that
that's
fanta
thanks
for
introducing
it's
nice
to
meet
you
just
as
a
general
note
for
everyone,
if
it
isn't,
if
it
hasn't
been
clear
in
the
past.
A
To
be
counted
as
a
member
of
the
community
doesn't
mean
that
you
have
to
contribute
code
or
that
you
have
to
necessarily
even
advance
to
projects
like
actually
just
coming
and
hanging
out
is
enough,
it's
nice
to
talk
to
people
and
exchange
ideas
and
talk
about
some
of
this
tech,
so
just
just
to
be
clear
in
case
that
wasn't
clear
before,
but
if
you
want
to
contribute
something,
oh
there's
all
kinds
of
things
to
do
so,
please
do
nice
all
right.
I
think
we
hit
all
the
first
timers.
B
B
All
right,
so
we
have
a
special
announcement
today
or
a
particular
person
who
I
really
really
hope
is
on
this
call
and
here's
ali.
Would
you
like
to
make
it.
A
Yeah,
hey,
look
well,
there's
kind
of
there's
kind
of
two
of
them
that
are
happening
today,
and
one
of
them
is
they
are
both
really
just
acknowledgments
of
two
individuals:
who've
been
performing
a
function
and
and
and
so
we're
not
really
doing
anything
other
than
just
recognizing
the
fact
that
they've
been
performing
that
function.
One
of
those
is
well
mesh,
mate,
patel
or
mr
josh
patel.
A
I
remember
one
of
the
first
conversations
that
josh
and
I
had
had,
and
I
really
appreciated
the
conversation
because
it
wasn't
the
easiest
one
for
anyone
to
have
necessarily
he-
and
I
were
talking
about
front
end
oriented
things
we're
talking
about
website
stuff
by
the
way,
mr
pandy,
we
there
are
about
six
websites
or
so
floating
around
here,
there's
a
new
one
in
development
right
now,
so
your
passion
for
websites
you're
in
a
good
place-
and
you
know
I
think,
josh.
A
io,
for
a
while
and
in
that
process
he's
brought
in
a
few
other
new
members
and,
as
he
has
he's
taken
the
time
to
shepherd
them
and
make
sure
that
they've
been
warmly
received
in
the
community
that
they've
understood
what
we're
working
on
and
he's
supported
them,
and
it's
not
just
the
people
that
he's
brought
in
any
he's
been
quick
to
volunteer
to
do
that.
For
for
anyone,
who's
asked
for
assistance
and
that's
what
being
a
mesh
mate
is.
A
So
today,
we've
we've
recently
asked
josh
to
join
the
program
formally,
and
I'm
thankful
that
he's
he's
agreed
get
a
lot
of
a
lot
of
people
coming
through
the
community
and
the
thing
is,
is
like
there's
a
I
feel
like.
I
feel
like
I'm
sitting
in
the
airplane
right
now,
with
with
this
next
statement.
It's
sort
of,
like
you
know,
there's
there's
a
lot
of
communities
to
choose
from.
Thank
you
for
flying.
A
You
know
layer,
five
community,
I
think
there's
a
lot
of
communities
to
choose
from
one
of
the
things
that
that
I
don't
think
all
of
the
communities
get
right,
and
hopefully
we
do
at
least
99
percent
of
the
time
and
that's
to
well
to
recognize
that
like
it's
about
the
people
more
than
it
is
the
projects,
the
project
and
the
tech.
Don't
get
me
wrong.
I
love
to
nerd
out
on
them
all
day
long,
but
if
it
weren't
for
everyone
here,
that's
showing
up
and
no
the
projects
wouldn't
be
there.
A
I
wouldn't
be
here,
I'd
be
doing
something
and
I'd
probably
like
to
do
less
and
so
for
all
of
you,
I'm
thankful,
and
for
people
like
josh,
I'm
thankful,
because
if
he
wasn't
here
I'm
helping
others,
then
you
know
people
new
people
wouldn't
come
and
existing
people
wouldn't
stay
so
so
congrats
josh,
thanks
for
taking
on
the
role
as
an
indentured
servant,
you'll
be
asked
to
do
only
more
so
I
joke
just
because
mesh
mates
they
get
pulled
in
a
lot
of
ways.
So,
thanks
for
stepping
up
josh.
A
Yep
one
of
the
things
that
josh
by
the
way
does
very
well
is,
if
you
haven't
noticed
well,
I
I
don't
know
that
it's
the
gift
of
gab
that
I
have,
but
it's
not
shutting
up.
Josh
josh
helps
me
with
that.
So
I
I'm
appreciative
in
that
regard
as
well.
A
There's
so
there's
another
announcement
that
I
wanted
to
make
today
and
I'll
go
ahead
and
share.
It's
actually
also
with
respect
to
mesh
mates.
A
Some
of
the
mesh
mates
have
been
here
for
a
while.
Clearly
they
haven't
had
their
fill
just
yet.
One
of
those
is
this:
guy.
A
I
think
it's
better
for
me
to
to
to
write
up
this.
A
But
nikhil.
H
Actually,
I
should
thank
you
thank
the
community,
thank
you
and
other
peoples
and
the
people
who
are
there
in
the
community
because
of
them,
I
was
able
to
you,
know,
stay
here
for
so
long
and
keep
contributing
without
thinking
about
moving
away
or
leaving
the
community.
It's
just
the
environment
or
the
thrill
that
I
get
whereby
contributing
or
guiding
others
helping
out
others
to
contribute,
which
makes
me
stay
here
for
long
and
long
ago.
H
That's
the
reason
I
have
seen
like
it's
almost
one
and
a
half
years
since
I've
been
here.
H
But,
to
be
honest,
I
haven't
thought
even
once
about
moving
away
from
the
community
or
leaving
any
role
as
such,
but
there
were
many
who
joined
with
me
with
me,
but
they
eventually
dropped
off
or
were
busy
with
some
of
the
work.
But
I
try
to
no
yeah
in
the
middle.
I
got
a
bit
away,
but
was
having
less
contributions,
but
yeah
not
with
code
but
with
other
experts
might
be
that's
the
reason
I
am
getting
this
today.
There
was
a
small
competition
or
a
funny
one
with
no
here
with
us.
H
B
H
B
B
All
right
I'll
take
over,
so
we
have
stick
on
coming
up
next
month,
which
is
from
february
22nd
to
25th.
B
There's
a
link
to
this
website
and
I
believe
you
can
go
sign
up
for
a
couple
of
workshops
for
a
couple
of
sessions
and
they
have
everything
going
on
a
good
place
to
get
started
a
good
place
to
go,
learn
some
things
post
that
another
big
announcement
so
that
life
currently
has
a
site
which
runs
in
jekyll.
B
But
for
the
past
three
months
or
so
we
have
been
working
to
migrate
it
to
another
platform
to
gatsby,
which
is
a
react
framework
and
a
couple
of
or
a
large
number
of
community
members
have
been
continuously
working
on
it
and
it
finally
goes
live
this
month.
B
B
B
It
finally
goes
like
this
month.
If
you
want
to
help
us
get
ready,
there
still
are
a
couple
of
issues
that
you
can
go
help
out
with.
If
you
want
to
contribute
code,
if
you're
not
you
do
not
have
the
time
or
you
don't
want
to
contribute
code
at
this
particular
moment.
B
You
can
also
help
us
out
by
going
to
the
site
and
well
telling
us
how
pretty
it
looks,
I'm
just
kidding
go
to
the
site
and
tell
us
if
you
can
spot
any
bugs
or
if
you
can
spot
any
sections
that
could
be
improved.
We
obviously
understand
that
site
can
be
improved
at
this
particular
point,
but
any
kind
of
feedback
is
very.
Very
welcome.
B
All
right,
I
think,
that's
it
for
the
announcements.
If
nobody
has
anything
else
exciting
to
tell
us,
let's
move
on
to
the
agenda
all
right
raj,
would
you
be
willing
to
start
us
off.
F
Yeah
thanks
thanks
everyone,
so
I
was
going
through
the
hand,
chat
installation
I
was
looking
like
we
have
to
clone
the
repo.
I
guess
we
have
four
thousand
plus
comments
and
it
will
take
too
much
time
to
clone
that
report.
The
new
code
inside
the
repo
and
install
the
hand
chat,
so
I
suggested
like
github
pages
one
of
the
ways
we
can
do
for
the
hand,
chart
installation
and
other
than
that.
I
was
confused
with
this
artifact
hub
with
operator
hub
in
operator
hub.
F
What
we
do
is
like
we
have
to
raise
some
pr
to
upgrade
our
charts
and
everything
like
it
will
get
some
delay.
So
that's
why
I
was
searching
for
the
github
pages
like
it's
a
committed
decision,
so
it's
just
a
solution
from
my
side.
B
F
Yeah,
so
the
context
is
like
we
have,
I
think,
some
charts
in
the
chat
directory
right,
so
we
can
build
an
action
which
will
build
those
chart
and
create
a
like
accessible
link
in
a
different
branch
called
gs
pages.
We
can
call
it
as
gs
pages,
so
we
can
deploy
this
branch
with
the
github
pages
so
that
we
can
directly
go
to
like
installing
helm
repo
from
the
github
pages.
F
So
maybe
I'll
have
one
question
here
right
for
you:
is
it
possible
to
club
different
help
chats
from
different
other
repositories
into
one
yeah?
It
is
possible
just
you
have
to
write
the
logic
of
that
like
we
have
to
bundle
those
chat
and,
like
you
have
to
mention
the
path
where
you'll
pick
the
helm,
charts.
Okay,
so
other
other
repositories
are
also.
A
Yeah,
hey
yeah,
sorry
yeah,
then
this
is
a
great
suggestion.
It's
been
one
that
I'm
surprised
we
haven't
gotten
too
earlier,
and
it's
just
an
acknowledgement
that
helm
charts
are
an
artifact
of
builds
or
should
be
an
artifact
of
builds
just
like
other
artifacts.
Just
like
a
new
homebrew
package
is
produced.
Our
new
scoop
package
for
mastery
cto
helm
is
a
way
of
installing
meshri
and
that
so
the
helm
chart
should
be
published
alongside
in
the
same
process.
A
So
I'm
really
glad
that
we're
getting
to
this.
Finally,
it's
actually
been,
I
think,
totally
unrelated
to
raj,
bringing
it
back
up
some
others.
Some
other
users
were
stumbling
into
issues,
usability
issues
with
the
chart,
and
so
so
it's
a
very
timely
item.
A
Manually,
which
is
like
yeah,
you
know,
like
they've,
just
been
ignored.
I
mean
that
process
has
been
ignored,
so
there
is
no
process
other
than
just
manually
handcrafting
and
updating
and
revving.
The
version
number.
A
Upgrade,
I
don't
believe
so
because
I
could
be
so
the
so
one
of
the
other
contributors
here,
sort
of
the
helm
chart
maintainer.
If
you
will
is
asuko
asuko
lee,
and
so
in
slack
he
goes
by
yeah
and
he's
been
perf.
I
guess
I
originally
put
it
up
there
in
artifact
hub
I'm
unsure.
A
If
I
were
to
guess
I
would
say:
I'm
75
sure
that
artifact
hub
has
a
link
to
where
we
publish
the
chart
and
it's
okay
and
you
know,
since
you
publish
the
chart
and
there's
a
manifest
that,
like
you,
can
read
that
manifest
over
http
and
like
I
think
it
just
sort
of
reads
the
manifest
every
so
often,
and
I
don't
know
that
we
have
to
curate
that
on.
F
Artifact
hub,
okay,
I
didn't
know
about
this
artifact
hub,
but
I
saw
the
helm
installation
from
that
website.
Mastery
dot
io
like
there,
it
is
like
first
you
have
to
clone,
then
install
from
that
directory.
A
Silly,
it's
sort
of
like
yeah
right
exactly
I
mean
we
should
eliminate
those
instructions,
there's
no
need
to
clone
the
repo.
I
mean
that's
off-putting
for
many
who
would
rather
not
you
know,
who'd
rather,
rather
just
you
need
to
clone
a
repo
to
use
the
home
chart.
If
you
want
to
you
know,
you
don't
even
need
to
clone
a
repo
to
use
the
kubernetes
manifest
you
can
just
use
a
you
know.
A
Http,
you
know,
use
a
url
to
it
so
to
clarify
here
and
provide
a
little
bit
of
context,
especially
raj,
as
you
go
to
potentially
hopefully
maybe
solve
this
issue.
Is
there
are
a
couple
of
considerations
to
take
into
account?
One
is
just
the
current
state
of
things
which
is:
there
are
the
source
code
for
the
helm,
charts
or
or
the
helm
chart,
I
should
say,
is
in
the
main
measuring
repo
under
your
slash,
install
so
yeah
something
something.
A
We're
not
the
location
that
we
publish
the
charts
to
the
chart
to
is
well,
it's
the
meshri.io
repo
under
install
helm
or
something.
So
we
don't.
We
you
and
we
use
this
to
serve
the
small.
We
use
that
github
pages
instance
to
serve
the
small
http
file,
the
manifest
for
the
chart,
and
that
can
change
it's
a
little
bit.
You
know
it's
like
hey.
Why
are
you
doing
that?
If
you've
got
the
source
here,
why
aren't
you
just
building
it
and
publishing
it
there?
A
Originally,
it
was
because
the
github
pages
is
there's
a
different
github
pages
instance
running
in
the
main
mastery
repo
and
it's
for
docs.mastery.io,
but
it
didn't
use
it
previously.
It
was
so
there
was
some
good
logic
as
to
why
there
was
a
segregation
why
we
chose
to
publish
the
chart
over
there
and
leave
docs
here.
A
I
don't
know
that
there
that's
much
of
a
consideration
anymore,
that
that
really
needs
to
happen,
that
we
couldn't
just
have
the
source
and
the
published
chart
in
the
same
repo
or
it's
fine.
If
they
get
left
how
they
are.
There
are
github
action.
I'm
telling
raj
telling
you
some
things
that
you
know
but
just
sort
of
bringing
us
all
up
to
the
same
up,
speed
there.
A
There
are
some
there's
a
pre-written,
github
action,
I
think
from
the
helm
project
itself
that
helps
you
with,
like
you
know,
packaging
your
chart
and
then
publishing
yeah
publishing
it
to
the
same
repo
or
a
different
repo.
So
so
again,
if,
if
we
consolidate
or
not
it
probably
doesn't
matter
now,
avishak
brought
up
a
good
question
and
it
was
actually
one
that
was
brought
up
in
github
discussions
a
little
while
ago.
A
If
I
can
navigate
do
the
the
measuring
repo
we,
you
know
a
little
under
used,
but
you,
but
occasionally
used
is
the
discussion
section
here
and
one
of
those
was
for
this
topic
of
creating
a
release
pipeline
and
asuko.
I
brought
it
up
and
I
don't
know
if
he
had
asked
or
someone
had
asked
somewhere
that
hey.
Maybe
this
is
what
he
had
asked.
A
Was
the
question
of
hey?
Should
we
centralize
all
of
the
should
we
have
central
source
for
I'm
trying
not
to
use
the
word
charts
the
plural,
because
I
don't
know
if
that's
correct,
but
should
each
adapter
have
its
own
definition
of
its
section
of
the
chart
and
then
because
they
rev
individually,
they
are
their
own
components
that
have
their
own
life
cycle
and
they
get
released
independently.
A
A
A
The
third
step
would
be:
oh
hey,
you
know.
Maybe
we
should
go
ahead
and
take
the
individual
sections
of
this
overarching
chart
and
and
place
those
into
other
repos,
so
so
those
the
second
and
third
steps,
I'm
glad
that
rodolfo
is
on
because
we've
spun
back
up
the
continuous
integration
working
group
yeah.
B
Okay,
let's
move
you're
next.
I
Screen
so
they're
still
working
progress,
but
no
the
current
pr,
which
was
involved
regarding
the
update
in
the
s
p,
produce
right.
So
this
was
merch
right
now.
The
changes
which
are
particularly
made
by
first
of
all
few
changes.
The
service
message
message
is
now
redefined
to
service
mesh
and
we
also
added
few
more
things
to
the
definition
of
a
mesh
like
the
version
of
that
particular
mesh
and
labels
and
annotations
that
are
present.
I
I
We
would
also
change
the
way
we
are
defining
our
mesh
in
the
office.
Most
probably
so
I
haven't
spent
a
pr
yet,
but
if
you
want,
I
can
show
you
what
we
are
doing
so
basically,
instead
of
in
on
nutshell.
Basically,
instead
of
sending
a
string
telling
which
particular
mesh
we
are
running,
we
would
use
the
smp
pro
produce
to
define
that
particular
type
and
use
it
everywhere.
As
a
global
standard,
so
yeah
that's
what's
been
going
on
in
the
smp,
protofront
and
yeah.
I
A
Just
a
quick
comment,
and
not
necessarily
something
we
have
to
figure
out
here
or
not,
but
you
know
as
we
go
to
so
the
the
slash
service
protos
for
the
info
health
and
error.
I
I
For
some
reason,
my
internet
is
okay.
Okay,
so
let
me
just
you
want,
I
can
take
you
through
so
so
like
we
are
defining
error
in
a
standard
way,
so
we
could
use
it
everywhere,
which
we
are.
I
Similarly,
if
a
process
is
running,
we
can
define
whether
this
is
running
or
it
is
ideal
or
not,
and
if
you
go
to
info
yeah
basic
info,
so
this
is
just
a
abstract
version
to
define
any
service
which
we
have
right.
So
that's
what
is
being
done
over
here.
I
Oh
actually,
that
we
can
discuss
upon
on
like
before
this.
It
was
present
in
the
mesh
kit
repo
as
we
know,
but
since
we
wanted
to
buff
up
the
smp
spec
2.
So
we
thought
this
might
be
the
place
for
it.
A
I'm
I'm
not
I'm
neither
condoning
nor
rejecting
or
just
just
a
just
a
question
to
yeah.
J
Yes,
michael
here,
I
wondered
a
little
bit
about
the
same
thing.
J
A
You
know
where,
where
the
tests
are
and
their
status,
and
we
were
kind
of
talking
about
where
to
land
the
fact
we
needed
some
some
protos
to
describe
that
and
where
to
land
those,
my
general
guidance
was
like
hey.
If
we're
going
to
be
defining
spec
and
kind
of
protos
and
making
updates
like
you
know,
we
want
to
continue
to
make
smp
a
real
boy
to
borrow
from
pinocchio.
C
Reasons
why
we
will
be
added
this
one
infinity.
One
is
how
to
explain
it's
basically
to
improve
the
importance
of
smp
as
a
project,
and
the
second
thing
is
to
avoid
mesh
kit
dependency
on
on
airport,
because
we
are
using
cuttle
in
learned
file,
which
uses
a
very
deprecated
version
of
flying
group,
which
is
different
from
our
mesh
kits,
which
makes
a
lot
of
difference.
So
you
know,
in
order
to
avoid
that
dependency,
the
dependency
about
it.
We
try
to
move
it
through.
Yes,.
J
Okay,
your
line
was
a
bit
bad
or
maybe
my
line
my
line
was
my
line
was
maybe
breaking
up
a
bit,
but
does
this
mean
that
these
protos
or
similar
protos
would
be
redefined
in
mesh
kit?
Or
what
does
this
mean?
We'd?
Be
importing
the
service
mesh
performance
library
into
adapters,
for
instance,.
I
Most
probably,
we
would
be
importing
the
service
mesh
performance
library
to
the
adapters.
If
you
want
to
use
this.
J
What's
the
what's
the
what's
sort
of
like
the
functional
hierarchy
who
should
know
about
what
just.
C
Am
I
audible
right
now,
yeah
much
better
so
to
answer
that
question?
Basically,
in
an
ideal
case,
we
should
have
had
this
in
a
separate
repo
where
basically
it
should
be
independent
of
smp,
but
we
don't
have
one
right
now
and
the
only
two
options
that
we
have
is
on
on
either
incident
or
mesh
kit
or
smp,
and
we
chose
smp
because
of
the
dependency
conflict.
That
happened
when
using
meshgate.
E
I
So
should
we
create
a
different
grepo
itself
for
this
kind
of
produce
or.
C
J
One
aspect,
one
aspect
is
also
another
possibility-
would
have
been
to
to
have
to
just
duplicate
it
instead
of
importing
the
service
mesh
performance
library
into
say,
service
mesh
adapters,
because
one
thing
is
also
then
untangle
it
if
you
want
to
sort
of
like
remove
dependencies
afterwards,
but.
C
I
And
like
to
add
to
your
point,
I
guess
if
we
go
that
route
even
produce
like
where
we
are
defining
a
general
mesh
itself
like
this
one,
this
also
shouldn't
exist
in
smp
itself.
If
we
are
crea,
if
we
are
planning
on
creating
one
different
draper
for
all
the
pro
tools
defining
basic
general
stuff
right.
J
But
there's
in
other
places
it's
sort
of
more
it's
more
a
dependency
that
you
actually
copy
the
proto
file
and
then
create.
B
Okay
did
also
would
you
like
to
give
us
an
update.
K
K
A
Nice
cool
yeah,
I'm
I'm
mostly
entirely
razzing
raj,
so
good,
yeah,
perfect
everybody's
welcome
to
come,
but
rudolph
is
tracking
a
lot
of
there's
surprisingly,
a
lot
to
do
with
continuous
integration
and
actually
it's
it's
kind
of
dumbfounding
that
we're
as
this
far
along
in
the
project
and
we're
not
auto
publishing
a
home
chart
like
this.
It's
bad.
B
C
C
So
what
conducts
basically
means
is
we
can
have
multiple
configurations
for
for
measuring,
and
in
this
case
we
can
see
the
local
and
the
production
configuration
so
while
running
reset
command.
C
What
this,
what
it
used
to
do
was
to
pick
up
the
latest
blocker
amplifier
and
what
we
needed
to
do
was
to
consider
the
the
channel
and
the
version
of
that
particular
context.
The
current
context
has
been
selected,
so
that
was
the
issue
and
yeah.
We
fix
it
using.
We
pick
up
the
current
context
and
we
check
its
channel
and
we
just
fetch
the
the
compose
file
that
is
corresponding
to
the
version
of
the
current
context.
C
So
it's
not
the
latest
version.
So
if
I
were
to
run
this
before
I
before
we
fix
this
shoe,
it
will
just
pick
up
the
latest
docker
canvas
file.
But
if
I
run
it.
C
So
it
will
pick
up
the
docker
compose
file
that
is
based
on
version.
C
C
We
need
to
have
a
confirmation
where
we
should
ask
the
user.
Are
you
sure
you
want
to
reset
this
reset
the
config
file
reset
the
measurement.yaml
file?
So
that's
another
issue
and
it's
still
a
draft
here.
I
am
still
working
on
it,
but
yeah
you
can
see
in
action
here.
So
are
you
sure
you
want
to
continue
and
if
I
press
a
y,
then
it
will
reset,
and
if
I
press,
then
it
will
show
an
about
temperature
message
which
needs
to
be
changed.
In
my
opinion,
maybe
change
it
to
something
different.
C
C
A
Is
anybody
else
here
looking
to
work
on
measuring
ctl,
it's
a
golang
based
cli.
It
uses
cobra
as
its
framework.
It
uses
viper
a
little
bit
as
well,
there's
a
bunch
of
stuff
to
do
in
there
and
that's
why
I
asked
so
for
those.
A
A
Any
other
feedback
for
navendu
just
wait
way
to
tear
through
it.
Then.
J
I
think
it's
very
nice,
it's
very
good
to
get
the
confirmation
first
reset
in
place.
I
wonder
whether
it
could
be
useful
to
just
take
a
backup
of
the
configuration
that
is
to
that
is
replaced,
meaning
you
know
just
make
a
copy.
J
J
A
Let's
think
about
that,
for
for
a
minute
like
hey,
why
wouldn't
we
we're
like,
like
you
know,
take
it
takes
up
almost
no
disk
space.
It
could
prevent
someone
from
getting
really
upset
about
losing
their.
You
know
their
customizations
yeah,
it's
one
more
thing
for
us
to
potentially
sort
of
manage,
but
if
we
don't
put
a
lot
of
guarantees
around
it,
if
we
just
every
time
that
every
time
that
they
reset
their
config,
we
just
push
to
it.
A
The
the
file
name
is
config.yml,
so
we
just
maybe
push
to
like
config.yml.bak,
and
we
just
keep
one
copy
and
we
just
like
you
can
go
one
one
back
in
history
or
something
if
we
keep
it
fairly
simple.
It
doesn't
doesn't
cost
that
much
in
terms
of
our
time
to
provide
the
feature.
J
Yes,
that's
something
that's
another
line
size
out.
On
the
other
hand,
you
know
we
are
asking
for
the
next
set.
You
know
why?
Wouldn't
we
we're
asking
for
an
explicit
confirmation?
Are
you
really
sure,
but,
but
still
you
know,
sometimes
one
press
is
yes
a
bit
too
quickly.
I
do
so
it
could
be
practical,
but
I
wouldn't
sort
of
make
a
big.
You
know
just
one
one
backup
copy
one
version
back,
not
nothing.
Fancy
see.
A
The
nice
thing
is
that,
like
with
that
said,
for
my
part
with
that
type
of
a
suggestion,
and
please
everyone,
that's
on
the
call
like
you
all
use
software.
That
does
this
kind
of
a
thing.
So
you
know
you
all
have
a
valid
opinion
here,
like
from
my
perspective,
if
there,
if
an
auto
backup
was,
you
know,
saved
each
time
well,
you
might
almost
be
able
to
just
forgo
the
question.
Maybe
because,
because
you
just
say
great,
your
command
has
been
executed
and
it's
been
reset
by
the
way.
J
I'm
sorry
it's
unmuting
myself,
I'm
muting
myself,
because
maybe
you
would
like
you
would
like
to
have
a
silent
option.
J
Yeah
yeah,
exactly
because
maybe
you
would
like
to
run
this
in
in
a
ci
cd
pipeline
or
see
a
pipeline,
then
you
might
have
to
have
a
silent
option
and
then
you
would
still
have
possibility
to
have
back
up
just
in
case
I'm
just
like
improvising.
I
don't
know
what
did
I
say.
A
Yeah,
actually,
that's
a
good
point
that,
like
hey
you,
I
would
say
from
my
perspective,
irrespective
of
whether
or
not
a
backup
is
taken,
which
I
think
is
generally
a
good
idea
like
it's
not
harmful
it
doesn't.
You
know
like,
irrespective
of
that
there
we
probably
should
ensure
as
a
principle
that
any
time
that
there's
an
interactive
prompt
there
is
also
a
dash
dash
skip
flag
or
there
there's
some
mechanism
by
which
those
that
are
scripting
the
cli
can
now
granted
if
they're
scripting
the
cli.
A
Yes,
they
could
also
script,
and
you
know
answering
yes,
but
but
it
might
be
just
more
convenient
and
we'd
be
able
to
address
it
sort
of
more
holistically.
If
there's
a
gl,
maybe
it's
a
global
flag
or
it's
a
command
specific
flag.
That's
it
wouldn't
be
necessarily
skip,
it
would
be
skip
or
silent
or
it
would
be
silencers
or
something
like
that.
A
B
All
right,
I
took
a
notification
system.
B
Hopefully
that
should
help
all
right.
We
almost
said
time
here
we
were
supposed
to
do
a
walk
through
the
left
ng
site,
but
well
we
can
do
it
next
week.
That
would
probably
be
better
because
we'll
have
a
couple
of
other
things
sorted
by
then.
Okay,
apart
from
that,
I
think
that's
it.