►
Description
Envoy on Windows: Use-cases, roadmap, and more - Sunjay Bhatia, David Schott
Ready to dive a little deeper into the world of Envoy on Windows? Learn about the ongoing efforts to enable the vast ecosystem of Windows applications to leverage the Envoy proxy, what it can do now, and what is coming next. Contributors have been hard at work bringing Windows platform support to Envoy. The project hopes to enable the vast ecosystem of Windows application architectures to leverage Envoy’s rich feature set and benefit from the vibrant Envoy open source community. This talk will show how Envoy users can start to use and evaluate Envoy on Windows, demonstrate how Envoy can be used to enable cloud-native applications on Windows, and discuss the roadmap ahead.
A
Hello
all
welcome
to
our
talk
today.
We're
gonna
be
talking
about
envoy
support
on
windows.
My
name
is
sanjay
batter,
I'm
a
south
carolina.
Previously.
I've
contributed
to
windows,
container
support
in
cloud
foundry
application,
one
time
and
and
contributed
to
the
diego
container
scheduler
in
cloud
foundry
right
now,
I'm
a
full-time
contributor
to
the
envoy
on
windows,
work
and
presenting
with
you
today
is
david.
B
B
So,
what's
on
the
agenda
today,
we'll
be
starting
out
looking
at
the
motivations
behind
porting
on
way
to
windows,
it's
history
of
how
we
got
here
at
our
first
alpha
release.
What
does
the
alpha
release
actually
mean
how
to
get
started
with
it?
You
know
showing
a
demo
of
envoy
on
windows
in
action
as
well
as
after
the
demo
going
over
future
plans
roadmap,
and
you
know
how
to
get
involved
with
the
community
and
we'll
wrap
up
with
a
q
a
session
after
that
so
envoy,
on
windows.
B
Why
onware
was
developed
for
linux
first
and
it
works
great,
but
the
reality
is
that
in
industry
today
many
organizations
have
a
mixture
of
os
platforms
in
their
environments,
essentially
without
ongoing
windows.
Those
organizations
and
users
are
faced
with
two
choices:
use
a
different
proxy
across
windows
and
linux,
or
rewrite
all
windows,
applications
and
migrate
them
to
link
to
linux,
both
of
which
are
pretty
costly
and
expensive
undertakings
that
take
time.
B
B
Essentially,
you
know
you
don't
need
to
train
personnel
for
multiple
solutions
that
are
contingent
on
which
operating
system
you're
running
for
your
apps
also
of
note
is,
of
course,
the
rich
feature
set.
So
getting
on
way
to
compile
and
run
natively
on
windows
is
only
going
to
make
it
possible
for
the
project
to
deliver
value
through
its
rich
features
to
windows
as
well.
B
B
B
B
There
are
no
envoy
executables
on
windows.
Yet,
however,
we're
working
on
that
so
currently,
the
expectation
is
that
users
need
to
build
the
project
from
master.
The
alpha
also
means
that
we're
still
soliciting
feedback
from
our
users.
You
know
we
expect
that
users
will
run
into
builder
usage
issues,
and
you
know
we
will
be
trying
github
frequently
and
looking
at
you
know
what
are
the
the
top
pain
points
that
are
being
reported
by
our
users.
B
B
B
You
know,
for
example,
a
signal
handling
or
process
life
cycle
control
is
something
that
we
will
be
looking
at
as
well
as
looking
at
the
tracing
extensions.
However,
there
might
be
some
features
that
we
find
will
need
to
be
disabled
permanently,
such
as
hot
restart,
so
we
will
be
assessing
those
and
trying
to
enable
as
many
of
these
as
possible
as
we're
iterating
through
beta
and
eventually
aga
release.
B
So
to
get
started,
as
I
mentioned
before,
you
need
to
build
envoy
from
the
master
branch.
This
is
actually
considered
release
quality
at
all
times,
because
there's
a
lot
of
testing
that
goes
on
before
code
gets
into
that
branch
to
get
started.
There's
a
few
build
instructions,
basically,
on
the
envoy
proxy
site,
we've
added
windows
instructions.
Next
to
the
linux
building
instructions.
B
There
is
also
a
docker
image
available
as
well.
If
you
want
to
build
envoy
on
that,
so
follow
those
urls
one
last
gotcha
tip
would
be
that
you
have
to
be
perhaps
careful
with
the
shell
when
invoking
bazel
on
windows,
we
have
specifically
tested
the
msys2
bash,
but
there
are.
There
are
other
shells
like
power
fill
and
command.
A
A
A
A
So
we're
editing
some
files
on
that
on
that
remote
server,
and
here
we
have
the
docker
compose
setup
for
our
demo.
You
can
see
the
service
configuration
for
the
the
front
envoy
proxy.
We've
got
some
ports
that
we're
exposing
to
that
windows
host
as
well
as
some
mounted
blind
mounted
directories
that
are
going
to
be
inside
that
service
container.
A
Similarly,
we
have
a
similar
setup
for
the
dog
service
and
the
cat
service.
That
will
be
our
two
upstream
services
to
access
the
demo
from
our
local
workstation.
We've
got
some
forwarded
ports
set
up
in
our
vs
code
ssh
session.
So
let's
bring
up
the
demo.
We
can
do
a
docker
compose
up
detach
to
get
our
services
running.
A
A
A
We
can
look
at
the
status
of
the
clusters,
everything
that
you
would
typically
expect
from
the
convoy
admin
interface.
Look
at
the
stats.
We
can
see
that
we've
got
a
few
requests
completed
for
each
of
our
upstream
services,
so
everything
looks
good.
This
is
what
you
would
typically
expect,
and
nothing
different
on
windows
from
what
you
would
see
on
your
envoy
instance
on
linux
or
other
platforms.
A
This
is
so
we
can
start
to
get
mtls
between
our
front
envoy
and
our
back-end
service
and
similarly,
on
the
upstream
envoy
configuration
for
the
services.
We
have
the
same
thing
this
time
in
the
downstream
tls
contacts
on
the
listener,
we're
presenting
the
certs
and
validating
the
ca
of
the
search
presented
to
the
upstream
envoy,
so
just
to
show
an
example
of
the
dynamic
configuration
it
starts,
updating
what
happens
when
we
update
the
upstream
envoy
with
an
invalid
serve
what
happens?
A
A
A
All
right
so
that
update
should
get
picked
up
by
envoy
and
when
we
go
to
query
our
services
eventually,
all
right,
once
the
cache
is
cleared
out,
we
get
a
error,
a
tls
error
from
the
front
envoy
saying
that
the
certificate
verification
failed.
So
we
can
see
that
that
half
of
the
mutual
tls
is
is
working.
A
So
that's
great
and
let's
update
back
to
original
state
and
do
a
fix
our
configuration
here
so
we'll
be
able
to
get
our
dogs
and
cats
back
and
now,
let's
demonstrate
the
other
side
of
the
mtls
handshake
and
give
the
upstream
envoy
make
it
do
some
more
strict
validation
of
the
cert
that
the
front
crafty
envoy
is
presenting.
So
here
we'll
match
some
subject:
alternate
names
we'll
match
and
have
an
exact
match
and
we'll
match.
The
name
foo,
which
we
served
downstream
envoy
is
presenting,
is,
is
not
does
not
have
in
it.
A
So,
let's
again
do
a
move
to
get
the
config
update
and
we'll
be
able
to
see
a
different
error,
a
certificate
unknown
error
coming
from
the
upstream.
So
it
does
not
able
to
verify
that
certificate,
so
mtls
an
important
thing
in
securing
identity
and
encryption
and
an
important
feature
that
windows
apps
will
be
able
to
transparently
and
windows.
App
deployments
will
transparently
be
able
to
take
advantage
of
if
their
envoy
sort
of
mesh
is
configured
with
this
to
be
able
to
verify
identity
of
upstream
and
downstream
services.
B
B
A
B
B
B
B
B
B
B
B
B
A
So,
what's
next
for
envoy
on
windows,
we're
planning
on
providing
beta
release
binaries
for
envoy
on
windows
in
the
116
release
range
you
can
follow
the
github
milestone.
That's
linked
there.
Some
specific
plan,
improvements
that
we
have
are
to
enable
some
of
the
features
and
extensions
that
are
currently
disabled
through
any
user
feedback
and
fix
any
rough
edges
that
we
get
there
improve
event,
loop
performance
and
improve
process
lifecycle
control.
So
some
of
the
integration
with
the
windows,
service,
control
manager.
A
A
A
So
finally,
we'd
like
to
extend
a
huge
shout
out
and
special
thank
you
to
the
contributors
from
microsoft,
vmware
and
the
envoy
maintainers
that
work
tirelessly
to
make
envoy
on
windows
a
reality,
and
with
that,
thank
you
all
for
attending
our
presentation.
We
hope
it
was
informative
and
we'd
like
to
open
it
up
for
questions,
hey
y'all.
If
anyone
has
any
questions,
please
ask
us:
now
we
have
a
few
minutes
potentially
to.