►
From YouTube: Layer5 Community Meeting (Sept 3rd, 2021)
Description
Layer5 Community Meeting - Sept 3rd, 2021
Agenda:
- Community handbook Review by Anita
- kubernetes-cluster-running Image for Labs by Suryashankar
- Traefik Mesh Labs by Aditya
- Review required on Mesheryctl Blog post (docs) by Rahul
- Display badge for Beta feature by Ishita
Review draft of this blog
- Bundling seed content at build time by Rudraksh
- Changes in Meshery UI by Nikhil
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
A
A
C
D
My
name
is
tavari
hi
everyone,
I'm
from
vidskua
I'm
in
my
third
year
I
have
started.
I
started
web
development
in
my
first
year
only,
but
I
didn't
get
a
chance
to
get
a
few
internships
or
work
on
personal
projects
because
of
my
college
life
and
when
lockdown
started.
I
started
working
on
a
government
project
made
a
website
for
the
government
and
moved
forward
with
all
the
skills
I
have.
D
E
I
started
coding
since
back
for
like
one
or
two
years,
and
mostly
I
have
mostly
till
now.
I
have
done
competitive
programming
solving
every
problem.
So
now
I
decided
to
do
some
development
work
and
I
came
across
open
source
projects,
so
I
was
exploring
around
that.
I
found
mystery
community
on
lfx
foundation,
so
I
just
joined
here
to
learn
and
grow
as
a
contributor
in
the
community.
B
B
A
A
B
That
is
awesome.
There
might
be
something
to
being
perpetually
optimistic,
like
that.
That's
paying
off
for
rude
rocks,
rudraksh
any
there's
a
couple
of
newcomers
on
the
call
and
some
folks
well
who
might
follow
in
your
footsteps
at
any
sage,
advice
that
you
might
offer
to
people
to
to
completely
put
you
on
the
spot.
F
Yep
so,
let's
step
for
thank
you,
everyone.
It's
been
a
pleasure
contributing
to
this
community
and
engaging
with
you
all,
and
I
still
remember
those
small
steps
that
I
started
working
on
here,
like
the
first
fix
that
I
sent
was
that
slack
notify
on
star
workflow
it's.
It
was
a
pretty
small
step,
but
that's
how
you
start
and
it
slowly
slowly
takes
you
places
so
keep
engaging
and
don't
think
to
don't
mind
working
on
small
things
and
starting
on
small
things.
First,.
B
That's
awesome,
that's
great!
If
I
have
to
add
to
that
actually
rudraksha.
I
think
that's
a
very
there's
a
there's,
a
salient
point:
there's
actually
quite
a
few
points
to
make,
but
to
reinforce
that
I'll
say
that
shreyas
who's,
who,
I
think
is
the
same
treyas
jane.
That's
on
the
call,
don't
forget
everybody
to
put
your
last
names
on
the
in
zoom
if
you
can
just
because
well
I'm
for
I'm
fortunate
that
there's
only
one
lead
on
the
call
at
the
moment.
B
B
Actually,
he
was
also
successful
in
getting
his
sign
off
on
the
on
his
git
commit
going,
which
can
be
a
snag
that
people
run
into
for
some.
It
can
be
forking
the
repo
keeping
your
local
fork
in
sync
and
like
just
all
those
mechanics
of
literally
contributing
in
that
way,
those
can
snag
the
smallest
or
the
biggest
of
pull
requests.
B
So
it's
better
when
they
snag
the
small
ones
first,
so
you
can
get
a
smooth
process
going
so
but
yeah
just
that
that
whole
mantra-
that's
just,
I
think,
great
advice
from
red
rocks
as
you
go
to
engage
in
these
projects
or
maybe
anywhere
else,
the
smaller.
You
start,
the
more
likely
that
you'll
be
successful
like
because
you
yeah
you
just
build
up
a
pattern
of
success,
so
yeah
good,
yeah,
nice
also
one
other
thing
I'll
call
out
just
that.
B
Redrock
continues
to
do
really
well,
and
it's
helpful
that
we
call
out
for
for
michael
for
utkarsh
for
there's
a
lit
for
there's
a
list
of
other
maintainers
on
the
call
there
there's.
If
you
just
look
at
the
folks
that
are
on
the
call,
there
are
by
account
more
contributors
than
there
are
maintainers
and
so
be
kind
to
your
maintainer.
B
It
takes
folks
a
little
while
to
review,
especially
if
they're
going
to
give
feedback
that
isn't.
Might
not
be
considered
curt,
they
don't
have
much
time.
So,
if
they're
being
brief,
take
it
in
stride
because
they're
just
trying
to
make
it
around
to
respect
everyone's
contribution
and
give
some
feedback
do.
If
you
can,
please
do
as
much
homework
as
you
can
onto
your
own.
B
The
maintainers
here
and
the
other
contributors
here
are
have
do
a
great
job
of
espousing
the
culture
of
the
community,
which
is
helping
others
or
paying
it
forward
with
others
and
acknowledging
that
the
things
we're
trying
to
do
here
are
fairly
big
and
there's
no
way
in
the
world.
Any
one
of
us
can
do
them
onto
their
own,
or
even
just
10
of
us
like
it
takes
a
village
right.
It
takes.
B
B
B
I
I
get
to
learn
something
new
every
day.
I
just
saw
him
just
taught
me
something
new
earlier.
Thank
goodness
he's
not
on
the
call,
so
we
don't
get
his
ego
any
any
bigger
than
it
is,
but
everybody
is
entitled
to
to
learn
quite
a
bit,
and
hopefully
everyone
is
at
a
very
quick
clip,
actually
the
smarter
that
all
of
you
are
individually,
the
more
fantastic
things
we'll
do
together.
So
so
I
certainly
desire
for
everyone
to
be
well
equipped.
A
B
Yay
yay,
this
is
I,
I
have
to
say
something
here
as
well,
and
that
is
that
each
of
the
names
that
you
see
listed
they
shouldn't
be
entirely
for
anyone.
Who's
been
around
for
more
than
a
week
like
you've,
probably
bumped
into
those
names.
These
names
and
these
individuals
have
been
in
the
community
for
some
time
they
have
been
learning
themselves.
They've
also
been
they've
demonstrated
that
they
also
will
share
their
knowledge.
B
We'll
see
what
happens
after
a
couple
of
months,
we'll
see
if
they're
still
happy
about
it.
But
the
point
is
the
reason
that
they
were
selected
and
asked
to
be
an
intern
is
because
they
were
already
here
doing
good
things,
helping
helping
others
contributing
engaging
learning,
and
so
when
people
do
that,
all
that
we
desire
to
do
is
support
them
in
that,
if
they're
being
productive
and
they're
being
helpful
for
being
a
good
community
member.
In
that
way,
it
takes
a
lot
of
forms.
It's
not
it's
not
about
contributing
code
per
se.
B
We
just
want
to
reinforce
that
and
support
that
so
so
really
what's
happening.
Today
is
yes
an
acknowledgment
of
the
the
notion
that
these
four
gentlemen
are
entering
into
well
three
months
of
indentured
servitude,
maybe
but
but
they're
entering
into
these
internships,
but
that
they
are
it's
also
an
acknowledgment
of
what
they've
already
done.
They've
already
done
quite
a
bit,
and
hence
it's
it's
more
of
a
recognition
of
what
what
the
what
they've
been
doing
so
pretty
cool.
If
you
see
them,
say
hi.
A
G
Yeah
sure,
okay,
hey
everyone,
and
for
the
past
one
month
we've
been
trying
to
make
an
update
to
the
previous
handbook
because
it
was
not
so
organized
and
there
was
so
much
repetition
in
the
words
and
the
sentences
and
everything
so
it
tries
to
like
it's
come
true
that
just
make
sure
it's
good
enough.
It's
a
good
fit
to
put
on
the
website
and
we
try
to
put
it
together
in
this
new
dock.
G
B
So,
by
the
way
this
is
coming
from
mesh
mate
anita,
I
don't.
Some
of
you
may
be
familiar
with
mesh
mates
program.
Some
of
you
might
be
familiar
with
anita
she's,
pretty
active
in
the
community
and
actually
impressively
so
because
she's
she's
doing
she's
doing
a
number
of
things
out
anita.
One
of
if
you
don't
mind
my
sharing,
I
you
don't,
you
know,
share
as
much
as
you
want
you
want,
but
I
understand
you've
been
studying
some
kubernetes
recently.
G
Well,
yeah.
Fortunately,
I've
been
trying
to
prepare
myself
for
the
kubernetes
certification
examination.
I
think
that's
like
one
of
the
requirements
to
like
take
on
for
the
new
role
that
I
just
got
in
the
mata.
Yes,
so
I'm
putting
in
all
that
I
know
I
guess
it's
not
been
easy,
but
I'm
trying
my
best.
G
Actually,
it's
it
turns
out.
A
lot
of
persons
have
shown
interest
in
this
particular
certification,
especially
people
who
want
to
like
dive
into
the
kubernetes
ecosystem.
It's
a
good
addition
to
your
resume
and
also
it's
actually
good
to
have
a
deeper
understanding
of
kubernetes
generally.
So,
if
you
want
to
like,
have
a
more
deep
understanding
of
what
kubernetes
and
docker
is
all
about,
it's
like
a
good
start.
You
can.
You
can
meet
me
up
in
this
slack
and
I'll,
give
you
the
resources
that
I'm
going
through.
You
don't
have
to
take
it
immediately.
G
B
The
other
thing
that
anita
was
just
saying
about
the
community
handbook,
it's
worth
reiterating
that
all
of
you
are
including
myself
or
just
are
part
of
the
community
and
the
community,
like
any
other,
has
norms
and
has
hopefully
some
principles.
We
I
like
to
think
that
we
do,
and
but
we
also
have
different
mechanics
by
which
the
community
runs
and
different
resources
that
are
available
to
people
who
join
and
what
does
it
mean
to
join
like
there's?
Actually
a
lot
like
what
are
the
projects,
what
technologies
are
used
and
so
on?
B
Are
the
resources
for
learning
something
like
kubernetes
or
just
or
a
surface
mesh,
there's
a
whole
ton,
there's
a
ton
and
what
anita
has
been
corralling
is
gathering
up
that
information
into
a
central,
easily
referenceable
location
into
this
handbook.
So
there's
a
google
doc
that
she
was
just
showing
it
where
all
of
you
are
welcome
to.
B
She
was
soliciting
your
input,
she's
saying
please
come
review
the
outline
of
topics
to
cover
and
then-
and
I
think,
actually
yeah
this
full
dock
right.
This
this
dock
has
all
of
the
actual
content
as
well.
It's
not
just
the
outline
that
you're
showing
but
the
full,
and
so
particularly
anyone
who's.
Whether
you've
been
here
for
a
long
time
or
you
just
joined
10
minutes
ago.
B
You've
got
something
to
say
here
like
this
is
a
really
excellent
document
to
review
comment
on
turn
on
suggestion
mode
and,
like
start
suggesting
away,
fix
the
spelling
error.
What
have
you
the
there's,
an
early
ver,
there's,
a
number
of
people
who've
been
working,
a
number
of
people
actually
worked
have
been
working
through
this
and
but
anita
is
where
mesh
mate
anita
is
wearing
the
the
captain's
hat
so
to
speak
or
leading
the
charge
here
and
so
or
she's
carrying
the
torch.
B
Maybe
is
the
other
way
of
thinking
of
it,
but
that
goal
of
having
this
publicly
published
it's
in
part
like
it's
in
draft
mode,
publicly
published
at
the
url
in
the
zoom
chat
and
it'll,
be
what
a
great
set
of
info,
what
a
very
commonly
referenced
set
of
info.
That
will
be
so,
please,
please
think
on
it.
Please
give
it
a
read
through
and
add
to
it
point
out
things
that
are
potentially
missing.
A
A
Just
to
add
to
that
I
think
that's
a
problem
with
category,
because
it's
happening
with
me
as
well,
not
only
with
the
cuban,
because
the
lab
that
I
have
written
for
traffic
mesh,
I
have
it
like
in
locally.
I
have
it,
starting
with
mini
cube
and
the
one
I
have
in
my
pr.
It
starts
with
a
kubernetes
cluster,
both
of
them
don't
like
they
don't
start
with
like
both
of
them.
The
measuring
server
always
keeps
crashing.
So
it's
a
category
issue.
It's
not
with
the
image
id.
A
I
B
H
H
H
E
Actually,
what
you
can
do
is
you
can
open.
This
thing
is
in
another
tab.
That
is,
if
you
would
see
that
maximize
button
on
the
left
side-
yeah
yeah
yeah,
if
you
could
open
it
on
another
tab,
now
you
can
access
console
logs.
So
probably
there
might
be
some
errors
if
you
can
open
it
up
in
actually
in
the
same
tab
where
we
just
opened
for
you
in
the
browser
in
the
browser.
E
H
H
E
H
E
B
Okay,
great
sounds
like
you
guys
are
done
so
as
a
reminder,
I'm
always
good
to
give
context
for
everyone
else
as
to
what
we're
what
we're
chatting
on
so
there's
context
in
the
zoom
chat
about
how
you
all
can
learn
to
service
mesh
using
those
labs
and
how
each
of
you
can
contribute
to
the
labs.
There's.
B
An
open
request
for
a
couple
of
new
labs
and
suhani
is
on
the
call,
miss
agarwal,
who
has
politely
and
persistently
I'm
introduced
to
people
to
the
efforts
here,
she's
she's
on
point,
if
you
will
trying
to
trying
to
track
these
down
so
she's
got
she's
got
a
couple
of
outstanding
requests
for
new
labs,
and
then
I
think
you
know
like
this
issue,
probably,
and
maybe
a
couple
of
others
so
so,
engage
there
great
way
to
learn
and
contribute.
At
the
same
time,.
A
No,
I
guess
so,
let's
move
on
to
the
next
topic,
so
it's
by
aditya,
so
the
traffic
mesh
lab
he
has
made
up
here
so
aditya
you'd
like
to
talk
on
that
yeah
I'll
just
share
my
skin.
I
was
having
the
same
problem
as
surya
shankar,
but
the
implement
just
it's
just
a
little
different.
So
what
I
have
done
is
basically
to
get
the
cumulative
kubernetes
cluster.
You
need
to
run
this
command
and
then
it
shows
that
kubernetes
is
started
and
then,
if
you
get
the
nodes,
it
takes
some
time.
A
B
A
A
J
J
I
did
get
a
few
reviews
like
to
add
some
pictures
here
and
there
to
make
it
more
enjoyable
to
read,
but
other
than
that.
I
think
the
content
is
good
to
go.
So
if
there's
anyone
willing
to
read
and
give
a
good
review
on
this
they're
most
welcome
the
links
on
the
meeting,
which
I
guess
and
also
on
the
kitchen
blog
blog
kitchen
in
slack.
J
B
B
But
it's
a
good
it's
good
to
follow
up
to
make
sure
that
it's
accurate,
because
because
it's
embarrassing,
when
it's
not
when
when
the
documentation
doesn't
reflect
reality,
which
is
actually
something
we
were
kind
of
talking
about
on.
The
call
on
the
mesh
redevelopment
call
on
wednesday
is
the
notion
that
there's
a
balance
between
night,
you
know
nicely
curating
hand,
curating
documentation
and
describing
behavior
of
software.
It's
really
helpful
in
documentation.
B
That's
something
that
people
can't
glean
from
the
ui
or
from
looking
at
the
help
text
in
on
the
cli
is
like
is
when
the
documentation
actually
tells
you
what's
going
to
happen
behind
the
scenes.
That's
really
helpful
and
that's
something
that
us
humans
have
to
go
write
like
write,
write
docs
for
the,
but
there's
something
that
we
can
ask
the
robots
to
do
the
machines
to
do,
and
that
is
to
auto,
generate
some
portion
of
the
documentation.
B
The
portion
that
we
can
ask
them.
The
machines
to
do
is
like
in
context
of
measuring
ctl,
it's
like
well,
those
commands
are
in
in
the
code
those
the
code
has,
we
can
use
goto.
We
can
use
a
couple
of
different
mechanisms
to
help
auto
publish
what
the
series
of
commands
are
and
what
flags
are
are
literally
in
the
code
and
so
there's
some
amount
of
rework.
That's
going
on
in
measuring
docs.
Now,
there's
a
reference
guide
to
measuring
ctl
and
there's
some
rework
that's
going
on
so
there's
the
other.
B
J
B
B
B
Commanding
because
you're
working
with
the
commands
like
commanding
measuring
deployments,
if
you're,
really
gonna
focus
on
context
because
context
is
about
context,
describes
measuring
deployments,
and
so
this
is
awesome
like
go.
Go
deep,
go
go
long
and
go
deep
on
just
just
the
context
command.
There's
a
fair
bit
to
to
do
there.
What's
lesser
important
is
regurgitate
I'm
assuming
that
this
is
in
part,
maybe
a
regurgitation
of
what
you'll
find
in
the
documentation,
which
is
not
bad
but
really
what's.
Insightful
and
helpful
is
describing
the
behaviors
like.
B
When
is
it
that
you
would
use
the
context
view
switch
and
like
it
would
be
good
to?
I
think
you're
you're
calling
it
out,
but
it
said
it
says
to
switch
I'm
pointing
to
like
the
last
paragraph,
to
switch
the
content.
The
current
context
passively
use
view
switch
cool.
What
does
passively
mean-
and
I
call
it
out-
you
don't
have
to
answer
it's
kind
of
a
rhetorical
question.
B
It
is
like
that's
actually
really
important,
because
the
people
can
screw
up
their
systems
if
they
not
knowing
that
one
of
these
commands
may
like
totally
delete
their
current
deployment
and
redo
a
different
deployment
and
stuff.
So
it's
an
interesting
thing.
I
think,
if
you're
going
to
explain
context
so
by
the
way
rahul.
This
is
great,
like
the
the
feedback
that
I'm
giving
is
just
hopefully
to
uplift
what
you're
doing
and
enforce
it
or
reinforce
it.
B
One
thing
you
might
want
to
do
is
like
you,
don't
have
to
fully
describe
it,
but
it
would
be
good
to
highlight
the
notion
that
there's
two
release
channels
because
part
of
configuring,
your
contacts,
it's
really
like
you're
configuring,
your
mesh
redeployment.
Maybe
you
want
all
the
adapters.
Maybe
you
want
to
run
from
the
stable
release
channel
or
from
the
edge
release
channel.
B
This
is
awesome,
it's
great,
that's
good
and
by
the
way,
just
for
everyone
or
like
rahul.
How
long
have
you
been
in
the
community?
Like
I
joined
last
week,
yeah,
I
know
look
at
that.
You
already
got
a
blog
post
in
draft.
I
mean,
like
that's
fanta,
that's
like
a
great
context
for
everyone
to
understand
as
well.
So
you
didn't
waste
a
moment.
That's
fantastic!.
A
B
B
Cool
okay,
so
ashida,
I'm
going
to
do
my
best
to
speak
to
this,
just
because
we
can't
we
actually
can't
hear
you
your
voice
isn't
coming
through
at
all
and
so
not
a
big,
not
a
big
deal.
Let
me
let
me
speak
to
this
briefly
and
talk
about
the
nice
work
that
ashita's
been
doing
so
so
two
things
briefly.
So
so,
okay
in
mesherie,
which
is
our
largest
project.
We
have
other
projects
in
the
community,
but
this
is
our
biggest.
L
B
L
M
B
Well,
both
of
you
guys
took
the
words
out
of
my
mouth.
Are
they
at
least
of
my
opinion
that,
like
hey
yeah,
that
that
looks
looks
pretty
good
like
it's
not.
You
know
not
uncommon,
to
see
something
like
that
and
that
yeah,
especially
if
you
offset
it
with
a
color,
I'm
not
you
know
with
I,
I
it's
some
color
like
between
somewhere
between
orangish
and
yellowish.
Maybe
we've
all
been
trained
throughout
our
lives.
That
green
is
good.
Red
is
bad
somewhere
orange
to
yellow,
is
warning
sort
of
be
careful
or
use.
B
K
B
B
A
N
I
B
B
The
dot
six
release
is
chalking
up
to
much
of
the
same
like
entirely
new
concepts
and
constructs
applications.
Filters
patterns,
like
the
emergence
of
these
three
constructs,
which
is
quite
significant,
so
there's
so
megana
and
zane,
are
trying
to
get
us
organized
to
in
advance
of
making
their
release
to
trying
to
get
us
organized
so
that
we
can
have
a
a
release,
announcement
blog
and
maybe
a
collection
of
blogs.
B
Because
there's
you
know
if
you
think
about
it,
there's
sort
of
the
announcement
that
goes
out
that
maybe
highlights
the
big,
the
big
meaty
chunky,
new
features
that
have
come
out.
This
super
sexy
eye,
candy
stuff
that
entices
everyone
to
come
and
try
out
the
stuff.
You
know
the
things
that
you
all
have
made
but
like,
but
if
you,
if
you
want
to
explain
just
this
one
concept,
you
know
filters
or
just
patterns
like
well,
gosh,
that's
a
whole
blog
post
onto
its
own.
B
If
you
really
want
to
explain
it,
and
so
what's
trying
to
be
organized
here
is
capture
is
probably
like
capturing
the
the
topics
that
should
be
covered
like
what
all
did
we
contribute
in
this
release
and
so
there's
a
milestone.
There's
a
in
github.
We
sometimes
are
good
about
marking
a
given
issue
as
belonging
to
a
milestone,
milestone
being
a
release.
You
know
this
release,
so
oh
wow
wait
a
second.
B
When
did
this?
Oh
okay,
boy
for
a
second,
I
thought
that
this
was
like
merged
back
in
february,
and
it's
just
now
and
we're
just
now
making
a
release.
Okay
anyway,
point
is.
This
is
one
using
that
hyperlink
is
one
way
of
and
by
the
way
everybody
on
the
call.
Can
everyone
do
me
a
favor
just
to
show
that
you're,
even
listening
and
engaged?
B
Can
you
click
on
the
link
in
zoom
to
zoom
chat
or
click
on
the
link
in
the
layer,
five
community
meeting
here,
and
I
can
see
all
of
your
little
cursors
if
you're
doing
it
or
not
so
quick
test,
see
who
all
is
awake
point
is
is
just
to
like
make
sure
that
a
everyone
should
be
able
to
access
these
docs
like
these
are
your
docs
as
much
as
anyone
else.
This
is
your
work
come
and
represent
it.
Well,
there's
a
lot.
That's
gone
into
this
minor
release.
B
We
are
shoving
a
lot
into
these
minor
releases
because
we
got
a
lot
to
get
done
before
we
get
to
a
1.0
and
there's
a
ton
of
things
to
talk
about,
there's
like
any
number
of
whether
it's
a
blog
post
or
a
short
video
recording
or
a
static
screenshot
or
an
animated
gif
like
the
beta
label,
a
sheeta
there.
It
is
like
some
people
might
say,
adding
that
label
is
a
small
contribution.
B
Well,
guess
what
it
actually
has
a
major
effect,
it's
something
we
have
to
go
talk
about.
Well,
what
do
you
mean
data
like
well?
What
should
I
expect
from
this
is
this:
is
this
gonna
work,
or
is
it
gonna
stay
the
same
during
the
next
release,
like
there's,
actually
kind
of
a
lot
to
explain
and
probably
a
screenshot
to
include
in
the
release
somewhere
that,
like
now,
there
are
beta
features
and
like
oh,
we
should
probably
clarify
and
classify
these
as
beta
features,
what's
kind
of
nice
about
using
that
subscript
or
the
superscript.
B
B
I
hope
that
all
of
you
that
are
on
the
call
really
get
the
sense
that,
if
you're
spending,
if
you're
on
the
call
and
you're
spending
time
here
like
make
the
best
of
it,
come
and
get
involved
and
make
your
mark
you're,
encouraged
to
and
we'll
be
talking
about
this
release
at
kubecon
for
sure
for
sure,
because
kubecon
isn't
until
october
11th
through
15th
somewhere
in
there,
and
if
we
haven't
made
this
release
by
then
we're
we're
probably
in
trouble.
I'm
sure
that
we
will.
This
is
just
so
anyway.
B
There's
a
couple
of
if
you're,
all
wondering
and
thinking
like.
Well,
I
don't
know
what
went
into
the
release
like
use.
These
two
links
go
look
up
what
was
in
there
or
check
this
out,
go
give
rahul
the
right
feedback
that
he's
looking
for
and
do
this
do
measure
ctl
system
context,
because
rahul
is
telling
us
how
to
do
this.
I'm
sorry.
B
B
So
anyway,
point
is
thank
you,
megan
and
zane
for
stepping
up
to
help
organize
this.
There's
you'll
need
as
much
help
as
as
you
can
get
as
you
go
to
kind
of
you
know,
so
I
think
megan
and
zayn
that
ideally
the
first
goals
here
are
doing
what
you
exactly
what
you're
doing,
which
is
kind
of
highlighting
the
the
big,
the
big
ticket
items
soliciting.
B
From
like,
ideally
not
that
this
isn't
meant
to
be
exclusive
at
all,
but
ideally
there
might
be
a
maintainer's
name
against
one
or
you
know
each
of
these
items,
if
only
to
make
sure
that
they're
doing
a
review,
not
that
they
necessarily
have
to
write
it,
but
just
because
they
will
have
they'll
be
able
to
help
qualify,
it
quantify
it
so
so
cool.
So,
for
my
part,
I'll
spend
a
little
bit
of
time.
You
know
adding
a
couple
of
topics
and
maybe
making
some
suggestions
about
names
and
things
but
yeah.
B
B
A
F
Assuming
it's
visible,
so
this
is
about
the
spec
that
we
had
a
while
ago,
bundling
sample
filters
and
applications
and
patterns
in
mystery,
so
that
mystery
can
act
as
in
as
a
content
repository,
and
we
can
have
some
content
that
people
can
try
when
they
are
mystery
for
the
first
time.
So,
if
you're
not
clueless
about
it,
some.
F
This
is
right.
Now
implementation
of
this
user
story,
it
could
be
bundling
seat
content
when
missing
server
builds
so
that
when
we
ship
it,
they
have
it
available,
and
this
is
some
update
on
this.
We
are
fetching
the
binaries
of
awesome
filters
right
now.
We're
fetching
it
from
my
own
folk,
where
I
have
released
them
and
probably
later
on
we'll
release
them
on
our
main
report.
Then
we
can
pull
them
off
and
pack
them
so
nothing
much
happening.
F
Okay,
this
is
anyways.
The
one
concern
that
I
have
about
filters,
though,
is
that
there
have
been
issues
through
time
that
filters
are
not
compatible
with
a
particular
version
of
the
data
plane
proxy.
Now,
I'm
not
sure
if
it
is
something
with
the
proxy
bosom
sdk,
so
incompatibility
due
to
filter
or
incompatibility
due
to
the
filter
configuration.
F
B
B
N
B
F
So,
basically,
right
now,
the
filters
that
we
have
in
washing
filters
are
uvanila
on
oil
filters,
so
they
will
turn
on
non-war,
and
this
is
the
onward
configuration
we
can
just
copy
it
from
here
and
paste
it
in
probably
still
onward
filter
crd
and
it
would
work,
but
the
thing
that
we
need
to
think
about
is
versions
so
across
versions.
These
filters
might
not
work
as,
as
was
the
case
here.
B
Yeah,
no
okay,
yeah
good
deal.
I've
listened
this
time.
Sorry
yeah
that
is
potentially,
that
is
a
separate
concern
from
the
two
concerns
that
I
raised
this
one
it
like
like
to
your
point.
It
might
be
the
it's
not
it's
like.
There's
man,
there's
like
two
things:
one
is
whether
you're
dealing
with
a
filter,
a
pattern
or
an
application.
B
Each
of
those
three
things
are
content.
You
know
like
to
measure
right.
Mescheri
can
deal
with
any
of
those
three
types
of
content
and
the
content
itself
like
if
you
make
a
change
to
the
filter,
to
have
it
behave
differently.
Well,
that
filter
might
have
its
own
version,
so
so
every
piece
of
content
may
have
its
own
version.
Okay,
that's
one
consideration.
B
The
second
consideration
that
you're
highlighting
is
beyond
that
to
use
a
filter
as
an
example,
this
filter
may
only
work
with
in
certain
service
mesh
environments
only
on
envoy
only
on
a
version.
You
know
this
version
and
so
yep,
that's
those
are
good
considerations
to
begin
to
document
and
it's
those
are
highly
related,
but
are
just
a
step
removed
from
seeding
content
and
doing
the
initial
registration.
I
mean
like
actually
part
of
the
initial
registration.
B
B
F
F
B
Yeah
so
universally
we
may
want
to
incorporate
a
manifest
with
the
any
given
piece
of
content
that
the
manifest
may
highlight
prerequisites
prerequisite
very
like
service
message
that
it
works
with
or
prerequisite
versions
of
infrastructure
that
it
will
only
work
on.
It
requires
also
the
manifest
could
capture
the
version
number
of
the
artifact
itself
and
potentially,
if
the
artifact,
if
the
content
itself
is
more
than
one
contains
more
than
one
artifact,
not
just
a
yama
file
or
not
just
a
binary,
but
multiple
files,
the
manifest
could
also
be.
B
You
know,
capture
the
index
of
like
what's
inside
there,
so
at
some
point,
if
you,
when
you
really
get
into
like
content
management
in
this
way,
what
you
end
up
doing
is
like
if,
if
michael,
has
written
a
nice
pattern
and
we
want-
and
he
wants
to
export
that
distribute
it
share
it.
Well,
there's
a
number
of
things
that
he
might
be
he
might
be
concerned
with.
He
might
want
to
guarantee
that
it
works
for
people.
So
it's
in
part
what
you
were
just
saying
about
prerequisites
and
having
the
right
infrastructure.
B
It's
also
the
case
that,
like
well,
who
authored
this
thing
in
the
first
place,
it
might
be
nice
for
him
to
be
able
to
capture
the
fact
that
he
had
authored
it,
that
he
versioned
it,
starting
that
that
he
versioned
the
pattern
of
v1.
Other
people
have
mutated
or
he
added
separate
concern.
He
is
himself
he
has
versioned
it,
and
so
what
was
the
history
of
that?
Also?
Maybe
he's
saying
in
this
pattern.
B
Anyone
could.
These
are
customizable
areas
of
the
pattern
that
anyone
is
welcome
to
customize
and
manipulate.
But
if
you
want
to
subscribe
to
michael's
pattern-
and
he
goes
to
make
another
release,
if
you've
changed
this
area
of
the
yamo,
well
then
you're
in
the
line
of
fire,
because
he
may
well
overwrite.
That
so
is
are
there
areas
so
like
there
becomes
a
lot
of
those
types
of
concerns,
so
you
just
opened
up
a
can
of
worms.
My
friend.
F
C
C
C
B
B
The
correct
answer
is:
let
the
users
decide
give
them
a
few
predefined
themes,
let
them
switch
between
them
and
then
ultimately,
let
them
customize
it
as
customize
it
as
well.
If
they
it
worth
us
spending
art
excuse
me
spending
our
time
to
customize
to
to
allow
them
to
customize.
Probably
not
probably
there's
more
important
things
for
us
to
go.
B
Do
like
right
now,
anyway,
that
doesn't
mean
that
bringing
in
a
theme
and
supporting
switching
between
themes
like
that
can
be
that's
you
know,
probably
sometimes
we
we
should
get
to,
and
it
could
be
that
one
of
the
themes
is
just
like
this
one
of
the
things
that
you've
done.
I
think
you've
done
a
good
job
of
flattening
the
cards
or
taking
off
like
we've
gotten
kind
of
deep
on
some
of
the
cards.
B
You've
added
some
you've
softened
up
the
cards
that
are
here
at
least
for
what
I
can
tell
it's
a
bit
fuzzy
on
my
in
the
sharing.
But
what's
nice,
it's
elegant,
it
gives
you
a
sense
that
you're
interacting
with
a
high
quality
piece
of
software,
one
thing
and
that's
absolutely
desired
right.
Absolutely.
B
B
B
C
B
So
good,
so
you
the
link
to
the
anyone
who
has
everyone.
That's
here
has
access
to
the
figma
design
files.
So
if
anyone
has
other
feedback
from
the
kill
sharma,
please
please
give
it.
I
think
nikhil.
We
should.
I
mean,
for
my
part,
there's
something
here
at
minimally
that
the
cookie
crumb
trail
that
you
have
in
the
top.
B
Well,
that's
nice!
It
lets
the
user
know
where
they
are.
Maybe
that's,
maybe
exposing
that
as
a
sub,
a
sliver
like
a
sub
menu
still
still
telling
them
they're
on
applications,
big
and
bold,
but
but
then,
as
a
sub
menu
item,
a
secondary
bar,
giving
them
a
cookie
crumb
that
they
that's
navigable
navigable
navigateable.