►
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
Hello,
everyone
and
welcome
to
the
cncf
on
demand.
Webinar
include
introducing
niso
the
kubernetes
api
traffic
explorer
for
kubernetes,
I'm
rafael
and
I'm
an
upline
co-founder
and
leading
on
customer
experience
teams
and
I'm
honored
to
be
here
today
and
share
how
our
open
source
project
help
developers,
devops,
sres
testers
and
basically
anyone
who
runs
their
api
in
a
kubernetes
environment
troubleshoot
their
apis.
A
A
I'll
start
by
explaining
the
pain
in
a
high
level,
and
I
will
do
a
quick
overview
of
museum
to
get
everybody
in
sync:
don't
worry
if
you've
never
developed
a
single
code
to
kubernetes
api
you're
still
good
to
go
now.
You
can
try
that
then
we'll
jump
into
a
hands-on,
how-to
demo
I'll
show
you
how
you
get
from
zero
to
once,
a
hero
getting
all
the
apis
tracked
with
mizu
and
how
you
can
actually
even
do
an
on-demand
tracing
for
a
simple
scenario.
A
Summer
summary
and
takeaways,
and
couple
of
frequently
asked
questions
that
got
our
miso
users
and
customers
intrigued.
So
we'll
answer
them
here
and
give
you
the
next
steps
and
with
that,
let's
dive
into
what
happened.
So,
first
of
all,
if
you
are
a
back-end
developer,
this
slide
is
for
you.
We
feel
your
pain,
kubernetes
developers
are
troubleshooting
in
the
blind
and
it's
time-consuming
not
to
mention
frustrating.
A
A
In
this
picture,
you
can
see
we
had
the
monolith
on
the
left
hand,
and
we
had
three
parts.
We
had
the
external
apis.
Those
are
the
github
twitter,
google,
facebook
that
used
to
do
the
the
single
sign-on,
logins
right
or,
for
example,
the
stripe
for
payments
right.
They
stay
the
same.
You
just
call
them.
You
get
a
response
right,
no
problem.
You
can
even
do
that
with
a
curl
command.
A
However,
your
code
base,
all
those
interfaces
that
you
expose
are
now
internal
apis.
They
represent
a
significant
portion
of
the
business
logic
that
replaces
what
used
to
be
a
public
interface
in
the
monolith.
So
remember
you
just
used
to
just
do
an
instance
of
a
class
and
then
dot
and
autocomplete
to
get
access
to
that.
Now,
you
actually
need
to
call
an
api
function.
A
There
are
exponential
more
apis
to
debug
the
behavior,
just
moving
from
something
that
runs
locally
in
the
same
memory
to
network
serving
multiple
business
cases.
Sometimes
it's
not
just
me
calling
that
code,
many
other
microservices
regaining
the
ability
of
the
reuse.
We
can
use
that.
However,
now
the
apis
are
more
complicated,
harder
to
debug
covered
under
new
variety
of
new
protocols,
for
example
jrpc
and
rest.
You
can
have
both
of
them
even
called
over
the
network,
meaning
hey
tcp.
Sometimes
the
server
is
not
responding.
You
got
500
and
encrypted
so
with
that
how
you
debug.
A
A
It
requires
a
new
ecosystem
to
support
it.
Here
is
a
look
into
what
api
people,
what
the
api
people
have
today.
If
you
have
just
apm
it's
like
me
telling
you
you
have
access
to
the
cpu
percentage
10
years
ago.
It's
not
enough
existing
solutions
focus
on
limited
information
that
tells
very
little
of
the
story.
So
if
you
look
at
like
distributed
telemetry
and
tracing,
they
do
give
us
the
ability
to
understand
like
the
response
and
the
response
code
and
the
path.
A
However,
engineers
need
access
to
more
information
in
order
to
travel
to
the
aps,
and
they
usually
need
it
now
over
several
micro
services
communication,
including
the
api
payloads
between
them
and
maybe
into
the
message
queue
for
example,
on
the
or
the
third
party
as
well,
and
they
needed
of
course
now.
So
what
do
we
do?
A
A
A
A
So
how
about
we'll
just
take
mizu
for
a
spin
all
right,
so,
let's
jump
into
the
demo.
What
I
want
to
show
you
is
how
you
can
download
meizu
deployed
into
your
kubernetes
cluster
and
start
debugging,
the
application
super
fast.
So
what
you
see
here
is
we've
stock,
just
a
demo
application.
It's
installed
on
my
kubernetes
cluster
here
those
are
the
pods
and
here
I'm
going
to
actually
start
using
mizu.
So
the
first
thing
we
want
to
do
is
download
miso.
How
can
you
do
that?
A
You
go
to
google
and
if
you'll
type
kubernetes
traffic
viewer,
you
will
see
the
github
repo.
You
will
probably
see
the
up
nine
blog
about
it
and
the
getmizu.io
page,
which
either
one
will
get
you
the
command
that
you
need.
You
just
scroll
here
copy
the
command
that
you
need
and
just
paste
it
into
your
cmd
line.
A
What
will
happen?
It
will
just
download
meizu
it's
a
file
around
like
43
megabytes
and
let's
verify
that
we
actually
have
the
file
and
it's
got
the
right
permissions.
That's
great,
which
version
of
music.
Are
we
using
right
now?
Miso
version
will
test.
29.0
today
is
march
22.
So
that's
the
version
that
we
have
today,
okay,
good.
Now
what
I
want
to
do.
I
want
to
actually
start
playing
with
miss,
so
what
I
need
to
do
is
just
normally
do
mizu.
Sorry
for
that.
A
A
You
can
see
the
pods
are
deployed
here
and
there
is
a
demon
set
per
node,
and
this
is
the
api
service
that
you
can
see
here.
Let
me
just
do
that
here
we
go
now.
We
have
miso
under
one
side
my
application.
On
the
other
side,
let's
bring
up
the
network
config
and
do
a
small
refresh
and
you
can
see.
I
have
all
the
traffic
data
here
similar
to
that.
But
let
me
show
you
something
else:
let's
do
a
login
that
is
actually
not
gonna
work.
So
if
I
do
log
in
that
you
can
see.
A
I
know
myself
here
the
401
that
we
saw
here
yeah.
We
can
see
it
here
from
my
computer
to
front
end,
but,
however,
we
can
actually
see
what
happened
from
the
front
end
to
the
user
right.
So
I
can
click
on
that
and
just
click
response
and
see
the
request
response.
I
can
see
that
oh
not
found,
for
example,
if
I'll
do
something
different,
let's
say
I'll
use,
my
username
and
I'll
just
add
couple
of
characters
to
the
password.
A
A
A
I
got
100.,
so
I
want
to
kind
of
figure
out
where
the
problem
is.
We
can
see
if
we
open
the
dev
tools.
Let's
just
do
that
again,
we
can
see
that
we
got
the
406,
so
we
got
the
406
from
here.
Let's
trace
it,
what
we
can
see
is,
first
of
all,
it's
an
http
request
right.
So
let's
go
in
http
edit,
the
filter
here
great
now.
What
I
want
to
do
is:
okay,
let's
see
who
is
actually
involved
with
that.
So
let's
do
that
again.
A
A
So
we
see
redacted
we're
going
to
touch
that
in
a
second
and
we
can
see
it's
not
acceptable
and
we
can
actually
see
the
code.
Another
code,
the
exception
that
that
code
through
and
what
was
the
problem
here.
Okay,
I
want
to
debug
that
one
level
further.
First
of
all,
I
want
to
see
who
plays
with
whom
here.
So,
let's
look
at
the
service
map?
A
Look
at
the
service
map-
and
this
is
a
service
map
inferred
from
traffic.
So
we
can
already
see
what
we
have
here.
We
have
front
end
calling
cards
front,
end,
calling
user
front
encoding
orders
orders
is
calling
payments
interesting,
let's
create
a
mizzou
tapping
regex
that
will
kind
of
capture
that
so
what
we're
going
to
do
going
back
to
my
screen,
ctrl
c
and
as
you
can
see,
control
c
just
removes
mizu
completely
from
the
cluster.
A
No
traceback
no
problem
and
what
I
want
to
do
is
I
want
to
have
a
regular
expression
that
catches
like
front
front-end
orders
and
payments
and
remember
the
reduct.
I
want
to
see
all
the
data
no
reduction,
because
I
want
to
debug
everything
again
now,
this
time
we're
tapping
only
four
pods
and
let's
give
it
a
second
here
we
go
and
now
let's
do
the
same
thing.
So,
let's
clear
the
cart,
okay
and
add
holy
again,
add
to
cart,
and
you
know
just
for
the
sake
of
it.
A
Here
we
go
stop
perfect.
Now
we
basically
have
the
trace
of
the
application.
So
look
we
got
my
browser
calling
front-end
front-end,
calling
customers
literally
showing
me
the
request
and
the
response.
Remember
we
had
that
reducted
now
we
can
actually
see
the
address
and
everything
that
we
need
here
great
after
customer
after
the
the
user.
What
we
got
we
are
having
orders
doing
a
post
with
all
the
data
to
payments,
great
I'll
move
myself
here
and
we
can
actually
see
the
entire
request
and
the
response
remember
here
we
only
see
the
orders.
A
What
is
the
response?
Oh
no
payment
is
false
payment
declined.
Why
is
it
200,
then?
Maybe
I'll
call
my
third
party
or
maybe
we'll
call
the
service
owner
and
kind
of
check
with
them.
Okay,
great
payments,
then
we
see
orders
still
checking
things
with
the
user
and
then
frontend
service
get
from
orders
406,
which
is
making
sense.
You
you
ask
for
that,
and
orders
now
responds
with
not
acceptable,
giving
you
giving
the
front
end
gateway
the
information
they
need
and
the
message
to
bring
to
the
customer
as
well.
A
A
Did
I
have
to
change
my
code,
no,
nothing
by
the
way,
on
top
of
that,
showing
an
open,
opi,
open
api
spec
for
that
and
you
can
just
go
here,
look
at
the
front
end
and
maybe
send
that
to
someone
else.
Here
is
the
post
to
the
card.
You
can
grab
it
from
here
and
then
do
it
with
the
curl
command
or
something
like
that,
whatever
you
want
and
that's
how
you
debug
with
mizu,
with
literally
less
than
a
couple
of
minutes,
going
back
cleaning,
mizu
just
control
c
again,
I
use
the
no
reduct.
A
Of
course
you
can
have
a
profile
that
says
what
are
you
reducting
and
what
not
there
is
set
of
policies
and
I'll
touch
that
in
the
q,
a
so
with
that
going
back
to
our
presentation,
okay,
switching
back
to
the
slides.
So
let's
talk
about
couple
of
frequently
asked
questions
that
we
got
from
our
customers.
How
do
I
tap
my
entire
cluster,
which
might
be
useful
if
you
have
like
a
dev
environment,
multiple
namespaces,
you
just
want
to
tap
everything
start
from
there.
A
How
can
I
redact
remove
the
items
from
observed
traffic,
which
again
you
know,
especially
if
it's
production,
but
also
like
in
pre-production?
Maybe
you
don't
want
to
share
the
authorization
keys
if
the
api
keys
that
the
individuals
are
using,
how
would
you
be
able
to
reduct
that
from
data
are
you
running
as
a
sidecar
I'll,
explain
that
which
permissions
does
miser
require
to
run
and
and
what
is
the
overhead?
A
A
Can
I
reduct
or
remove
items
from
my
observed
topic
so
out
of
the
wa
out
of
the
box.
Mizu
does
reduce
values
such
as
token
authentication
password
it
does
that
on
the
header
level
and
the
body
of
the
request
and
response.
So
it
kind
of
gives
you
a
clear
thing:
we
literally
took
a
whole
document
or
article
in
our
documentation
to
kind
of
define
what
are
the
rules
and
explaining
how
you
can
remove
or
add
to
that
list.
A
So,
for
example,
if
you
have
your
own
special
header
or
key
or
value,
then
you
can
definitely
add
that
as
a
one
time
to
your
client
and
share
it
with
people
or
just
in
a
centralized
way
in
the
meizu
pro
just
define
it
one
time
and
then
nobody
will
be
able
to
do
that
and
that,
if
you're
using
the
open
source
dash
dash,
no
dash
reduct
will
just
open
everything
for
you.
If
you
need
to
debug
something-
and
you
don't
want
to
reduce
at
all,
you
can
even
make
that
the
default.
A
Are
you
a
sidecar?
No,
next,
no
sorry!
Actually
we
started
as
a
sidecar.
The
problem
is
that
you
are
doubling
the
resources.
It
was
too
super
super
hard.
What
we've
converted
to
is
a
demon
set
per
node
that
is
actually
have
a
pod
that
obeys
the
regular
expression
or
the
namespace
and
one
more
pod
for
the
web
server.
That
kind
of
shows
you
all
the
traffic
and
everything,
so
it's
very
lean,
but
definitely
a
main
tool
and
with
a
control
c
you
just
clear
everything.
A
Let's
go
into
the
permission,
so
permissions
in
kubernetes
are
super
hard
to
explain.
We
again
created
an
article
just
for
that
describing
all
the
permissions
and,
of
course
you
can
do
the
meizu
check
pre-install
and
then
check
after
the
installation
on
a
high
level.
Okay,
as
a
rule
of
thumb,
if
you
have
coup
ctl,
if
you're
using
coop
ctl
to
manage
your
cluster,
deploying
removing
deployments
changing
port
forwarding,
etc,
you
are
most
likely
ready
to
go
with
all
the
main
features
of
mizu
for
mtls
and
tls.
A
Some
of
them
are
here
actually,
and
it's
fine,
if
you're
not
feeling
comfortable
with
that,
you
don't
have
to,
and
we
still
show
you
the
unencrypted
traffic
if
you're
using,
for
example,
the
linker
d,
then
there
is
a
seamless
integration
you
can
do.
That
same
goes
for
istio
and
the
last.
What
is
the
overhead
of
the
capturing
so
hard
to
say?
A
Because
it
depends
on
a
lot
of
parameters
such
as
your
node
specifications,
such
as
the
amount
of
traffic
that
you're
going
to
do
like
requests
per
second
and
even
the
size
of
those
requests.
From
what
we've
seen
it's
none
to
very,
very
low
amount
of
resources
that
are
actually
being
consumed
by
mizu.
You
can
also
define
what
mizu
will
use
and
miz
runs
in
lower
priority
than
normal
applications,
which
means
by
default.
We
prefer
your
application
to
work
rather
than
us,
seeing
the
data.
Of
course
you
can
switch
that
automatically.
A
You
can
just
say.
I
want
to
run
higher
priorities,
for
example,
as
a
standard
debug
tool
for
everything
you
prefer
to
see
that
let's
say
you
have
a
a
loop
that
goes
over
and
over
causing
cpu.
You
want
to
see
what
started
that
maybe
from
an
api,
then
that
would
be
great,
so
mostly
again,
operation
super
low,
even
the
encrypted
data
and
the
ebpf
overhead
is
very
minimal,
and
you
can
try
that.
I
will
definitely
try
that
before
I'll
go
into
some
edge.
A
Cases
of
you
know
like
apis
that
are
doing
50
mega
megabytes
per
second
and
they're,
overwhelming
monitoring
or
normal
systems
worth
it
next
steps.
So
you
get
mizu
from
getmizu.io
or
from
the
github.
We,
where
you
can
just
build
it
yourself,
documentation,
getmizu.io
docs,
our
miso
community,
where
you
can
just
come
and
share
problems,
thoughts,
questions
it's
super
fun
to
to
hear
from
what
people
are
using
music
too.
A
As
I
said,
somebody
came
and
just
asked
us
to
compile
mizu
for
raspberry
pi,
because
he
had
kubernetes
of
works
very
pies,
crazy,
amazing
one
more
thing.
Next
week,
we're
going
to
have
another
on
demand
from
the
undemand
webinar
from
the
upnine
family
done
by
no
other
than
tom
akhurst.
The
founder
and
maintainer
of
walmart
he's
going
to
explain
how
we
took
warmock
into
the
kubernetes
microservices
world.
Here
is
the
link,
and
thank
you
very
much.