►
From YouTube: OnlineMeetup #6 - July 14, 2020
Description
In this season's meetup, we wanted to go back to WebAssembly and the kind of extensions the community is building. We have some guest speakers and Solo.io engineers on had to chat about WebAssembly for Envoy Proxy.
Thanks to our guest speakers for sharing what they've built:
* Blake Covarrubias - Sr Product Manager for Consul @HashiCorp
* Bryant Hagadorn - Security Engineer @IBM
Questions, comments or have a wasm module to share? DM me on https://slack.solo.io at Betty Junod
Download the presentation
https://speakerdeck.com/soloio/online-meetup-number-6-july-14-2020
Learn More
https://www.solo.io
https://webassemblyhub.io
Get Involved:
GitHub https://github.com/solo-io/wasme/issues
Review the OCI image spec https://github.com/solo-io/wasm-image-spec
Project envoy-wasm https://github.com/envoyproxy/envoy-wasm
SDK
* https://github.com/proxy-wasm/
* https://github.com/solo-io/proxy-runtime/
A
So
I'm
really
excited
about
that
turns
out
they're,
both
security
modules,
and
then
we
have
a
community
q.
A
what
we're
going
to
do
here
is
there's
been
a
good
amount
of
questions
that
have
come
up
in
the
community
slack
related
to
web
assembly.
So
what
I
wanted
to
do
was
kind
of
read.
You
know,
recap
them
all
for
the
folks
on
to
the
folks
on
the
meetup.
A
B
Now
this
this
technology
of
a
wasm,
vm
or
wasn't
sandbox
is
not
limited
to
the
browser.
You
can
take
the
code
of
the
wasan
vm
and
integrate
it
with
whatever
application
you
write
and
that's
exactly
the
work.
That's
done
in
envoy
they're,
integrating
a
webassembly
vm
into
invoice
with
the
goal
of
allowing
you
to
extend
our
envoy
in
a
way
that
doesn't
require
rebuilding
it.
C
A
B
B
You
know
your
app
inside
the
data
center
or
the
cloud
it
travels
through
envoy
in
what's
called
the
filter
chain
and,
for
example,
in
that
before
here,
you
can
see
that
we
have
a
bunch
of
filters
that
can
manipulate
the
request,
so
we
can
do
auth
rate
limiting
handle,
grpc
or
whatever
custom
logic.
You
want
to
add
there
so
always
extendable
in
the
sense
that
you
can
write
new
filters
and
add
them
to
the
android
filter
chain
to
do
additional
functionality.
B
B
The
filters
today
are
required
to
be
written
in
c
plus
class,
and
you
cannot
load
them
as
a
shared
library.
They
have
to
be
built
into
envoy,
which
means
that
you
have
to
compile
envoy
from
scratch
using
bazel,
and
then
you
have
to
distribute
this
new
image
to
be
used
in
your
in
your
solution
right,
and
that
also
means
you
have
to
keep
track
of,
for
example,
android
security
releases,
because
you
have
to
do
this
process
of
rebuilding
all
over
again
to
get
the
latest
updates.
B
B
And
what
they've
done
in
android
technically
is
to
write
a
c
plus
filter.
Then
what
it
does
is
actually
load
your
wasim
code
and
proxy,
the
c
plus
pascals
into
the
wasim
module
right.
So
in
the
after
model,
we'll
be
using
upstream
envoy,
directly
from
docker
hub
and
we'll
configure
it
to
load
our
webassembly
module
from
wherever
it
is.
B
If
it
can
be
on
on
the
same
container
or
it
can
be
in
an
http
server
or,
for
example,
we
have
webassembly
hub
for
exactly
this
type
of
distribution
problem
and
when
envoy
receives
the
module,
it'll
activate
it'll,
be
in
the
chain
and
your
the
request
will
go
through
that
model,
which
means
that
you
can
influence
the
behavior
of
every
request
that
going
through
envoy
without
recompiling.
It
essentially.
A
No
sorry-
and
I
just
like
advanced
this
left
for
you
so
with
that
thanks
for
that
recap,
you've
also
just
kind
of
explained
how
these
things
work,
and
I
think
one
of
the
things
that,
with
this
is
that
there's
a
lot
of
different
terminology
out
there
and
shorthand
as
well
as,
like
you
know,
shorthand
you
know
the
acronyms
and
what
have
you
so
I
wanted
to.
If
scott
scott
weiss,
I'm
gonna
unmute
you,
if
you
can
kind
of
give
a
little.
E
E
E
There
are
lots
of
different
runtimes
that
can
utilize
wasm
and
we're
seeing
new
use
cases
come
up
for
it,
like
I
think,
open
policy
agent
is
another
project.
That's
considering
talking
about
or
started
implementing
support
for
using
wasa
modules
to
allow
users
to
you
know
define
policies
imperatively
rather
than
declaratively.
E
A
Thank
you
and
then,
since
we've
we
initially
launched
this
in
december
and
we
had
an
update
in
march
of
this
year
and
I
was
just
checking
this
the
other
day
and
there's
over
200
community
repos
available.
So
this
is
pretty
it's
pretty
exciting
to
see
folks
get
interested
and
also
especially
building.
A
And
then
sharing
so
that
other
people
can
see
the
examples
play
with
it
and
then
maybe
that
inspires
them
to
build.
You
know,
try
building
something
else,
but
I
thought
this
was
good,
because
there's
a
lot
of
people
use
the
shorthand
and
then
sometimes
it
could
get
a
little
confusing
as
to
like
what
is
what
and
so
scott
you
want
to
talk
a
little
bit
about
about
this
little.
E
Sure
so
this
is
a
brief
rundown
of
the
user
experience.
So
what
does
it
actually
mean
from
a
usage
point
of
view
when
you're,
using
these
components,
the
webassembly
hub
and
wazmi?
To
add?
Let's
say
you
want
a
a
custom
behavior
like
yvonne
was
describing.
You
want
to
add
something
to
your
filter
chain.
You
want
to
add
a
custom
filter,
that's
going
to
apply
some
logic
or
behavior
on
the
request
path.
You
know
data
is
coming
in
and
out
of
envoy.
You
want
to
put
a
filter
on
that
somehow.
E
So
what
do
you?
Do?
You
write
a
module
in
any
language,
there's
a
certain
interface
that
so
this
is
an
interface
that
envoy
exposes,
which
is
a
bit
more
low
level
and
then
there's
an
interface
that
was
me
exposes,
which
is
a
little
bit
higher
level,
more
user-friendly
and
we've
provided
libraries
for
each
language,
and
you
can
also
build
your
own
modules
directly,
not
using
the
wazmy
libraries
and
then
just
you
can
package
the
module
into
an
image.
That's
then
deployable
using
wazmy.
E
So
there's
like
the
build
concern
you
can
build
in
any
language.
You
can
so
you
can
basically
build
the
module
either
using
a
wasm,
supported
language
or
you
can
build
your
own
module,
which
will
include
compilation,
and
then
you
can
build
the
image
from
that
and
deploy
the
image,
and
this
will
all
happen.
E
A
Yeah,
and
so
with
that,
I'm
really
excited
to
have
both
blake
kovaruvius
senior
product
manager
from
hashicorp
and
bryant
hagedorn
security
engineer
from
ibm.
These
two
gentlemen
have
built
some
built
up,
was
me
module
for
envoy
and
posted
them.
They
are
shared
publicly
in
the
webassembly
hub.
I
have
links
to
those
to
their
repos
at
the
end
of
this
presentation,
so
we'll
send
that
out,
but
I
will
now
would
like
to
like.
Let
me
stop
sharing.
A
F
Yeah
sure
thing
thanks
betty,
so
yeah.
Let
me
share
my
screen.
We'll
kick
things
off
so
just
to
set
a
little
bit
of
context.
This
is
the
filter
that
I
built
it's
available
on
github.
If
you
want
to
go,
you
know,
look
and
find
it
and
browse
through
the
code,
but
this
was
really
done
as
an
exercise
to
learn
about
them.
Learn
about
running
these.
You
know
modules
when
inside
of
envoy,
I
never
done
this
before.
F
I
was
curious,
and
so
this
is
really
just
kind
of
a
you
know,
experimental
proof
of
concept
that
I
put
together.
It's
not
really
something
you
should
use
in
production,
but
it
did
help
me
to
to
learn
and
understand
how
things
work.
You
know
in
the
process
of
writing
this.
I
did
take
the
time
to
kind
of
comment
all
of
the
code
in
detail,
so
you
can
kind
of
see
each
of
the
function
calls
and
where
that
what
those
functions
are
kind
of
hooking
into.
F
As
far
as
the
the
wasm
spec
what's
exposed
via
the
abi
and,
what's
being
called,
it's
pretty
good
to
follow
and
get
a
good
grasp
of
what's
happening.
But
what
I
built
just
to
demo
this
is:
I
built
a
sample
application.
This
is
a
two-tier
application,
that's
running
within
console
service,
mesh
and
I'll
get
to
the
app
in
a
second.
What
I
have
is,
I
have
a
web
front.
End
that's
deployed
within
the
service
mesh
and
I
have
that
front
end
is,
is
fronting
a
download
server.
F
I
have
two
versions
of
this
download
server,
v1
and
v2,
and
I
just
deployed
the
second
version
ahead
of
time
for
sake
of
time
for
the
demo,
but
here's
the
scenario,
so
we
go
over
to
the
app.
This
is
an
application
which
provides
a
media
library,
say
you
can
upload
videos
or
any
kind
of
media
that
you
want
and
make
those
available
to
end
users.
So
if
someone
wants
to
access
something,
they
can
just
click
on
it,
they
get
a
download.
F
You
know
dialogue,
they
can
download
that
file
but
say
you
know,
this
is
publicly
accessible
on
the
internet
and
now
because
it's
publicly
accessible,
you
know,
maybe
it
was
posted
on
hacker
news
or
reddit.
A
lot
of
people
are
downloading
the
content
and
my
bandwidth
costs
are
going
through
the
roof.
So
I
want
to
reduce
and
kind
of
control
how
who
can
access
these
files-
and
you
know
my
download
server,
which
is
sort
of
serving
these.
F
Maybe
it's
you
know
a
application
that
I
don't
have
either
access
to
the
code
or
can't
easily
modify
that,
and
so
what
I
will
do
is,
instead
of
changing
anything
there
I'll
implement
these
controls
within
webassembly
and
envoy.
So
if
I
take
a
look
here,
going
back
to
the
service
match
view,
sorry,
let's
just
dive
into,
we
have
a
sidecar
proxy
deployed
for
the
web.
App.
F
If
I
click
into
this,
I
can
see
that
it
has
an
upstream
dependency
on
this
download
service
and
then
again,
if
I
go
back
over
to
the
download
service,
I've
got
the
two
versions
running
v1
and
v2,
and
what
I
currently
have
is
all
of
I
have
a
traffic
splitter
set
up.
All
of
the
traffic
is
going
to
the
v1
service
instance
of
the
application,
so
we
saw
you
know
just
a
moment
ago
that
those
files
are
unprotected.
F
F
I
am,
I
have
you
know
the
wasm
module
that
I've
built
and
I
am
loading
it
from
a
file
path
and
injecting
that
into
my
you
know,
case
yaml.
So
I
just
this
is
a
regular
deployment
and
then,
when
envoy
loads,
it's
loading,
this
filter
from
disk,
and
so
I
want
to
then
you
know,
move
over
to
v2
of
my
service,
which
has
this
filter
deployed.
So
I'm
going
to
adjust
this
weight.
F
Switch
100
of
the
traffic
over
to
the
v2
and
then
I'll
do
a
console,
config,
right,
service,
splitter
and
now
we're
redirecting
traffic
over
to
that
instance
of
envoy,
with
this
wasm
filter
running
which,
if
we
now
click
on
one
of
these
resources,
we
see
that
now,
access
to
these
files
are
unauthorized,
nothing,
you
know,
would
be
accessible.
So
how
do
we
gain
access?
So
what
this
filter
does
is
it?
F
F
So
what
it
does
is.
This
is
based
off
of
a
filter.
That's
available
within
nginx
called
secure
link.
I
basically
rebuilt
and
kind
of
re-implemented
version
for
envoy,
and
so
what
happens
is
you
would
take
the
request
path
of
the
resource,
you're
trying
to
access
and
a
shared
secret,
and
you
concatenate
them
together.
F
So
then,
you
know
these
links
can
be
distributed
to
say
folks,
who
have,
or
I
want
to
give
access
to
this
media
server
and
not
have
other
folks
who
are
just
coming
across
the
link
online.
You
know
being
able
to
download
this
content
and
obviously
increase
my
bandwidth
bills.
So
that's
kind
of
you
know
the
example
of
what
I
built,
maybe
a
use
case
of
where
you
might
use
this.
Obviously,
the
workflow
generating
these
urls
is
a
little
rough,
but
hopefully
you
get
the
idea
of
what
this
is.
A
D
Right,
thank
you.
Thank
you
very
much,
really
cool
demo,
there
blake
so
I'll,
just
kind
of
go
into
a
little
bit
of
a
powerpoint
presentation
on
kind
of
the
problem
that
I
was
trying
to
solve.
Like
blake,
I
was
just
pretty
much
just
trying
to
play
around
with
the
tool
set.
The
wasme
tool
set
see
how
it's
similar
to
docker
hub
and
just
kind
of
play
around
with
the
the
different
functionalities
that
it
gave.
D
So
at
the
time
I
was
working
on
what's
called
security,
headers
and
security.
Headers
are
an
oauth
kind
of
like
best
practice
recommended
the
way
that
they're
kind
of
implemented
is
usually
on
a
language-by-language
basis
and
basically,
what
they
do
is
they
tell
the
browser
how
it
can
interact
with
the
rest
of
the
internet?
So,
for
example,
some
websites
might
request
certain
fonts
or
might
request
bootstrap
from
a
cdn.
D
It
basically
allows
the
browser
to
actually
grab
those
resources
or
restricts
those
resources
and
the
main
kind
of
thread
vectors
that
we're
avoiding
here
would
be.
You
know
cross-site
request
forgery,
cross-site
scripting,
those
sorts
of
issues,
so
previously
the
ways
that
you
can
set
these
response-
headers
there's
three
engine
x.
D
Of
course
you
can
alter
your
engine
x
configuration
you
just
have
kind
of
these
manual
adding
of
headers,
and
it
gets
pretty
messy
pretty
quickly,
especially
when
you
have
a
lot
of
different
nginxes
attached
at
the
docker
file
level
at
the
ingress
level
and,
of
course,
there's
no
egress
with
nginx
ingress
and
kubernetes
and
then
as
well.
You
could
do
it
inside
of
the
actual
language
or
the
framework.
That's
serving
all
of
your
restful
calls.
So
here's
how
express
does
it
with
helmet,
which
is
the
one
that
I
mentioned
earlier.
D
However,
at
the
time
I
thought
it
was
kind
of
silly,
though
there's
all
of
these
different
language
utilities.
I
think
there's
there's
probably
30
or
40
different
language
ways
to
do
this.
I
thought
it
was
kind
of
silly
and
it'd
be
neat
if
the
actual
envoy
sidecar
proxy
could
respond
with
these
request.
D
D
All
right
so
here
I
have
just
a
simple
book
info
sample
running
I've.
Just
done
all
the
basic
steps
on
istio.io
it's
running
on
gke
and
it's
running
on
top
of
istio
1.6.
I
believe-
and
you
can
see
product
page
in
my
network
request-
is
returning
these
response.
Headers
and
you
all
might
be
wondering
if
I
just
left
my
facebook
open,
I
actually
didn't.
I
could
show
you
what
a
really
really
mature
website
probably
has
inside
of
its
response.
Headers
and
I'll
show
you
how
we
maybe
kind
of
get
closer
to
that.
D
D
They
have
https
upgrades
all
sorts
of
things
that
the
browser
knows
how
to
interact
with
cross-site
script
protection,
those
sorts
of
things,
so
I'm
just
gonna,
show
you
very
quickly
kind
of
the
infrastructure
I
have
set
up.
I
have
the
wires
from
the
operator
running.
I
have
the
crds
running.
I
have
istio
running
just
with
the
pro
like
the
default
settings
and
then,
of
course,
book
info,
like
I
showed
you
with
the
side
cars
injected.
D
And
to
my
understanding
what's
happening
here
is
that
it's
pulling
the
webassembly
hub,
filter
down
from
webassembly
hub
and
it's
applying
it
to
the
envoy
proxy,
and
in
this
case
I
think
it's
not
going
to
hit
any
particular
deployment
of
the
pod.
So
it's
actually
going
to
hit
everything.
That's
in
my
current
name
space,
so
I
believe
it'd
be
all
the
stuff
that
we
saw
earlier
running
in
the
default
namespace.
So
all
of
bookinfo
would
have
this.
Ideally
you'd
probably
want
to
only
have
this
served
to
the
ui.
D
In
the
meantime,
I'm
going
to
throw
this
product
page
in
here
and
scan
the
site
for
the
current
security
headers
that
are
getting
that
we're
getting,
and
we
can
see
that
it's
giving
me
an
f.
So
definitely
a
lot
to
change
here
and
I
think
it's
actually
a
503.
But
I
promise
you
before.
It
definitely
was
an
f.
D
E
D
All
right
so
my
apologies,
so
I've
actually
updated
my
sto
version
and
I
think
it's
not
working
with
this
1.6.2,
so
apologies
for
that
one.
I
think
I
updated
it,
but
I
just
spun
up
this
cluster,
but
I'll.
Just
I'll.
Take
you
to
this
medium
article
that
I
wrote
about
this.
Essentially,
what
should
happen
is
these
five
headers
will
get
added
to
the
request
and
then,
if
we
were
to
reach,
go
inside
of
securityheaders.com
and
check
it
we'd
see
that
some
of
these
headers
have
been
applied
so
yeah.
So
it
looks
like
it's
just.
D
Maybe
an
output
updated
version
of
istio
that
I've
used
used
here
so
yeah.
That's
that's!
Basically
it
I'll
definitely
try
to
update
that
kind
of
the
next
steps.
Ideas
I
have
for
the
project
would
be
to
dynamically
load.
Some
of
these
values
in,
like
whatever
you're
serving
from
bootstrap
google
fonts,
storing
the
configuration
inside
of
a
secret
or
config
map
and
then
kind
of
applying
least
privilege
automatically
so
flagging
violations
as
they
happen
and
then
maybe
automatically
suggesting
headers.
A
And
so
let
me
hang
on
so
the
steps
of
share,
screen
and
present
awesome
so
we'll
get
that
out.
We'll
get
also
the
links
to
their
repos
out,
so
everyone
here
can
check
out
and
also
both
brian
and
blake
are
also
in
the
webassembly
hub
channel
inside
the
community
slack.
So
for
you
know,
if
you
have
questions
as
you're
playing
around
with
the
filters,
you
can
just
go
and
tag
them
and
ask
them
questions
too.
A
B
Yes,
so
anfoy
lets
you
essentially
I'll
separate
it.
So,
first
in
the
initial
versions
of
the
wasme
interface,
you
couldn't
really
do
much
body
manipulations.
It
was
very
early
phases,
but
recently
they've
been
adding
this
stuff
in
so
you
can
manipulate
headers.
You
can
manipulate
body
response,
headers
a
response
body
metrics.
B
So,
for
example,
if
you
don't
really
care
that
much
about
you
know
the
request
itself,
but
you
just
want
to
count
at
the
counter
when
you
see
a
certain
pattern
and
you
can
do
that,
you
can
interact
with
other
services.
So,
for
example,
when
a
request
come
in
pause,
it
call
out
to
another
http
service
and
then
based
on
the
response,
you
know
make
a
change
to
the
request.
Deny
it
something
similar
to
xot,
for
example.
A
C
Yeah
absolutely
so.
The
short
answer
is
the
current
version
of
waz
me
doesn't
support
1.6,
but
we
are
actively
working
to
bring
that
support
and
it
should
be
coming
very
very
soon.
Basically,
because
there's
not
like
a
hard
cut
release
every
time
the
avi
has
breaking
changes
in
envoy
wasm.
We
kind
of
have
to
build
a
compatibility
matrix
into
waz
me
itself,
so
we
just
haven't
added
1.6.
A
B
Upstream
envoy,
I
think
the
the
best
supporter
language
is
c
plus
plus,
and
then
the
upstream
sdk
also
added
rust,
and
you
can
see
them
there's
a,
but
maybe
I
can
send
you
the
link
essentially
there's
a
the
goal
with
the
wasm
support
is
to
also
extend
it
more
than
just
envoy,
also
to
other
proxies.
So
there's
a
github
org
for
that
purpose,
and
you,
the
c
plus
pass
and
sdk
and
rust
sdks
are
there,
and
I
can
share
that
link
later.
A
A
Yeah,
you
know,
actually
maybe
that's
we
can.
We
can
add
those
links
at
to
to
this
presentation
as
well,
when
we
send
it
out
just
so,
people
can
check
it
out
because
it's
also
a
community
project.
You
know
the
overall,
like
community,
is
happy
to
share
and
play
with
things
that
other
folks
create
and
then
just
based
on,
like
you
know,
popularity
and
interest,
I
think,
is
how
more
things
will
get
supported.
A
A
B
So
yeah
there's
two
ways
depending
on
your
use
case
and
one
sec.
Let
me
mute
the
noises
in
here,
so
if
you
want
to
share
information
just
in
the
context
of
a
single
request,
there's
a
function
called
a
set
property
proxy
set
property
and
proxy
get
property,
and
if
you
want
to
share
a
globe
as
something
that's
global
to
a
global
state
and
that
will
you
know
kind
of
like
maybe
encounter
or
something
like
that,
there's
a
shared
data
so
get
your
data
set
your
data.
B
Oh
yeah,
depending
on
the
use
case,
I
think
most
commonly
you
use
you
a
lot
of
times.
Filter
and
envoy
can
interact
with
each
other.
So,
for
example,
an
auth
fielder
can
provide
an
identity
and
then
an
arabic
filter
will
apply
policy
based
on
that
identity
and
they
use
the
mechanism
similar
to
that
set
property.
Shared
property,
where
it's
information
only
persisted
for
the
context
of
the
request.
A
Yeah
so-
and
this
next
part
on
what's
next
is
couple
of
things-
first
is
shane.
If
you
could
talk
to
the
folks
about
kind
of,
what's
currently
in
development
right
now,
explain
these
a
little
more
and
then
the
next
one
was.
We
had
some
open
questions
that
would
we'd
like
to
pose
to
the
audience
here,
and
then
we
can
also
to
have
additional
questions
that
folks
on
the
phone
have.
C
Yeah
absolutely
so.
These
are
the
three
big
things
in
wasn't
land
that
we're
working
on
at
solo.
So
the
first
one
is
we're
bringing
wasm
support
to
blue
enterprise
right
now.
It's
only
available
on
the
open
source
version
of
glue,
but
we've
had
a
lot
of
interest
from
our
enterprise
clients
as
well.
So
that's
coming
very
soon
we're
also
building
a
new
release.
That's
going
to
be
built
on
a
much
newer
version
of
envoy
wasm.
C
Our
current
version
is
only
about
six
weeks
old
based
on
the
envoy
wasn't
master,
but
you
know
this
stuff
moves
pretty
quickly.
So
there's
already
been
a
few
breaking
changes
that
we're
looking
to
fix
up
and
get
new
versions
of,
and
then
istio16
support
is
the
other
big
thing
we're
working
on
which
we
already
talked
about
a
little
bit.
But
hopefully
we
can
get
that
on
pretty
soon
as
well.
A
Awesome,
thank
you,
and
so
with
that
outside
of
just
general
questions
folks
on
the
phone
may
have
and
you're
all
able
to
unmute
yourself
pretty
easily
to
meet
yourself
and
ask
any
other
questions
you
may
have,
but
some
of
the
big
things
we
wanted
to
ask
the
folks
that
were
interested
in
webassembly.
Is
you
know
what
other
languages
are
you
most
interested
in
outside
of
the
ones
that
we've
mentioned
here?
A
Are
the
other
service
meshes
or
just
other
envoy
based
thing?
Envoy-Based
tools
that
you're
interested
in
using
webassembly
with
what's
cool
is
blake,
showed
it
working
with
working
with
console.
So
anything,
that's
theoretically
any
solution,
that's
using
envoy
can
use.
You
know
webassembly
other
kind
of
filters
that
people
are
interested
in
or
thinking
about,
ideas
that
you
may
have.
We
have
a
few.
A
You
know
envoy
having
envoy
work
with
glue
enterprise,
we're
curious
to
know
if
anybody
else
has
been
looking
at
using
webassembly
in
their
company,
for
you
know,
corp,
like
actual
like
business
use,
and
thinking
about,
like
you
know,
outside
what
other
integrations
or
features
are
needed
to
have
that
be
in
kind
of
a
more
beyond
kind
of
like
a
prototype
use.
So
we
were
curious
to
understand
these
types
of
things
so
and
anything
else.
So
this
is
kind
of
open,
open
q.
A
for
folks.
G
Okay,
so
maybe
I
will
start
so.
We
currently
are
working
with
istio
service
match
and
the
current
approach
was
to
implement
an
adapter
to
a
mixer,
which
was
the
I
don't
know
how
to
call
it.
The
old
architecture
of
istio
since
the
istio
changed
the
architecture,
and
there
is
no
more
mixer
or
even
mixer,
is
now
deprecated.
G
We
are
most
interested
in,
I
would
say
golang
in
this
case
tinygo,
since
our
developers
and
our
services
are
mostly
written
in
go,
and
we
are
looking
also
for
some
for
some
features
to
web
assembly
hubs.
Since
we
saw
that,
for
example,
you
cannot
delete
a
attack
that
you
pushed
to
web
assembly
and
if
you
push
something
wrong
or
you
want
to
improve
your
attack,
there
is
currently
no
way,
and
maybe
a
private
version
of
web
assembly
hub
would
be
nice
tool
for
us,
since
we
are
doing
an
enterprise
project
and
not
everything.
G
A
G
A
G
B
D
I
just
had
maybe
a
quick
question
for
the
community.
Anyone
could
maybe
answer,
but
this,
like
the
scope
of
what
these
these
models
can
do,
is
pretty
interesting
and,
like
super
large,
does
anyone
like
see
it
going
against
the
design
principles
to
integrate
like
a
newer
control,
plane
component
say
like
an
operator
that
maybe
stores
that
the
shared
data
or
stores
some
sort
of
state
and
then
that's
kind
of
it
kind
of
regulates
the
different
mods
and
modules
that
it
connects
to?
B
Yeah,
it's
actually
funny
you
ask,
because
naturally,
once
you
it's
evolved
here
by
the
way-
and
once
you
have
a
new
data
plane
component,
it's
only
natural
to
want
the
corresponding
control
plane
component
to
manage
it.
So
there's
a
few
things
you
can
do
here.
One
anvi
is
in
the
process
of
adding
something
called
filter,
config
discovery
service
which
can
allow
you
to
delegate
the
filler
config
to
a
separate
xds
server.
B
So
let's
use
an
ito.
For
example,
I
can
have
the
hcl
filter
crd
inject
the
wasm
filter,
but
instead
of
providing
the
config
inline,
I
tell
it
go
get
your
config
from
that
xds
server
and
that
will
allow
a
packaging,
a
control,
pane
component
for
it,
and
I
think
our
vision
was
that
a
module
will
not
only
include
the
data
plan
component,
but
also
the
control
plane
component.
D
B
G
I
know
that
this
this
project
is
kind
of
new
and
it's
it's
on
it's
just
starting,
but
I
think
there
is
many
things
that
documentation
doesn't
contain
and
currently
writing
an
and
plugin
in
assembly,
script
or
c
plus
plus
in
wasm,
is
kind
of
hard.
I
think,
because
many
things
are
I
undocument
undocumented
and
you
need
to
take
a
look
into
the
code
of
sdks
and
that's
that's
one
thing
I
would
say
that
could
be
could
be
improved.
G
B
Yeah,
thank
you
for
the
feedback.
I
think
our
main
challenge
with
providing
stable
documentation
is
that
the
code
itself
is
not
stable.
So,
for
example,
shane
said
between
hco16
and
one
seven.
We
already
saw
some
breaking
changes
in
the
host
sdk
code,
so
this
will
something
that
will
naturally
improve
over
time
and
especially
once
it
gets
upstream
into
envoy
and
the
api
stabilizes.
C
C
Yeah,
so
we
don't
have
a
like
a
fully
functioning
like
tested,
end-to-end
version
yet,
but
you
know
at
a
minimum.
I
think
they
changed
like
the
method
signature
on
on
request,
headers
non-response
headers,
and
they
added
like
an
extra
field
in
there.
So
there's
a
couple
things
you
need
to
update
in
your
your
filter
and
your
c
plus
plus
code,
but
you
know
it's
basically
just
kind
of
build
it
against
latest
and
see
see
what
breaks
is
kind
of
the
quickest
way
to
debug
down
to
what's
changed.
C
Sure,
yeah
and
just
kind
of
on
that
note
as
well
related.
So
we
are,
I
don't
know
if
this
is
going
to
change
in
the
future,
because
these
things
change
pretty
quickly
but
like
as
of
right.
Now,
the
you
know,
that's
like
we
said
we're
targeting
the
latest
version
of
envy.
Wasn't
that
we're
targeting
the
exact
same
avi
commit
release
that
the
current
alpha
release
of
one
seven
for
istio
is
targeting,
so
there
should
be
pretty
good
support
for
that
as
well.
When
that
comes
out.
A
Cool
any
other
anyone
any
other
questions,
comments,
requests
actually
and
then,
between
this
and
like
the
next
time,
we
have
another
meet
up.
If
folks,
if
anybody
on
this
call
gets
inspired
and
if
you
build
a
filter
and
share
it
happy
to
have
folks
share
and
demo,
I
think
that's
one
of
the
nice
things
about
doing.
Meetups
like
this
is
to
have
people
kind
of
share
why
they
did
why
they
got
interested
and
then
what
their,
what
they're
trying
to
prototype
and
they
kind
of
walk
through
that
process
with
everyone
else.
A
And
a
couple
of
links
here
so
we've
got
the
the
the
web
assembly,
the
wazmi
is
open
source,
and
so
it's,
if
you
find
issues
or
if
you
have
requests
like
chris,
you
had
some.
You
know
comments
on
if
you
needed
certain
things
and
documentation
or
please
go
ahead
and
file
an
issue
that
helps
us
to
track
and
then
also
there
is
the
oci
image
spec.
A
If,
if
anyone's
curious
on
how
we're
actually
storing
the
modules,
the
format
of
the
modules
themselves
and
then
a
link
to
the
envoy,
wasn't
it's
not
yet
fully
in
upstream
envoy,
it's
kind
of
in
a
separate
repo
that
this
work
has
been
going
on.
So
if
people
want
to
check
that
out
and
then
we
have
links
here
to
the
the
filters
from
both
blake
and
bryant
and
brian's
blog.
Thank
you
for
writing
that
any
other
questions
or
comments
from
the
group
here
today.
F
You
know
I
wrote
my
filter
using
the
assembly
script,
sdk
that
you
you
folks
put
out
and
it
was
great
to
get
started
and
but
when
I
kind
of
wanted
to
use
more
advanced
functionality
like
I
was
looking
to
possibly
use
an
http
call,
it
saw
that
that
wasn't
supported
in
the
version
that's
published.
I
think
on
npm
there's
some
newer
versions,
but
those
weren't
running
under
the
proxy
there's
just
some
issues
from
the
development
standpoint
that
I
was
kind
of
stumbling
through.
A
As
always,
if
you
have
a
question
that
comes
up
later
slack.sloio,
if
you're
in
there,
if
you're
already
in
there,
there's
webassembly
hub
as
a
channel
if
you're
not
yet
in
there
go
ahead,
please
join
the
community,
we're
you
know
we're
all
in
there.
Folks
are
asking
and
answering
questions
for
each
other,
so
it's
a
nice
way
to
kind
of
connect.
A
I
will
send
out
the
recording,
as
well
as
the
slides
and
the
additional
links
to
some
of
the
things
that
you've
all
mentioned
as
well
on
the
on
the
languages
and
it's
and
other
stuff,
so
that
you
all
have
it
and
then,
if
there's
any,
if
there's
any
other
requests
that
come
in
as
we
go
just
hit
me
up,
you
can
dm
me
or
any
other
team
here
or
pop
it
into
the
channel
thanks
so
much
for
joining
today.
Thank
you,
blake
and
brian
for
sharing
see
y'all
next
time.