►
From YouTube: 2020-11-19 Istio Community Meeting
Description
On November 19th, there were updates from working groups, a demo, discussion time, and questions from users. Demo: "What's new and exciting in Istio 1.8?", will be led by Neeraj Poddar, Co-founder & Chief Architect, Aspen Mesh
A
Okay,
so
welcome
everybody
to
the
istio
community
meetup.
My
name
is
maria
cruz,
I'm
a
program
manager
in
the
google
open
source
program
office,
and
here
today
we
have
a
mirage,
polar
who
is
going
to
be
presenting
the
latest
developments
for
the
the
last
release
of
istio
or
that
the
release
that
is
coming
up
but
niraj
is
gonna,
tell
us
more
and
I
think
we
can
see
your
screen
mirage.
So
whenever
you
want
to
start
the
floor,
is
yours.
B
Thanks
maria
hello,
everyone
I
am
niraj,
I'm
the
co-founder
and
chief
architect
at
aspen
mesh.
I've
also
been
a
long
time,
maintainer
and
contributor
of
instio
project
and
I'm
currently
on
the
toc
and
steering
committee.
So
I'm
excited
to
talk
about
all
the
new
and
exciting
features
that
are
in
istio
1.8.
So
before
we
go
into
it,
I
want
to
make
sure
everyone
is
aware
of
the
1.8
status.
The
s2
community
is
working
really
hard
to
get
1.8
out.
B
B
First
off
the
release
itself
was
a
community
effort.
It
took
a
lot
of
effort
from
contributors
across
different
organizations,
so
I
just
did
some
git
commands
to
to
surface
this
information,
which
is
we
have
1025,
plus
new,
commits
since
release
one
seven.
So
that's
a
lot
of
comments
added
by
all
the
maintainers
and
in
this
video.
B
Each
of
these
commits
mostly
tie
back
to
a
pull
request,
because
in
a
pull
request,
you
can
have
lots
of
commits
which
we
all
squash
and
merge.
So
this,
even
if
this
number
seems
low
for
a
three
and
a
half
month
effort.
It's
a
lot
of
pull
requests
and
a
lot
of
code
changes
that
have
gotten.
There
are
110,
plus
unique
contributors
from
several
different
organizations
that
have
worked
for
stu
1.8
release,
and
then
I
just
want
to
give
a
shout
out
to
the
release.
B
B
We
were
focused
on
promoting
the
existing
features,
so
we
have
a
feature
escalation
process
in
a
future
maturity
process
in
store
where,
if
a
feature
comes
in
as
experimental
or
alpha,
we
make
them
beta
and
then
stable.
So,
as
the
community
has
a
lot
of
contributions
from
different
organizations
and
different
people,
we
want
to
make
sure
we
take
a
step
back
and
promote
features.
B
At
the
same
time,
we
are
adding
new
capabilities
right,
improving
quality,
adding
tests
and
improving
our
documentation
has
always
been
one
of
the
key
areas
of
focus
and
then
making
sure
we
have
security
as
a
key
core
principle
for
istio
discovery.
Moving
from
a
microservices
control
plane
to
monolith
in
this,
I
think
it
was
done
like
in
one
six
or
one
seven.
B
B
We
have
expanded.
The
multi-cluster
use
cases
made
improvements
in
the
documentation
so
that,
as
companies
as
organizations
are
growing,
they
can
actually
expand
their
mesh
and
have
more
and
more
clusters
and
workloads
in
them
and
then
focus
on
diagnostic
tools
so
that
we
can
surface
to
our
users
if
they
are
having
issues
in
their
mesh.
How
can
they
quickly
get
all
the
information
and
debug
it
right?
So
this
is
obviously
an
ongoing
effort.
B
It
has
been
continuing
for
quite
a
few
releases
and
it
will
continue
even
in
one
line,
but
one
eight
have
some
has
some
significant
improvements
in
these
areas,
which
I
will
highlight
in
my
next
slide
and
the
new
features
that
we
have
added
again.
This
is
not
an
exhaustive
list
by
any
means.
There
are
quite
a
few
new
features,
but
two
things
that
I
wanted
to
highlight
was
from
the
telemetry
point
of
view.
B
We
have
added
support
for
open
tracing
and
the
open
tracing
agent,
in
addition
to
the
existing
support
for
jaeger's
track,
driver
and
zipkin,
and
then
in
the
security
authorization
side
of
things.
There
is
a
new
policy
audit
command
where
you
can
actually
see
what
would
have
happened.
Actually
this
is
the
audit
one.
So
in
this
you
can
log
and
look
at
your
authorization
policies
and
inspect
as
requests
are
getting
rejected
or
accepted
right.
So
this
gives
you
another.
This
solves
another
puzzle
in
the
whole
policy
enforcement
and
your
compliance
journey.
B
So
these
are
some
of
the
few
highlights.
I
have
for
stu
1
8
release
the
first
one
which
I'm
really
excited
to
talk
about
is
helm.
V3
support
is
back
so
for
those
who
have
watched
and
been
on
the
stoo
journey
for
our
from
early
days.
You
know
that
helm
was
the
main
tool
for
installing
and
upgrading
sto
helm.
2
obviously
had
some
security
issues,
so
we
had
taken
back
him
to
support
and
then
in
the
releases
from
one
six
one,
seven
and
now
one
eight.
B
We
always
we
have
introduced
things
like
istio
ctl,
based
support
operator
based
support.
But
now
I'm
excited
that
in
one
eight
we
are
supporting
helm
v3.
The
good
thing
about
all
these
three
installation
mechanisms
is
underneath
they
use
the
same
exact
helm,
charts
for
steel
discovery
base
and
gateways.
So
you
get
the
same
underlying
components
and
customizations.
B
Just
your
install
workflow
is
different,
and
this
was
specially
added
back
based
on
popular
demands.
We
had
been
conducting
user
service,
the
user,
the
user
experience
working
group
has
been
doing
an
excellent
job
of
gathering
feedback,
and
we
had
heard
that
many
of
our
many
of
the
users
are
using
help
in
the
existing
environments
to
install
and
manage
the
life
cycle
of
other
applications.
B
B
The
current
support
for
helm
in
one
eight
will
be
alpha
and
I
look
forward
to
getting
feedback
from
folks
as
what
more
enhancements
they
want,
so
we
can
make
improvements
in
one
line
or
even
in
batch
releases
in
one
eight
right.
The
second
interesting
feature
is
proxy.
Dns
interception.
Again
it's
a
new
feature.
It's
an
alpha,
so
the
key
benefit
here
is
the
sidecar
proxy
can
now
be
configured
to
intercept,
dns
requests
and
resolve
those
requests.
B
B
The
secret
discovery
service
sds,
which
is
the
default
way
of
discovering
secrets
in
istio
since
1
6,
since
we
removed
file
based
secret
discovery,
it's
now
running
in
sdod,
so
the
reason
this
is
important
is
previously.
The
sds
server
was
running
an
istio
agent,
which
runs
inside
as
a
separate
process
in
the
stop
proxy
container
and
the
istio
agent
used
to
talk
to
the
student
discovery
service
just
for
signing
the
certificates.
B
This
move
makes
the
security
model
better.
Where,
especially
specifically
for
gateways,
you
don't
have
to
provide
all
the
secrets
that
the
gateway
needs,
but
stod
can
rather
look
at
those
secrets.
Look
at
the
specific
secrets
which
a
gateway
needs
load
it
up
and
only
pass
those
secrets
down
to
the
gateway
proxy.
So
it's
from
the
user
perspective.
It
does
not
change
any
behaviors
in
your
system,
but
it
just
makes
it
more
secure.
B
B
Issues
in
istio
or
they
ask
for
help
and
discuss
and
slack
we
often
seen,
then
we
our
developers,
need
to
have
a
bunch
of
back
and
forth
to
get
all
the
information
before
they
can
actually
help
them.
So
this
tool
is
a
great
way
of
grabbing
all
the
information
from
your
cluster
or
for
a
specific
pod,
so
that
in
one
single
snapshot
you
can
upload
the
cluster
configuration.
You
can
upload
what's
happening
in
your
istio
pods.
What
is
the
onward?
B
Configuration
looks
like
what
is
the
sd
ctr
analyze
surfacing
any
errors,
so
all
of
that
information
is
collected,
a
tarball
will
be
produced
and
you
can
just
upload
it
on
a
github
issue
or
share
it
across
your
team
members.
So
you
can
easily
debug
and
diagnose
issues
in
your
mesh.
The
last
thing
is
the
release
notes
this.
These
links
right
now
might
not
work
until
the
release
is
actually
published.
B
So,
hopefully,
after
soon
after
my
presentation
is
done,
the
release
will
be
published,
but
I
will
highly
recommend
all
the
users
of
istio
if
there
are
new
users
who
are
moving
to
going
to
be
moving
towards
you
and
using
one
eight,
please
look
at
all
the
release,
notes
to
understand
the
capabilities
and
features
that
have
been
added
in
one.
Eight
next
thing
that
I
want
to
talk
about
is
upgrade
notes,
so
existing
users
of
s2,
if
you're
on
sto17-
and
you
want
to
move
to
one
eight.
B
The
community
does
a
great
job
of
capturing
various
settings
that
have
changed
various
features
that
might
have
deprecated
that
you
are
using
and
we
we
want
to
make
sure
that
your
upgrade
and
migration
is
as
smooth
as
possible
and
a
big
part
of
that
is
paying
attention
to
the
upgrade
notes
that
our
developers
have
produced
for
one
eight,
I'm
just
highlighting
three
key
things
that
folks
should
be
aware
of
first
is
mixer
is
actually
removed.
In
hto18
we
have
been
talking
about
mixer
or
telemetry
v1
being
deprecated
for
two
releases.
B
Now
I
think
one
six.
We
had
officially
made
telemetry
v2
as
the
default
telemetry
mechanism,
but
we
but
v1
was
still
supported
in
one
seven.
It
was
officially
deprecated
and
now
we
have
removed
it.
So
all
of
the
users,
if
they're
still
using
telemetry
v1,
now
need
to
move
to
v2.
As
you
know,
the
v1
mechanism
doesn't
exist.
Additionally,
if
you're
using
some
mixer
adapters
and
the
s2
community
has
not
provided
you
equivalent.
If
there
is
no
equivalent
mechanism
for
you
to
achieve
that
functionality,
please
file
bugs.
B
B
The
reason
we
so
this
plug-in
itself
was
not
very
well
maintained,
and
in
sto18
we
have
added
the
dns
interception
in
proxy.
So
we
decided
to
deprecate
this
officially
and
move
users
over
to
the
new
mechanism
if
needed,
and
the
third
thing
is
a
lot
of
onward.
Filters
have
been
that
onward.
Filter
names
have
changed
and
the
old
names
have
been
deprecated
by
envoy.
B
This
means,
if
you're
creating
custom
onward
filter
resources.
You
need
to
make
sure
that
you
move
the
new
name
in
istio
1.8.
I
think
we
are
supporting
both
old
and
new
names,
but
going
forward
in
1.9
only
the
new
names
will
be
supported.
So
this
is
the
release
where
you
should
do
your
migration,
all
right.
B
So
just
some
book
housekeeping
items
here.
How
do
you
get
the
release?
So
you
can
go
to
the
latest
release
page
in
github
and
download
180.
Once
it's
published
a
few
helpful
suggestions
from
me
new
users,
I
would
highly
recommend
that
you
read
and
start
with
the
getting
started
guide.
This
is
the
easiest
way
to
install
istio
for
demo
purposes
or
just
kicking.
The
tires
installation
guides
are
a
very
valuable
tool
where
we
explain
all
the
different
options
for
supporting
sdo,
so
it
will
cover
istio,
ctl
or
in
cluster
operator
or
helm.
B
V3
and
we
also
explain
the
trade-offs
between
them,
so
you
can
make
an
informed
choice
based
on
your
requirements,
and
the
last
is,
if
you
are
upgrading
to
sto,
please
go
through
the
upgrade
guide.
It
gives
you
various
options
where
you
can
do
an
in-place
upgrade
or
a
revision
based
upgrade
or
you
can
test
the
new
version
doing
a
canary
deployment.
B
So
all
of
these
options
and
resources
are
available
to
you,
read
them
and
then
move
to
one
eight
and
give
us
feedback
right.
So
now
I
have
a
demo
prepared
where
I'm
gonna
be
installing
stu
with
1.8
and
show
you
how
the
istio
ctl
bug
report
tool
can
be
used.
But
before
I
move
to
the
demo,
are
there
any
questions
I
can
answer
for.
C
B
If
you
have
used
some
of
the
earlier
mechanisms
to
use
to
install
sdo,
currently
it
will
be
removing
the
control
plane
and
installing
the
new
control
plane
with
helm.
You
can
do
it
in
a
phased
way.
Where
you're,
you
know,
you
don't
have
to
delete
everything,
but
at
a
high
level.
That's
what
it
means
now
remember
when
you
are
removing
the
control
plane.
If
you
don't
remove
the
custom
resource
definitions,
your
resources
will
still
remain
and
then
your
workloads
and
the
traffic
between
workloads
will
also
continue
to
work.
B
A
B
B
Yeah,
this
is
the
right
one.
Yet,
yes,
okay,
so
I'm
gonna
be
following
the
helm
guide
that
we
that
we
have
for
one
eight
for
installing
and
upgrading
sto.
So
I
you
know
just
to
make
sure
I
have
a
high
probability
that
my
demo
actually
works.
I
have
those
commands
in
my
batch
script,
so
I'm
gonna
copy
them
one
one
by
one.
So
first
thing
I
always
recommend
when
you
are
moving
to
istio
is
or
installing
stu
is
making
sure
you
have
the
right,
kubernetes
version.
So
in
my
cluster.
B
B
B
Next
up,
I'm
going
to
grab
the
latest
release
of
istio
and
in
this
case
I'm
going
to
use
this
awesome
download
script
that
we
have
and
provided
the
specific
revision.
The
revision
here
is
180
rc,
dot,
zero.
That's
just
because
the
official
release
is
it's
not
available
right
now,
once
the
official
release
is
available,
you
don't
have
to
provide
the
sto
version
here.
So
let
me
just
do
that,
so
it
goes
and
fetches
the
tarball
and
it
will
automatically
untie
it
for
me.
B
So
now,
if
I
see
in
here,
I
have
my
sto180rc
0.,
it's
a
good
start.
Next,
I'm
going
to
follow
that
documentation
and
that
documentation
for
istio
for
installing
a
steer
using
helm.
The
next
step
is
to
create
the
sq
system
namespace.
So
that's
what
I
do
and
then
I'm
going
to
install
the
charts
manually.
So
istio
comes
with
many
charts
which
are
all
inside
this
directory
to
get
a
minimal
installation
of
sdo.
B
You
need
to
at
least
install
two
charts,
and
here
we
are
going
to
go
beyond
that
and
just
install
the
ingress
gateway
chart2.
So
the
first
one
is
this
command
for
installing
the
base
chart.
So
the
good
thing
about
using
helm
is
it
gives
you
the
flexibility
of
managing
these
charts
themselves.
It's
not
wrapped
around
with
your
ctl,
but
at
the
same
time
it's
more
commands
that
you
have
to
run.
So
this
is
good.
B
So
now
I
have
the
base
chart
install
base
chart
is
basically
responsible
for
installing
some
cluster
level
resources,
so
it
will
create
service
accounts
in
this,
your
system
that
will
be
used
by
various
sto
components.
It
creates
a
webhook
configuration
validation,
webhook
configuration
for
me.
It
also
creates
cluster
roles
which
you
can
see
and
then,
if
I
look
at
my
helm
command
now,
I
have
one
chart
installed
to
the
your
base.
B
Next
thing,
which
is
very
important,
is
to
make
sure
you
have
third
to
make
sure
to
check
whether
you
have
third
party
charts
enabled
in
your
cluster
or
not.
So.
This
is
really
important
because
istio
ctl
and
operator
based
installs,
automatically
detect
your
cluster
detect
from
your
running
cluster,
where
the
third-party
tokens
are
enabled
and
accordingly
adjust
the
chart
values.
Helm
won't
do
that,
so
to
deter
to
make
sure
your
cluster
has
first
party
chart
supported
third
party.
You
can
run
this
command
if
it
returns
to
you
this
json.
B
B
Right
so
with
this
done
now,
if
I
go
and
visit
just
your
system,
there
you
go
so
now
I
have
my
sdod
container
running,
which
is
good
right.
I
can
look
at
the
logs
to
make
sure
that
I
don't
get
any
errors.
It's
always
a
good
same
thing
to
do
whenever
you
install
all
right
so
far
so
good
it
did
some
reconciliation.
It's
all
happy,
then
I'm
going
to
install
the
ingress
gateway
chart.
B
B
So
now,
when
I
get
my
pods
they're
coming
up,
all
of
them
have
two
containers,
which
is
a
good
sign.
That
means
they
have
the
side
car
proxy
injected.
There
you
go
so
now
all
of
them
are
running.
I'm
gonna
apply
the
gateway
resource
so
that
I
can
reach
these
reach
my
booking
for
application
from
outside.
B
So
this
just
shows
the
entire
helm
based
installation
for
sto18
and
then
adding
applications
in
your
mesh.
Like
you
always
do
and
you
you
can
similarly
use
the
helm,
upgrade
commands
to
change
the
configuration
or
helmet
install
if
you
want
to
go
back
and
remove
things.
The
last
thing
that
I
want
to
demo
is
the
amazing
stu
ctl
bug
report
tool.
So
I'm
gonna
do
this.
B
So
if
this
is
only
available
in
one
eight,
but
you
can
run
it
against
an
older
cluster
too,
that's
the
good
thing
about
this
command.
So
if
you
look
at
the
helm,
it
shows
you
what
bunch
of
options
you
have
and
what
it
does,
but
the
best
thing
to
do
is
just
run
it.
So
if
I
run
this,
it
will
print
out
a
bunch
of
things
that
it
is
doing.
B
B
All
right,
so,
if
you
see
there's
a
lot
of
amazing
information
here,
so
it
will
run
analyze,
issues,
it'll
analyze,
to
look
at
your
existing
cluster
configuration
and
if
there
are
any
issues
with
that,
so
it
runs
it
on
all
the
namespaces
by
default.
If
you
have
not
provided
any
options,
so
it
is
just
saying
that
one
of
the
namespaces
doesn't
have
the
injection
label.
B
B
There
you
go
so
these
are
the
gateways
that
we
applied
and
obviously
there
is
no
sensitive
information
stored
in
this.
So
all
of
this
information
can
be
easily
shared
in
a
you
know,
github
issue,
for
example,
so
it
also
describes
various
events
and
the
parts
which
unites
your
system.
So
you
get
a
good
state,
good
snapshot
of
your
control
plane
moving
forward.
This
is
the
most
interesting
and
attractive
part
for
me.
B
It
will
go
to
all
your
name
spaces,
look
at
all
the
parts
which
have
proxies
and
then
dump
out
detailed
information
about
those
proxies
so
for
each
sidecar
proxy.
It's
giving
you
all
the
configuration.
So
this
this
is
a
very
big
cluster
dump
of
everything
that's
happening
in
your
own
voice,
so
you
can
understand
whether
your
configuration
that
you
have
applied
is
actually
getting
enforced.
If
there
are
issues
where
there
were
conflicts
and
your
configuration
didn't
get
applied
or
envoy
has
rejected
things,
so
it's
really
really
helpful
going
further.
B
B
Again,
you
don't
have
to
have
prometheus
for
this.
It
just
queries
the
data
from
the
sidecar
proxies
itself
and
gives
you
the
current
snapshot.
So
with
that,
I
think
my
demo
is
done
this.
I
will
encourage
everyone
to
explore
this
tool
and
especially
if
you're
filing
bugs
in
a
store
use
it
so
that
it
reduces
your
back
and
forth
with
the
community,
and
you
can
quickly
resolve
any
issues
you
have
so
with
that
I'm
going
to
stop
sharing,
and
if
there
are
any
more
questions
I
can
answer,
I
would
love
to.
E
B
Really
good
question,
so
I
think
in
one
eight
istio
community
has
taken
a
stance
of
the
add-on.
Management
is
completely
to
the
users
themselves,
so
they
are
currently
moved
into
a
samples
directory
to
indicate
that
the
istio
provided
add-ons
are
not
directly
production
ready,
so
like
they
still
provided
sample.
Prometheus
should
not
be
used,
should
not
be
used
in
production.
You
should
you
can
use
a
helm
chart
for
prometheus
if
you
want,
or
you
can
use
cube
ctl,
but
the
life
cycle
management
of
that
is
completely
outside
the
lifecycle
management
of
stu
itself.
B
I
think
that
right
now
is
again
inside
samples,
so
as
as
part
of
the
the
istio
release
package,
if
you
go
inside
samples,
add-ons
there's
a
grafana
sample
and
then
those
istio
dashboards
still
are
there.
You
can
apply
them
using
tube
ctl
apply
the
this
change
to
move
them
from
a
part
of
the
hto
charts
to
the
samples
was
just
to
signal
that
it's
meant
to
be
customized
by
users
and
meant
to
be
made
production
ready
by
them.
F
I
think
too,
we're
not
so
worried
about
supporting
the
charts
themselves,
as
we
are
that
we
we
don't
want
to
be
the
ones
supporting
your
installation
of
grafana.
Absolutely
we
are
not
experts
in
that
space.
You
definitely
do
not
want
our
advice
in
that
area.
There
are
other
people
who
are
way
better
at
that,
but
as
far
as
the
chart
itself,
I
I
think
we
would
likely
provide
a
decent
amount
of
support
there.
Yeah
yeah,
the
dashboard
itself.
You
mean
yes,
yeah.
F
A
A
A
A
Room,
okay
and
I'm
gonna,
okay,
so
thank
you,
everybody
for
for
coming
back
to
the
main
room
to
say
bye,
and
I
hope
that
you,
like
the
the
time
to
connect.
On
a
more
personal
note,
I
wanted
to
thank
niraj
for
presenting
today.
Thank
you
so
much
and
anybody
who
wants
to
present
a
demo.
This
is
where
I'm
collecting
information
on
the
to
discuss.
A
I
just
share
the
the
link
on
the
chat
box,
so
please
come
forward
any
application
of
istio
or
any
use
case
that
you
have
that
you
want
to
show
how
you're
using
istio.
We
would
love
to
to
hear
about
that.
I
want
to
share
one
more
thing
with
you
all
before
we
leave,
and
that
is
a
survey,
and
I
know
we
don't
have
most
of
the
people
here.
A
Oh,
thank
you
so
much
jamie
yeah
that'll
be
awesome.
The
survey
allows
us
to
collect
feedback
about
the
this
event,
and
so
we
can
learn
what
you're
interested
in
and
what
is
most
useful
to
you.
So
jamie's
gonna
share
that
on
the
chat
box
here
and
yeah
I
wanna.
Thank
you
all
for
coming,
and
I
also
let
you
know
that
in
december
we're
not
gonna
have
a
meet
up
because
it's
very
close
to
the
to
the
holidays
and
the
next
meetup
is
gonna
be
in
january.