►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Everyone
to
cloud
native
live
where
we
dive
into
the
code
behind
cloud
native,
I'm
taylor
dolezal,
head
of
ecosystem
at
the
cncf,
where
I
work
closely
with
end
users
as
they
navigate
their
cloud
native
journeys.
Every
week
we
bring
a
new
set
of
presenters
to
showcase
how
to
work
with
cloud
native
technologies.
A
They
will
build
things,
they
will
break
things
and
they
will
answer
your
questions.
In
today's
session.
Jason
morgan
has
joined
us
to
talk
about
surface
mesh
in
production
101
with
linker
d.
This
is
an
official
live
stream
of
the
cncf
and,
as
such
is
subject
to
the
cncf
code
of
conduct.
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
the
code
of
conduct.
Basically,
please
be
respectful
to
one
to
all
of
your
fellow
participants
and
presenters
and
with
that
I'd
love
to
kick
it
over
to
jason.
B
A
A
B
Here
this
guy,
you
can
find
me
on
twitter
github,
not,
but
I
can
see
any
reason.
You'd
want
to
find
me
on
github
or
on
the
linkedin
slack,
as
at
jason
and
probably
on
the
cncfs
like
so
all
right.
That's
that's
it
for
slides.
What
I
want
to
what
we're
going
to
talk
talking
about
today
is
how
to
run
linkedin
production.
B
So
the
first
thing,
if
you're
out
there
we're
going
to
we're
going
to
get
post
in
the
chat
is
buoyant
the
company
I
work
for
the
people
that
make
linker
d,
publish
a
run
book
of
how
to
how
to
do
linkedin,
prod
right,
like
we
do
a
couple
things
that
are
are
pretty
important.
Specifically
right.
We
talk
about
things
you
need
to
be
aware
of
before
you
deploy
potential
gotchas
and
things
to
check
on,
and
that's
essentially,
what
today
is
going
to
be
about
sound.
A
B
That's
works,
hi,
munch,
all
right,
so
should
we
agree?
Oh
one
other
thing
a
great,
a
great
thing
to
check
out.
If
you
like
this
stream,
we
also
have
a.
We
also
have
a.
This
is
based
off
a
webinar
that
one
of
my
colleagues,
charles
pretzel,
did
that's
a
recorded
service,
mesh
academy
presentation
and
let
me
just
open
that
up
nope
wrong.
Sorry,
totally
wrong
thing:
service
mission
academy:
there
we
go
this
thing,
this
thing:
liquidity
in
production.
B
B
So,
let's
start
when
you
or
what
this
is
right,
we
are
we're
not
going
to
do
an
introduction
to
linkedin
or
an
introduction
to
what
service
mesh
is
right,
I'll
I'll
I'll
give
you
a
quick
overview,
because
I
feel,
like
that's
useful,
every
single
time
I
do
it.
A
service
mesh
is
kind
of
a
a
weird
name
for
a
network
of
a
bunch
of
little
load,
balancers
that
sit
between
your
applications
and
do
stuff
with
your
application
traffic,
so
they
intercept
and
then
and
then
use
your
your
application
traffic
to
do
stuff.
B
Typically,
that
stuff
is
adding
some
security
by
encrypting
the
traffic
and
identifying
the
various
parties.
In
the
conversation
it
adds
it
makes
it
a
little
bit
easier
to
monitor
by
adding
some
standard
observability
where
you
can
see
things
like
success
rate
saturation
latency
for
your
applications
and
then
it
can.
It
can
improve
on
the
reliability
of
your
service
to
service
communication.
B
So
that's
that's
the
very
fast
service
mesh
definition
and
that's
as
far
as
I'm
going
into
that.
This
is
also
not
going
to
be
like
a
super
deep
dive
into.
How
do
I
do
certificate
rotation
or
you
know,
even
how
do
I
do
monitoring
I'm
going
to
tell
you
a
little
bit
right?
But
if
you
want
to
learn
more
about
debugging
monitoring,
anything
like
that
go
check
out
that
service
mesh
academy
link
the
resolution.
Oh
yeah.
B
Sorry,
john
john
jonathan,
is
this
a
little
bit
better,
hopefully
and
I'll
make
all
of
them
a
little
bit
bigger.
So
if
you
check
out
the
whole
service
mesh
academy,
link
you'll
see
all
like
the
buoyant.
You
know
buoyant
webinars,
right
and
of
course,
you'll
have
there's
linguity
101
on
this
channel
too
yeah,
and
so
so
that's
the
start.
So
before
we
do.
B
Right,
let's
talk
about,
let's
talk
about
what
like
what
do
you
need
to
do
before
you
go
to
production
and,
like
I'm,
a
huge
fan
of
checklists?
I
just
think
it
helps
me
not
forget
things
that
I
shouldn't
forget
right.
Fonts
are
not
super
clear.
I
can't
do
anything
about
the
font
but
I'll
take
that
to
feedback
to
the
people
that
do
the
website
because
yeah,
I
guess
I
don't
know
a
ton
about
fonts.
Sorry.
B
Shell
script
code
so
yeah,
I
think
a
checklist
is
really
handy.
The
production
runbook
here
has
a
bit
of
a
checklist
built
into
it.
The
things
I
would
tell
you
is
one
first
off
look
at
this
runbook
before
you
go
to
prod
with
with
linkerd
and
look
at
a
runbook
for
your
for
your
thing.
Whatever
your
product
is
before
you
go
to
production
right
or
build
one
yourself.
If
there
isn't
one
that
already
exists,
two
linkery,
let's
just
take
check
out
linker
d
and
the
link
install
command.
B
So
if
I
do
the
linker
d
cli,
it's
got
this
install
install
mode,
and
if
I
look
at
help
it's
got
some,
it's
got
some
flags.
I
can
set
right
a
bunch
of
stuff
to
say
here
about
the
flags,
but
an
important
one
is
linker
d.
Has
a
h
a
mode
for
installing
this
doesn't
go
by
default.
B
It
forces
you
to
have
at
least
three
nodes
in
a
cluster.
If
you
want
to
install
link
or
dnha
mode,
because
linker
ds,
linkery's
mode,
splits,
the
control
plane
components
into
three
replicas
instead
of
just
one
right
and
those
replicas
have
anti-affinity
rules
on
them.
So
they
can't
run
on
the
same
node
right
so
like
the
bare
minimum
you
want
to
do
if
you're
running
liquor,
d
in
production
is
have
three
replicas
and
have
them
not
on
the
same
node.
B
So
if
one
node
goes
down
you
can
you
know
you
can
recover
right,
the
other
thing
aj
mode
does
that
is
awesome.
Is
it
will
enforce
a
policy
that
your
pods
can't
start
if
the
lingerie
proxy
injector
isn't
running
right?
So,
let's,
let's
talk
about
why
that
is
just
real,
quick
right
if
you're
using
a
service
mesh,
because
mtls
is
important
or
required
for
your
environment.
B
B
Requirement,
you
don't
want
your
pod
to
start
if
it's
not
getting
a
proxy
injected
with
it
right,
so
the
atm
mode
will
will
say:
hey
pods,
you
can't
start
if
you
can't
start
if
the,
if
the,
if
the
lingerie
proxy
injector
isn't
working
sounds
sounds
nice
right,
but
maybe
maybe
you
see
like
where
this
might
be
a
problem
right.
B
So
if
you,
if
you
when
you
install
with
mode,
you
want
to
be
sure
that
you
annotate
cube
system
and
you
annotate
like
these,
like
infrastructure,
specific
name
spaces
with
a
little
a
little
note-
and
I
forget
what
that
is,
but
that's
why
I
have
my
slides
here:
let's
go
aha
mode:
there
we
go
this
little
little
annotation
you
can
put
in
and
I'll
try
and
get
that
sent
to
the
chat.
B
Oh
yeah,
sorry,
here's
a
use
it
in
slideshow
mode
right.
This
hold
on
I've,
got
a
little
laser
pointer,
come
on
buddy!
Please
work!
No,
it's
not
gonna.
Do
it
anyway
got
a
little
annotation,
we'll
put
in
the
chat?
Oh
great.
That
basically
tells
tells
the
namespace.
B
Oh
thomas
rucker
is
asking:
if
this
is
the
cncf,
finland
event
live
stream.
It
is
not.
I
don't
think
taylor
doing
that.
A
Yeah,
it
is
not,
but
I
could
definitely
check
on
that
and
get
you
some
info,
thomas
yeah,
sorry
you're
in
the
wrong
classroom.
B
All
right
so
anyway,
quick
quick
bit
about
aha
mode,
be
sure
that
you've
got
the
the
right
thing
installed.
The
other
thing,
I
would
say
is
if
you're,
installing
blinker
d
and
you're
going
to
production
right,
consider
using
helm
and
not
the
linker
d
install
right,
so
lingua
dcl
is
great
right.
It's
handy!
A
B
You
know
say
what
you
want
about
it
right,
but
in
general
like
it,
it
puts
you
into
a
bit
more
of
an
imperative
mode
right.
I
am
saying:
hey
cluster
go.
Do
this
that
or
the
other
things?
Oh
thanks
gerald,
so
gerald
just
posted
the
link
to
the
to
the
linkedin
runbooks.
Thank
you
for
that,
but
it
kind
of
gets
you
in
this
like
telling
the
cluster.
B
What
to
do
right,
like
in
in
an
imperative
fashion,
where
what
you
really
want
to
be
doing
is
something
like
helm
to
do
it
in
a
bit
more
of
a
declarative
way,
and
I
guess
it's
not
really
imperative,
but
it
it
feels
more.
More
of
that
method,
and-
and
I'll
tell
you
like-
I
see
most
people
that
are
are
successful
with
lingerie
and
prod
using
helm,
and
we
recommend
it
oh
and
store
your
configs.
B
Take
your
values
file
and
all
your
overrides
that
you
use
for
the
helm,
chart
and
store
that
in
version
control
like
this
is.
This
is
a
heavy
ask
for
all
your
there.
Please
store
store
your
configs
and
all
your
values
in
version
control
like
it's
crazy
clutch,
and
if
you
lose
that,
like
you,
find
yourself
in
a
in
a
bad
spot,
the
other
one
I'd
say
is
use
your
own
use.
B
B
Right,
we're
gonna
see
a
bunch
of
stuff,
but
this
this
url
is
the
path
to
our
image
and
it's
using
an
internet-based
registry.
Oh
hey
son,
great,
to
see
you
it's
using
an
internet-based
registry
that,
like
might.
B
It
might
not
be
available
right
run
your
own
registry.
If
you
want
stuff
to
be
highly
available,
it's
a
great
call
it.
You
know,
there's
a
ton
of
great
open
source
registries,
I'm
wearing
my
my
vmware
shirt
today.
You
know
check
out
harbor.
It's
awesome,
there's
a
bunch
of
other
great
ones
too,
like
I'm
not
telling
you
harper's
better
than
your
other
registry,
but
it's.
B
B
Let's
get
this:
let's
get
this
going,
I
got
a
production,
deploy
that's
held
up
right,
you
get
you
get
all
that
get
all
that
accountability
internally
after
after
the
registry
write
a
couple
things
that
you
want
to
plan
for
right,
like
liquidity,
is
good
and
it's
stable
in
general,
people
find
that
it
just
works
right,
which
is
just
really
good
right.
B
It's
a
it's
a
good,
it's
a
pretty
good
thing
to
say
about
the
project
right,
but,
like
the
end
of
the
day,
nothing
always
just
works
right,
like
you
have
to
monitor
an
alert
on
your
link
or
the
environment.
You
have
to
know
what
you're
going
to
do
for
that
right.
I'm
making
sense
so
far,
taylor
is
it's
all
resonating
with
you
right
like
it's.
B
It's
kind
of
it's
kind
of
simple
advice
and
we'll
we'll
do
a
bit
more
in
in
demos
in
a
minute,
but
I
just
want
to
make
sure
that
y'all
are
thinking
about
this
right
before
you
go
so
plan.
Make
a
plan
for
monitoring
and
alerting
that
run
book
will
will
help
you
think
about
it.
You
know
there's
well
I'll
dive
into
a
whole
section
on
monitoring,
alerting
in
a
bit.
B
Also
you
want
to
get
you
don't
need
to
become
deep,
lingerie
experts
right,
like
one
of
the
things
that
we
like,
or
we
say
positively
about
lingerie-
is
that
you
don't
need
to
develop
deep,
lingerie
expertise.
But
how
do
I
know
if
linkery
is
healthy
on
a
class
there?
Well,
I
know
enough
to
just
go
in
here
and
run
liberty
check
right,
and
it's
going
to
tell
me
what
the
current
state
of
my
environment
is
right,
but
you
need
to
know
you
need
to
know
how
liquidy
works.
B
I
I
just
want
to
dive
into
quick,
really
quick,
and
this
might
be
good
for
a
a
little
white
board.
B
Well,
yeah,
it's!
It
was
fully
charged
yesterday,
but
all
right
yeah,
I'm
going
to
give
up.
So
here
I've
got
like
a
like
what
what's
a
fictional
kubernetes
class
there.
I
have
an
ingress,
a
bunch
of
proxies,
so
these
proxies
are
the
data
plane
and
together
the
data
plane
and
the
control
plane,
make
up
your
service
mesh
right
and
we're
going
to
need
for
all
these
things.
There
are
three
tiers
of
certificates.
B
There
is
a
root
certificate
which
isn't
ever
going
to
be
in
the
cluster
right,
but
is
the
is
the
source
of
the
trust
that
everything
else
everything
else
uses
that
when
you
install
link
or
d,
especially
when
you
install
it
with
the
helm,
chart
you're
going
to
be
forced
to
generate
an
intermediate
ca,
so
a
certificate
authority
that
you'll
give
to
the
control
plane
and
that
the
control
plane
will
use
to
create
and
rotate
the
certificates
for
your
workloads.
And
then
every
workload
is
going
to
get
its
own
certificate
right.
B
That
will
be
generated
by
the
control
plane
and
used
to
use
to
positively
identify
that
workload
right
and
if
you
watch
some
of
the
linkedin
overviews
we'll
talk
about
what
these
certificates
are
and
a
bit
more
about
how
they
work.
But
but
you
need
to
have
a
sense
of
what
certificates
are
involved.
What
you're
going
to
use
for
your
root
ca?
Are
you
going
to
generate
your
own?
Are
you
going
to
use
the
corporate
ca
that
you've
got?
You
know
in
your
environment
or
are
you
going
to?
Are
you
going
to
build
one?
B
B
B
Sorry,
my
my
amazon
spy
device
was
talking
to
me.
Okay,
so
certificates
figure
out
what
you're
doing
great
tool
to
create
man
gerald.
You
are
like
hitting
it
up.
Man.
Thank
you
so
much
for
this,
this
feedback
all
right,
so
you
need
you
need
a
plan
for
certificates
and
then
have
a
plan
for
how
are
you
going
to
rotate
certificates
in
your
environment,
specifically
this
intermediate
certificate.
B
B
It's
super
handy,
it's
worth
using
it'll
work
with
whatever
other
certificate
authority.
You
have
well
not
whatever
it'll
work
with
a
lot
of
certificate
authorities.
It
makes
it
pretty
straightforward
to
programmatically,
generate
generate
the
the
intermediary
certificate
and
then,
of
course,
plan
out
the
integration
with
your
your
certificate
authority,
quick
check
in
making
sense
so
far.
B
That's
most
of
what
I'm
gonna
say
about
certificates,
so
folks
like
if
this.
If
this
is
like
a
topic
where
you're
you're
wishing
for
way
more
depth
check
out,
I
I
don't
think
you
do
gerald,
that's
been
fantastic
and
if
you're,
if
you
want
a
deeper
dive
in
this,
go
check
out
that
service
mesh
academy
link
that
you
saw
earlier
we'll.
A
B
That
we'll
talk
about
linker
d
and
certificate
authorities
and
there's
talk
in
there
either
that
exists
now
or
that
we're
getting
ready
to
do
fairly
soon
in
a
deep
dive
in
a
certificate
management
with
lingerie
and
also
check
out
the
production
run
books
we'll
talk
about
it
all
right.
So
that's
that's
certificates,
quick
talk
about
aj
mode
right!
This
control
plane
here
is
really
it's
really
like
a
couple
different
components,
but
when
you
install
something
in
a
ta
mode,
we
make
multiple
replicas.
B
Okay,
I
can't
have
complete
that
so
I'm
now
in
the
liquidity
name
space,
you
can
take
a
look
at
our
pods,
where
we
can
see
that
I've
got
three
copies
of
each
of
my
components.
I
also
have
resource
requests
and
limits
set
for
all
these
things
that
are
fairly
reasonable,
but
but
they
may
not
be
they're,
not
gonna
they're,
not
gonna
work
for
every
single
environment
right.
So
one
thing
I'd
ask
you
to
do
is
set
up
monitoring.
B
Look
at
your
environment
test
out
test
out
the
things
that
you
do
before
you
make
changes
to
your
production
cluster
and
see:
do
you
have
do
you
have
the
resource
requests
and
resource
limits
that
work
for
your
application?
Are
you
seeing
pods
get
killed
right
like
if
you
are
like
like
do
something
about
it
right
and
speaking
of
which
we're
gonna
talk
about
debugging
like
right
after
monitoring,
I'm
going
to
show
you
a
little
bit
of
how
we're
going
to
use
the
cli
to
to
plug
in
still.
B
A
Yeah,
please
let
us
know
if
you
have
any
questions,
just
feel
free
to
throw
them
in
the
chat
we'll
get
them
asked.
If,
if
jason
doesn't
see
it
I'll
be
sure
to
raise
it
up
to
him
as
well.
B
Cool
thanks
and
yeah.
You
interrupt
me
too
taylor.
If
anything,
if
there's
anything
you
want
to,
you
want
me
to
double
tap
on
absolutely
going
back,
be
sure
that
you
set
that
annotation
at
a
minimum
on
your
cube
system
namespace
to
allow
pods
in
that
namespace
to
start,
even
if
this
proxy
injector
isn't
working
right.
So
there's
a
rule
now
in
place
because
we
installed
it
in
mode.
There's
a
rule
that
says:
don't
let
a
pod
start
if
this
isn't
running
right
but
like
if
this
service.
B
All
right,
I'm
looking,
so
we
have
a
question
from
guyanaraj
and
I'm
sorry
I
can't
explain,
k
native
yeah
but
happy
to
you
know.
If
anyone
wants
to
see
k-native
and
liquidy
at
some
point,
we
could
also
do
a
live
stream
on
that
anyway.
This
this
thing
relies
on
the
cube
system.
If
cube
system
won't
start
without
it
and
it
won't
start
with,
it
won't
start
with
a
cube
system.
You
get
into
a
vicious
cycle.
B
Oh
man,
we're
getting
amazing
questions.
So,
let's,
let's
hop
in
gan,
raj,
again
linkery
and
seo
you
typically
are
using
one
or
the
other
right
like
they're
you're,
not
you're,
like
they're
they're,
competing
products
right
so
they're.
You
know
in
general,
you
do
you'd
use
one
or
the
other
I'll
tell
you
to
use
linkedin,
but
I
work
for
points.
So
that's
my
job
right
but
like
istio
is
also
a
great
tool.
Depending
on
your
use
case.
B
Shell
script
code
wants
to
know
how
proxy
container
injection
work
and
how
cube
ctl
applied
to
text
as
a
chain.
Yeah
awesome,
amazing
question
right.
So
the
way
proxy
injection
works
is,
is
we
just
send
an
annotation?
So
we
presentation?
B
You
could
set
it
on
one
of
three
levels
you
can
set
it
on
the
namespace.
You
can
set
it
on
the
actual
workload
object.
So
when
I
say
workload
I
mean
deployment
deployment,
stateful
set
or
daemon
set.
I
think
those
are
the
workloads
that
I
can
think
of.
So
you
set
an
annotation
inside
the
specification
that
says:
hey.
B
Please
inject
this
workload
with
the
linker
d
proxy
and
you
set
any
any
rules
on
it
that
you
that
you
need
like
you
could
tell
to
like
skip
certain
ports
or
treat
certain
ports
in
a
special
way
like
whatever
you
want
to
do,
but
the
annotation
or
the
annotation
is
the
way
that
you
set
up
injection.
B
B
The
on
the
workload
right
when
you
put
it
on
the
namespace
when
you
put
the
namespace
level
once
it
won't
take
effect
until
the
pod
gets
restarted,
for
whatever
reason
right.
So
if
you
want
to
annotate
namespace
go
in,
in
fact,
I
think
I've
got
emoji
photo
set.
Let's,
let's
just
do
this
k
get
pods
dash
a
oh
emoji
photo's
already
injected.
B
Okay,
well
less
good,
but
I
could
set
it
on
the
namespace.
So,
let's
actually
just
well,
I'm
not
gonna!
Do
it
now,
because
I
I'd
have
to
like
look
stuff
up
and
that
would
be
annoying,
but
you
can
set
on
the
names
level
and
just
do
a
cube.
Ctl
rollout,
restart
on
the
on
the
namespace
and
everything
will
pick
up
the
proxy
and
I
think
that's
all
your
question
shell
script.
But
please
let
me
know
if
that,
if
that
works.
B
M
mr
feed,
mr
feed,
I
think
sorry,
if
I
said
your
name
wrong
is
the
viz
component.
Normally
in
solid
production
environments,
oh
man,
that's
a
great
great
question.
I'm
just
going
to
park
that
because
I'm
like
I'm
just
about
to
go
into
it
short
answer
is
yes,
it
is
commonly
installed,
but
it's
not
commonly
installed
with
just
the
vanilla
insulation
and
I'll
I'll
dive
right
into
that
thomas
rucker
ruker.
B
Ken
raj,
like
is
asking
some
interesting
questions
in
here.
I
I
love
it
man.
Thank
you
so
thomas
ruker,
I
I
hope
I
said
that
right
while
I'm
here
would
anyone
happen
to
know
when
the
non-kate
slinkerty,
oh.
A
B
Yeah
man
like
so
I
can.
I
can
actually
answer
that.
Well,
I
can
answer
that
as
well
as
anyone
can
publicly
answer
that,
because
it's
not
like
we
don't,
we
don't
know
exactly
when
linkedin
is
going
to
start
supporting
non-kubernetes
workload,
but
the
current
tentative
plan
is
that
the
2
13
release
are
somewhere
around
the
213
release
of
linker
d.
We
should
include
the
ability
to
run
linker
d
outside
of
kubernetes
cluster
and
there's
a
ton
more.
I
can
say
about
that
and
please
feel
free
to,
please
feel
free
to
connect
with
me.
B
I'm
on
twitter,
I'm
in
the
cncf
slack
the
link,
ready
slack
and
I'm
happy
to
give
you
way
more
details
on
that.
If
you're
interested
I'm
not
going
to
answer
any
of
the
issue,
questions.
B
B
Oh
shell,
swift
code
asks
if
they
can
hard
code
the
proxy
container
in
the
deployment.
Probably,
but
don't
like
don't
do
that
right,
like
you,
want
the
proxy
injector
to
do
its
work
right
like
it's.
It's
specifically
going
in,
and
you
know
it's
a
mutating
web
hook
right.
B
B
So
it's
something
that
you
could
do,
but
I
would
I
would
recommend
against
right
and
if
you,
if
you
were
to
ask
the
community
for
help-
and
you
were
doing
that
like
the
first
thing,
people
would
say
would
be
like
get
that
stuff
out
of
there
and
then
try
again
right
so
you're
you'd
be
setting
yourself
up
for
failure
all
right.
So
going
back
and
and
requests.
B
Someone
asked
the
great
question
that
I'm
I'm
gonna
get
to.
I
promise,
oh,
mr
mr
feed,
so
let's
hop
into
your
stuff
now
so
monitoring,
linkery.
B
Monitoring
monitoring,
linker
d,
it's
something
you
need
to
plan
for.
So
if
you
look
at
linkedin,
in
fact,
I've
got
a
live
link
or
dashboard
that
anyone,
if
you
feel
like
looking
at
it,
go
check
out
my
dashboard.
So
I
know
I
share
this
link
every
time.
B
I
do
one
of
these,
but
but
check
this
out
right
like
with
this
dashboard,
you
can
see
you
can
see
a
couple
things
right
like
I
can
see
the
state
of
my
cluster
from
the
perspective
liquidity-
and
this
is
the
linker
d,
dashboard
or
linker
d
viz
right.
It's
an
extension.
B
I
can
use
to
look
at
and
diagnose
my
my
my
lingerie
install
itself
right
and
like
you
can
see
that
here
right,
liquid
evas,
because
I'm
not
using
a
ta
load
on
my
cluster.
Some
of
the
pods
have
restarted
and
they
haven't
been
injected
right,
so
I
can
go.
Do
a
rollout
restart!
B
B
Okay,
so
I'm
just
gonna
go
ahead
and
well,
it's
probably
a
bad
idea
to
do
it
right
there
in
the
oaks,
I'm
in
the
wrong
cluster.
Sorry
k,
ctx,
get
ops,
a
roll
out,
restart
employee.
B
Yeah,
come
on
yeah,
so
we're
going
to
lose
this
we're
going
to
lose
this
dashboard
for
a
bit
right,
but
you
can
use
the
tooling
that
that
viz
component
to
look
at
your
own
linkedin
environments-
it's
actually
really
handy,
so
I
would
use
it
when
you
go
to
production,
but
you
need
more
than
just
just
lingerie
and
that
lingerie
viz
component
it
by
default
installs
an
in-memory,
prometheus
and
grafana
that
you
can
use
to
to
pull
up
metrics
right
in
the
if
you
if
you've
used
prometheus
in
production.
B
The
first
thing
you
should
think
is
wow
like
I
bet
an
in-memory
prometheus,
doesn't
last
for
very
long,
and
it
doesn't
right.
Like
you
can't
you
can't.
You
can't
rely
on
that
when
you
go
to
prod,
so
you
have
to
have
a
plan
for
what
are
you
going
to
do
for
collecting
the
prometheus
data?
From
from
the
proxies
right,
you
don't
need
to
have
linkudviz
installed
to
grab
the
data
from
the
proxies
with
with
prometheus
the
the
documentation
on
how
to
use
an
external
prometheus
is
out
there.
B
It's
public:
it's
it's
a
very
common
procedure,
but
just
make
sure
that
you've
you've
seen
that
and
again
go
back
to
that
lingerie
production
run
book.
It
will
talk
about
some
options
you
have
for
getting
that
data
out
and
and
some
good
patterns
then
go
beyond
that
right,
whether
or
not
you're
using
prometheus
and
grafanada
to
to
monitor
it
right
it.
It
might
be
wise,
depending
on
what
you
do,
for
monitoring
to
look
at
a
third
part
of
your
paid
tool
right,
there's
like
datadog,
there's
new
relic.
B
There
are
other
monitoring
tools,
feel
free
to
put
them
in
the
in
the
chat,
but
there's
there
there
are
tools
out
there
to
make
monitoring
easier.
Also,
the
company
I
work
for
buoyant
right.
We've
made
a
tool,
that's
a
paid
tool
that
you
can
use
to
you
know.
Do
a
lot,
do
a
lot
of
the
alerting
and
monitoring
around
linker
d
right
and
ultimately
it's
there
to
try
and
turn
it
into
a
bit
more
of
a
managed
service
for
you.
B
So
if
you
go
to
production,
you
can
also
do
less
of
this
checklist
and
just
pay
some
people
some
money.
But
that's
that's
kind
of
your
your
call
here,
but
no
matter
what
make
a
plan
for
storing
your
metrics
right,
like
like
all
this,
make
a
plan
before
you're
going
on
a
prod,
have
an
idea
of
what
you're
gonna
do
before
you
run
into
the
situation,
so
you're
not
scrambling
right,
like
linkery
or
any
service
mesh
right.
It
is
critical
path
for
your
applications.
B
B
On
the
hook
not
understand
how
do
you
address
this
that
or
the
other
failure
scenario
as
you're
losing
production
traffic,
like
that?
That's
painful,
so
plan
for
alerting
and
monitoring.
When
you
look
at
when
you
look
at
the
lingerie
control
plane
itself,
I
know
but
you're
you're
going
to
be
okay,
buddy
you'll
be
okay,
eventually,
sorry,
it's
taken
longer
to
come
up
than
it
off
to
anyway.
B
If
you
look
at
the
lingerie
dashboard
and
it's
healthy
you'll
see
the
success
rates
for
the
linkedin
control,
plane,
components
and
there's
no
reason
that
those
should
ever
go
some
of
y'all
try
to
get
me
in
trouble,
there's
no
reason
it
should
ever
go
below
100.
B
I
want
to
be
clear
to
everybody
on
the
call
right,
like
I
work
for
the
company
that
makes
liquor
d.
I
think
linkery
is
a
great
tool
and
I'm
going
to
say
positive
things
about
everything
everything
we
talk
about,
I'm
not
going
to
tell
you.
I
can
tell
you
one
another
I'd
say
if
you're
evaluating
service
meshes
try
some
different
options
right
and
consider
what
are
the?
What
are
the
things
that
you
care
about
for
the
mesh
and
and
evaluate
based
on
that
linker
to
use
fast?
It's
lightweight,
and
I
think
it's
absolutely
awesome.
B
Look
at
the
events
so
that
the
kubernetes
events
in
your
environment,
right
like
if
you're
seeing
control,
plane
components,
get
killed
so
out
of
memory
killed
right
like
you,
have
bad
resource
requests
and
limits
and
you're
gonna
need
to
you're
gonna
need
to
address
that
right
and
please
make
a
plan
to
monitor
your
certificates
right.
I
can't
tell
you
how
many
times
I've
seen
people
come
in
to
come
into
liquidity
slack
because
they've
had
it
they've
had
their
issuer
issue
or
certificate
expire
right.
B
Aren't
going
to
be
able
to
get
generated
and
that's
going
to
be
a
big
problem,
because
people
aren't
your
components,
aren't
going
to
trust
each
other
anymore.
So
watch
your
shirts
and
again
point
cloud
automatically
watches
your
shirts
for
you
and
is
really
aggressive
about
about
notifying
you.
B
All
right,
quick,
hop
over
to
questions.
Sorry,
I'm
I'm
not
sure
how
I'm
gonna
say
your
name
there,
if
you're
using
linkedin
with
something
like
stuff
storage.
How
does
it
work?
I
don't
know
I
don't
know
a
ton
about
ceph
and
the
integration
right.
So
it's
like
anything
else,
right
linguity
will
handle
your
tcp
traffic.
It's
going
to
do
it's
gonna,
do
really
intelligent
stuff
with
your
http
and
grpc
traffic,
and
it's
gonna
treat
other
like
other
tcp
streams
that
it
it's
not
clear
about.
B
It's
generally
gonna
treat
those
as
generic
tcp
trunks,
and
so
you're
gonna
get
different
metrics
off
that
than
you
will
off
something
that
understands
really
well.
How
hard
is
it
to
enable
trace
logs
for
your
sidecar?
So
actually
we're
going
to
talk
about
that
in
just
a
minute.
So
five
fires.
B
Sorry,
if
I
said
your
name
wrong
there,
we'll
we'll
talk
about
enabling
logs
in
just
a
second.
So
with
that,
that's
my
monitoring
pitch
right.
The
the
long
story
short
is:
have
a
plan
check
that
production
run
book
because
it's
got
it's
got
steps
and
then
and
then
just
make
sure
that
we're
you
know,
make
sure
that
you're.
You
understand
it
well
enough
that
when
something
starts
to
happen
like
how
do
I
know
if
a?
B
How
do
I
know
if
a
pod
is
injected
right,
like
you
should
you
should
have
that
answer
for
yourself
right
like
how
do
I
know
when
I
look
at
my
so
when
I
look
at
all
the
positive
plus
there
right
right,
this
is
on
my
on
my
bigger
class
there.
I
can
tell
just
by
looking
at
it
right
what
what
things,
what
things
are
in
a
good
state,
what
things
aren't
right
and
how
many
pods
are
injected
right,
so
I
can
tell
that
this
thing
or
sorry.
B
B
B
B
Yeah,
okay,
well,
there's
something
weird
in
my
script:
regardless
right:
let's
get
our
pods
again.
I've
got
liquidity
running
if
I
want
to
debug
the
control
plane
right
like
the
first
thing
I
do
is
just
go
check
out
the
events
right,
so
I'm
in
the
I'm
in
the
name.
Okay,
so
let's
see
get
events
right
and
we
can
sort
by
time
stamp,
which
is
a
handy
one
that
I
always
like.
I
always
save
this
command
off
the
site,
because
I
never
remember
the
syntax
for
sorting
by
timestamp.
B
Oh,
let
me
copy
give
me
just
a
sec
betty.
There
we
go
so
I
get
events
I
start
by
the
time.
Let
me
make
this
a
little
bit
smaller
right.
Forget
events.
Look
through
the
events
right,
because
it'll
tell
you
if
something's
going
on
this
is
the
history
of
pods
in
this
name
space
right
so
like
like
everything
else,
you
do
in
kubernetes
events,
logs
custom
objects
now
for
the
default,
linguity
installation,
you
don't
have
any
custom
objects.
B
You
need
to
worry
about
right,
yeah,
you
don't
have
any
custom
objects
you
need
to
worry
about,
but
using
kubernetes
events
will
get
you
a
lot
of
details.
Checking
out
the
pods
like
are
all
the
pods
in
my
liquidity,
namespace
healthy,
all
right!
Well,
okay,
I've
got
everything's
up
and
I
don't
have
any
restarts.
So
that's
like
that's
a
pretty
good
start.
A
B
So
oh,
and
what
are
these
various
components?
I've
got
the
destination
service
which
or
the
destination
pods
which
tell
me
about
the
endpoints
and
help
me
help.
My
pods
help
my
my
proxies
pick
where
to
route
traffic.
I've
got
the.
B
B
So,
let's
see
some
logs
k
logs
this
guy
and
oh
right,
you
have
to
pick
a
container
right,
so
a
tip
that
I
use
all
the
time
right.
Let's
see
normally.
B
B
B
So,
let's
just
share
this
real
quick,
so
I
can
set
the
log
level
in
a
couple
different
places
be
aware:
linguine
linkerd's
control,
plane
used
to
be
all
written
and
go,
and
now
some
components
are
starting
to
get
written
in
rest
and
there's
some
stuff
about
why
it's
now
easier
to
do
rust
for
kubernetes
control,
plane
components,
but
it
has
become
easier,
and
so
you
should
expect
more
control,
plane,
components
to
get
to
get
written
and
rest
because.
A
B
Is
a
really
interesting
language,
and
this
isn't
the
time
for
that
talk,
but
there's
some
stuff
there
suffice
to
say
be
aware.
Different
different
controllers
use
use
different
formats
for
setting
the
log
level.
Everything
everything
is
out
there
in
the
documentation
and
you
can
see
it
all
in
the
helm
chart
in
the
helm
chart
doc.
Specifically,
how
do
you
set
the
lock
level
in
general?
You
can
set
it
globally
at
the
class
there
or
per
individual
workload
right,
so
just
be
aware
how
you
how
you
want
to
do
it?
B
A
B
B
So
there
are
different
log
levels
to
set,
which
is
the
whole.
The
whole
point
of
that
story
again
the
message
that
we
can
see
here
I
can
see
that
certificates
are
being
generated
and
why
I
can
see
you
know
some
information
about
my
issuer
search
whatever
right,
some
just
generic
stuff
about
about
this
environment,
and
this
is
a
great
place
to
go.
If
you
want
to
debug,
what's
happening
with
certificates
and
the
deeper
your
log
level,
the
more
information
you're
going
to
get
so
that's
the
identity
service.
B
I
could
also
check
out
the
actual
proxy
right
was
that
I
linkery
proxy,
a
proxy
pretty
proxy
right.
This
one's
actually
pretty
pretty
simple,
because
we
don't
have
a
very
verbose,
debug
level.
If
folks
are
yeah.
One
also
great
see
you
on
there
is.
You
know,
I
know,
there's
a
there's
a
new
relic
integration,
I'm
not
sure
about
dynatrace,
but
I'd
be
surprised
that
there
wasn't
I'm
just
not
super
familiar
with
dynatrace
from,
if
I'm
being
honest
but
but
check
him
out.
B
B
Organization
invested
time
and
we're
happy
to
make
it
easier
for
them
to
to
support
you
so
going
back
looking
at
the
proxy
logs,
I
can
see
data
about
specifically
who's
talking
to
this
component
and
why
right
look?
B
I've
got
some
failures
about
a
inbound
connection
and
what's
going
on
so
if
I
were
debugging
put
this
into
a
trace,
a
trace
mode
output,
the
logs,
something
because,
like
even
even
just
with
no
traffic,
this
is
already
a
lot
of
data
and
if
you're
seeing
traffic
and
you're
in
trace
mode,
there's
going
to
be
so
much
text
here
that
you
basically
just
want
to.
You
want
to
set
the
log
level,
save
the
logs,
try
and
reproduce
the
behavior
that
you
saw
and
then
set
the
log
level
back
normal
right.
B
That's
the
that's
the
basic
flow!
And,
last
but
not
least,
I
want
to
talk
about
the
the
init
container.
I
think
it's
just
like
video
net,
this
one's
underneath
right.
So
this
is
this:
is
your
dive
into
what's
happening
with
ip
tables
right,
so
it'll
output,
the
existing
iptables
configuration
when
it
starts
it
will
output
what
it's
doing
and
it'll
output?
B
So
I'm
just
kind
of
pointing
you
at
different
places.
You
can
go
with
the
tooling.
That's
that's
the
basic
kubernetes
tooling,
and
we
also
have
linkedins
cli
itself,
which
gives
us
some
tools
that
are
a
bit
they're,
fairly
simple
to
consume.
So,
first
off
and
really
the
most
important
one
just
check
your
version.
B
Right,
like
you,
want
to
be
on
the
latest
patch
version,
for
whatever
release
you're
on
and
in
general,
things
are
n
minus
two,
so
we're
on
2.11,
so
you
can
be
2.11
210
or
two
nine
today
right,
but
if
you're
on
two
nine
go
be
on
two
nine
five,
if
you're
on
210
go
beyond
whatever
the
latest
210
releases,
which
I
don't
remember
what
that
is
so
get
the
latest
latest
patch
version
on
what
you're
doing
beyond
that,
we
have
this
handy
dandy,
lingerie
check
liberty
check,
can
also
output
data
as
json,
so
I've
seen
people
put
this
in
a
little
container
and
just
run
it
periodically
and
just
dump
this
to
something
or
you've
got
you've
got
all
tons
all
kinds
of
options.
B
Also
another
boy
cloud
plug
it.
It's
got
all
this
data
for
you,
so
you
can
get
a
sense
of
what's
going
on
in
your
environment,
but
this
just
tells
me
am
I
happy,
and
there
are
some
things
I
can
do
with
lingerie
check
beyond
just
beyond
just
running
the
generic
one
I
can
check.
I
can
check
my
proxies.
I
can
check
my
config.
I
can
pre-check
before
I
do
an
install
it's
a
great.
It's
a
great
command
use
it.
It
should
be
the
first
step
if
you
suspect,
something's
wrong,
run
lingerie
check.
B
I
can
get
proxy
metrics
with
linkery
diagnostics
and
I
can
get
details
about
the
identity
or
the
authorization
all
right.
So
there's
there's
a
couple
other
things
that
I
can
do
as
I
look
in
there,
but
I'm
not
really
gonna.
I'm
not
really
gonna
go
too
much
further
down
that
road.
Unless
anyone
has
a
specific
debugging
question,
also
hi
billy
hi
to
billy.
I
hope
I
set
your
name
right
there.
B
Oh
last,
but
not
least,
tap
so
winkerd
linkerty's
dashboard
comes
with
this
tap
functionality
and
tap,
allows
you
to
check
on
the
state
of,
or
it
allows
you
to
see
metadata
about
the
requests
between
your
components.
Right,
it's
it's.
What
gives
you
that
hey
like
this
path?
You
know
when
I
called
this
path.
I
succeeded
when
I
called
this
other
path.
It
failed
right
like
that
data
is
super
valuable.
You
can
access
the
tap
data
via
the
link
or
dtli
oops.
B
You
can
access
that
data
via
the
link.
Your
dtli
linkedin
vis
cap
right,
I'm
not
gonna,
I'm
not
gonna
actually
do
a
tap.
Oh
thanks
gerald,
I'm
not
gonna,
do
a
tap
now,
but
I
could
tap.
I
could
tap
a
particular
deployment
right
and
see
what
requests
are
coming
in.
I
could
tap
an
individual
pod
and
I
can
make
really
specific
rules
to
filter
filter
that
down.
B
B
A
I
don't
think
there's
too
much.
I've
got
some
like
just
smaller
ones
around.
You
know
like
like
why
linker
d,
I
I
know
the
answer
and
love
the
blog
post
and
that
so
that's
kind
of
what
I'm
getting
at,
but
the
the
reason
as
to
why
linker
d
doesn't
use
envoy.
B
Yeah,
okay,
great
so
there
there
is
a
there
is
a
blog
post,
which
let
me
pop
up
here,
pretty
convoy
yeah.
B
Why
lingerie
doesn't
use
how
much
I'll
I'll
post
that
in
the
chat,
long
story
short
right
for
us
when
we
wrote
linker
d2
right,
there
was
a
deliberate
decision
made
to
write
our
own
proxy
right
and,
and
it
comes
down
to
more
than
anything,
not
to
say
anything
bad
about
envoy
right,
but
the
rust
programming
language
was
kind
of
becoming
more
serious
at
the
time
that
we
were
rearing
liquor
d
and
like
like
at
the
end
of
the
day
when
you're
writing
a
proxy,
you
want
two
things
right:
you
want
it
to
be,
you
want
to
be
secure
and
you
want
to
be
fast
right
and
you
want
to
be.
B
I
guess
three
things
you
want
to
be
small.
You
want
to
be
secure.
You
want
to
be
fast
right,
so
you
need
it
to
be
in
a
compiled
language.
That's
not
garbage
collected
right,
because
garbage
collection
that
process
of
cleaning
out
your
memory
adds
all
sorts
of
safety
which
is
great,
but
it
it
also.
It
also
slows
things
down.
B
As
it
does
garbage
collection
right
then
after
that
right,
then
then,
after
that,
right
like
you
want
it
to
be,
you
want
to
be
small
right
so
again,
a
compiled
language,
that's
very
efficient
right
is
a
big
deal
and
you
want
it
to
be.
B
You
want
to
be
secure
right
so
that
the
downside
of
writing
in
c
or
c,
plus,
plus,
right
or
not
having
garbage
collection
is,
is
that
you,
you
know
there
are
like,
like
c's,
c
and
c,
plus
plus,
are
kind
of
famous
for
being
hard
to
manage
memory
and,
like
I'm,
not
a
good
enough
programmer
to
explain
to
you
why
that
is
or
how
that
works.
I
wouldn't
even
consider
writing
those
things,
because
that's
that's
hard
and
I'm
just
not
that
good
at
it
right
rust.
B
The
compiler
for
rust
is
specifically
built
to
avoid
memory
management
errors
or
to
catch
them,
as
it
does
the,
as
does
the
compilation
and
again
I
don't
even
know
enough,
but
rust
explain
why
that
is
but
dig
in
for
yourself
right
and
and
see
what
makes
sense,
but
it
is
by
writing.
In
rust,
we
made
the
linkard
e
proxy,
really
performant
real
and
really
memory
safe
right.
B
So,
in
our
view,
like
you
want
it
to
be
fast,
small
and
secure,
and
you
get
that
just
by
using
rust
and
that's
like
here
just
by
using
the
lingerie
proxy
and
writing
it
in
the
rest
language,
and
that
was
worth
the
cost
of
having
to
build
our
own
proxy
right.
And
it's
purpose-built
right
like
envoy's
great,
but
it's
general
purpose
right
link
reduced
proxy
is
ju.
It
just
does
what
the
control
plane
does
like
go,
try
and
use
it
for
something
else.
B
Could
I
use
your
liquidity
proxy
to
do
this
and
she's
like
no
like
just
go
just
go
like
you,
can
take
some
libraries
you
use
and
build
your
own
rest
proxy,
but
like
lingerie's
proxy,
like
only
does
what
the
control
plane
tells
us
to
do,
it's
not
it
doesn't
have,
doesn't
have
room
for
a
misconfiguration
right
like
if
you
look
at
if
you've
got
something
that
that
manages
envoy
like
envoy's
heart,
right,
there's
great
stuff
in
there
right,
but
it's
it's
hard,
so
be
sure
that
be
sure
that
and
be
sure
that
whatever
you're
using
you've
seen,
you
know
that
it's
really
good
at
configuring
envoy
and
watch
it,
because
there
are
no
matter
what
service
mess
you're
using
there
are
vulnerabilities
that
will
come
up
due
to
configuration
mismatches
between
those
two
projects
which
we
get
to
avoid
because
we
have
a
purpose-built
proxy
and
they'll
talk
about
that
more
in
the
article
all
right,
I
wanna
just
do
five
minutes
on
upgrading.
B
Can
we
can
we
talk
about
that
real,
quick,
all
right?
So
the
first
thing
I'm
going
to
tell
you
about
upgrading
lingerie
versions-
is
test
test
test.
It
in
non-production
be
real,
like
keep
your
stuff
in
version
control,
try
a
dry
run
of
what
you're
doing,
right
and
and
validate
that.
The
second
thing
I'll
tell
you
is
that
the
data
plane,
those
proxies-
will
work
with
up
to
two
versions
ahead
of
control.
B
B
Don't
skip
versions.
Okay,
don't
go
from
2-9
to
211
if
you're
doing
an
in-place
upgrade
right.
I
want
to
be
very
clear
about
what
I
mean
there
right.
There
are
two
ways
to
upgrade:
essentially
you
can
upgrade
your
live
environment
or
you
can
build
a
brand
new
cluster
at
the
new
version
and
switch
over
to
the
new
class
there.
B
I
have
I'm
not
going
to
tell
you
which
way
to
do
it
right
because,
like
I
think,
ultimately,
that's
going
to
depend
on
you,
there's
a
lot
of
folks
making
a
lot
of
hay
about
why
git
ops
is
a
great
operating
pattern
right
and
I
I
agree
with
them
right,
but
but
your
situation,
I
don't
know
every
everybody's
situation.
I
think,
if
you
can
do
it
with
fully
disposable
clusters,
do
it
that
way,
don't
ever
upgrade
anything
right.
B
Just
deploy
new
clusters
with
new
infrastructure
go
from
there,
but
if
you
are
upgrading,
don't
skip
versions
and
even
if
you
are
doing
a
wholesale
new
cluster
test
before
you
shift
your
traffic
over.
I
know
this
is
like
I
know
that's
obvious
right
but
like
I
just
want
everyone
to
really
really
have
that
in
their
mind
right
because
it's
a
it's
an
easy
place
to
hear
yourself
and
actually
yeah
gerald,
just
posted
a
link
to
upgrading
the
other
one
I'd
say
is
look
at
the
docs
about
upgrading
versions.
B
B
We
talked
about
behavior
changing,
but,
like
is
everyone
reading
upgrade
notes
like
have
I,
like
I've,
upgraded
things
in
production
without
reading
upgrade
notes
before,
like
I'll
I'll
admit
it,
maybe
I'm
the
only
one
but
like
I
doubt
it
right
so
consider
strongly
reading
upgrade
notes,
definitely
test
right
and
and
be
aware
that
in
some
versions,
especially
the
change
from
2
9
to
210,
there
are
behavior
changes
that
are
that
are
significant
and
they
can
cause
problems
if
you're
not
tracking
on
it.
B
If
you're,
not
testing
right
beyond
that,
I
I
would
again
strongly
recommend
you
use
helm
and,
if
you're
using
helm,
no
helm
right
like
I
want
you
all
to
see
something.
So
this
is
our
our
our
linkerity
expert
put
this
together
and
and
talked
about
upgrading
right
and
their
thing
their
thing.
They
talk
a
lot
about
helm,
upgrade
and
reuse
values
versus
reset
values.
A
B
Upgrade
to
the
old
version,
okay,
so
be
aware
of
helm
and
and
how
it
works
right.
That's
that's
the
big
story
right
check
up
great
notes,
don't
skip
versions.
You
know
like
with
everything
else,
make
a
plan.
B
You
know
measure
twice
cut
once,
especially
when
you're
dealing
with
production
traffic
right
like
a
service
mesh,
sits
in
between
your
production
traffic
man
gerald.
I
just
want
to
say,
hit
me
up
after
this
on
slack
I'd
love
to
I'd
love,
to
send
you
a
thank
you.
You've
posted
so
many
great
links,
I'm
crazy,
grateful
and
and
yeah.
So
now
I
guess
we've
got
a
couple
minutes.
Is
it
okay
to
do
questions
absolutely.
A
B
I
want
to
make
sure
that
I
answered,
I
answered.
Someone
had
a
question
that
I
loved
earlier
yeah,
so
mr
mr
feed,
there,
yes
or
they
asked
well,
he
probably
for
mister-
is
the
viz
component
normally
installed
on
production
environments,
yes,
but
the
the
prometheus
they
typically
folks
externalize
the
prometheus.
They
use
their
own
prometheus
instance
and
they
connect
the
linguity
dashboard
to
that
they
don't
use
the
built-in
prometheus
that
comes
with
it,
but
linker.
A
A
B
You
can
always
just
install
it
and
uninstall
it
right,
like
negative,
is,
is
much
less
like
much
less
important
than
the
rest
of
it
right
so
like
here
in
my
cluster,
I
don't
have
liquor.
Dv
is
installed,
but
even
if
I
installed
linker
d
itself
with
with
him,
I
can
just
go
in
here
and
type
linkedin
is
installed.
B
B
All
right
so
now
I'm
just
checking
the
vis
extension
so
check
again.
Like
I
told
you,
it
has
different
modes
that
it
can
be
in.
I
can
wait
for
it
to
be
ready.
I
can
pop
in
a
dashboard.
I
can
do
the
debugging
I
want
to
do
and
then
I
can
turn
it
off
I'd
say
in
general:
it's
not
a
high
cost
thing
to
leave
up
and
running,
and
I
wouldn't
I
wouldn't
remove
it.
B
B
There's
any
any
new
ones
up
here:
oh
yeah,
so
shell
script
code,
that's
a
great
one,
so
the
the
resource
utilization
comparison.
You
know.
A
B
Right,
like
remember,
we,
the
com,
where
we're
the
buoyant
folks
different
people,
will
say
different
things.
We
did.
We
did
a
benchmarking
of
seo
versus
linkery
right
now
we
used,
we
use
the
benchmarking
suite
from
the
folks
over
at
kinvoke
and
I'll
put
the
put
the
link
in
the
chat
right.
So
we
did
it
twice
last
year
this
this
article
talks
all
about
the
the
ways
we
did
it
right,
but
we
found
when
we
tested
it
with
this
third-party
benchmarking
suite,
not
our
not
our
benchmarking
suite.
B
We
found
that
we
saw
like
a
dramatic
difference
in
latency
and
resource
consumption,
with
linker
d
versus
istio.
But
again
do
your
do
your.
B
Right,
it's
totally
totally
worth
that
yeah
gerald.
I
will.
I
will
look
you
up
right
after
this
on
linkedin,
so
I
got
to
copy
and
paste
it.
There.
A
Absolutely
no!
Thank
you.
So
much
jason.
It's
it's
been
wonderful
to
have
you
on
again
it's
I.
I
love
that
we
keep
meeting
like
this
on
these
streams
very
very
soon
in
cubecon.
So
just
a
reminder
to
all
of
you.
Attending
kubecon
eu
make
sure
to
grab
your
reservations,
both
your
hotel
and
your
flight.
If
you're
looking
into
that,
I
just
booked
mine
recently
and
saw
that
things
were
filling
up.
So
the
cncf
is
looking
at
getting
a
few
more
blocks
on
that
front,
but
time
is
definitely
of
the
essence.
A
It
looks
like
it's
going
to
be
a
popular
conference.
It'll
be
a
lot
of
fun.
I
hope
to
see
their
chatting
about
cubecon.
If
not,
the
talks
will
be
available
after
that.
So
lots
lots
of
good
sessions
lots
of
good
day
zero
events
should
be
fun.
Thank
you.
Everyone
for
joining
the
latest
episode
of
cloud
native
live.
It
was
great
to
learn
from
jason.
A
We
enjoyed
the
interaction
and
questions
from
the
audience,
always
a
lively
discussion
next
week,
we'll
be
joined
by
richard
collins
on
the
topic
of
workload
misconfiguration
the
number
one
security
threat
when
using
kubernetes.
Thank
you.
So
much
for
joining
us
today.
Thank
you
again
so
much
jason
and
we
hope
to
see
you
soon
thanks,
everybody
yeah.