►
From YouTube: Istio Networking WG Meeting - 2019-01-03
Description
- Modeling the sidecar via Gateway
- Discuss solution for https://github.com/istio/istio/issues/7665
- Zone aware LB
- Port mapping
A
A
B
A
Interesting,
thank
you,
our
kind
of
put
that
on
oh.
If
he
wants
it,
he
wants
to
schedule
a
review.
Oh
pretty
good
part,
and
that
was
the
thing:
okay,
okay,
we
don't
have
any
agenda
for
today,
so
I
guess
we're
strictly
an
advocate
Genda
and
either.
This
is
gonna,
be
a
very
short
meeting
or
something
interesting
experiment.
Okay,
what
did
we
discuss
last
modeling's
like
her
anything
else,
to
discuss
there
so
at
least
as
discussed?
Probably
but
I
haven't
caught
up
in
it.
A
A
A
A
B
G
G
Ever
say
about
that:
we're
still
we're
still
kind
of
discussing
it.
I
actually
did
some
work
over
the
holiday
and
think
you
know,
I
found
a
few
things.
I
actually
understand
why
boys
doing
better,
whether
or
not
it's
doing
the
right
thing
is
another
question,
but
I
think
we
can
take
that
offline.
Okay,.
E
One
more
remedy:
the
issue
about
location
based,
good
balancing
thing,
not
location
below
that
zone,
although
yeah,
and
so
there
was
a
I-
think
it's
still
not
that
full
flashed.
But
there
was
a
PR
one,
the
API
that
where
we
would
actually
add
that
to
the
Destination
Truth
and
it's
a
bit
crude.
But
if
we
have
time
we
could
just
simply
go
to.
A
E
D
E
So
this,
along
the
lines
of
telephone
matrix
of
locality
weights,
it's
not
matrix,
it's
it's
like
on
a
destination
rule
our
destination
drew
they're,
like
you
know
getting
at
some
point.
We
can
specify
a
top-level
destination
rule
that
has
this
information
embedded
inside
it
and
oh,
this
is
the
master
back.
Sorry,
oh.
E
B
E
That
it,
the
thing,
went
and
because
I
thought
like
that
seemed
to
be
the
same
thing
that
we
discussed
don't
know.
I'm
thinking,
like
maybe
I,
missed
out
something
else.
All
this
I
can't
see
it
on
the
screen,
but
basically
it's
just
saying
that,
like
you
know
from
and
which
means
you
can
specify
a
top
level,
a
global
destination
tool
where
this
is
set-
and
others
would
just
simply
inherit
from
this,
but
it
still
doesn't
cover
things
like
you
know.
E
You
want
to
have
a
fallback,
so
on
or
like
you
know,
this,
this
seems
imply
it's
solved.
You
know
it
always
a
traffic
split,
but
this
is
also
based
on
the
current,
unlike
or
so
on.
Why
does
not
have
the
ability
to
do
that
fall
back
properly?
It
doesn't
have
that
the
whole
thing
in
place.
So
what
it
can
do
is
this
that
can't
do
something
more
like
you
know:
if
zone
1
fails,
then
go
to
zone
2
and
then
to
zone
3,
or
vice
versa.
E
But
this
is
a
given
they
keep
in
mind.
This
is
not
evaluating
the
load
on
that
zone
and
then
setting
it
is
like
a
manual
override
where
I
as
a
knee
user,
for
example.
This
was
from
Intuit
and
flashing,
both
who's
right
there,
a
gap
I
as
a
user
would
specify
like
in
90
person,
always
stays
in
US
and
10
person
can
be
spread.
You
know
to
here,
and
there.
E
Something
of
yeah
but
except
this
is
this-
is
this
happens
even
within
a
single
subset
right
I
mean
this
is
not
China
which
no
we're
routing.
This
is
just
saying
that
you
know
if
I
want
most
probably
you
would
always
be
setting
something
like
from
region,
1
zone,
1
to
region,
1
zone,
1,
100
and
then
the
rest
would
already
and
in
case
of
Maria
use
such
the
other
regions.
E
But
that
is
still
I
mean.
That's
the
only
way
we
have
today,
because
I
know
it
does
not
have
that
notion
of
you
know.
Even
it
sorry
it
has
it,
but
we
don't
have
active
health
checking.
We
don't
do
like
most
of
the
that
people
do
so.
Consequently,
what
happens
that
we
have
to
trigger
things
and
I'm
going
to
say
you
have
to
go
into
a
different
zone
now,
but
so
that's
the
problem.
We
can
always
get
this
done
with
an
outlier
detection
thing,
but
the
mileage
might
vary.
E
Thing
about
this
is
that
we
don't
need
to
set
up
the
the
AZ
in
an
way
like
like
what
do
you
should
do
in
the
past,
because
this
is
all
relative
to
a
local
envoy.
It
yeah,
but
short
answer
is
yes.
Today
we
actually
like
men
on
white,
connects.
We
talk
to
the
API
server,
get
the
AZ
associated
with
it
on
Y
and
then
I'm
gonna
set
set
this
thing
up
properly.
E
Is
that
the
locality?
Oh
you
mean
the
in
Anwar
in
pilot
engine
powered
in
pilot.
There
is
a
PR
and
player.
That's
out
there
to
implement
this,
but
yeah
once
again.
What
has
to
be
done?
Yes-
and
you
know
this
also
like
kind
of
makes
all
caching
painful,
because
you
now
have
to
make
a
connection
of
like
you
know-
reason
one
you
have
a
cache
of
it.
Yes
or
region.
Do
we
have
a
different
cache
of
PDS
because
the
weight
settings
would
differ,
but
a
region
by
region
basis,
yeah.
E
The
eye
it
would
have
been
great
if
that
whole
intelligence
was
then
unvoiced
such
that
it
could
automatically
see,
and
we
can
just
apply
this
one
time
to
all
envoys.
But
the
way
it's
being
done
is
that
if
there
is
no
longer
a
notion
of
like
you,
know,
unwind
knowing
I'm
in
region,
one
so
I'm
actually
gonna
try
to
do
other
regions.
It
basically
has
like
thumbs
up
locations
with
priorities,
and
it
decides
it
out
from
the
highest
priority
to
the
lowest
priority.
The
completely
agnostic
manner.
D
C
E
Requires
that
unwise,
with
the
local
zone
I
mean
you
have
you
have
to
tell
on
why
what
zone
it
is
running
in
and
that
basically
means
like
you,
take
control
over
the
Envoy
and
like
a
fun
way?
I,
don't
you
know
us
best,
one
and
within
kubernetes
at
least
that
zone
information
is
not
actually
available
on
every
odd
like
when
you
start
talk,
you
have
a
go
top
and
service
registry
and
get
that
information.
I,
don't
know
how
it
works
within
cloud
foundry.
It's.
E
E
E
It
is
a
next
try.
Any
there
are
several
issues.
One
is
its
next.
One
would
be
this.
It's
PMB
overhead
because
of
the
kubernetes
crying
:
to
that
I
have
60
and
before
every
sidecar,
yeah
necessary.
Second,
one
being
that
until
you
query
that
information,
you
cannot
start
the
sidecut
so
which
is
also
a
you
know.
It
increases
the
time
to
start
up
the
sidecar.
E
F
E
E
C
E
Off
locality,
yes,
and
also
what
I'm
saying
is,
if
you
do
zone
aware
outing,
then
you
you
have
certain
limitations.
The
newer
API,
the
the
thing
that
is
here
is
actually
using
the
locality,
weight
and
load
balancing
thing
and
one
way,
and
that
thing
is
kept
mutually
exclusive
from
the
zone.
Aware
outing,
which
is
the
legacy
zone,
aware
doubting
that
left
hat,
and
so
the
newer
one
has
some
features,
such
as,
like
fallback
to
different
priorities
and
a
bunch
of
other
things
that
the
older
one
does
not
have.
E
E
Yes,
it
is
still
back
last
I
mean
like
I,
don't
know
being
heavy
and
so
on
like
the
way
they
have
done.
This.
The
whole
thing
was
very
biased
towards
the
use
cases
in
Squire
and
a
couple
of
other
people,
and
so
the
whole
thing
that
impact
direction.
It
worked
out
to
hobbies
themes
like
gold,
but
it's
completely
messed
up
when
it
comes
to
the
general
purpose
mesh
on
a
kubernetes
or
CF
cluster.
So
that
part
is
there
I,
don't
know
how
to
like
expose
her
face.
A
E
C
E
So
no,
then
you
the
active
health
checking
when
you
actually
code
the
endpoints
in
a
cluster.
You
have
to
tell
it
what
zones
and
regions
those
endpoints
are.
Okay,
the
active
health
checking.
All
it
does
is
that
automatic,
so,
instead
of
an
outlier
reduction
which
actually
like
you
know,
first
makes
a
request
and
then
seen
things
are
failed
and
we
tries
and
so
on
and
so
forth.
E
E
E
A
A
E
F
F
E
F
A
E
Yeah,
and
that
is
about
I
guess
Rand
will
take
a
look
at
the
fights.
Are
PR
pay
close
attention
to
the
collector
field?
The
selector
feel
that
you
had
was
one
which
actually
had
you
know,
labeled
as
a
sub
objects
that
you
can
actually
have
different
types
of
selector,
not
necessary
labels,
but
x.509
certificate
feels
that
you
can
actually
provide
or
so
on
and
so
forth.
Yeah.
A
E
F
E
E
E
Other
ad
hoc,
oh
and
one
final
things:
what
happens
to
the
ports
in
the
sidecar?
This
thing,
when
you
don't,
when
you
specify
a
port
on
which
you
want
the
egress
listener
to
be
present,
does
that
automatically
I'm
guessing
it
automatically
implies
the
only
route
traffic
to
the
specific
ports
service
is
like
that
map
for
egress?
Yes,
yeah
ye
grace!