►
From YouTube: Keynote: CNCF Project Updates - Michelle Noorali, Senior Software Engineer, Microsoft Azure
Description
Keynote: CNCF Project Updates - Michelle Noorali, Senior Software Engineer, Microsoft Azure
Project representatives will share their updates:
Linkerd update, presented by Oliver Gould
Fluentd update, presented by Eduardo Silva
Prometheus update, presented by Tom Wilkie
About Michelle Noorali
Michelle is a software engineer on the Azure Container Service team at Microsoft and a core maintainer on the Kubernetes Helm project. She co-leads SIG-Apps which is the Kubernetes special interest group for running and managing applications and workloads on Kubernetes. She has previously spoken at CloudNativeCon/KubeCon 2016 EU & NA.
About Oliver Gould
Oliver is the CTO of Buoyant, where he leads open source development efforts. Prior to joining Buoyant, he was a staff infrastructure engineer at Twitter, where he was the tech lead of Observability, Traffic, and Configuration & Coordination teams. He is the creator of linkerd and a core contributor to Finagle, the high-volume RPC library used at Twitter, Pinterest, Soundcloud, and many other companies.
About Eduardo Silva
Eduardo is an Open Source Engineer at Treasure Data. He currently leads the efforts to make logging more scalable in Containerized and Orchestrated systems such as Kubernetes.
About Tom Wilkie
Tom is the founder of Kausal, a new company working on Prometheus & Cortex. Previously he worked at companies such as Weaveworks, Google, Acunu and XenSource. In his spare time, Tom likes to make craft beer and build home automation systems.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
Welcome
who's
excited
for
coop,
con
and
cloud
native
kind.
Let
me
hear
y'all
whoa
I,
like
the
word.
That's
really
awesome,
alright,
so
I'm
Michelle
nor
Lee
I'm,
all
the
things
that
Dan
mentioned
thanks
for
that
intro
Dan
I'm.
Also
so
I'm
co-chair
of
this
conference
I've
had
a
great
time
putting
together
the
schedule
alongside
Kelsie
Hightower.
We've
got
lots
of
great
sessions
scheduled
for
you,
in
addition
to
normal
talks
and
sessions,
we're
also
going
to
be
getting
updates
from
SIG's.
If
you're
wondering
what
a
cig
is
si
G
stands
for
a
special
interest
group.
A
This
is
how
we
in
the
cloud
Native
community
get
together
and
talk
about
specific
areas
of
interest.
There
will
also
be
cig
deep
dive
sessions.
These
are
longer
more
collaborative
sessions
for
you
to
participate
in
as
well
as
for
you
to
get
to
know
one
another
in
person.
In
addition
to
that,
we'll
also
have
technical
salons
today,
tomorrow
and
Friday.
These
are
an
opportunity
for
you
to
get
your
hands
dirty.
A
There
are
contributors
and
experts
from
all
of
the
CN
CF
projects
here
at
this
event,
ready
and
willing
to
help
you
get
started
answer
any
questions
you
might
have
even
walk
you
through
tutorials,
so
really
take
advantage
of
that,
and
also
we
work
on
these
complex,
distributed
systems
ourselves
being
distributed
all
over
the
world
and
across
time
zones.
So
take
advantage
of
this
opportunity
and
I
encourage
you
at
any
level
of
experience,
to
take
advantage
of
this
opportunity
to
meet
people
in
three
dimensions
today
tomorrow
and
Friday.
A
So
the
scenes
yes
currently
hosts
14
projects.
This
is
insane
one
because
the
CNC
F
is
less
than
two
years
old
and
two
because
the
CNC
F
was
hosting
just
eight
projects
in
March
of
this
year.
At
the
last
cloud
native
con
and
coupe
con
event
in
Berlin,
it's
remarkable
to
me
quickly.
Things
are
moving,
how
many
organizations
are
coming
together
and
how
much
the
community
has
grown.
I
mean
seriously
from
up
here.
I
have
an
amazing
view.
A
Raise
your
hand
if
this
is
your
very
first
cloud
native
pine
or
coop
Kline
conference-
that's,
oh,
that's!
Actually
more
than
I
was
expecting.
That's
a
lot
of
talk,
that's
a
lot
of
y'all,
because
the
last
event
was
less
than
half
this
size
and
all
of
the
conference's
before
this
one
don't
even
match
the
number
of
people
that
are
here
today.
A
Well,
we
had
the
rise
of
micro
services,
which
is
this
idea
that
you
have
loosely
coupled
services
that
implement
business
logic
and
are
independently
deployable.
This
is
great
for
your
organization,
because
you
can
now
have
teams
that
have
specialized
areas
of
a
concern,
and
those
teams
are
also
enabled
to
deliver
changes
faster
and
more
frequently.
A
We
also
see
saw
the
increasing
need
to
decouple
the
application
from
the
environment
that
it's
running
in
so
the
infrastructure.
It's
running
on
with
the
rise
of
the
cloud.
An
amazon
had
a
lot
to
do
with
that.
It
suddenly
became
a
waste
of
time
to
manage
your
own
physical
infrastructure
and
being
in
the
cloud
renting
servers.
A
Kubernetes
was
also
the
first
project
to
be
donated
to
the
CN
CF
and
it
also
inspired
the
creation
of
a
CNC
F,
because
Google
wanted
to
donate
this
technology
to
a
vendor
neutral
party
and
from
there
the
CNC
F
has
been
building
this
powerful
toolkit
that
enables
us
to
build
and
scale
these
modern
application.
Architectures
and
environments
look
at
where
we
are
now
three
of
the
largest
cloud
providers
announce
their
own
managed
kubernetes
services.
A
A
We'll
also
see
a
big
win
in
the
cloud
native
storage
space
with
CSI
support
in
alpha.
The
container
storage
interface
enables
out
of
tree
volume
plugins
in
kubernetes.
Now,
if
you're
thinking
well,
why
does
this
even
matter?
Let
me
tell
you,
enabling
CSI
support
in
kubernetes
lowers
the
barrier
of
entry
for
storage
vendors,
wanting
to
support
kubernetes,
giving
us
all
more
storage
options
in
the
long
run
and
further
preventing
the
risk
of
vendor,
locking
and
like
we're,
seeing
with
the
CSI
initiative.
A
These
higher
order
systems
like
kubernetes
depends
on
other
loosely
coupled
cloud
native
technologies
and
components
core
DNS.
It's
a
great
example
of
that
Cortinas
is
a
generic
DNS
server
that
can
talk
to
multiple
backends
like
XP,
kubernetes,
caching,
mild'
middleware
and
others
due
to
its
plug-in
style
architecture.
A
Today,
I
get
to
announce
that
core
DNS
is
one
day
and
it'll
be
available
in
1.9
kubernetes
1.9
on
an
alpha
basis
as
a
replacement
for
kube
dns,
adding
even
more
features
than
we
currently
have,
and
more
performant
functionality.
There's
a
core
DNS
technical
salon
happening
today
at
3:40.
If
you're
interested
in
learning
more
another
component
to
know
about
its
container
D
an
industry
standard
container
runtime
a
container
runtime
is
the
thing
that
enables
you
to
execute
containers
and
manage
images
on
a
host.
A
A
A
Another
project
that
came
out
of
rocket
was
the
container
networking,
interface
or
CNI,
and
most
of
this
take
this
one
for
granted.
Actually
most
of
us
take
this
one
for
granted,
and
this
this
is
the
specification
and
API
for
connecting
and
improving
containerized
workloads
from
the
network.
It's
used
by
rocket
kubernetes,
openshift,
Cloud,
Foundry,
mais,
au
s--
and
the
list
goes
on.
A
Cni
is
also
approaching
a
one
dot
o
release
the
maintainer
czar
looking
for
feedback
on
what
you'd
like
to
see
in
1.0.
So
if
you
have
something
get
in
their
issue,
queue-
and
let
them
know-
we've
talked
so
far
about
projects
and
the
CNC
F
that
enable
you
to
work
with
containers
and
make
your
workloads
portable
and
that's
important
for
building
the
services
that
power
your
business,
but
just
running
containers
isn't
going
to
be
enough.
A
You've
you're
also
going
to
need
intelligent
ways
to
figure
out
what
the
heck
is
going
on
inside
of
these
complex
systems.
I
found
it
interesting
that
Twitter,
a
company
known
for
its
micro
services
architecture,
has
its
own
observability
engineering
team
that
focuses
on
this
area.
Let's
switch
gears
and
talk
about
a
set
of
projects
under
the
CNC
F
that
fall
into
this
category
of
observability,
starting
with
container
monitoring
with
Prometheus
here
with
us
today,
is
Tom
wookie
from
developer.
B
Hello,
everybody
wow.
This
is
a
very
big
cloud,
a
bit
very
big
crowd,
isn't
it
so
prometheus
Prometheus
is
an
open-source
monitoring
system
and
time
series
database
really
specifically
designed
for
dynamically
scheduled
environment
like
kubernetes.
It's
got
a
powerful,
concise,
query
language,
a
really
efficient
storage
engine,
a
really
simple
operational
model
and
was
the
second
project
accepted
into
the
CN
CF
after
kubernetes
I'm,
really
here
today,
to
talk
mainly
about
Prometheus
to
doto
the
the
second
major
prometheus
release
we
did
on
November.
B
The
8th
Fabian
noticed
basically
that
with
Prometheus
1
dot,
oh
really
highly
dynamic,
kubernetes
environments
would
put
a
bit
of
strain
on
the
storage
engine,
especially
if
you're
doing
things
like
continuous
deployment
and
had
a
high
churn
of
very
short-lived
containers.
So
he
developed
along
with
Brian
and
Goutham
who's
in
the
crowd
somewhere
a
brand
new
storage
engine
for
Prometheus
significantly
improving
the
performance.
B
This
is
a
graph.
The
top
line
is
Prometheus
1.5,
the
bottom
lines
of
Prometheus
2
dot.
O
we
see
about
a
3x
reduction
in
CPU
usage,
a
2x
reduction
in
disk
base
and
over
a
hundred
X
reduction
in
IO.
It's
hugely
performant,
and
these
are
real-world
use
case
numbers
that
you'll
you'll
get.
If
you
run
it
next.
I'd
like
to
talk
about
the
Prometheus
community,
we've
had
an
absolutely
stellar
year.
B
B
Finally,
they
we've
got
a
jam-packed
edge
for
Prometheus
events,
we're
running
a
Prometheus
tool
on
at
ten
past
eleven
various
other
talks
you
consume
on
slates
and
finally,
we're
going
to
finish
up
with
some
drinks
at
8:00
p.m.
go
to
the
Prometheus
blog.
If
you
want
to
sign
up
and
find
out
more
details
about
that,
thank
you.
A
A
C
Hello,
everyone
wow.
This
is
huge
compared
to
Berlin
as
Michelle
said
well
before.
To
start
talking
about
zoondy,
I
would
like
to
start
talking
about
logging
and
logging
in
general
exists,
because
just
one
reason
is
because
you
want
to
do
some
kind
of
data
analysis,
which
means
to
try
to
get
some
insights
from
your
own
applications.
And
how
do
we
accomplish
that?
C
But
that's
one
thing,
but
if
we
want
to
do
data
analysis
and
if
you
have
multiple
applications
and
to
consider
now
that
we
have
containers
orchestrators,
you
have
to
consider
that
you
need
to
centralize
all
of
this
information
in
one
place
so
how
to
solve
that
problem.
It's
not
easy
from
the
beginning,
but
every
problem.
If
you
understand
it
very
well,
you
can
come
up
with
the
right
solution
and
the
strategy
from
an
engineering
perspective
was
ok.
C
We
have
a
problem,
we
have
different
messages
from
different
places
and
we
come
up
with
a
design
which
is
called
the
login
pipeline,
which
said:
ok,
you
have
some
messages
that
are
arriving
through
some
input.
May
you
need
to
filter
this
information
parse
this
information
stored
somewhere
and
then
ship
this
information
back
at
the
beginning?
It's
not
that
easy
to
understand,
but
basically
you
have
an
input
and
you
need
an
output,
but
in
the
middle,
when
working
with
logging,
there
are
many
things
that
are
really
relevant.
C
Data
transformation
is
one
of
them
and
that's
what
fluency
is
a
full
solution,
like
log
aggregation
log
transformation
that
allows
you
to
connect
to
the
data
from
one
place
to
another,
with
a
strong
focus
on
logging,
of
course,
and
ok,
we
understand
what
is
the
problem
with
logging
and
most
of
you
or
half
of
you
are
using
fluent
in
the
remai
perspective.
So
a
we
have
some
news,
and
today
this
morning
our
principal
maintainer
of
fluency
Masahiro
has
announced
said
that
flow
in
d1
tatto
has
been
relisted.
C
Thank
you
thanks
a
also
to
the
whole
feedback
that
we
have
get
from
the
community
you
as
an
individuals,
as
representatives
companies
has
made
this
possible.
You
have
to
understand
that
behind
us
a
project
they
are
engineers,
there's
a
team
but
also
there's
people
who's,
providing
the
right
feedback.
You
know
what
you
are
doing
this
wrong
and
from
a
point
perspective
if
we
can
fix
that
means
that
we
are
solving
the
problem
better
and
that's
the
whole
things
today.
We
are
doing
this,
but
tomorrow
we
had
to
make
it
better,
so
they
move
forward
today.
C
What
else?
Ok,
whether
thou
also
comes
with
multi-process
support,
it
support
also
sub
second
time
resolution.
We
have
include
native
TLS
and
encryption
inside
flow.
Indeed,
so
it
will
be
more
easily
to
make
the
plugins
ecosystem
work
in
a
secure
way
when
sending
data
from
one
place
to
another.
Also
performance
is
a
critical
thing,
so
we
come
up
with
a
new
design
for
stored
in
the
data
into
the
local
buffers
for
reliability.
C
And,
of
course,
when
you
talk
about
containers
and
cloud
also,
you
have
to
consider
that
sometimes
the
logs
needs
to
be
sent
to
a
different
place
needs
to
be
cheaper
as
time's
the
network
fails,
you
have
power
outage,
and
things
does
not
go
well.
That's
why
we
have
a
protocol
which
is
called
forward
which
aims
to
be
used
to
send
logs
from
one
place
to
another,
but
also
that
is
it's
not
that
all
it
includes
security
and
allows
to
allow
us
to
do
some
kind
of
load
balancing.
C
So
you
can
have
your
own
H,
a
a
scenario
in
your
own
architecture,
and
when
you
talk
about
log
in
log
in
this
is
one
thing
from
the
beginning:
cut
zones
like
okay
I'll,
look
at
that
logs
by
this
times.
More
than
that,
and
if
you
think
carefully,
and
you
look
at
the
future,
you
can
imagine
that
the
data
is
flowing
from
one
place
to
another
over
and
over.
C
So
the
next
natural
step,
of
course,
is
to
keep
continue,
making
fluently
more
integrated
with
services
like
kaha
for
data
streaming,
so
the
strong
focus
with
fluidity
will
be
to
make
more
friendly
with
data
streaming
services
like
Kafka,
and
as
of
now
we
have
a
secure,
Kafka
connectors,
it's
very
secure.
We
have
it
support
Kerberos
and
all
that
things
that,
in
the
CAF,
Kasai
are
required
for
security.
Okay,
so
one
thing
is
its
locks.
They
always
connected
to
data
streaming,
but
also
when
you
think
about
how
your
systems
are
working.
C
You
would
like
to
have
some
notions
about
how
your
login
pipeline
on
this
case
flew.
Indeed
it's
working
internally
and
that's
why
our
investment
has
been
also
in
a
better
integration
with
primitives
and
we're
happy
to
announce
that,
with
all
this
coming
out
of
one
that
all
we
also
improving
our
monitoring
for
our
login
pipeline.
So
data
streaming
monitoring,
but
also
cross-platform,
is
really
important.
C
That's
why
I
flew
in
d1
that
o
has
been
ported
to
Windows
systems
and
converse
reliable
for
your
windows
services,
and
you
can
imagine
for
the
beginning
that
this
does
not
sound
too
natural.
But
there
are
many
windows
services
running
around
and
also
they
have
the
same
problem.
They
have
a
lot
of
three
panes,
a
lot
of
log
messages
from
different
applications
and
they
need
to
centralize
these
partes
information
and
ship
this
out.
So
that's
why
fluently
on
Windows
also
is
a
huge
wind
for
everybody
this
year
and
some
community
stats.
C
C
All
of
the
other
plugins
are
made
by
individuals
and
companies
to
solve
different
integration,
and
when
a
set
planes
I
mean
a
plug-in
is
used
to
call
it
information
from
an
input
to
apply
a
special
filter
or
a
custom
parser,
or
send
this
information
to
a
custom
output
or
destination,
and
in
our
official
repository
there
are
many
repositories
for
fluently.
We
have
around
$50,000
pools
a
day
and
growing.
That
is
a
huge
number
and
in
the
last
month,
is
increasing
like
crazy
and
also
from
a
code
perspective.
C
We
have
more
than
hundreds
of
developers
who
has
contributed
this
year
and
from
an
ecosystem
project
or
service.
We
have
can
see
that
we
have
500
contributors,
so
I
would
say
that
flew
India
is
growing
a
lot,
and
that
means
it's
not
just
about
growing
also
is
about
solving
the
problem
better,
as
I
said
before,
I'm
happy
to
say
that
flew
Indy,
it's
becoming
an
industry
standard
for
logging,
and
it's
not
just
me
saying
this
illusion
is
the
companies
who
are
adopting
this
technology.
C
Ok,
fluently
is
a
project
we
have
plugins,
we
have
community,
but
also
I
would
like
to
say
that
flew
in
D
is
a
whole
ecosystem
and
a
spar,
tosai
ecosystem.
We
have
more
components,
and
always
we
are
looking
for
ok,
how
we
can
make
it
better,
how
we
can
improve
performance,
how
we
can
make
it
lightweight.
Sometimes
we
get
some
feedback
through
in
the
right
it
works,
but
sometimes
you
know
it's
consuming
a
lot
of
memory.
Okay,
sometimes
it's
improve
the
configuration,
but
in
the
earliest
scenarios
it's
okay.
C
There
are
critical
environments
that
generate
thousands
and
thousands
of
logs
and
messages
per
second,
so
how
we
can
make
it
better?
How
can
make
it
stable
so
unhappy
to
introduce
you
to
a
new
child
project
of
the
flu
in
the
ecosystem,
which
is
called
fluent
bib
fluent
bed
has
been
development
for
along
two
years.
It
started
as
a
lightweight
solution
to
forward
locks
to
flu.
C
Indeed,
but
it
brought
a
lot
of
traction
in
the
last
time
and
with
a
lot
of
traction,
I
mean
the
feedback
from
the
users
was,
please,
can
you
start
integrating
with
all
this
database?
Can,
oh,
can
I
use
a
influenza
B,
okay,
so
flu
in
bed
started
to
grow
and
also
behave
as
an
alternative
to
implement
the
same
login
pipeline.
C
Thus
does
not
mean
that
is
competed
with
flu
in
D,
but
has
a
different
focus
for
a
different
needs
and
full
impede
its
reading
in
C
language,
which
has
said
that
is
one
of
the
most
attractive
things
for
most
of
the
users
also
has
a
pluggable
architecture.
We
have
35
plugins.
So
if
we
have
C
developers
here,
you
can
start
contributing
your
plugins,
but
also
have
to
say
that
you
can
write
your
own
plug-in
golang.
C
That
is
a
really
really
good
thing,
so
we
have
some
community
members
running
their
own
goal
and
plugins
and
being
integrated
inside
flow
in
bed
and
firm.
It
also
is
fully
a
synchronous,
a
band
ribbon
and,
of
course
it
has
a
small
memory
footprint
that
is
part
of
the
core,
but
from
a
integration
with
all
services.
This
month
we
are
releasing,
and
next
wrists
videoed
are
13,
which
will
have
full
integration
with
Kafka
with
permit
use.
It
done
really
can
work
really
well
on
Cooper
minis
append
filters.
C
You
can
append
labels
metadata
and
all
that
kind
of
information
that
is
really
relevant
for
the
login
scenario.
So
the
road
map
is
the
symbol.
We
are
having
an
expression
and
for
the
next
year
we
want
to
focus
on
a
really
new
buffer
mechanism
and
that
buzz
filtering
for
everybody
and
if
you're
around
the
conference,
I
will
like
to
invite
you
to
participate
and
get
with
the
flow
in
the
community.
We
have
the
flu
in
this
alum.
Today
we
have
the
whole
flu.
Indeed,
most
of
the
court
developers
are
here.
C
A
They
make
a
request
in
a
distributed
system.
Tracing
can
help.
You
understand
the
journey
of
that
transaction.
The
open
tracing
project
consists
of
vendor-neutral
a
vendor-neutral,
open
standard
and
instrumentation
for
distributed
tracing,
making
it
easier
to
integrate
within
your
projects
and
without
having
to
be
locked
into
a
specific
tracing
vendor.
A
The
opens
tracing
tracing
project
consists
of
a
language
api's
that
implement
the
distributed
tracing
standard
standard.
The
project
recently
added
four
new
language
api
is
bringing
the
total
number
to
nine.
This
team
has
also
been
working
on
engine
access,
tio,
envoy
and
link
D
integration.
Open
tracing
has
a
vibrant
ecosystem
as
well
check
out
these
stats.
A
Jaeger
is
a
distributed.
Tracing
system
that
implements
the
open
tracing
API.
You
can
use
Jaeger
to
trace
a
single
transaction
throughout
your
architecture
and
visualize.
It
Jaeger
was
originally
built
by
the
engineering
team
at
uber
and
this
project
projects
team
members
have
been
working
on
UI
improvements,
usability
improvements
for
viewing
large
traces.
It
also
supports
multiple
backends,
like
Cassandra
and
elasticsearch,
and
has
several
new
client
or
several
client
libraries
with
C++,
the
one
being
the
newest
and
they're,
currently
working
on
integration
with
other
CN
CF
projects.
A
So
we
talked
about
all
the
container
vents
which
allow
you
to
run
lots
of
different
services
in
a
portable
fashion,
and
then
we
talked
about
how
you
observe
what's
going
on
with
all
of
those
services,
but
the
whole
goal
is
for
your
system
to
act
reliably
in
the
first
place
in
the
world
of
complex
topology
of
services.
The
this
concept
of
a
service
mesh
has
become
increasingly
important
to
ensure
reliable
communication
between
services.
A
D
Thank
You
Connor
cloud
native
Connor,
yes,
Oh,
how's,
everyone
doing
ok
before
I
talk
about
linker,
D
I,
know
a
lot
of
you
have
laptops
out,
and
phones
and
you're,
not
really
listening
to
me.
So
I
want
to
ask
you
to
go
to
emoji,
Votto
and
just
vote
on
your
favorite
emojis.
Throughout
my
talk.
Hopefully,
you'll
do
a
really
cool
app
demo
in
about
a
minute
we'll
see.
D
So
the
last
six
months
since
I
last
spoke
to
you
in
Berlin,
the
linker
D
team
has
been
exceedingly
busy.
We've
done
a
release
about
every
two
weeks,
but,
more
importantly
than
alinker
D
team.
You
folks
have
been
really
really
busy
you're
adopting
link
to
link
OD,
you're
testing
it
out
you're,
bringing
in
a
production,
you're
writing
really
good
issues
and
PRS
that
that
are
get
to
the
heart
of
the
things
and
are
helping
us
learn
a
lot
about
the
service
machine
ecosystem.
D
Most
importantly,
a
lot
of
you
have
shared
the
challenges
working
with
linker
team,
given
really
asana
stand.
Constructive
feedback
and
you've
told
us
about
the
challenges
that
your
organizations
and
teams
face
and
moving
to
new
technology
systems,
and
so
I
know
it's
a
scary
new
world
of
new
technology.
But
I
really
do
appreciate
that
a
lot.
Many
of
you
have
been
so
open
and
sharing
your
problems
and
challenges
with
us
and
that's
led
us
to
think
a
lot
about
the
service
mesh
and
linker
DS
place
in
it
and
the
future
of
the
service
mesh.
D
Now
that
we
have
this
word
that
is
and
talking
with
many
of
our
customers
and
users
that
we've
kind
of
come
on
something
new
and
now
I'm
really
happy
to
introduce
a
new
project
called
conduit.
It
is
not
related
to
delink
or
D
explicitly
except
many
of
the
people
who
worked
on
linker
D
and
have
been
supporting
Lickety
for
years.
Also
worked
on
conduit.
D
So,
let's
see
if
this
demo
actually
works
all
right,
so
hopefully
you've
seen
this
page
at
this
point.
If
you
have
a
computer
out
and
you
played
with
it,
I
would
bet
that
if
you've
clicked
around
enough,
you've
probably
found
some
problems.
It
doesn't
quite
work
perfectly
because
of
software,
and
so,
if
we
look
at
kubernetes,
we'll
see
that
we've
got
this
service
running
in
kubernetes
says
everything's
running
it's
healthy.
It's
green,
wonderful,
but
we
still
these
problems.
D
They
I
can't
know
about,
and
so
I'm
going
to
show
you
how
easy
it
is
to
use
conduit
to
figure
this
out.
First
things:
first
I'm
just
going
to
install
conduit
I'm,
not
touching
the
running
system.
This
is
running
into
its
own
namespace.
Totally
aside
totally
separate
you
can
see
we
did
install
prometheus
as
part
of
that
and
that'll
start
over
the
next
few
seconds.
D
We
can
look
and
see
it's
running
just
a
small
little
cluster
there,
and
so
the
magic
really
happens
is
when
we
add
our
our
new
sidecar,
our
conduits
sidebar,
into
the
running
app.
While
it's
running
and
while
you're
clicking
on
it-
and
hopefully
nothing
goes
down-
that's
the
trick.
Okay,
here
we
go
boom
and
we
redeploy
your
app
while
you're
clicking
on
it
and
now
there's
a
sidecar
running
dealing
with
all
of
the
inter-service
communication
and
I
just
want
to
start
yet
getting
some
information
about.
D
What's
going
on
in
the
system
and
so
I'm
gonna
do
this
watch
command
and
hopefully,
as
the
plus
two
rolls
and
as
you
click
around
we're
gonna
start
to
see
some
things
here.
I
can't
force
that
to
happen.
This
could
be
a
Wi-Fi
issue.
Of
course.
Oh
there
we
go
and
we
see
something.
Staying
out.
Most
of
the
things
are
under
missus
rate.
One
of
them
is
at
zero,
that's
bad!
D
What
is
going
on
so
we
see
we
request
rates
and
we
see
latency
is
latency-
is
quite
low
I'm
below
what
can
we
do
to
find
out
more
about
about
this
failing
endpoint,
and
so
what
I
think
is?
Maybe
the
coolest
part
of
conduit
or
really
makes
me
happy?
Is
this
tap
command
and
what
tap
does?
Is
it
sends
this
query?
I,
say
I'm
going
to
look
at
this
one
method.
It
sends
this
query
into
all
the
proxies
as
they're
running
and
fetches
it
out
and
puts
them
right
on
my
CLI
for
you.
D
If
the
wireless
works,
oh
look
immediately.
Thank
you.
Yeah.
We
see,
we
have
failures.
These
are
G
RPC
failures.
We
see
a
200
status
code,
so
most
things
would
say
this
is
fine,
but
we
see
a
G
RPC
status
of
unknown.
We
have
found
the
problem,
and
this
is
all
running-
live
just
bullet,
pointing
an
RPC
into
the
proxy
and
pulling
data
abot.
It's
beautiful
so
that
must
you
know
most
of
you
link
to
you
sue
say
what
better
buck
be,
at
least
a
100
Meg's.
To
do
that
right!
No
we've
got
much
better
here.
D
D
So
conduit
does
not
replace
link
ready,
link.
Rd
is
supported.
We're
gonna
continue
to
make
it
better
make
it
work
for
everyone.
Kannada
is
a
new
kind
of
clean
break
for
us
to
really
focus
on
the
lightweight
zero
configuration
aspects
of
what
we
think
a
service
mesh
should
be
we're
gonna
be
talking
about
a
bunch
of
the
conference.
We
have
a
boost
supply
booth
over
in
a
sponsor
area.
There's
a
panel,
my
co-founder
Williams
on
right
after
this
and
I'll
be
doing
a
null
link.
D
A
Thanks
Oliver
all
right:
let's
talk
about
envoy,
the
network
is
inherently
unreliable.
This
problem
gets
even
worse
and
more
painful
and
a
complex
system
of
distributed
services
envoy
is
an
edge
and
service
proxy
that
makes
the
network
transparent
to
applications.
It
runs
alongside
out
an
application
and
abstracts
the
network
by
providing
some
common
features
in
a
platform
and
language
agnostic
manner
on
ways.
A
One
boy
was
originally
built
at
lyft
and
ended
up
being
deployed
as
an
edge
proxy
and
then
as
a
sidecar
service
of
service
proxy
forming
a
mesh
over
hundreds
of
services
of
at
lyft
transitioning,
millions
of
requests
per
second.
When
all
service
traffic
goes
through
a
mesh
like
this,
it
becomes
much
easier
to
visual
visualize.
The
problem
areas
tune
performance
and
ensure
that
your
services
are
communicating
for
lively
envoy
is
at
a
1.5
over
lease
today
with
a
G
RPC
v2
API
now
production-ready
envoy
is
also
experiencing
amazing
community
growth.
A
Er
PC
is
an
open-source
RPC
framework
released
by
Google
in
G
RPC.
A
client
application
can
directly
commute
call
methods
on
a
server
application
on
a
different
machine.
As
if
it
were
a
local
object,
making
it
easier
to
create
distributed
applications
and
services,
google
has
benefited
from
having
something
alike:
G
RPC
internally,
something
like
a
uniform
across
platform,
RPC
infrastructure
that
has
allowed
them
to
roll
out
fleet
wide
improvements
in
efficiency,
security,
reliability
and
behavior
analysis.
A
key
for
supporting
the
type
of
growth
that
Google
has
experienced.
A
The
team
is
currently
working
to
support
more
languages
and
improving
connectivity
and
performance.
The
community
release
cadence
is
really
strong
and
there's
several
sessions
on
G
RPC
today,
if
you're
interested
in
learning
more
so
so
far,
we've
talked
about
projects
that
enable
you
to
run
containers
in
your
cloud
native
environment.
We've
talked
about
how
to
observe.
What's
going
on
with
these
cloud
native
applications,
and
then
we
talked
about
ensuring
reliability
with
your
services.
This
last
one
is
important
because
nobody
likes
to
be
stuck
not
even
your
micro
services.
A
Last
but
not
least,
let's
talk
about
two
projects:
news
to
the
CNCs
in
the
realm
of
security.
One
problem
with
the
internet
is
that,
like
everyone's
trying
to
lie
to
you-
and
this
gets
even
more
terrifying
when
you're
trying
to
update
your
software
I,
don't
know
if
you've
noticed
lately.
I
tough
is
a
software
update,
spec
perfect
for
people
who
are
paranoid.
It
expects
that
attackers
will
compromise
servers,
keys
and
anything
that
they
can
get
their
hands
on.
The
goal
is
to
retain
as
much
security
as
possible.
A
A
Notary
is
an
example
of
a
project
that
has
adopted.
Tough
notary
can
be
added
to
any
digital
distribution
system
to
ensure
the
secure
download
of
packages,
and
we
look
forward
to
a
0.6
release
from
them
very
soon.
The
docker
platform,
the
mobi
project,
Motorola
Solutions,
VMware,
Linux,
kit,
Kwai
and
kubernetes-
are
all
using
notary
and
tough
I'll
just
end
with
it's
super
important
for
us
as
a
community
to
provide
a
solution
for
trusted.
Cross-Platform
delivery
of
content
to
ensure
no
bad
blood
at
the
end
of
the
day.
A
A
A
lot
of
these
projects
that
are
coming
up
have
been
around
because
people
have
been
experiencing
all
these
problems
in
a
cloud
native
environment,
but
they
just
you
know,
we're
coming
together,
we're
learning
from
each
other
we're
sharing
problems
and
solutions
and
yeah
it's
cheesy,
but
it's
really
cool
and-
and
so
I'm
really
excited
to
have
all
of
you
here
today.
Your
first
cloud
native
gun
and
coop
con
conference
and
next
up.