►
From YouTube: Layer5 Community Meeting (Sept 17th, 2021)
Description
Layer5 Community Meeting - Sept 17th, 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
Well,
so
we're
just
kind
of
hanging
out
for
a
moment
until
a
couple
more
folks
join,
but
while
we're
waiting,
I'm
ultimately
going
to
hand
off
hosts
here
to
navindu
but
I'll
say,
while
we're
waiting,
we
do
have
a
community
tradition
of
saying
hi
to
newcomers
getting
to
know
everybody,
and,
and
so,
if
you've
got
any
newcomers
on
the
call
now's
your
chance
to
say
hi
and
introduce
yourself.
B
A
Luis
nice
to
have
you
yeah
yeah,
but
but
yeah
so
luis,
there's
there's
a
couple.
It's
great
to
have
you
there's
a
couple
of
things
to
say
to
to
make
sure
that
you
feel
warmly
welcomed.
One
of
those
things
is
the
if
it
so
happens
that
that
you
are,
in
addition
to
english,
also
speak
spanish.
A
C
A
Good
cool
by
the
way
since,
since
we're
getting
to
know
luis
I'll
also
say
well
actually
luis,
let
me
let
me
put
you
on
the
spot.
If
I
can
this,
will
this
will
really
break
the
ice
that.
D
A
B
A
Yep,
nice
well
hey
by
the
way,
so
for
the
last
couple
of
years
we
I
was
down
in
guadalajara.
Where
was
I
guadalajara?
No
was
it
a
heck?
I
don't
know
a
couple
years
ago
down
giving
a
workshop
in
person,
it
was
fantastic,
turns
out,
turns
out
that
it
was
right.
It
was
timed
very
well
with
independence
day,
so
there's
a
lot
of
tequila
that
happened
that
weekend
for
me,
but
yeah
next
year.
A
Next
year
we
got
to
participate,
we
participated
virtually
and
so
and
then
this
year
we're
participating
again
and
it
turns
out
jesus
and
rodolfo
rodolfo
martinez
between
the
two
of
them
and
then
also
boy,
and
is
it
antonio
boy?
This
is
embarrassing.
I
think
it's
antonio.
I
have
to
go.
Look
his
name
up.
It
escapes
me,
but
he's
contributed
to
the
mess
redox
a
lot
and
and
so
they're
this
time,
they're
hosting
they're,
they're
gonna,
introduce
people
to
mashari
and
to
the
projects
here.
A
So
that's
that's
fantastic
anyway,
really
nice
to
have
you.
I'm
excited
that
that
I
get
to
work
on
my
spanish
so.
C
A
Cool
okay,
well
good!
Well,
vendi
can
I
can
I
hand
it
back
to
you.
E
Yes,
thanks
lee
before
we
get
on
with
the
agenda,
is
there
anyone
else
new
on
this
call?
This
is
your
chance
to
introduce
yourself
to
the
community
and
get
introduced
to
the
community.
So
if
you
are
new
on
this
particular
call,
oh
darren
go
ahead.
A
Good
darren
will
introduce
in
chat
fair
enough.
E
All
right,
I
don't
think
there
is
anyone
else
who
is
new,
so,
let's
get
on
to
the
topics
for
today
magna.
Do
you
like
to
talk
about
the
ring
release
and
the
blocks.
F
Yeah
sure
so
right
now
we
have
around
four
blog
posts
that
we
need
more
people
in
for
are
waiting
for
more
volunteers.
For
that
and
I'll
just
give
me
a
minute
I'll.
Just
let
you
know
the
ones.
G
So
since
many
people
are
new
I'll
just
give
a
overview
about
what
this
is,
so
we
are
gonna
have
version
0.6.0
release
soon,
and
so
we
are
preparing
our
release
block
as
well
as
release
note
for
that,
and
we
have
highlighted
our
features
and
we
are.
We
want
people
to
write
blogs
on
it.
So
this
is
the
epic
on
it
and
we
have
all
the
features
listed
here.
G
So
all
of
them,
except
four
of
them,
have
been
assigned
to
people
and
most
of
them
some
of
them
have
completed,
and
some
are
yet
to
finish.
But
we
have
four
unassigned
features.
So
if
anyone
would
like
to
write
blogs
on
this,
please
feel
feel
free
to
go
check
out
and
we,
you
might
want
to
get
a
testimony
to
yourself.
G
So
I'll
also
mention
the
four
which
are
the
pending,
so
we
have
applications
that
spending
and
the
filters
that
spending
and
mesh
map
beta
and
dynamic
management.
So
there
are
four,
so
please
feel
free
to
go
through
that
link
and
get
yourself
assigned.
If
you
are
interested
to
write
down
I'll
put
the
link
on
the
chat.
A
Nice
to
just
recap
that,
briefly
for
everyone,
that's
on
the
call,
so
mesherie
is
nearing
the
v06.0
release.
The
goal
is
some.
You
know
toward
the
end
here
in
a
couple
of
weeks
like
toward
the
end
of
the
month,
certainly
in
advance
of
kubecon
will
this
will
be
mescheri's
first
kubecon
as
a
member
project
as
such
we'll
have
office
hours.
That
we'll
be
sure
that
all
of
you
are
aware
of,
and
probably
many
of
you
well.
Any
number
of
you
will
be
invited
to
participate
and
talk
about
your
engagement
in
the
project.
A
A
So
so
that's
good,
but
on
the
blog
post
that
zane
is
talking
about
so
as
as
the
we
prepare
for
the
v060
release,
there's
a
lot
of
things
to
write
up
and
tell
the
world
about
last
time
when
we
did
the
v050
release
between
you
know,
I
don't
know,
I
can't
recall-
and
I
hope
I
don't
miss
anyone
but
largely
asuko
li
who's,
a
mystery
maintainer
and
michael
gefeller.
Another
mystery
maintainer
had
put
a
given
a
heavy
hand
to
writing
up
functionality
that
was
released,
and
then
it
was
a
lot.
A
Technically,
it's
it's
probably
a
major
release
because
we're
adding
architectural
components
but
since
we're
not
to
a
1.0,
yet
we're
we're
being
reserved
with
the
release
numbering.
A
So
what
zane
is
saying
is
here's
an
opportunity
to
one
get
your
name
out
there
on
on
the
v060
release,
whether
you
contributed
to
the
code
in
that
area
or
not
that
doesn't
matter
like,
but
but
writing
it
up
or
taking
a
snapshot
or
just
participating
and
trying
to
kind
of
get
get
the
word
out,
whether
that's
in
mesh
redux
or
in
a
couple
of
different
blog
posts
on
these
topics.
A
So
actually
right
now,
I
don't
see
a
name
necessarily
against
two
github
actions
that
were
created
in
this
release.
Time
frame-
and
maybe
there
are
people
that
are
on
top
of
those
already.
But
but
those
are
you
know
in
concept,
simple
enough
that
anyone
can
go
digest
what
those
are
and
and
add.
If
you
write
a
few
things
about
it,
so
so
jump
in
like
hey
the
whole.
A
All
of
what
we
do
here
is
community
driven,
so
so
yeah,
megana
and
zane
are
championing
and
organizing
the
variety
of
things
that
need
to
be
written
up
and
described
in
this
upcoming
release
so
feel
free
to
engage.
E
Yeah
thanks
for
that
and
the
issue
that
I
just
showed
here
is
on
the
comments
so
feel
free
to
jump
there
and
engage.
There
are
many
child
issues,
so
you
can
pick
any
of
these
up
and
make
a
write-up
about
it.
Adding
to
that.
Our
next
item
is
on
starting
a
new,
build
and
release
meeting.
E
I
mean
a
cia
meeting
that
happens
every
every
other
thursday.
So
since
our
initiatives
nca
can
be
linked
to
measure
and
we
have
an
upcoming
release
coming
up.
What
we
are
proposing
to
do
is
is
to
convert
that
meeting
into
a
build
and
release
meeting
so
starting
next
thursday,
we
will
have
a
built-in
release
meeting,
with
the
focus
on
making
sure
that
measure
is
ready
for
release.
So
we
will
be
talking
about
test
strategies,
writing
unit
test
and
making
sure
that
everything
is.
E
Before
we
before,
we
make
the
next
release-
and
there
are
a
couple
of
dogs
linked
here
and
I
will
send
out
an
update
soon.
So
if
you
are
subscribed
to
the
community
calendar,
you
should
receive
an
update
about
this
meeting.
So
this
is
just
an
fyi
before
that
and
we
are
also
proposing
to
conduct
this
meeting
at
a
new
time.
So
the
current
time
is
1
pm
central
and
6
p.m.
E
Gmt
11
30
pm
ist,
so
we
can
maybe
like
if,
if
if
most
of
us
in
the
community
want
a
change
of
time,
maybe
we
can
do
that
like
I
know
for
some
most
of
the
folks
here
it
is
quite
late
the
time
so
what
we
can
do
is
we
can
have
a
poll
in
slack
or
you
know,
in
one
of
our
mailing
lists
and
what
we
can
do
is
we
can
try
to
come
up
with
a
new
plan.
E
A
A
The
service
mesh
patterns
project
doesn't
have
a
lot
of
workflow
or
github
actions.
Yet,
ultimately,
it
will.
A
Having
said
that,
there's
been
a
lot,
that's
been
automated
and
that's
good,
there's
more
to
be
automated
and
actually
much
of
that
automation
needs
to
happen
around
qa
around
quality
and
that's
one
of
the
things
that's
been
on
the
messiah
roadmap
for
a
while,
as
we
turn
the
corner
as
we're
over
the
v0.5,
the
halfway
mark
to
1.0
as
we're
over
that
hump
begin
to
establish
some
some
practices
toward
better.
You
know
toward
higher
quality
right
as
a
matter
of
fact,
so
I
don't
know.
A
If
he's,
let
me
see
if
he's
on
the
call,
I
don't
want
to
embarrass
it,
but
so
there's
a
principal
architect
who
just
reached
out
35
minutes
ago
from
comcast
who's
long
been
a
friend
of
his
name
is
jeffrey.
I
mean
he's
long
been
a
friend
of
mesherie
and
of
layer,
five
of
the
stuff
that
you
all
are
doing
here.
He
was
asking
for
references
of
measuring,
deployed
in
production,
and,
and
so
he
works
at
a
service
provider
that
service
provider
uses
more
than
one
mesh.
A
He's
long
been
interested
in
what
we're
doing,
and
apparently
it's
gaining
steam
there.
His
suggestions
and
things
that
they
should
do,
and
so
my
point
is
that
increasing
the
quality
of
the
project
becomes
more
and
more
important
as
we
as
more
and
more
people
look
to
adopt,
and
so
that
doesn't,
as
a
matter
of
fact,
increasing
quality
shouldn't
slow
us
down
in
terms
of
the
functionality
that
you
all
are
creating.
A
As
a
matter
of
fact,
it
should
speed
it
up.
There's
any
number
of
you
that
engage
with
users,
helping
or
or
other
contributors
you
help
them
overcome,
bugs
or
overcome
environment
issues
like
issues
in
their
environment,
the
less
time,
the
less
bugs
that
we
have
the
less
time
that
we
you
all
spend
on
that
activity,
which
actually
means
more
time
for
creating
new
features.
A
So
so
good.
So
the
venue
was
just
saying
we're
going
to
take
the
continuous
integration
meeting,
expand
it
beyond
just
build
to
build
and
release
and
then
focus
a
bit
on
release
to
get
a
test
strategy
written.
There
is
an
existing
test
plan,
so
the
test
strategy
would
talk
about
things
like.
Oh,
are
we
going
to
use?
Do
we
need
a
certain
unit
test
percent
coverage
or
what
are
the?
What
tooling
does
the
integration
test
use.
A
Cypress
is
an
example
of
one
of
the
tools
that
the
project
uses
to
help
facilitate
integration
tests,
and
so
the
test
strategy
is
about
the
approach.
The
test
plan
ends
up
being
a
release,
specific
set
of
individual
and
actually
bendy.
Do
you
mind
if
you
don't
mind
to
go
to
the
test
plan?
It's
a
list
of
specific.
A
Behaviors
or
features
to
verify
over
time,
this
thing
grows
because
more
features
get
added
and
over
time,
what
we
want
to
do
is
collectively
automate
these
things
like
identify
how
much
test
coverage
these
areas
have
and
identify.
You
know
both
in
terms
of
integration
tests
and
things,
integration
unit
tests,
so
yeah
there's
just
some
additional
background
as
to
what
that
other
meeting
is
about
it
meets.
A
A
60,
there's
way
more
than
60
things
that
you
can
do
with
measuring
so
there
there
are
additional
tests
to
define
eventually
here
shortly,
we'll
be
having
pow-wows
or
working
sessions.
Where
we've
been
doing
this
for
measuring
ctl
actually
did
does
someone
other
than
navendu
or
li?
Does
anyone
want
to
talk
about
how
those
nashville
ctl
ph?
Maybe
do
you
want
to
talk
about
the
measuring
ctl
bug
smashing
sessions?
We
would
basically
use
a
similar
format
for
release
readiness
sessions.
A
I'm
not
seeing
anyone
else
to
pick
on
necessarily
so
the
point
is
you
just
schedule
sessions.
People
come
on.
People
put
their
name
next
to
one
of
the
rows
here
or
multiple
of
the
rows,
and
just
verify
that
that
behavior
is
that
things
are
still
working.
Well,
yep
these
these
are
ripe
for
automation.
There
are
many
of
these
test
cases
that
are
already
covered
by
automation.
A
Really
a
great
place
for
well
those
that
are
into
devops
or
into
administration
like
you
can
be
really
impactful
here
in
the
project.
There
are
many
people
who
join
the
community
who
want
to
contribute
or
write
code
or
or
and
less
and
and
we
need
some
powerful
users,
those
that
are
putting
on
their
user
hat
and
being
really
finicky
being
really,
you
know
so
that
we
can
identify
issues
with
the
project.
E
Thankfully,
so
this
area
is
open
for
our
participation,
so
feel
free
to
jumping
on
slack
or
talk
to
us
to
get
your
hands
on
these
writer
next
up.
We
have
our
topic
about
mesh
map,
so
mesh
map
is
one
of
those
projects
that
we
have
been
working
on.
That
is,
that
has
not
yet
been
released
to
the
general
general
set
of
users.
E
So
we
have.
We
have
a
mesh
map
alpha
program
that
is
running
right
now,
to
engage
with
users
and
help
improve
mesh
map
or
find
some
bugs
or
improve
user
experience
and
all
those
stuff.
So
we
have
an
alpha
program
opened
up
so
before
we
talk
about
that,
we
have
a
demo
on
meshed
map
doctor
who
will
be
demoing,
but.
E
D
Yep
so
as
nevermind
was
mentioning,
that
is
a
designer
as
well
as
a
visualizer,
so
what
you
you
can
do
using
mesh
map.
At
least
I
mean
what
we
have
currently
very
much
function.
Is
you
can
you
can
design
your
service
mesh
I
right
now.
I
I
only
have
the
is
your
adapter
running,
so
that
is
showing
only
istio
service
mesh
the
components
of
the
css
mesh,
so
you
can
see
all
of
the
components
are
still
service
machines.
D
If
you
have
my
message
supports
out
of
the
box
of
many
versions
of
htr.
As
you
can
see,
so
you
can
select
any
version
that
you
want
to
right
now
the
default
is
1.98
if
you
would
have
more
than
one
rafter
running.
Unlike
me,
I
have
only
steered
after
running
off
mission
that
is
showing
only
one
one
component
dropbox.
You
will
have
min.
Let's
go
to
the
patterns
in
patterns.
What
you
can
do?
We
have
many
patterns
here.
D
D
What
this
is
basically
representing
is
a
is
the
is
what
your
cluster
would
look
like
once
you
click
on
deploy,
so
we
have
this
sample
app
gateway
and
then
virtual
service.
So
we
are
directing
here
that
how
the
cluster
would
look
like
what
these
applications,
what
these
applications
are
supposed
to
look
like.
So
if
you
would
click
on
it,
if
you
want
to
edit
something
you
can
go
ahead
and
edit
the
details,
and
once
I
click
on
different,
which
I'm
not
sure
refresh
it.
D
But
if
I
click
on
this
one,
it
will
ensure
that
the
state
of
the
cluster
looks
exactly
how
this
particular
architecture
diagram
is.
So
it's
a
in
concept.
It's
it's
like
a
architecture
diagram,
but
far
more
powerful
than
what
the
design
like
for
a
far
more
powerful
than
any
of
the
architecture,
designers
that
anyone
have
used,
because
this
can
completely
tr.
This
can
do
bi-directional
translation,
so
what
we
have
here
is
translated
into
the
into
the
actual
cluster
state
as
well
as
if
you
would
go
to
the
visualizer
right
now.
D
Visualizer
is
heavily
under
under
development.
So
but
still
we
should
be
able
to
see
the
state
of
the
blister
in
here.
I
don't
know
it's
taking
a
while.
D
So
the
deal
that
is
that
is
being
shown
here
is
coming
from
missing.
Mesh
thing
is
one
of
the
components
that
misery
actually
points
deploys
to
your
cluster.
So
let's
see
the
logs
of
the
items
that
it
is
discovering.
D
So
these
are
the
logs
that
are
coming
from
mesh
sync
4..
If
a
pod
has
more
than
one
container,
that
is
something
also
the
visualizer
supports.
We
can
also
get
in
the
interactive
terminal.
The
log,
as
probably
everyone
can
see
the
logs
are
streaming.
It
is
also
capable
of
detecting.
If
something
was
changed
in
the
in
the
state
or
not.
If
it
was
only,
then
it
will
send
the
update,
or
else
it
will
skip
that
thing.
This
is
a
so.
D
This
is
a
visualizer
and
as
we're
showing
this
is
the
designer
you
can.
You
can
design
new
patterns
right
from
here.
So
let's
say
you
want
to
drop
in
a
destination
rule.
Here's
the
essential
rule.
You
can
control
the
ear
stuff
from
from
this
particular
form
and
delete
it
or
basically
do
any
kind
of
designing
right
in
the
designer.
E
Thank
you
utkarsh
for
the
demo,
so
this
is
mesh
map
and,
as
I
mentioned
before,
you
can
sign
up
to
test
out
mesh
map
in
the
alpha
program
and
you
can
find
like
you
can
just
add
your
names
in
the
meeting
minutes.
E
All
right,
yep,
thanks
again
utkarsh,
that
was
a
cool
demo.
Let
me
just
share
my
screen.
Okay,
so
deborah
would
not
be
able
to
join
us
today.
So
basically,
we
wanted
to
showcase
this
new
organization.
Read
me
so
github
has
just
added
this
new
feature
and
we
have
a
new
readme
in
the
file
and
basically
it
gives
an
idea
about
all
the
different
projects
that
we
do
here
in
life.
E
So
these
are
all
the
projects
as
well
as
how
we,
how
we
handle
community
in
in
laravel.
So
you
can
take
a
look
at
the
look
here
and
like
if
there
are
any
changes
that
you
suggest
feel
free
to
talk
about
it
in
slack
or
on
github,
open
up
an
issue.
If
you
wanted
to
want
to
add
something.
E
All
right,
moving
on
to
the
next
topic,
anita
anita,
will
be
doing
a
review
on
the
clarify
community
handbook
anita.
Would
you
like
to
talk
about
it.
H
Been
an
exciting
journey
so
far
trying
to
put
up
this
handbook
and
yeah
from
everyone
that
contributed.
We
want
to
thank
you,
first
of
all,
like
thanks
to
everyone
that
put
their
hands
together
on
this
handling
together
and
yeah.
They
will
create
a
little
something
up,
because
this
looks
way
better
than
what
I
actually
pictured
so
that
yeah.
This
is
an
awesome
job.
So
far
the
handbook
is
coming
together.
H
H
It's
so
far,
goodness
is
supposed
to
update
this.
She
hasn't
made
any
updates,
yet
I
reached
out
to
her.
She
said
I
should
create
the
pull
request
before
the
end
of
today,
so
we
should
be
expecting
a
request
on
this,
but
so
far
the
text
I
did
the
fonts
are
still
disturbing.
I
mean
fonts
is
conflicting
with
the
original
fonts
layer,
five
fuses,
and
that's
also
disturbing,
and
also
I
noticed
that
there's
very
little
space
on
the
edge
of
this.
A
To
ad-lib,
while
she
unfreezes
well,
I
guess
it's
somewhat
self-explanatory,
like
there's
a
bunch
of
resources
in
the
community,
and
those
resources
have
been
described
in
various
google
docs
and
in
various
readmes
and
and
so
anita
and
ruth
have
been
leading
the
charge
to
try
to
bring
a
lot
of
that
info
into
an
ease
and
a
central
location.
One
that's
easily
referenceable
and
it's
looking
pretty
good
a
lot.
A
A
lot
of
folks
have
contributed
to
it,
and
so
some
of
that
same
information
can
be
exposed
in
the
github
org
overview
or
the
the
other
one
that
I
can't
remember
if
dabo
priya
just
showed
it,
but
but
anyway
anyway,
it's
great
yeah
this
one.
This
one
actually
can
get
even
more
fancy
potentially.
A
But
it's
things
like
the
this.
Is
things
like
this
and
the
layer
5io
site
that
are
important
to
have
well
curated,
because
they
end
up
representing
much
of
the
work
that
goes
on
in
the
here.
They
end
up
being
kind
of
a
single
point
of
reference
for
all
those
things
so,
and
I
must
say
that
the
site
looks
pretty
fine.
A
So
anita
you're
back,
I
was
just
ad-libbing.
H
Okay,
yes,
so
mostly
what's
left,
is
to
include
links,
probably
of
updates
on
a
few
grammar
grammatical
errors
and
yeah.
It
looks
better
than
what
we
have.
H
It's
an
issue
that
makes
update
with
organized
so
if
you
could
jump
back
and
forth
and
also
we
have
to
add
a
link
to
each
of
these
like
they
have
to
profess.
You
need
links
to
that,
because
if
you
go
back
to
this,
you
still
have
to
click
another
link
and
that's
like
extra.
They
actually
have
direct
internships
here.
Who's
curious
about
them
can
just
quickly
click
on
it
and
go
there
and
make
a
review
and
about
the
internship
program.
H
Is
there
a
way
we
can
like
highlight
person
that
maybe
participated
in
internships
from
for
a
particular
section.
H
If
that's
possible,
because
I
I
feel
it
would
actually
be
nice
to
see
that
we
were
able
to
participate
in
internship
on
the
later-
it's
really
nice
to
put
out
there
too
and
yeah.
A
Definitely,
there's
yeah,
there's
a
nice
graphic
about
mescheri
being
the
number
one
most
popular
lfx
internship
as
well
for
all
of
the
linux
foundation,
projects
which
include
all
of
the
cncf
projects
which
like,
but
that
would
be
that's
something
to
take
pride
in
to
to
put
in
there
as
well.
So
it's
nice,
it's
really
great
by
the
way
so
of
what
anita
like
it's
like,
basically
implicit
to
all
of
the
things
that
are
being
discussed
today.
A
If
it's
not
clear
to
you,
there's
sort
of
an
implicit
call
for
participation,
so
anita
has
had
any
number
of
people
contributing
to
this,
and
there
are
some
undone
things.
It's
really
close,
but
it's
a
great
that's
a
great
place
to
go,
jump
in
and
contribute
it's
it's
actually
for
anyone
who's
relatively
new,
like
it's
a
great
read
anyway,
there
are
many
things
that
are
done
in
the
community
and
and
most
of
them
they
follow
the
same
path.
A
The
same
paradigm
of
they
are
open
opportunities
to
you
so
go
take
the
opportunity,
so
let
go
and
if
you
don't-
but
if
you
don't
know
about
it
like
go,
go
read
through
the
handbook.
There's
a
lot
of
stuff
going
on
if
you're
into
rust,
there's
some
rustling,
that's
being
tossed
around
and
being
done
if
you're
into
c,
plus
plus
there's
a
there's
a
project
for
that,
if
you're
into
golang,
if
you're
into
react.js,
if
you're
into
it
like
there's,
there's
a
lot
of
things
are
going
on.
A
So
there's
a
lot
of
things
that
are
not
don't
have
to
do
with
code
as
well
and
there's
a
number
of
you
on
the
call
who
are
focused
on
non-code
things.
They
are
most
impactful,
so
so
have
a
read
and
give
give
anita
some
feedback
and-
and
then
let's
get
this
sucker
published
yeah.
H
E
If
next
is
about
the
binary
place,
would
you
like
to.
G
Yeah
sure
I'll
share
my
screen
yeah
sure,
so
we
are
going
to
put
in
a
minus
release
announcement.
So
right
now
I
have
just
added
the
release
notes,
starting
from
v4
5.48
to
5.57.
G
There
is
a
lot
of
release
notes
like
especially
in
the
general
part,
so
I
have
just
cut
out
some
and
put
in
a
few
major
ones,
and
also
we
need
to
think
about
the
feature
highlights
we
might
want
to
add
connection
with
that
again
considering
there
have
been
a
lot
of
changes
in
the
connection
wizard
and
we
can
also
put
in
the
alpha
program.
Okay,
like
we
can
put
it
in
the
alpha
program,
call
out
here
as
well.
G
A
So
this
is
another
yeah
there's
another
great
great
example
of
non-code
things.
Non-Code
things
to
go
do
so
right
now,
when
a
measuring
release
is
made,
there's
no
email
that
automatically
goes
out
and
lets
people
know
that
hey
maybe
they
should
go
update
their
system.
Maybe
they
should
try
out
the
new
features
there's
so
so
jamie
was
asking
about
workflow
earlier
this,
the
one
of
the
goals
for
this
for
the
mind-
I
guess
it's
technically
not
in
mind,
for
these
small
small
releases-
is
to
have
those
released.
A
The
the
publishing
of
an
email
like
this
to
be
automated,
because
the
way
that
the
release
notes
are
collected
that
that's
in
an
automated
way
so
sending
out
an
email
using
a
github
action,
pretty
easy
to
do
so.
Ultimately,
this
type,
this
these
smaller
releases,
can
have
automated
emails,
go
out
that
are
html
formatted
and
look
pretty
decent.
A
Yeah,
but
in
the
meantime,
also
for
the
larger
releases,
there's
a
bunch
of
active,
we
bet
with
their
they're
over
3000
people
subscribed
to
the
community
mailing
list
and
we
barely
let
them
know.
What's
going
on
like
there's
a
lot
of
you
that
have
done
some
really
neat
things
really
neat
things
darren
is
fixing
the
mystery
operator
which,
like
who
knows
how
how
long
like
we
never
had
the
helm
deployment
of
it.
Working
like
it
should
be.
So,
thank
goodness
darren
is
here
so,
but
that's
actually
something
to
talk
about.
A
It's
like
what
is
the
messaging
operator.
What
are
the
two
custom
controllers
that
the
custom
controllers
that
are
inside?
How
did
that?
How
does
that
work?
My
hope
it,
and
so
like
any
email
on
that
it
would
be
educational
to
a
lot
of
folks.
Amia
was
just
asking
about
some
of
that,
like
hey,
what
are
these
components
and
what
do
they
do?
There's
a
lot,
that's
written
in
measuring
docs,
but
it's
also
nice
to
get
bite-sized
chunks
in
your
mailbox
about
how
things
work.
A
Some
of
you
tanooge,
I
don't
think
he's
on
the
call
at
the
moment
he
has
done
a
lot
with
adobe
after
effects
so
helping
curate
small
video
clips.
It's
really
helpful
if
you're
like
me,
you're
a
lazy
reader
and
you
enjoy
a
video
more
than
you
do
reading.
So
we've
got
very
little
videos,
there's
another
opportunity
to
jump
in
and
do
some
things
yeah.
A
A
Logs
of,
what's
all
been
changed,
if
you
can
dissect,
if
you
can,
if
you
have
enough
context
for
what
the
heck,
adding
loading
spinner
means
or
whatever
any
of
those
mean,
but
what's
even
more
helpful
is
when
someone
like
aditya
here
is
doing
or
anyone
else
on
the
call
is
able
to
write
it
write
a
paragraph
like
to
describe
some
new
thing
so
that,
like
the
mouse
right
now
was
on
the
last
step
of
the
connectivity
wizard
the
connection
wizard,
it
was
the
finished
step.
Well,
what
is
that?
A
A
These
are
things
that
are
open
to
you
all.
So
not
only
are
all
of
you,
hopefully
learning
collectively
as
we're
going,
but
also
part
of
the
like
intentional
goal
here
is
that
I
don't
know.
If
I
don't
is
that
many
of
you
are
advancing
through
either
through
your
careers
or
through
your
through
recognition
of
things
that
you've
done
become
this
community
and
is
very
much
so
it
operates
differently
or
a
bit
differently
than
others.
Like
it's.
It's
about
you,
it's
about
elevating
the
works
that
you
do
so
go.
A
Take
advantage
of
writing
a
blog
post
and
getting
it
out
there
there's
a
number
of
people
who
aren't
in
the
community
anymore,
because
they've
been
hired
away
because
of
the
the
works
that
they've
done
here
so
and
that's
a
that's
a
beautiful
thing.
Some
people
get
hired
away,
but
still
stick
around.
There's
a
couple
of
you
that
are
on
the
call
right
now
that
that
is
the
case
and
that's
a
wonderful
thing
that
only
that
only
reinforces
that
those
individuals
are
still
being
fed
or
still
still
enjoy.
What's
going
on.
A
And
that
concludes
our
program
for
the
day,
I
think,
does
anyone
anyone
have
anything
else.
They
want
to
chat
about.
I
Hey
lee,
I'm
back
with
audio
okay,
so
I
have
a
question
about
the
the
hand
shot
thing.
I'm
not
sure
if
I
should
ask
here
or
wait
for
the
next,
like
the
mastery
cto
meeting.
J
I
So
yeah
for
the
hem
shot
for
those
who
don't
have
the
contest.
Basically,
there
are
some
users,
but
also
lee
reported
that
the
headshot,
the
mastery
operator
hemshot,
is
basically
broken
because
of
the
version
upgrade
from
b1
beta1
to
re1.
So,
oh,
by
the
way
I
forgot
to
introduce
myself,
I'm
a
new
member.
I
So
I
tried
to
fix
it
and
then
I
realized
there
are
some
issues
other
than
the
worsening
of
the
hem
shot.
So
the
change
that
I
make.
Basically,
I
there's
another
pr
that
in
the
mesh
sync,
because
that's
where
the
no
the
battery
operator,
because
that
that's
where
the
crds
are
generated,
so
I
also
submitted
a
pr
here.
I
So
basically
what
this
api
is.
I
basically
upgraded
the
controller
gen
version
from
3.0.3.0
to
0.6.1
so
that
we
can
use
the
existing
make
command
to
update
the
crd
here
for
the
broker
and
then
for
the
mesh
sync,
I
believe,
yep
and
then
I
just
basically
copy
them
over
to
the
2d
symmetry
operator,
hem
shots,
and
then
there
we
have
this
pr
in
the
mastery
and
that
fakes
part
of
the
problem,
so
that
you
know
we
can
see
all
the
parts
are
getting
deployed
and
installed
into
a
cluster.
I
But
then
I
think
one
of
the
maintainer
pointed
out
when
issues
is
that
the
the
broker
and
the
meshing
messaging
part.
They
are
not
president
in
the
cluster
and
then
I
I
took
a
look
at
how
the
the
mesh
ctl
mastery
cto
is
implemented
and
then
the
way
it
it
install
everything.
Is
it
points
to
the
emo
files
like
this
one?
It
has
you
know
these
samples,
there's
the
broker
and
the
messaging
to
do
the
installation
for
broker
and
msync,
but
we
are
missing
these
two
in
the
mastery
hem
chart.
I
I
A
A
Yes,
darren,
yes
like
there
was
so
one
of
the
prior
maintainers
who's
about
he's
about
four
days
away.
He's
got
two
months
of
inactivity
and
it's
about
to
hit
so
his
maintainer
role
will
open
up
next
week.
They're
really
really
nice,
guys
just
you
you,
but
yeah.
There
was
so
part
of
it.
Part
of
the
yes
is
the
short
answer.
Part
of
the
thought
process
here
historically
had
been
that
there
was
well.
You
know
what
let
me
not
take
you
through
it,
because
I
don't
think
it
really.
A
It
doesn't
really
matter
yeah,
it's
basically
an
oversight
or
an
undersight
of
like
not
not
ensuring
that
the
great
the
definitions
are
created,
but
there's
no
inst,
no
custom
resources
actually
defined
and
yeah.
Surprisingly,
it's
taken
us
this
long
to
identify
that.
That's
an
issue
like
that.
That
issue
has
plagued
a
couple
of
deployments.
A
As
a
matter
of
fact,
there
was
well
there's
a
user
from
personal.ai,
which
is
a
young
startup
they're
doing
some
some
cool
things
they're
trying
to
deploy
in
eks
and-
and
this
exact
issue
was-
was
the.
I
A
I
don't
think
he
took.
You
won't,
find
disagreement
here,
you're,
right
and
and
you're
actually
looking
at
the
right
spot
to
have
that
defined
and
yeah.
We
would
like
to
converge
on
helm
as
like
between
manifests
and
helm,
to
converge
on
the
use
of
of
helm
and
by
the
way
darren.
You
might
darren.
You
might
know
this
already,
but
just
to
orient
you
a
little
bit
further
that
so
the
source
for
the
helm
charts
is.
A
I
Yeah,
so
I
will
update
a
pr
that
I
have
under
the
masteries
to
add
those
meeting.
Cr
instance,
you
know
yeah
moves
into
these
hem
shots
and
then
that
fix
you
know
one
of
the
two
remaining
problems
and
then
the
other.
The
last
problem
that
I
found
is
that
in
this
deployment
we
only
have
the
manager
container
in
the
part.
I
If
you
go
to
the
manifest
and
then
defaults,
that's
what
we
use
in
the
mastery
ctl
to
deploy
the
the
mastery
operator
part
and
then
there
is
a
container
called
our
bag.
That
let
me
search
for
containers.
I
I
Containers
and
then
you
know,
444
indicates
that
this
container
uses
the
computer
to
buyback
proxy
image,
and
then
we
have
another
container.
Of
course
that's
what
we
know.
You
know
we
use
the
master
operator
so
which
makes
when
we
use
the
mesh
mastery
ctl
to
do
deployment.
A
That's
actually
yeah,
that's
kind
of
where
I
am
as
well,
and
utkarsh
is
another
individual
that
so
so
the
the
maintainer
abhishek
isn't
on
the
call
and
had
largely
been
a
single
individual
kind
of
wrangling.
The
operator
I'm
yeah.
A
A
I
It's
probably
doing
some,
you
know,
processing
of
the
network
traffic
into
the
pod.
You
know
so
that
it
I
don't
know
you
might
feel
that
some
some
of
the
network
that
coming
from
outside-
or
you
know-
I
don't
really
know
the
implementation
of
this
container,
because
it
seems
to
me
it's
fabric.
I
A
A
Which
yeah,
which
is
what
it
highlights
there,
that
that
gen,
the
controller
that
you're
the
the
controller,
that's
being
updated,
is
cube
builder,
so
yeah,
I
don't
know
either
I'm
just
misremembering
that
we
chose
the
other
or
like
yeah.
He
was.
We
needed
the
operator
quickly.
I
Yeah,
I
guess
I've
updated
my
pr
so
that
it
is
consistent
with
the
mastery
cto,
because
now
the
handshake
is
not,
you
know
it
doesn't
match
what
we
have
in
the
studio.
At
all
the
hand,
shots.
A
I
I
A
Know
about
we're
about
to
make
a
release
and
actually
that
so
this
right
now,
the
way
that
we
are
is
will,
I
think,
those
that
are
trying
to
deploy
into
eks
or
into
a
managed
kubernetes
may
still
would
still
run
into
this
issue.
Okay,
if
we
do
actually
on
that,
I
guess
like
a
quick,
quite
yeah.
If
we
do
an
intermediary
merge
of
this
pr
and
understanding
that
we
still
have
a
couple
of
open
issues,
we'll
be
in
a
better
position,
does
will
that
cause
an
issue
for
you.
I
Oh,
I
can
add
the
missing
pieces
to
this
gr
later.
You
know
in
my
afternoon
time
before
we
merge
it,
because
I
test
it
locally
by
by
manually
deploying
the
two
missing
cr
instance,
and
then
it
works
fine.
You
know
so
my
plan
was
to
basically
add
those
two
missing
yemos
to
the
same
hem
chart
and
then
you
know
perfect
yeah.
I
I
can
do
that
because
that's
what
I
did
in
my
local
testing
and
that's
the
cluster
that
I
have
and
yeah
that's
the
broker
and
then
the
mesh
sync
here
and
then
we
have
those
two
parts
and
then
the
operator
is
able
to
pick
up
to
reconcile
them,
because
I
can
see
that
from
the
logs.
You
know
it's
reconciling
the
brokers
and
then
the
messaging
somewhere
yeah
reconciling
messaging.
I
A
Cool
yeah
that'd
be
good.
It's
a
good
step
forward,
yeah
by
the
way
darren,
while
you're
in
there
or,
if
you're
in
that
same
spot,
the
re.
If
there's
a
misspelling
of
the
reconciling,
not
that
this
really
matters.
But,
oh
really,
I.
I
Yeah
I
see
yeah.
I
didn't
really
check
the
message.
Yeah!
No,
okay,
are
you
updated
as
well?
Thank
you
for
putting
that
up
darren.
That's
great
yeah!
That's
what
I
all
I
have,
because
I
haven't
really
been
here
for
a
long
time.
You
know
just
like
10
days.
That's
basically,
all
the
understanding
that
I
have.
A
That's
good
man,
yeah
are
impacting
already
trying
my
best
yeah,
that's
good.
It's
really
good!
I
mean
it's
actually
really
impactful,
that's
why
we
want
to
get
it
get
it
merged,
because
there
are.
There
are
a
couple
of
users
who
are
sort
of
sitting
there
without
without
an
active
mesh
sync
and
like
mesh
is
still
functional.
You
can
still
do
a
lot
of
performance
management,
but
the
other
two
thirds
of
what
measuring
does
now?
You
really.
You
really
need
mesh
sync,
so
I
think
it's
good.
E
A
We
should
move
to
helm
the
there's
a
couple
of
we
can
make
another
release
like
before
we
get
to
v060
like
yeah,
there's
a
couple
of
things
that
need
to
get
for
those
that
are
starting
on
the
mesh
map.
Alpha
program,
they're
in
need
of
another
release,
and
so
there's
a.
E
A
There's
been
just
as
darren
looks
at
this
as
well
or
gets
familiar.
There's
mesh
kit
is
a
central
library
that
a
lot
of
the
meshry
components
use
and
it
has
some
helm
that
has
some
functions
for
interfacing
with
helm.
So
just
a
reference.
A
A
I
think
that's
it.
It's
a
great
nice
community,
nice
to
see
you
guys
same
time
next
week.