►
From YouTube: WebAssembly Filters Meeting (Nov 29th, 2021)
Description
WebAssembly Filters Meeting - November 29th, 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
So
good
morning,
good
afternoon,
good
evening,
where
are
you
joining
from?
If
you
are
new
to
the
meeting
meeting,
please
introduce
yourself
also,
please
don't
forget
to
add
your
name
to
the
meeting
minutes.
Let
me
share
the
link
to
them.
A
If
you're
new
to
the
meeting,
please
introduce
yourself,
if
you
have
issues
with
the
audio,
you
can
use
the
chart.
B
B
So
yeah
now
I'm
going
to
demo
the
inventory
volunteer
for
it.
That
is
actually
a
way
of
representing
the
filters
that
can
be
dropped
onto
a
node
in
my
snap.
So
I
have
mesh
map
over
here
and
I'm
currently
dropping
a
component.
B
And
we
can
actually
take
a
filter
and
then
drop
it
onto
a
component
over
here.
So
this
way
like
you
can
see
that
there's
a
inventory
wallet
over,
which
shows
the
number
of
in
number
of
items
inside
that
a
particular
inventory
wallet.
So
this
is
what
we
call
as
an
inventory
wallet
so,
and
these
are
items
that
are
inside
that
so
right
now
we
have
two
ny
filters,
so
this
is
a
way
of
representing
the
filters
that
are
attached
to
a
particular
node
as
of
now
so.
B
So
is
that
it
I
mean
like
do
any
of
you,
have
any
comments
or.
C
I
felt
the
anti-climatic
for
a
second,
I
guess
that's
it
by
the
way.
Okay,
sorry
just
checking
my
microphone.
My
mic
check
check,
check,
check,
okay
cool,
so
so
you
dropped
two
filters
on
there
and
with
the
discussion
that
utkarsh
was
having
last
week,
we
were,
he
was
introducing
everyone
to
some
of
the
istio's
new
apis,
for
you
know,
manipulate
managing
webassembly.
C
Plug-Ins,
I
think,
is
what
they
were
the
new
term,
but
part
of
that
management.
Was
we
discussed
a
little
bit
about
the
explicit
the
ability
for
a
user
to
explicitly
identify
what.
C
Where
and
what
sequence
to
chain
these
webassembly
filters
and
to
plug
them
in,
and
so
it's
a
curious
note
or
curious
like
like
this
is
a
really
advanced
concept
for
this,
this
user
interface
here,
but
I'm
curious
as
a
user
potentially
drops
in
more
than
one
filter.
C
C
In
terms
of,
and
this
isn't
I'm
just
kind
of
you
know
thinking
aloud,
this
isn't
like
a
a
critical
item.
It
doesn't,
I
think,
a
lot
of
times.
Excuse
me,
I
think,
a
lot
of
times
people
think
of
this
type
of
a
design
as
traffic
flowing
from
left
to
right,
just
because
it's
there's
sort
of
a
there's,
an
implicit
convention
of
drawing
there.
Your
diagrams,
like
that,
there's
nothing
on
this
diagram
right
now
that
indicates
the
flow
or
the
direction
of
what
filter
would
be
invoked
first,
and
so.
C
Consequently,
there
isn't
necessarily
meaning
to
the
fact
that
one
filter
is
on
the
left-hand
side.
One
filters
on
the
right-hand
side
like
that:
there's
no
and
I'm
assuming
that,
as
someone
goes
to
edit
that
filter
and
configure
it
that
part
of
that
configuration
would
be
identifying.
C
You
know
which
of
the
two
comes
first
in
the
chain.
You
know
which
the
two
comes.
First,
in
the
sequence
I
mean
that
doesn't
necessarily
need
to
be
at
least
now.
It
doesn't
need
to
be
visually
reflected,
but
I
figure
I'll
just
you
know,
draw
attention
to
this
and
let
it
kind
of
permeate
in
the
background
about
the
potential
like
utkarsh.
Last
time
we
were
speaking
about
filter
chaining
last
week
and
the
ability
for
a
user
to
identify
what
sequence
to
place
these
there
was.
If
memory
serves.
C
That
was
fairly
curated,
like
there
were
potentially
three
pre
designated
spots
that
you
could.
It
was
like
pre-authentication,
post
authentication,
something
like
that,
and
so
not
that
we
want
to
necessarily
curate
or
design
this
particular
service
mesh
agnostic
experience
around
one
specific
service
mesh,
but
it's
worth
just
a
moment
of
reflection
to
think
about.
You
know
to
see
your
chaining
filter
chaining
and
how
that's
visualized.
A
Also
so
today,
if
you
get
time,
I
will
actually
also
demo
that
how
we
can
like
measure
all
the
machine,
didn't
add
a
line
of
code,
but
mystery
supports
it
wasn't
plugged
in
now,
so
you
can
actually
use
that
for
dropping
in
remote
over
some
binderies.
So
that
is
something
that
I
mean
mishmap
can
also
probably
bring
in.
That
is
right
now.
I
think
this
thing
like
we
get
this
particular
ui.
A
The
this
would
interface
only
if
you
drop
in
on
the
filter,
but
because
misery
supports
yeah,
it
supports,
wasn't
plug-in,
so
you
can
actually
do
the
exact
same
thing
that
we
were
doing
earlier
with
basically
longer
the
yamaha,
more
verbose
channel
and
more,
I
would
say
more,
a
comprehensive,
which
is
more
specific
to
onward
and
sdo
so
yeah.
Basically,
we
can't
probably
bring
in
that
particular
component
support
for
the
artwork
content
in
mesh
map
as
well.
That
is,
if
you
drop
in
boston,
plug-in
component.
A
C
Wow
there
was
something
fairly
special
about
what
karst
just
said,
that
I
don't
know
that
everyone
necessarily
grocked
or-
and
that
is
that
you
know
a
lot
of
times
when
people
are
coming
to
a
service
mesh
for
the
first
time
and
they're
they're
understanding
it.
C
It
certainly
used
to
be
the
case
that
there
was
well
there
was
a
sense
of
like
magic,
sprinkles
happening
in
the
background,
like
you
would
onboard
your
workflow
onto
a
surface
mesh
and
then
magically
you
get
like
without
any
code
change,
you
get
well
any
number
of
things
new
telemetric
signals.
You
know
traces
logs
and
metrics
about
your
new
observability
observable
signals
that
are
coming
out
of
your
workload.
C
You
get
some
additional
security,
you
can
eat
all
these
things
and
and
you
get
all
that
without
any
code
change,
and
it
feels
like
to
some
of
us
that
that's
like
wonderful
and
it's
a
warm
blanket
or
to
some
of
the
rest
of
us.
It's
like
wait.
It's
like
someone's
trying
to
it's
like
the
magic
behind
the
scenes
makes
us
feel
uncomfortable
because
it's
like
wait.
C
Wait
a
second
what's
really
going
on
back
there
like
and
so
anyway,
when
we
reflect
on
what
woodcrush
just
said,
so
so
that
it
was
that
statement
when
you
bring
your
workloads
to
a
service
mesh,
there's,
there's
no
code
change
needed
and,
like
I
think
you
just
said,
mescheri
supports
a
new
set
of
apis
coming
fresh
out
of
istio,
with
no
code
change
to
mesherie,
which
okay,
that
I'll
take
it
as
a
warm
blanket.
I
guess
like
that.
That's
pretty
cool.
C
So
good
just
to
round
off,
I
guess
nitish,
if
you're
looking
for
feedback
from
folks
and
so
by
the
way
for
for
reuben
and
hardit
and
deep
and
anyone
else
who
might
not
have
been
around
a
lot
of
the
calls
for
a
while
and
michael.
C
You
know
like
the
reason
that
the
tisch
is
showing
this
is
so
that
you
can
express,
you,
know,
weigh
in
and
any
any
feedback
is
valid
feedback.
Sometimes
it's
just
like
there's
two.
Sometimes
it's
like
hey.
Why
are
those
two
items?
Those
two
filters
inside
of
that
inventory?
C
C
C
B
Yeah
and
just
a
small
correction
like
yeah,
this
is
currently
supported
for
other
components
as
well,
not
only
for
sto
that
is
like
if
you,
if
the
component
actually
has
the
name
filter
on
it,
it
actually
treats
it
like
a
filter,
and
that
allows
it
to
do
this
thing.
So
right
now,
that's
how
far
we
are
right
now
so,
but
probably
we
might
have
to
you
know,
make
it
more
strict
or
something
but.
A
Yeah,
actually
so
about
that,
although
we
haven't
gone
so
far
here
yet,
but
the
idea
was
that
probably
we
should
treat
onward
filter
like
a
trait
rather
than
so.
If
someone
is
not
aware,
trade
is
actually
an
home
construct,
open
application
concept,
so
yeah,
but
the
idea
was
actually
to
treat
onward,
filter
and
stuff
like
this
as
street.
The
benefit
would
be
that
trades
already
have
that
metadata
that
to
what
this
particular
thing
can
be
attached.
A
So
in
that
case,
if
you
won't
have
to
build
anything
on
the
q1,
it
would
be
already
provided
by
the
adapters.
Basically,
the
confidence
is
actually
generating
it,
so
that
that's
something
that
we
can
probably
look
at
not
not
today
later,
because
one
of
the
issues
that
we
will
we
can
actually
encounter
is
that
probably
probably
honorific
dot
sto
is
not
going
to
work
if
we
drop
it
on
linkedin,
confident
or
yeah.
So
that's
something
we
will
have
to
take
care
of.
A
Not
I
mean
definitely
in
future,
because
we
haven't
got
too
far
with
them,
generating
trades
and
workloads
all
this
all
of
those
things
same
time,
so
yeah
just
a
suggestion.
C
A
So
our
next
item
is
actually
from
gaurav.
It's
called
of
the
block
called
so
quorum
is
not
on
the
cause,
but
just
to
give
a
brief
idea
that
what
this
topic
was
all
about.
So
in
case
someone
is
here,
I
see
a
lot
of
folks
on
the
call
today
and
that's
that's
not
very
common
with
wars
and
calls,
but
I
see
a
lot
of
folks
in
here.
A
So
probably,
if
someone
is
interested
in
the
in
this
particular
thing,
they
can
actually
collaborate
with
curve,
so
just
introduce
what
the
topic
is
dropping
is
actually
having
multiple
imports
in
the
ui.
What
that
is
so
if
you
would
actually
open
a
machine,
you
can
go
in
under
configuration.
There's
a
section
called
buttons
filters.
Applications.
Let's
talk
about
patterns
first,
so
in
here
you
can
see
actually
two
buttons.
One
is
upload
by
url.
One
is
upload
by
upload
pattern
directly
from
file
systems.
If
you
click
on
it,
you
would
actually.
A
You
would
actually
have
this
particular
file
file
open
file
system,
api,
from
which
you
can
actually
upload
your
pattern,
yaml
directory.
The
second
thing
that
you
get
is
actually
import
by
url
in
here.
You
can
actually
paste
in
any
http
url
and
that
would
actually
download
that
particular
pattern
down
to
that
particular
pattern
and
will
actually
also
save
it
to
your
particular
account.
A
The
third
thing
that
also
misread
ui
messaging
server
supports
is
actually
the
ability
to
import
import
patents
from
github
or
remote
for
other
remote
providers,
private
repositories,
public
repositories
both
are
supported
depending
upon
the
provider
that
you're
using
it
has
it
can
it
also
supports
recursive
import.
That
is,
you
can
specify
that
okay
in
this
particular
repository
I
want
to.
I
want
to
import
every
pattern
that
exists
in
this
particular
directory,
so
yeah.
These
are
some
things
that
actually
mystery
servers.
A
Api
supports
right
now,
but,
as
you
can
see,
we
are
not
exposing
those
those
functionalities
at
the
moment,
but
this
is
something
that
gaurav
has
been
working
on
for
a
while,
but
I
think
collaboration
is
always
good.
So
if
someone
wants
to
collaborate
wants
to
take
a
look
at
it
that
how
this
these
things
are
working,
you
can
actually
contact
korrev
on
stock
or
if
you
have
a
bit
of
issue,
do
we
have
a
bit
of
issue
about
this?
I
think
we
do.
A
Novendo,
I
wonder
if
you
might
be
able
to
find
that
one.
So
I
think
let
me
do
it
add
the
link
to
the
issue.
You
can
actually
comment
on
the
issue
if
you're
interested
in
this,
whatever
I
think
the
the
link
to
the
doc
is
something.
Let
me
it's
another
chat.
This
is
where
it's
documented
that
how
the
ap
actually
works
so
yeah
if
you're
interested
collaborate.
A
Let's
move
on
to
the
next
topic
and
that's
for
alan
and
alan's
not
actually
here
so
early.
Would
you
like
to
speak
a
bit
about
it
because
actually
it's
been
a
while,
I
think,
if
alan
mentioned,
he
doesn't
have
access
to
a
talk
or
something
oh
yeah.
Maybe.
C
Yeah,
hey
mesh
mate,
aditya
he's
not
he's
not
on.
Is
he
so
if
he
isn't,
I
will
happily
steal
his
thunder.
C
All
right
all
right
good.
Let
me
give
some
context
for
this
particular
line
item,
which
is
so
alan
is
has
been
in
the
community
for
a
little
while
he
is
his
forte
is
ux,
and
so
he
he
had
been
expressing
some
opinion
or
giving
some
feedback
about
an
upcoming
design,
and
I
think
it
was
really.
It
was
just
one
quick
point
that
he
had
made
and
I
think
it
was
apt
that
is
on
the
concept
of
service
mesh
patterns.
So
wait
a
second.
C
So
on
this
call,
we
occasionally
talk
about
web
assembly
filters
just
onto
their
own,
the
tech
that
goes
inside
how
how
to
provide
support
for
any
envoy
based
data
plane,
of
which
I
don't
know
whether,
like
five
or
six
or
more
service
meshes
with
envoy.
C
As
this
data
play,
we
we
spend
some
of
that
time,
looking
at
istio,
specifically
because
it's
really
the
only
service
mesh
out
there
that
officially
supports
webassembly
filters
at
the
moment,
but
any
of
the
envoy-based
data
planes
are
capable
and
we've
proven
that
a
couple
of
times
over
good.
C
C
When
someone
goes
to
choose
some
pre-written
patterns
and
deploy
them
up,
apply
those
patterns
to
their
infrastructure
today
to
date
that
has
been,
you
know,
just
a
growing
collection
as
a
matter
of
fact
we're
talking
about
it
at
kubecon,
china,
but
there's
just
a
growing
collection
of
pre-written
patterns
like
best
practices
that
people
can
choose
to
go
deploy.
C
There
hasn't
been
really
a
catalog
of
what
those
are,
and
so
there
were,
I
think,
last
week,
just
two
fairly
quick
mock-ups
created
for
mesherie.io,
where
a
catalog
of
patterns
would
be
presented
to
a
user.
That's
that's
perusing.
The
website
they'd
be
able
to
filter
on
different
types
of
patterns
and
then,
when
they
click
on
a
pattern,
they
would
potentially
get
a
modal
like
this.
You
know
more
or
less
just
a
regular
shopping,
cart,
sort
of
catalog
experience.
They
click
on
a
pattern,
get
more
details,
see
related
patterns.
C
If
they,
you
know,
see
the
compatibility
of
the
pattern
when
they
might
want
to
use
it
when
they
don't
and
at
some
point
like
like
immediately,
it
would
be
like
they
would
click
to
copy
that
url.
Take
that
url
and
import
the
pattern
into
meshri
at
some
point
potentially
in
the
future.
Maybe
that's
a
little
more
of
a
direct
connection,
but
but
if
you
kind
of
get
the
point
about
this
catalog
and
letting
people
peruse
it
and
find
you
know
common,
you
know
best
practices
that
they
might
want
to
apply.
C
If
you
think
about
that
same
concept
toward
filters.
Web
assembly
filters
that,
in
the
upcoming
release
of
mesherie
v0.6,
which
is
like
would
rc1
come
out
on
friday,
thursday
last
week.
So
so
v0.6
is
just
around
the
corner.
It
will
come
with
some
a
few
patterns
and
a
few
filters
out
of
the
box.
You
can
add
your
own,
but
it'll
also
come
with
some
baked
in
and
okay.
Well,
when
the
user
goes
to
spin
up
mesherie
and
kind
of
look
around
and
look
at
what
you
know
what
they
can.
C
What
filters
are
available?
They're
not
going
to
be
very
well
described
at
the
moment
like
it's
going
to
be
the
name
of
the
filter,
which
is
hopefully
indicative
of
like
what
the
thing
does.
But
if
someone
wants
to
find
out
more
about
like
if,
if
the
name
of
the
filter
is
the
the
jwt
9000,
which
I
think
is
literally
the
name
of
one
of
the
the
pranav,
was
it
pranav
bot
that
had
written
this,
the
jwt
manipulator
9000
like
what
does
it
do?
C
C
Is
there
something
more,
you
know
more
simple
that
can
be
presented
more
simpler
is
there's
something
simpler
that
can
be
presented
that
where
people
just
have
a
hyperlink
and
it'll
take
them
over
to
the
filter
itself,
where
it
was
sourced
from
explain
some
stuff
about
the
filter,
or
is
that
just
a
poor
man's
catalog
like?
Should
we
anybody
have
thoughts
about
this?
I
suspect
it
would
help
if
we
brought
up
measures,
ui
and
sort
of
sort
of
took
a
look
at
what's
currently
there.
C
C
Nice,
oh
got
it
hardy,
yep,
very
good,
yeah,
that's
a
good
question
already.
So
hardy
was
like
as
we're
talking
about
this
potential
filter
catalog,
it's
like
yeah.
This
is
a
similar
concept
to
what
we
were
just
discussing.
This
is
a
little
bit
yeah.
I
don't
know
like
like
the
service
mesh
catalog
that
we
were
just
looking
at.
I
think
that
that's
pretty
similar
here.
Let
me
there's
this.
C
You
know
grab
that
this
is
a
draft
version
of
what
the
catalog
would
be,
but
like
people
can
go
out,
choose
from
the
catalog
and
say
yeah
that
one
they
can
import
it
like
into
their
deployment
that
I
think
in
this
way,
these
two
concepts
are
kind
of
similar
like
there
there's
a
hub,
there's,
there's
an
online
catalog
people
can
bring
and
contribute
to
so
just
kind
of
like
like
a
docker
hub
for
the
yeah
and
so
but
for
the
web
assembly
filters
to
the
extent
that
that
hub
isn't
a
standalone
site.
C
So
if
you're
running
mesherie
deployed
either
locally
or
in
your
remote,
your
kubernetes
cluster,
if
you're
in
this
app
and
you're
actively
managing
your
infrastructure,
you're
actively
managing
your
mesh,
I
think
the
the
only
the
nuanced
difference
would
be
that
you
might
have
a
catalog
here
as
opposed
to
like,
and
it
would
be
sort
of
you
know
a
hub
inside
of
your
deployment
as
opposed
to
something
separate.
C
Hardy,
I
think,
has
made
a
good
analogy,
like
hey
here's,
a
way
of
sharing
webassembly
filters
or
like
a
docker
hub
like
there's
a
way
of
sharing
like
a
service
mesh
patterns
thing,
and
so
actually
you
know
hardy,
I'm
glad
you
brought
this
up
because,
for
my
part,
I
hadn't
like
a
next
step
beyond
what
I
was
just
describing
is
well
geez.
If
there's
a
catalog
of
pattern
of
service
mesh
patterns,
there's
a
catalog
of
webassembly
filters.
C
C
Not
just
the
patterns
are
not
just
the
filters,
but-
and
that's
certainly
something
to
think
about
like
should
that
experience
should
the
focus
of
that
experience
be
as
a
site
that
people
can
peruse
interact
with
add
their
own,
you
know,
do
do
hub
hub,
like
things
or
as
a
focus
on
the
ux.
C
C
Yeah,
so
so
it's
something
that
something
to
think
about,
like
there
have
been
a
number
of
people.
Who've
contributed
webassembly
filters
already,
there's
been
a
number
of
people
who
have
contributed
service
mesh
patterns
and
we're
trying
to
create
a
place
where
people
can
create
their
own
patterns
and
just
selfishly
hoard
them
or
where
they
can
share
them
with
others.
C
I
think
sometimes,
that
sharing
and
that
process
discovery
is
maybe
easier
if
it's
a
standalone
site
like
there's
the
barrier
to
looking
at
the
catalog
and
perusing
it
is,
you
know
as
low
as
it
can
be.
You
just
open
up
your
web
browser.
C
It
can
be
a
little
harder,
maybe
to
share.
I
mean
it's
really
easy
to
share
something
like
this.
Like
you,
click
on
it
and
like
oh,
you
know,
click
the
button
to
share
it
and
you
send
an
email
or
something,
but
but
it's
not
as
it's
not
it
is
so
that's
really
great.
An
aspect
of
having
a
catalog
in
messagery
is
like
if
you're
another
mesher
user,
then
you
can
ongoing
kind
of
track.
C
The
fact
that
you
shared
with
someone
else-
and
maybe
maybe
you
know,
nadish
who's
on
the
call-
maybe
he
only
wanted
to
share
his
pattern
with
foodkash,
that's
on
the
call
and
so
sharing
in
that
sense
is
maybe
easier
to
control
when
it's
in
application.
C
I
do
think
that
one
thing
that's
kind
of
a
challenge
for
new
users.
Is
they
come
into
mesherie
and
they
they
look
and
they
see.
Oh.
This
is
great
like
there's
some
there's
some
patterns
that
are
available.
There's
some
filters
to
use
okay,
so
yeah.
What's
this
test
filter
do.
C
C
A
So,
let's
move
on
to
the
next
item:
it's
from
actually
mario
or
arabic.
I
don't
think
of
the
sheikh
kumar
is
on
the
call.
So,
mario
do
do
you
have
do
you
have
any
updates,
not
not
maybe
in
terms
of
code,
in
terms
of
something
that
you
discovered.
While
you
were
looking
into
testing
uploading
and
deletion
of
buttons.
D
Yeah
sure
thanks
well,
I
was
taking
a
look
at
the
example
patterns,
provided
a
also
a
documentation
for
you
know
this
this
feature,
and
so
I'm
just
trying
to
I'm
actually
thinking
about.
What's
the
best
way
to
to
to
get
the
pattern
file
from
the
test,
so
one
option
is
to
add:
there's
a
fixtures
folder
for
in
in
cypress.
D
But
doing
that
might
not
be
the
best
option
because
you
know
if
there's
any
change
to
that
pattern,
maybe
we'd
like
to
use
the
latest
one.
So
then
I
was
looking
for
a
way
to
to
download
the
the
files
directly
from
from
github.
D
So
I'm
not
sure
what's
the
best
option,
maybe
we
just
we
really
don't
care
like
what
version
of
that
example
pattern
we
use,
but
maybe
we
do.
Anyone
has
any
feedback
about
that.
D
Like
do
we
really
care
like
if
we,
if
our
test
starts
using
an
outdated
pattern
file,
I'm
not.
D
D
So
there's
some
patterns
there
yeah
the
filter,
one
yeah,
that's
the
one
I
was
thinking
in
using
so
my
question
is
like
do
we
we
want
to
grab
the
latest
one
every
time
like
dynamically
download
it
from
github
during
the
test
run
or
or
just
copy
copy
it
look.
I
have
it
in
our
in
our
cypress
test
fixtures
file,
folder
file,
folder,
that's
my
question.
C
Let
me
I
think
I
was
trying
to
have
too
many
conversations
at
once.
For
my
part,
let
me
regurgitate
this
real
quick.
It
was
in
part
you're,
highlighting
that
as
we
go
to
have
these
end-to-end
tests
that
we
want
to
make
sure
that
the
tests
themselves
continue
to
be
valid,
and
as
such,
we
recognize
that
whether
you're
using
a
filter,
a
specific
version
of
a
filter
or
a
specific
version
of
a
pattern
that.
D
Okay,
so
then
would
it
work
if
let's
say
so,
I
can
grab
a
copy
of
this
file
paste
it
over
at
our
cypress
fixtures,
folder
and
just
version
it
as
0.0.1.
D
And
that
way,
whenever
there's
another
one,
you
would
have
to
manually,
add
it
and
then
and
then
I
can
make
a
dynamic
test.
So
just
like
you
know,
the
cyprus
is
based
on
moca,
so
we
can
make
some
dynamic
tests,
so
we
create
an
array
and
just
point
to
any
files.
D
D
Because
that
way,
because
otherwise
I
was
looking
at
a
way
of
downloading
like
the
latest
like
github
content,
but
maybe
that
would
have
some
more
complexity
whenever
we
want
to
look
at
like
different
versions
of
that
file,
not
sure
if
that's
possible.
So.
C
C
You
write
a
test,
you're
you're
you're,
taking
on
more
things
to
sustain
like
at
some
point,
the
tests
get
outdated
and
so
the
the
more
that
you
can
write
those
tests
to
be
anti-fragile
or
to
be
long-lived
or
or
to
like
part
of
that
is
what
you're
saying
is
like
to
also
just
not
produce
false
positives
understanding
that
a
test
itself
might
get
get
aged
that
that
thing,
I
think,
that's
universally
true,
like
yeah,
we
should
and
then
the
second
thing
that's
part
and
parcel
to
that
is
like
versioning
things.
C
It's
like
really
hard
to
argue
against
the
yeah,
the
benefit
of
like
versioning
stuff.
So,
like
the
part
of
your
proposal,
is
like
hey,
should
we
should
we
make
sure
that
we're
versioning
both
patterns
and
then
also
as
we
as
the
community
goes
to
at
least
seed
an
initial
set
of
webassembly
filters?
D
Yeah,
because
looking
at
the
test,
it'd
be
really
good
to
have
those
dynamic
tests,
because
whenever
there's
a
new
version
of
some
sample
filter
pattern
file,
we
want
to
test
against.
We.
We
just
need
to
copy
that
new
one
in
the
cyprus
pictures
folder
and
the
test
would
automatically
pick
it
up
as
long
as
well
there.
D
It
follows
like
a
naming
convention,
which
I
think
we
can
just
add
some
comments
in
the
in
the
test
itself,
like
just
so
that
it's
clear
you
know
just
maybe
there
could
be
some
regex
that
looks
for
all
istio
filter
filter
patterns,
regardless,
if
you
know
it,
they
end,
they
have
a
suffix
with
the
version,
but
then
again
that
the
test
would
repeat
itself
on
all
of
those
files
so
yeah.
I
think
that
that'd
be
really
good.
D
C
Thank
you
yeah
yeah.
Now
this
is
good.
I
mean
one
thing
to,
as
you
think
about
it.
One
thing
to
be
very
well
aware
of
is
well.
Is
the
there's
two
things
one
that
the
web
assembly
filters
that
are
being
included
as
seed
content,
like
as
initial
content
in
a
measure
release
those
aren't
versioned
today,
but
ashish
and
utkarsh,
and
maybe
rudraksha
somewhere
between
the
three
of
those
gentlemen?
C
So
at
some
point
those
filters
will
be
versioned.
There
is
okay,
okay,
fine!
So
then,
if
if,
if
that's
going
to
be
true
from
here
on
out
it
would
it
be
the
case
that
when
we
think
about
testing
those,
do
we
need
to
bother
with?
C
Well,
I
don't
know
like
I
guess,
there's
two
things
like
hey:
if
you've
got
some
filters
that
are
out
of
the
box,
like
hey,
there's
tests
that
can
be
written,
that
use
those
and
just
leverage
them
as
built-in
content
as
built-in
capabilities
and
go
do
things
with
them,
and
we,
if
we
expect
for
these
built-in
filters
to
be
long-standing,
like
you
know,
pretty
much
in
in
measuring
available
in
future
measuring
releases
for
as
far
as
the
eye
can
see,
then
it's
probably
a
pretty
good
idea
to
write
some
a
few
tests
around
those
because
they're
not
gonna
they're,
not
gonna,
go
away
necessarily
fine
good,
but
also
the
thing
that
you're
one
of
the
things
that
you're
highlighting
is
that
like
well,
and
it
was
an
utrush,
I
think,
was
just
talking
about
the
fact
that
mescheri
supports
you
can
do
a
measuring
deployment
and
then
you
can
let
you
can
import
in
new
filters
and
so
that
so,
okay,
fine,
so
that
functionality
needs
to
be
tested
as
well.
C
D
So
we're
talking
about
the
binaries
right
like
brushing
them
and
having
the
binaries.
Well,
if
you
ask
me,
I
think
that
the
upload
today
might
not
not
might
not
accept
like
binary
files,
at
least
that's
what
I'm
thinking,
because
the
the
jsx
that
I've
been
looking
at
for
for
the
uploads.
It
just
accepts
like
three
different
formats
like
yaml
and
other
two
one
or
two,
but
I
I
it
didn't
didn't
feel
to
me
like
it
would
accept
some
other
format.
A
So
actually
yeah,
it
does
accept
other
formats,
including
if
something
is
something
can
be
represented
at
securities,
manifest,
that's
a
format
everything
won't
be
able
to
like.
We
cannot
represent
everything
that
can
be
done
via
patents
in
manifest,
because
this
is
more
of
a
superset
of
even
kubernetes
manifests
the
second.
The
second
format
would
be
actually
cytoscape
json,
that's
a
format,
that's
supported.
The
third
format
is
actually
you
can
encode
everything
in
json
and
that's
also
a
support
format,
so
yaml
json
site
escape
json
in
communities
manifest.
D
A
Yeah,
actually
so
yeah,
so
in
the
in
the
ui.
The
the
format
that
is
visible
is
actually
the
reason
that
is.
The
case
is
because
you
can
submit,
if
submit
patterns
in
any
format,
as
I
mentioned,
yaml
json,
scientific,
json
or
humanities
manifest,
which
could
be
again
yamuna
jason.
Actually
yamil
is
the
only
one
supported
but
yeah
you
can't
submit
in
it
in
any
format,
but
the
way
we
store
it.
A
The
way
we
preserve
it
is
actually
in
yaml,
and
that
is
the
reason
that
you
can't
only
access
it
like
when
you
click
on
something
all
you
can
see
is
and
is
yaml.
It
doesn't
matter
if
you
uploaded
a
json
or
even
a
cytoscape
system
which,
with
all
of
site,
escape
annotations.
If
you
would
click
on
this
particular
panel,
you
would
be
able
to
see
it
in
yamanote,
because
that's
the
format
we
actually
stored
patterns
in
so.
A
Actually,
that's
that's
what
I
was
mentioning
under
this
topic
and
that
is
mystery
actually
supports
multiple
okay,
you
can,
I
cannot
say
so.
Mystery
can
actually
support
multiple
formats,
multiple,
multiple
ways
of
uploading
stuff.
The
thing
is
that,
right
now,
it's
not
quite
exposed
in
here
exposed
in
this
particular
ui,
but
that
because
measure
ui
is
not
the
only
client
of
machine
server
measuring
curtail
meshita
is
another
client.
D
D
Yeah,
I
mean
sorry,
I
tried
to
be
more
clear,
there's
an
accept
attribute
in
in
the
in
the
html
element,
so
I
thought
that,
since
it
didn't
say,
accept
and
then
the
format
that
we're
talking
about
it
wouldn't
accept
it,
but
it's
actually.
I
just
went
over
the
msdn
docs,
so
it'll
it'll
not
validate
the
format.
So
even
though
it
doesn't
say
like
a
specific
format,
this
is
just
for
the
for
the
browser
to
hint
or
to
hint
the
browser,
let's
say:
there's
a
file
picker.
D
A
Yeah
so
yeah,
actually,
as
I
was
mentioning
right
now,
ui
or
like
ui-
supports
only
uploading
yamas
it
it.
It
is
sort
of.
It
is
sort
of
limiting
the
capabilities
of
a
memory.
Server
machine
server
supports
multiple
other
formats,
but
the
reason
you
may
not
want
to
actually
change
the
are
you
all
right
we
mentioned.
Yama
is
normally
supported.
Format
like
we
specified.
A
Yeah
the
the
issue
would
be
that
if
you
would
actually
change
that
and
try
to
upload
json,
the
upload
won't
quite
work.
The
reason
is
that
mystery
server
machine
server
needs
to
know
what
format
it
is
so
that
it
can
do
the
transformation
internally
and
because
and
for
that,
actually
it
uses
content
type.
I
think
that's
the
header
it
uses
to
determine
what
the
content
type
is,
and
that
is
how
the
mystery
service
client
is
supposed
to
tell
that.
Basically,
the
approach
is
exactly
similar
to
how
communities
api
works.
A
Communities
api
also
supports
reformatories
and
protobuf
and
yama,
and
you
can
also
specify-
and
there
are
what
kind
of
thing
you
are
you
are
sending.
So
that's
the
exact
same
like
structure
mystery
server
also
adopts
in
here.
You
have
to
specify
that
what
it
is,
but
because
the
api
call
call
header
won't
have
that
header
attached.
A
It
won't
have
that
attribute,
so
it
won't.
Basically,
the
upload
would
fail
because
it
would
assume
that
it
is
actually
yaml,
because
the
client
said
so,
but
the
client
was
so
yeah.
I
hope
I'm
making
sense.
The
thing
is
that,
right
now
it
is
sort
of
hardcoded
why
that
is
the
only
content
that
that
can
come
up.
A
A
For
filters
actually
the
upload
would
go
through,
but
I
think
navindu
is
the
better
person
to
talk
about
that
because
yeah,
but
I
think
for
filters
the
upload
would
go
through
because
it
is
treated
as
a
byte.
So
anything
that
comes
in
that's
acceptable,
so
yeah,
I
think
that's
how
filter
approach
works.
It's
quite.
A
I
think
actually
another
thing
binary
is
specific
to
filters.
While
the
application
and
patterns
are
only
patterns
could
be
yarmouth,
json,
cytosaves
and
kubernetes
manifest
application
could
be
only
yaml
and
filters
can
be
binary
along
with
a
yaml
based
fiber,
so
yeah.
D
Yeah,
because
what
I'm
trying
to
say
is
that
when
we
use
a
browser,
the
the
accept
attribute
would
or
it
might
you
try
to
upload
a
filter
and
see
if
by
default
you
in
the
picker,
can
you
you
can
see
a
binary
like
do
you
have
binaries
in
your
when
you're.
D
You
see
they're
they're
highlighted
you
see,
so
that
means
that
we're
we
would
make
a
user.
Let's
say
you
have
a
binary
there.
Could
you
create
a
binary
just
even
though
it
doesn't
work
just
like
the
dot
like
just
right,
click
wherever
and
just
pretend
it's
a
binary
like
just
name
it
accordingly.
So
what
I'm
trying.
D
That
the
things
that
cyprus
can
test
is
like
this,
this
this
speaker,
so
so
by
draying
out
any
files
here,
we're
making
the
user
think
that
it's
not
supported,
but
it
is
so
the
way
to
make
this
not
gray
out
on
binaries
would
be
to
modify
our
our
component
so
that
the
asset
includes
the
binaries
extension
right.
D
So
then
they
would
those
binaries
wouldn't
gray
out
and-
and
I
I
and
any
user
would
would
not
assume
that
it's
not
supported,
because
because
that's
what
I'm
thinking,
if,
if
the
fi
that
the
file
grays
out,
I'm
thinking
it's
not
supported,
and
then
I'm
trying
you
know,
you
know
putting
that
user
hat
on
like
a
really
regular
user,
not
a
power
user.
That
would
like
just
go
to
the
code
base
or
I
don't
know
documentation,
and
you
know,
but
that's
just
an
observation
you
know:
does
it
make
sense
or
oh.
C
D
Okay,
okay,
good
yeah,
because
that
was
part
of
my
confusion
when
I
was
going
over
this
like
a
bit
like,
so
we
support
binary,
but
it's
not
in
the
accept
attribute.
So
then
it's
not
supported
or
is
it
supported,
and
that
that
made
me
like
stumble
a
bit
and
instead
of
making
some
progress
on
the
test,
I
was
focusing
on
that
or
maybe
just
thinking
about
different
test
inputs
like
maybe
we
should
test
with
different
formats
but
like
okay,
so
which
ones
are
they
so
then?
Now
that
we're
talking?
D
I
think
this
is
clearer.
So
so
I'll
just
take
a
look
at
the
binaries
or
maybe
I
could
wait
for
so
eventually
the
binaries
will
be
like
release
artifacts
off
of
those
of
that
ripple
right
correct,
so
so,
instead
of
me
building
them
and
then
adding
them
in
the
in
the
cypress
test,
maybe
better
for
those
binaries
to
be
taken
from
github.
D
I
don't
know
because
if
they're
artifacts
I
could
use
the
github
cli
and
just
grab
them
during
runtime
or
maybe
their
some
script,
so
that
so
that
they're
downloaded,
I
don't
know
but
anyways
yeah.
I
don't
want
to
take
all
the
meeting
time.
Sorry
so
so
that's
all
I'll
keep
taking
a
look
at
the
actual
test,
but
I
think
this
this
helps
a
lot.
Thank
you.
Thank
you
all.
A
Again
so.
D
Let's
so,
should
I
sorry
should
I
should
I
create
an
issue
based
on
this
observation
of
of
of
the
accept
format,
yeah
yep
sure
yeah,
please,
by
the
way,
just
okay
and
what's
what's
a
wasom
binary
format
like
what's
the
extension,
it's
was.
D
A
Yeah,
although
yeah,
it's
mostly
awesome,
it
could
be
dot
wad
as
well,
so
or
it
could
be,
none
as
well,
none
in
case,
so
some
operating
systems
do
support
content
with
no
extension
and
they,
yet
they
can
still
identify
what
content
type
it
is
unlike.
Unlike
windows,
windows
cannot
identify
if
you
change
the
extension
so
yeah
all
three
works.
Actually,
what
wasn't?
None.
D
Okay,
could
you
write
in
the
chat
like
the
formats
just
so
that
I
can
just
make
sure
I
don't
misspell
them.
Please.
A
Did
you
say
wd
or
wt
w80,
it's
very
simply
text,
so
you
can
write
smd
and.
C
C
Or,
like,
I
guess,
go
recap
real
quickly
for
me:
utkarsh
the
limitations
of
the
ui.
Did
you
say
that
users
can't
import
binaries
through
the
ui.
A
Yeah,
actually,
I
was
mentioning
that
that,
although
mystery
server
supports
importing
from
multiple
in
multiple
formats,
so
you
can
actually
say
side
escape
json,
it
will
just
work.
You
can
say
it's.
The
yarmouth
will
still
work.
If
you
say
nothing,
it
means
yaml.
If
you
say
it's
quantum
type
is
it
is
json,
it
can
accept
json,
and
you
can
also
say
this
is
kubernetes,
manifest
first
convert
and
then
save
so
that
is
also
acceptable.
A
while
the
ui
only
supports
yaml,
because
it
does
not
say
anything
so
server
assumes
it's
the
amulet.
A
If
you
upload
anything
else,
it's
going
to
error
out
because
it
does
some
validation.
It's
going
to
error
out
that
whatever
you
gave
in
that's
definitely
not
pattern
and
it's
going
to
written
an
error,
basically
a
while
in
the
actually
even
mesh
map
mesh
map
also
have
this
kind
of
validation.
I
mean
valid
mesh
map.
Also,
does
this
upload
form?
Basically
what
mesh
map
does?
Is
it
leverages
mystery,
server's
ui
to
specify
that
the
site
is
json,
save
this
but
convert
it
before
saving?
A
So
those
are
things
that
mesh
map
is
doing
while
ui
is
not.
I
think
messenger
ctl
also
supports.
I
think
it
supports
jason
as
well.
If
I'm
not
wrong,
but
that's
something
probably
push
can
talk
more
about,
but
he's
not
here.
Yeah.
B
I
I
had
a
doubt:
you
said
that
dot
word
files
can
also
be
here.
So
I
mean
I
was.
I
had
an
idea
that
only
the
compiled
wasn't
binaries
can
be
dropped,
that's
a
but
that's
not
that's,
just
a
text
file.
So
how?
How
are
we
supporting.
A
That
right,
yeah,
actually
so,
I
think
recently
not
recently
but
a
while
back
support
for
a
wasm.
There
is
an
echo
here
ago.
Support
for
wasm
text
was
also
added.
That
is,
you
can
write
simple
web
assembly
and
you
can
just
send
it
off
so
and
that
will
actually
work.
As
far
I
mean
as
far
as
I
remember
that
does
work.
B
For
the
onward
filter
resource
in
istio
you're
talking
about.
C
A
C
Yeah
apologies,
I
was
just
gonna
suggest
or
that
it
might
also
be
a
good
future
meeting
item
to
to
just
like
demonstrate
or
to
answer
that
same
question
that
you
just
answered,
but
through
demonstration
of
like
hey
walking
through
the
ux
of
importing
a
filter
into
the
ui
or
maybe
through
the
mastery
ctl,
it
might
serve
to
refresh
or
educate
the
rest.
You
know
some
of
the
rest
of
us.
C
Yeah,
okay,
oh
ashish,
you've
been
doing
a
lot
around
dynamically
importing
seed
content
in
some
of
the
same
ways
that
mario
was
just
discussing.
That
would
need
to
be
done
for
the
cyphers
testing.
It'd
be
probably
good.
If,
if
you
share
some
notes,
there
could
point
to
what's
being
done
now
should
be
in
mesh
redox
at
this
point.
So.
A
Cool,
so
we
have
a
few
items
left
on
the
agenda,
but
we
are
basically
it's
9
30.
It's
time
should
we
go
ahead
with
our
agendas
or
I
mean
is
everyone?
Is
someone
interested
in
looking
at
istio's
version
plug-in
support
in
michigan,
okay,
okay,
so
so
thank
you
for
coming
to
the
meeting
in
case
someone
wants
to
drop
off,
you
can
or
if
you're,
interested
in
support
for
wasn't
plug-in
and
machine.
Without
doing
anything,
you
can
actually
stay
so
yeah,
let's
get
started.
A
Let
me
let
me
pull
up
the
button,
which
was
here
well
right
now,
it's
not
okay
yeah.
So
this
is
a,
and
this
is
a
yaman,
as
everyone
can
see.
What
this
is
going
to
do.
This
particular
yamaha
is
that
it's
going
to
it's
going
to
okay.
Let
me
go
through
this
particular
in
case
someone
is
not
formula
of
how
patterns
look
like.
So
what
I'm
doing
in
this
particular
stage
is
actually
I'm
creating
a
namespace
test.
A
If
my
name
says
already
exists
this
stage
this
state
and
this
step
is
actually
basically
it
is
ignored
at
the
same
time,
partly
what
I'm
going
to
do
is
I'm
going
to
provision
istio
service
mesh
both
of
the
both
of
the
steps
are
going
to
happen,
partly
at
the
same
time.
What
I'm
doing
here
is
I'm
actually
saying
that
provision
seo
service
mission
is
the
iphone
system
name
space.
I
this
is
the
version
I'm
requesting
I'm
requesting
the
latest
one
that
is
1.12.
A
The
reason
is
that
I'm
demoing
more
than
plugin
and
that's
available
in
latest
latest
steam.
I'm
also
saying
that
hey,
please,
enable
automatic
cycle
injection
in
namespaces.
This
is
a.
This
is
an
expression
which
would
be
evaluated
on
the
runtime.
What
I'm
basically
saying
is
that
hey
go
ahead
into
this
particular
service
and
whatever
namespace,
that
I've
created
and
even
automatic
site.
Conjecture
in
that
particular
namespace.
These
two
steps
are
happening
manually
as
soon
as
they
come
as
soon
as
they
complete.
A
The
foreflow
would
move
on
to
this
stage
in
this
stage,
because
I
specified
dependencies,
I'm
saying
that
please
make
sure
that
you
run
this
particular
thing.
If
and
only
if
this-
and
this
step
are
not
only
complete,
they
also
complete
successfully.
Only
then
this
particular
step
would
be
executed
at
this
end
also,
this
particular
step
so
what's
going
to
happen
in
this
step,
is
actually
I'll
provision,
an
application,
because
I
want
to
demo
that
that
the
wasm
plug-in
is
actually
working
there
wasn't
binary
is
actually
working.
A
So
what
what
is
happening
is
I'm
actually
provisioning
an
application.
Replicas
are
going
to
be
one,
I'm
placing
a
label.
This
label
could
be
anything.
This
is
just
something
for
selectors,
I'm
spinning
up
nginx
nginx
image,
nginx
container,
because
that's
the
easiest
thing
to
do
this
is
this
is
it
this
is
all
you
need
to
actually
provision
a
particular
application
in
mystery.
It
will
also
ensure
that
you
can
access
it
in
access
it
from
your
browser,
because
it
provides
load
balancer
for
you
so
yeah.
This
is.
A
This
is
actually
more
than
enough
to
provision
application.
A
lot
of
stuff
in
here
is
not
actually
required
to
provision
application,
so
it's
it
looks
far
more
smaller
if
you
just
if
you
just
want
to
provide
an
application,
but
the
last
step
is
actually.
This
is
a
newest
audition
edition
that
I
was
about
to
talk.
Basically,
we
talked
last
week
also
about
this,
and
that
was
support
for
washington
plugin.seo.
This
is
not
something
that
we
added
support
for
manually
because
of
the
way
that
we
have.
We
have.
A
Basically,
we
have
architected
stuff
and
ashish
has
our
support
for
dynamic
corporate
registration.
So
what
happened
dynamically
was
was
my
adapter
was
already
running,
but
because
every
24
hours
it
takes
it
fetches
the
new,
a
new
istio.
Basically,
it
figures
out
that
okay,
there
is
a
new
seo
release.
Now,
if
there
is
a
new
release,
let
me
raise
a
new
confidence
and
automatically
the
support
was
added
for
this
particular
component.
A
So
now
I
can
so
if
you
have
adapters
running
and
if
it's
not
very
old
or
like
it's,
if
it's
not
a
month
or
two
month
old,
you
should
also
have
support
for
this
thing.
So
yep,
you
can
run
this
pattern
with
your
old
attack
old
adapter
and
it
should
just
work.
A
Fine
because,
like
I
didn't
change
the
line
of
code
for
this
thing
to
work,
and
once
all
you
have
to
do
here
is
what
I'm
doing
is
I'm
actually
specifying
that
hey,
please
put
in
this
particular
version
binary
in
the
selectors,
I'm
saying
that
match
all
of
the
workloads
which
match
which
have
this
particular
label,
and
that
is
actually
the
this
label
that
I
actually
attached
to.
It
is
a
fancy
label,
because
okay
that
could
so-
and
this
is
plug-in
config
plug-in
config-
is
actually
so.
A
If
someone
has
seen
onward
filter
support
for
sd,
which
was
earlier.
This
used
to
be
something
this
used
to
be
string
and
right
now,
no,
it's
not
it's
a
struct.
You
have
to
specify
it
in
this
particular
format.
You
cannot
encode
in
base64
and
they
do
stuff
like
that.
You
have
to
specify
it
in
map
kind
of
way.
That's
that's
how
it
is.
It
is
supposed
to
be
encoded.
Now,
if
you
want
the
the
particular
step
would
feel
what
I'm
saying
here.
Is
that
prefix
any
request
that
comes
that?
A
Has
this
particular
prefix?
If
it
has
get
method,
the
method
of
http
request
is
good,
then,
actually,
basically
add
authentication
onto
that,
and
these
two
credentials
are
actually
supported.
This
is
base64
encoded.
This
is
not
b64
encoded.
So
if
I
actually
apply
this
particular
yaml,
I
have
the
same
thing
here
and
it
was
actually
uploaded
dynamically.
So
if
I
do.
A
It
will
take
a
while,
because,
again
because
token
is
expired,
it
can
work
with
any
version
binary
right
yeah.
Actually
it
will
work
with
any
version
binary,
but
you
will
face
hiccups.
If
you
try
to
use
the
rate
limiter
one
we
have.
A
The
reason
is
that
actually,
I
would
have
demoed
that
one
instead
of
using
base
like
base
authentication,
the
hiccup
that
you
would
actually
face
is
that
the
the
configuration
that
it
accepts
is
in
base64
in
code
format
and
like
right
now
you
are
supposed
to
give
configuration
as
I
was
mentioning
you
have
to
give
configuration
as
if
it
was
a
struct
and
not
a
string
earlier
in
onward
filter.
I'm
refiller
used
to
accept
configuration
and
string
on
filters
still
actually
accepts
configuration
and
string.
A
So
if
you
would
actually
check
the
logs
the
thing
that
it's
in
the
configuration
that
it
receives,
it
is
actually
string.
So
actually
histo
is
serializing.
The
configuration
that
we
are
sending,
I'm
not
sure
why
but
yeah.
That's
that's
how
it
is
so
yeah.
Technically,
every
version
binary
should
work.
Even
the
even
the
ratio
would
work.
The
only
caveat
is
that
it
will
throw
error
that
hey
you
haven't,
provided
any
configuration
or
you
haven't
provided
me
actually,
instead
of
throwing
it,
it
would
actually
panic
but
yeah.
A
The
reason
we
actually
require
token,
if,
if
it
seems
unnecessary,
it's
not
quite
unnecessary.
The
reason
is
that
we
also
actually
keep
track
of
the
resources
that
you
have
provisioned
just
not
because
we
want
to
or
for
the
sake
of
keeping
track,
but
because
it's
also
useful.
We
also
make
sure
that
update
operations
are
actually
updated
and
not
treated
as
created,
and
basically
that
particular
data
helps
this
lot.
A
In
the
same
time,
it
is
supposed
to
help
us
map
the
state
of
the
cluster,
with
the
state
that
we
are
maintaining
internally,
so
that
we
can
do
mappings
of
the
state
of
the
cluster
in
the
internal
data
that
we
have
and
attach
other
material
to
it.
So
the
pattern
has
applied
successfully.
It
is
saying
pattern,
particularly
it
did
some
installation
enabled
automatic,
recycle
injection
also
deployed
this
particular
application
and
created
voice
and
plug-in
sample.
A
So
was
that
feedback
on
the
cli
was
that
yeah?
Actually,
this
is
something
that
mystery
server
does
generate.
It
sends
it
to
the
clients
as
well.
It's
it's
it's
ignored
by
the
ui
at
the
moment,
so
machine
server
does
send
this
feedback
that
what
exactly
happened,
because
sometimes
it
can
happen
that
partial
things
succeeded
partial
field.
The
reason
it
would
happen
is
that
you
said
that
this
thing
is
completely
independent
of
everything.
A
There
is
no
depends
on,
so
in
that
case
the
partial
workflow
would
still
pres
like
succeed.
So
in
that
case
actually
server
also
lets.
You
know
that
okay,
this
particular
section
failed.
While
these
all
succeeded
so
yeah,
it
does
send
you
the
feedback
that
what
exactly
happened
it
does
it
like
it
collects
aggregates
in
then
sense,
so
it's
not
quite
interactive
but
yeah.
It
does
sense.
Basically
it
sends
you
back
the
feedback,
so
yeah,
sorry.
C
Wow
I'm
getting
stuck
so
wait
remind
me
again,
the
that
was
a
synchronous,
a
synchronous
call
that
was
made
and
that's
the
how
the
responses
were
funneled
back.
A
So
actually,
the
api
is
sort
of
synchronous.
That
is
when
we
send
the
request
to
machine
server.
It
does
stuff
parallely
it
aggregates
all
of
the
things
happening.
So
that
is
why,
like,
if
I
probably,
if
I
apply
this
thing
again,
the
order
of
the
law,
the
order
of
the
messages
would
be
different
because
it
probably
is
things
getting
a
different
way,
but
it
aggregates
and
then
finally
sends
back
it's
not
a
it's.
It's
not
a
requirement.
It's
just
how
I
initially
created
the.
A
C
What
do
you
guys
think
briefly,
the
a
a
bit
of
a
different
ux
in
which
maybe
we
just
prepend
like
the
feed,
this
feedback
that
comes
back
is
wonderful.
It's
it's
detailed
confirmation
of
how
their
infrastructure
has
been.
You
know
how
their
request
has
been
fulfilled.
This
is
really
needed
in
the
measure
ui.
C
C
A
Everything
is
server
right
now
everything
was
sent
by
the
server.
Actually,
it's
so
server
just
sent
it.
The
original
responders
were
the
companies
which
are
handling
it.
So
some
for
example,
because
I
wrote
the
docs-
I
wrote
them
as
this
renault.
This
one
actually
came
from
mishri
cerveza,
because
misery
server
was
handling
the
deployment.
While
this
one
and
this
one
came
from
istio
adapter
because
they
were
hunting
these
components.
This
is
also
something
came
from
histo
adapter.
It
should
have
been
longer.
A
It
should
have
said
more
instead
of
just
saying
installed
right
now,
since
basically
it
meant
that
installed.
Is
your
service
mesh
but
yeah.
It's
not
saying
that
it
should
so
so
now,
as
I
was
talking
about,
the
application
has
been
deployed.
There
are
two
containers,
obviously,
because
I
said
I
specifically
instructed.
I
specifically
instructed
a
mystery
to
make
sure
that
the
automatic
side
conjection
is
enabled
on
test
namespace,
so
it
did
enable
that
and
after
that
it
provisioned
us
from
this
particular
application
for
me.
A
A
Yep,
so
it's
actually
showing
me
the
prompt
to
enter
username
and
password
and
if
I
hope
everyone
knows
there
is
no
authentication
and
default
engineering.
You
just
get
a
welcome
message,
so
this
is
something
that
was
indeed
added
by
the
by
the
packet
by
the
wasm
extension,
and
if
I
enter
admin,
3
admin
3,
that's
the
username,
that's
a
password,
and
I
click
on
sign
in
I
do
I
can
access
this
particular
page.
A
The
reason
admin,
3
and
admin
3
was
the
username
and
password
was
because
the
patent
that
I
actually
uploaded
a
pattern
that
I
uploaded
had
this
particular
credentials
in
this.
It's
just
b64
encoded.
It's
admin,
three
code
and
administration
written
in
an
encoded
format,
so
yeah
this
is.
This
is
how
mystery
supports,
wasn't
plug-in
without
adding
any
lines
of
code
and
it
will.
It
should
work
in
your
old
adapters
as
well,
if
it's
not
older
than
older
than
a
month
or
something
because
that's
basically
ashley
started
about.
A
Yep
so
yeah,
that's
yeah,
that's
that's!
Okay,
ashish
is
the
one
who
okay
yeah
so
yeah.
That's
also
something
that
I
was
sort
of
suggesting.
The
only
caveat
is
that
I
mean
you
are
the
one
who
has
actually
created
dynamic
computer
registration.
A
So
probably
you
would
face
the
trouble
to
identify
which
of
them
are
going
to
be
traits
and
which
of
them
are
going
to
be
workloads,
but
that's
something
that
would
be
probably
nice,
because
what
it
allah,
what
it
will
allow
in
terms
of
in
terms
of
mesh
map
or
even
for
validation,
is
that
is
that,
basically,
you
will
be
able
to
specify
that
this
thing
is
supposed
to
be
attached
to
something-
and
this
is
not
a
different
workload
and
also
you
would
be
able
to
specify
that
this
thing
can
be
only
attached
to
these
things
like
a
pod
or
a
a
port
or
a
deployment
or
a
rollout
or
application.
A
These
kind
of
things
so
in
terms
of
validation,
also
it
would
be
far
more
richer
in
terms
of
mesh
map,
also
like
the
ui,
would
get
far
more
richer
because
it
doesn't
have
to
do
things
manually,
which
is
which
is,
it
is
doing,
and
probably
it's
not
its
responsibility
adapter,
because
adapters
are
the
one
creating
the
confidence
they
should
have
the
responsibility
of
also
and
reading
it.
A
With
this
stuff,
like
with
this
kind
of
metadata
so
yeah,
I
think
that
this
should
be
trade
and
onward
filter
dot
is
there
should
be
probably
also
it
should
be.
A
trade
okay.
B
A
A
Actually
yeah
so
that
doesn't
like.
If
someone
is
running
an
older
adapter,
then
because
adapter
is
a
source
of
truth,
it
registered
schema.
So
it
said
that
this
is
not
workload.
This
is
this
is
not
trade.
This
is
workload
and
everything
is
going
to
work
out
just
fine,
even
if
mystery
version
is
latest
while
adapter
is
older,
because
adapter
is
like
authority
here,
investor,
it's
just
going
to
do
the
validation,
so
it's
it's
just
going
to
still
work
out
right.
So
where
would
the?
A
How
would
the
compatibility
break
unless
or
until
and
listen
until
you
were
talking
about
the
comp
like
market
compatibility
of
a
particular
pattern,
like
the
pattern
is
older,
while
the
adapter
is
newer.
C
Guys,
I
don't
know
that
people
have
seen
this
kind
of
software
that
much
actually
I
think
people
have
seen
this
kind
of
software
a
lot
and
they
see
it
in
the
form
of
like
a
virus,
which
is
to
say
that,
like
the
software
is
updating
itself,
it
is
the
year
2021.
So
I
guess
this
is
kind
of
appropriate,
but.
C
None
of
the
other
management
pieces
of
management
software
in
this
field
do
that
right,
like
I
haven't
seen
this
from
any
of
them,.
C
C
These,
you
know
base
things
and
then,
typically,
if
the
system
was
trying
to
support
being
remotely
managed
through
snmp,
it
would
also
come
with
its
own
mibs,
its
own
management
information
base,
like
its
own
special
package
that
that
describes
itself
and
that
you
can
query
and
keep
track
of
its
own
health,
and
so
when
a
management
system
would
go
over
and
talk
to
a
new
device,
usually
there's
a
bunch
of
engineering
time
and
coding,
and
things
that
have
to
go
on
to
like
support
that
new
device
and
you
type
the
new
package
and
to
build
in
that's
when
you're
gonna
wait
for
the
release
of
the
management
system
itself.
C
Sometimes
you'll
find
a
management
system
that
will
it'll
do
some
discovery
and
say
well.
I
did
find
this
other
simple
snmp.
I
can
treat
this
device
as
a
simple
snmp
device,
because
that's
as
far
as
I
can
get
with
it,
like,
I
don't
understand
the
new
packages
that
it
has.
So
at
least
I
could
do
that
much
like.
I
could
tell
you,
there's
a
device
at
this
ip
address
and
it's
responding
in
this
way
and
that's
about
it
like
from
here
on
out.
C
I
can
do
ping
tests
and
tell
you
if
it's
up
kind
of
a
thing
so
anyway
to
leapfrog
way
past
that
and
do
that
on
a
schedule
figure
it
out
download
the
new
software
deploy.
The
software
like
create
new
new
software
components
register
those
make
it
available
to
a
user
and
user
can
literally
just
use
it,
and
the
user
could
actually
see
those
changes
in
the
ui,
because
I
bet
you,
if
you
go
into
the
pattern,
configurator
you're
gonna
see
those
new
components.
C
This
is
pretty
ridiculous
and
I,
like
I'm,
just
being
honest,
I'm
being
truthful.
Like
you
know,
it's
like
almost
30
something
years
of
writing.
Software
for
me
and
creating
products
and.
C
C
C
Wow
well,
we've
got
some
docs
to
go
write
about.
You
know
some
of
the
aspects
of
these
things
and
to
go
because
right
now
the
service
mesh
patterns
documentation,
you
know
more
or
less
just
says
it
does.
It
doesn't
talk
about
this
stuff.
So
that's
really
interesting.
It's
really
interesting.
C
C
Well,
you
can
go
to
the
release,
notes
and
read
the
release,
notes
and
they've
probably
done
a
good
job
of
highlighting
the
big
changes
from
one
to
the
next
and
if
there's
like
a
you,
know,
caveats
to
upgrade,
but
also
like
a
software
like
this
is
readily
accessible
to
show
you
the
functional
differences
between
two,
the
two
and
to
show
you
here's.
What
you're
using
of
the
current
version
is
what
you're
not
using
of
the
next
version.
It
doesn't
have
to
grease
the
wheels
much
more
than
it
doesn't
have
to
do
an
automatic
upgrade.
C
C
C
Yeah
man
all
right,
well,
kubecon,
eu
or
cubecon,
whatever
there's
a
cfp
open,
and
I
can
just
see
the
the
title
to
that
submission
right
now,
like
I'm
just
there's
like
10
different
titles.
I'm
thinking
it's
really!
Oh
man,
god.
I
feel
sorry
for
some
of
the
competition
in
this
area.
Hey
they
just
they
just
don't
have
the
same
yeah
all
right.
C
She
should
brush
up
on
your
speaking
skills
because
it's
time
look
at
that
v060rc1
too
that's
cool.
C
C
No
thanks
for
having
us
down
to
see
this
through.
Does
anybody?
Do
we
think
that
we're
ready
to
have
intel
on
to
do
the
neural
networking
presentation
in
awesome
I
held
off
on
bringing
those
folks
on
they
were
very
you
know
happy
to,
but
I
held
off
just
because
you
know
we
got
a
lot
of
things
going
on
and
then,
but
out
of
just
having
them
present
doesn't
mean
that
we're
committing
to
anything.
C
I
was
highlighting
to
a
couple
of
you
over
the
weekend
that
uber
had
released
crisp,
which
is
really
interesting
to
yeah,
really
interesting
to
things
that
we're
doing
in
nighthawk,
and
it's
in
some
respects.
It's
like
geez.
That's
what
we're
trying
to
do,
which
is
fine
that
they
release.
It
is
actually
helpful
to
understanding
in
part
where
we're
trying
to
go
and
oh,
but
this
the
wasan,
the
the
neural,
networking
and
wassum
like
this
crisp
and
that
stuff
kind
of
go
hand
in
hand
and
like
some
really
interesting.
C
A
Okay,
let's
wrap
it
up.
We
are
27
minutes.
Oh
so,
let's
meet
tomorrow
in
our
developers,
meeting
different
meeting
bye,
guys.