►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-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.
Panel Disucssion: Is There Actually a Byte Behind All the Buzz? eBPF in Production! - Frederic Lardinois, TechCrunch; Andrew Sauber, The New York Times; Daniel Bernier, Bell; Purvi Desai, Google & James McShane, SuperOrbital
eBPF is a revolutionary and very hyped technology which has led some people to ask if there actually is a byte behind all the buzz. This panel brings together end users of eBPF that are actually putting it into production to find out whether it is a painful sting or sweet honey for their infrastructure. The audience won’t learn about futuristic buzzwords. Instead, they will understand how eBPF is changing networking, observability, and security in production today.
A
Thank
you
very
much
thanks
everybody
for
being
here.
Thank
you
guys
for
being
here
appreciate
it
this
late
in
the
afternoon,
just
before
the
reception
and
the
drinks
and
all
that
good
stuff.
After
a
long
day
of
talking
about
ebpf,
it's
time
to
talk
about
actually
putting
it
into
production,
which
I
love,
end
user
panels,
because
I
think
everybody
always
can
learn
something
from
those
ebpf
is
a
little
bit
different
I
think
because
most
of
you
probably
don't
consume
ebpf
directly,
Google
does
Maybe.
A
Most
of
you
probably
don't
right.
So
it's
kind
of
an
interesting
view
of
the
ecosystem.
I
think
that's
different
from
others,
but
before
we
get
started,
I'm,
Frederick
claudin,
why
I'm
the
Enterprise
editor
at
TechCrunch,
and
maybe
the
rest
of
you
can
just
briefly
introduce
yourself
because
I
don't
think
we
ever
slide
up
with
names.
B
A
B
Thank
you
we're.
We
have
a
number
of
clients
that
work
directly
with
psyllium
specifically,
but
also
have
started
to
extend
that
with
some
of
the
observability
capabilities
as
well.
So
we've
been
interfacing
very
closely
with
that
from
a
network
security
standpoint
and
then
extending
that
into
the
observability
realm
over
the
last
last
year.
C
I
think
I
have
to
answer
this
question
from
two
perspectives.
Okay,
one
is
representing
the
Google
hat
from
Google
perspective.
We
have
various
groups
using
ebpf
in
a
wide
range
of
application.
It
starts
from
networking,
compute
security,
Telemetry,
of
course,
which
is
like
the
key,
and
we
have
been
at
it
now
since
years,
so
I
would
say
we
are
also.
We
have
been
installing
evpf
programs.
Now
almost
millions
of
machines
and
almost
all
Google
traffic
I
would
say
it
touches
or
is
touched
by
ebpf
program,
one
form
or
the
other.
C
So
that
is
the
one
part
of
Google
and
actually,
if
you
see
even
the
vpf
core
coming
contributors,
we
have
a
lot
of
at
least
25
percent
of
the
folks
and
then
similarly
from
the
steering
committee,
we
participants
cheering
committee
too
now
the
second
angle,
which
is
more
of
a
kubernetes
engine
or
gke
and
anthos
and
GDC
there.
We
started
the
Journey
of
using
ebpf
based
data
plane
around
in
2019.
It's
not
even
2019-20
early
2019,
and
when
then
we
looked
at
all
the
ecosystem.
C
C
D
Divided
by
X,
so
no
we
don't
have
the
same.
So
you
have
two
Trends
into
ebpf.
We
are
consumers
of
psyllium
and
the
full
suit
of
observability
of
all.
We
started
now
with
tetragon
and
everything
as
a
consumer.
We
also
have
as
a
consumer
the
data
plane
V2
from
the
Google
environments
when
we
use
Google's
version
of
kubernetes
and
from
that's
more
like
production
oriented.
D
E
A
B
Yeah
definitely,
we
went
through
an
evaluation
process
for
the
the
main
product
we
were
working
on
through
our
firm
was
a
product
that
allowed
for
a
real
Dynamic
set
of
executions.
It
was
within
a
financial
services
firm
and
so,
when
you're,
allowing
like
data
from
a
number
of
different
sources
to
flow
through
your
production
system,
you
really
need
to
be
able
to
understand
kind
of
everything
about
the
the
network
path
and
the
network
execution
right.
Where
are
you
reaching
out
to
how
large
of
is
the
data
that's
coming
into
the
system?
B
And
how
large
is
the
data
going
out
of
the
system
and
then
get
that
extra
context
from
the
kubernetes
API?
And
so
we
needed
the
L7
filtering
that
cilia
provided
and
then
they
they
made
it
really
easy
to
pull
in
the
context
that
was
around
that
enable
and
enable
the
appropriate
level
of
experimentation
that
the
product
product
required,
while
still
locking
it
down
from
a
security
perspective.
So
we
started
from
the
network
security.
B
You
know
field
in
terms
of
evaluating
the
product
and
then
what
ebb
allowed
us
to
do
was
extend
that
into
the
you
know:
execution
level,
environment,
we've
heard
all
about
the
capabilities
of
you
know,
ebpf
filtering
and
things
like
that
today,
and
so
that
was
you
know.
We
started
in
the
network
security
path
and
then
went
into
kind
of
host
security
and
Gathering
that
information
we
needed
to
make
decisions
about
whether
users
should
be
allowed
to
do
things.
A
B
We
had
some,
we
had
some
hiccups
along
the
way,
but
they
were.
It
was
more
about
some
of
the
complexities
around
the
the
layer,
7
filtering
implementation
within
psyllium,
which
ends
up
delegating
to
Envoy
on
the
host.
The
ebpf
portion
of
that
has
been
Rock
Solid
in
terms
of
our
use
case
of
it,
and
you
know,
in
terms
of
the
amount
of
data
that
we're
piping
through
the
the
platform
it's
the
performance
has
been
spectacular.
Maybe.
D
Lived
Open
AV
with
ovs
and
all
those
things
so
I
I
have
some
scars
of
this
openstack
yeah
I
know
yeah,
but
the
networking
Parts
was
ugly
I.
Think
the
fact
that
we,
when
we
looked
at
this
from
a
technology
perspective,
it's
the
I,
would
say
the
backing
so
early
on
when
I
started
to
work
on
the
networking
side
of
the
Clusters
and
the
communities.
I
was
a
really
big
fan,
I'm
still
a
fan
of,
for
example,
Vector
packet
processing
VPP.
D
But
if
we
think
ebpf
is
kind
of
a
terraclet,
a
surreal,
the
atpp
coding
is
even
worse.
So
you
realize
that
there's
only
a
few
and
full
of
people
who
actually
know
how
to
code
this
while
adpf
everybody
is
actually
involved.
It's
in
the
kernel.
It's
it's
already
part
of
that
mainstream,
so
kind
of
it
might
there
might
be
some
paradigm
shift,
and
there
is
there
are
Powerline
shifts
to
this,
but
you
feel
a
bit
more
secure
than,
and
that
was
one
of
the
drivers
where
it's
actually
pushed
us
towards
that
technology.
A
C
So
we
did
evaluate
multiple
sets
of
data
plane
and
imagine
we
are
in
Google,
so
we
have
a
lot
of
Technologies
within
Google,
starting
from
our
USPS
or
starting.
If
now
you
can
actually,
when
VPP
we
had
actually
looked
into
so
overall
when
we
evaluated
all
of
this,
one
thing
was
very
clear
for
us
that
we
needed
to
do
we
needed
to
have
ebpf
the
reason.
Why
is
also
very
interesting
because
we
wanted
to
be
close
to
Applications.
C
It
is
important
to
have
the
application
context
be
available.
That
was
one
second.
The
ease
of
programming
Daniel
just
mentioned
it.
It
is.
It
is
super
easy
at
this
point
of
time
to
build.
On
top
of
it
now,
the
question
was
why
Celia
and
for
us
again
there?
The
answer
was
rather
straightforward
when
it
started
off,
so
there
was
an
option
of
either
we
build
something
inside
internally
or
we
adopt
a
open
source
project
which
was
active
doing
very
well.
So
from
that
perspective,
when
we
looked
at
the
landscape,
it
was
psyllium.
A
C
That
promise
and
others
on
modular
modularization
of
Celia,
the
main
thing
is
our
customers
want
our
users
want
power
of
and
as
we
call
it
where
they
want
to
use
open
source
function
or
they
want
to
use
Enterprise
functions
of
iso
Valentine,
and
they
also
want
to
use
all
the
goodness
that
Google
is
bringing.
So
when
we
have
to
do
this.
C
There
is
a
need
for
building
that
modular
architecture,
so
you're
working
with
psyllium
on
this
very
actively
to
make
psyllium
act
more
like
a
platform
on
which
we
can
bring
multiple
Network
functions
on
it.
At
this
point,
I
think
this
is
what
about
North
Star
is
North.
Star
is
to
have
the
dynamic,
Marketplace
open
ecosystem,
and
we
believe
we
can
achieve
with
this.
So
fair.
E
There,
oh
I'm,
just
thinking
about
my
answer
to
that
question
so
earlier
I
said
psyllium's
the
obvious
choice
if
you
want
fast
Network
policies,
but
obviously
there
are
other
ways
to
do.
Network
policies,
even
with
BPF
in
kubernetes
I,
think.
The
reason
that
we
went
with
psyllium
was
more
so
around
kind
of
the
community
and
the
yeah
kind
of
like
the
pedigree
of
the
team
working
on
psyllium
in
the
past,
we've
gotten
on
slack
and
asked
for
features
that
appeared
a
few
months
later
with
a
full
test
suite
and
it's
yeah.
B
B
There
were
a
couple
other
folks
that
were
experiencing
the
same
problem
and
were
able
to
to
narrow
down
and
that
that
kind
of
collaborative
approach
when
we've
got
you
know,
especially
in
an
Enterprise
environment
where
you,
you
know,
you
have
to
be
careful
about
what
data
you're
able
to
share
and
things
like
that,
but
we
were
really
able
to
work
well
with
that
team
and
felt
confident
in
the
community
as
we
built
our
product.
On
top
of
it.
D
Well,
I
do
like
the
community
a
lot
I
think
there's
leadership
in
the
vision
of
what
ebpf
does
it's?
Actually
not.
It's
actually
rare
that
you're
able
to
see
like
the
group
that
maintained
the
kernel
pieces
of
it
be
everywhere
reachable
every
day.
Actually
anytime.
In
the
other
day,
you
select
them
they're
going
to
answer.
You
have
a
question.
The
breadth
of
the
skilled
set
we've
seen
from
the
the
group
John
festabanda
was
speaking
this
morning.
D
Was
the
guy
doing
llvm
and
P4
at
Intel
before
so
you
think
about,
like
I,
want
to
do
ebpf
offload.
He
has
this
brains
already
hooked
on
this.
So
that's
really
strong
and
plus
the
user
committee
is
also
quite
impressive.
It's
rare
that
you
will
see
all
hyperscalers
involved
in
the
same
technology
and
adopting
the
same
technology.
Normally
you
end
up,
you
can
it's
it's
a
it's
a
fight
that
you
have
to
deal
with
now?
No,
it's
all
agreed
upon.
So
it's
actually
quite
interesting
for
us.
D
B
They
have
a
good
understanding
of
where
that
ends
up
when
it
comes
to
the
user's
hands
right,
I
think
John,
when
he
he
was
talking
this
morning
about
all
the
context
that
end
users
want
to
see
when,
when
stuff
comes
out
of
the
kernel
right,
you
don't
want
to
see.
You
know,
I
know
numbers
and
you
don't
want
to
see.
You
know
network
network,
namespace
IDs.
You
want
to
see
the
kubernetes
data
right
and
and
bubble
that
up
and
potentially
even
get
data
about.
B
You
know
cluster
and
you
know
the
even
higher
level
data
that
can
be
gathered
so
that
because,
when
you're,
trying
to
operationalize
products
in
this
space,
like
Andrew,
said
right,
you're
not
working
with
a
single
kubernetes
cluster
I
mean
that's,
that's
not
how
anyone
deploys
these
days
right.
There's
hundreds
of
clusters,
potentially
thousands
of
clusters
each
with
their
own
set
of
nodes.
So
you
you
need
that
context
to
be
able
to.
B
A
E
E
A
Sounds
good
now
as
you're
putting
old,
psyllium
and
everything
else
into
production.
How
much
of
that?
How
much
are
you
relying
on
your
own
in-house
experience
and
how
much
are
you
Outsourcing
to
to
vendors
at
this
point,
because
you
just
mentioned
a
couple
of
issues
where
I
was
like
that's
kind
of
a
problem
for
the
vendor,
maybe
more
than
the
community,
but
kind
of?
What's
the
state
of
play
there
for
you
right
now,.
D
It
depends
I
would
say
it
depends.
It
depends
on
how
ugly
your
applications
are.
If
you
end
up
with
in-house
growing
applications
that
have
like
I
have
July
move
systems
that
came
out
with
the
vax
vmx
system.
Still,
so
it's
not
something
that
you
can
easily
Port
into
an
application
into
activities
cluster
when
you
try
to
migrate.
So
there
are
some
hooks
to
do,
and
this
is
where
you
like
to
have
more
and
holding
from
the
actually
the
ethelium
guys
around.
Is
there
a
hook?
D
You
can
do
in
Epp
app
to
try
and
make
it
work,
and
actually
that
happens,
something
I
could
not
do
if
I
was
mainstream
any
kind
of
other
technology
or
even
the
major
vendors
which
I
normally
rely
on
I
end
up
with
it's
our
own
map,
we'll
have
it
in
three
four
years,
maybe
two
years
because
you're,
the
first
customer
that
asks
it
and
the
volume
is
not
that
big.
That's
the
end
story
on
ebpf.
You
don't
have
that
issue
anymore.
It's
gonna!
It
can
get
fixed
for
those
kind
of
things.
D
We
need
we're
more
involved
because
we
know
our
applications,
which
are
sometimes
really
custom
for
other
mainstreams.
We
actually
leverage
we
try
to
leverage
as
much
as
possible
data
ecosystems
if
it's
that,
if
it's
been
solved
somewhere
else,
why
do
we
need
to
reinvent
the
wheel?
Although
I
just
did
a
talk
about
Reinventing,
the
wheel
of
networking,
but
that's
pretty
much?
It.
B
Yeah
I
was
going
to
say
you
know.
A
good
consultant
answer
is,
is
it
depends
and
I
have
a
second
Daniel
there
and
and
say
that
I?
Would
you
know
the
the
large
percentage
of
Enterprise
customers
that
we
see
you
know
their
their
application?
Integrations
are
not
that
deep,
but
when
you
get
to
people
that
are
working
in
more
unique
environments,
we
have
a
customer
that
has
you
know,
devices
deployed
onto
onto
drones
and
things
like
that.
Those
are
the
people
that
that
have
a
more
deep
need.
B
You
know
when
you
have
like
unique
Hardware
or
unique
Network
requirements
right,
that's
where
the
hooks
and
the
the
capabilities
that
ebpf
provides
to
just
to
modify
your
execution
environment
without
needing
you
know,
you
know
from
the
outside
right
you.
You
can
really
reason
about
things
nicely
and
I.
Guess:
I've
drifted
away
from
the
question
a
bit,
but
I
think
the
community
is
strong.
The
vendor
ecosystem
is
strong
and
there's
I
think
there's
a
fairly
obvious
line
when
you,
when
you
start
to
go
down
into
the
implementation
of
when
you
know.
B
A
C
All
right
so
I
think
for
us
first
of
all,
Community
is
all
of
us,
so
that
is
the
key
thing
now,
even
there.
There
is
a
nuanced
answer.
So
when
we
talk
about
ebpf
generally,
they
come.
What
we
need
basically
is
inability
for
us
to
really
have
better
controls
on
who
can
install
evpf
programs?
What
kind
of
programs
can
they
install
in
in
a
way
we're
almost
looking
at
a
ebpf
program
registry
right,
who's
owning
it?
Can
they
really
install
those
hooks
if
and
what
Hall
have
they
installed
all
of
it?
C
So
that
is
one
part
of
it,
which
is
largely
from
the
evpf
community
and,
as
I
said,
it's
really
made.
We
that
that
is
a
need
for
us
from
throughout
Google,
as
well
as
my
own
products
then
comes
the
second
piece
of
it,
which
is
we
as
a
provider
of
the
kubernetes
engine
and
data
plane
for
that
over
there.
The
biggest
thing
that
we
need
is
an
ability
for
us
to
compose
multiple
like
putting
together
multiple
Technologies
for
our
users.
C
C
So
we
can't
just
have
this
that
bring
whatever
you
want
on
top
of
this,
and
then
you
know
it's
hard,
tough
luck!
So
we
we
basically
walk
a
line
where
we
bring
an
opinionated
solution
and
when
it
comes
to,
let's
say
kubernetes
data
plane,
which
gke
and
thought
should
you
see
and
there
at
the
same
time,
we
also
want
to
enable
customers
to
have
the
flexibility
so
from
the
community
there.
C
We
need
an
ability
to
really
bring
all
of
this
together,
making
it
modular
making
data
plane,
modeler
being
making
it
composable
and
it
it
should
all
work
together.
So
one
of
one
of
the
thing
that
I
see
when
users
really
look
into
this
problem,
is
they
all
need
in
in
some
ways
to
solve
the
business
problem.
C
D
One
Challenge
I,
see
at
the
moment
with
the
community,
not
really
the
community
I
think
the
overall
ecosystem
of
ebpf,
it's
kind
of
a
trendy
term
right
now.
So,
okay,
if
you
think
about
something,
it
needs
to
be
AIML
or
it
needs
to
be
vpf.
So
the
trick
is
that
ebpf
is
not
locked
to
psyllium.
Anybody
can
build
platforms
based
on
evpr
Technologies,
so
you
end
up
having
I
would
like
kind
of
in
my
my
utopian
world
would
be,
if
I
add
a
version.
D
It
probably
psyllium
could
be
kind
of
the
Sonic
PSI
version
of
things
like
a
common
data
plane
that
most
people
can
use
so
that
I
end
up
with
having
I
do
an
RFP.
I
have
25
versions
of
an
abpf
data
plane
that
almost
sometimes
do
the
same
thing,
but
not
just
enough
to
make
it
different
that
that's
where
I'd
say,
there's
communality
that
could
be
gained
out
of
this.
That
may
be
probably
the
80
80
20
rule
fits
one
data
plane
model
existing
for
everybody
pick
this
one.
D
If
you
want
to
come
with
it
customize
then
it's
when
the
what
we
said
about
the
modularity
can
come
in,
but
not
Reinventing,
every
time
that
that's
right
now,
my
scare
around
that
ecosystem.
So
it's
a
trendy
thing:
everybody
will
want
to
build
their
own
version
and,
at
the
end,
I'm
going
to
end
up
with
25
versions
of
a
data
plane
using
Celia
or
appf.
So.
B
Yeah
one
of
the
things
that
I
took
away
from
the
day
today
was
there
are
a
lot
of
really
powerful
tools
operating
at
the
you
know,
language
protocol
level
right.
We
we
heard
about
grpc
HTTP,
one
TLS
interception
right
and
each
one
of
those
had
its
Matrix
of
things
that
it
could
do
and
operate,
but
that's
not
the
way
that
we
think
about
it
from
an
application
perspective
right.
Your
your
application
has
to
talk
to
you
know
your
database,
your
other
services
and
the
protocols
aren't
gen.
B
You
know
for
that
communication
aren't
generally
dictated
by
you
saying
I
want
to
instrument
my
application
with
you
know
with
doing
you
know
this
grpc
support,
because
I've
got
this
great
Library,
that's
going
to
allow
me
to
observe
it
right,
and
so
what
I?
What
I'd,
really
love
to
see,
is
an
ability
to
well
and
from
that
last
talk
we
just
saw
virtually
right.
There
are
a
ton
of
really
excellent
tools
for
data
collection
when
you
get.
E
Andrew
yeah,
so
there's
two
things
that
I
think
we
need
from
the
community
at
the
moment
and
would
help
to
contribute
to
the
community
and
I
have
an
anecdote
attached
to
one
of
them.
So
I
really
enjoyed
tomas's
talk
earlier
from
taijera
about
debugging
ebpf,
because
in
the
in
the
past
you
know,
I've
worked
on
teams
where
we
got
used
to
staring
at
the
massive
IP
tables
dump
from
the
cni
and
like
do
the
jumps
in
our
head.
E
That,
like
you,
wouldn't
necessarily
expect
a
user
of
psyllium
to
do,
and
at
that
point
we
were
staring
at
this
byte
code
and
we're
just
like.
Well,
we
know
that
it's
the
same
byte
code
for
this
pod
and
that
pod
and
this
pod's
working
and
that
pod's
not
working.
So
it
must
not
be
BPF
and
it
turns
out
that
there
was
a
race
condition
in
the
eni
allocator
in
psyllium
that
had
already
been
fixed
by
datadog.
Shout
out
to
the
engineer.
E
At
datadog
that
fixed
that
problem,
but
it
was
kind
of
like
a
wild
west
in
terms
of
debugging,
and
it
kind
of
relates
to
this
observability
question
of
how
can
we
tie
what
we
used
to
think
of
as
a
socket
with
an
IP
address?
I
mean
well
whatever
NF
tables
type
debugging
to
this
new
world
of
you?
Have
these
TC
hooks
that
can
just
redirect
flows
to
other
interfaces
and
and
that
type
of
thing
and
I
think
we're
seeing
the
tooling
be
developed.
So
it's
really.
C
I
want
to
just
kind
of
Mike
I
had
something
to
this
in
terms
of
observability
I
feel
that
let's
say
whichever
ecosystem
you're
running
in
the
kubernetes
cluster,
even
either
it's
very
mental
or
on
a
cloud
provider
and
Cloud
providers,
they
bring
their
own
sdn
layer
under
the
hood.
I
think
there
is
a
need
to
connect
all
the
context
right
now.
It
seems
like
the
context
of
each
of
the
like
observation
point.
First
of
all,
they
are
not
consistent
and
even
if
the
context
is
consistent,
it
is.
C
C
That's
great
that
you
can
get
the
application
context
along
with
the
network,
which
was
which
was
really
not
possible
if
you
were
not
running
close
to
application.
But
then,
after
that
there
are
mother
layers
views
somehow,
if
you
are
able
to
kind
of
put
together
a
context-
and
that
is
where
I
think
at
least
all
people
are
even
trying
to
solve
this
problem
for
the
and
our
own
end
users.
B
Yeah
I
think
that's
a
you,
bring
up
a
great
point
about
the
fact
that
you
know
this.
These
kind
of
this
kind
of
tooling
is
awesome
at
the
kubernetes
node
level
when
you're
when
you're.
That
close,
but
then
there's
these
other
contacts
that
get
layered
on
top
no
matter.
You
know,
especially
in
the
cloud
providers
right
where
they
they've
got
their
their
Network
layer.
On
top
of
that,
including
their
own
network
security.
B
That
then
you
get
to
you,
you
lose
the
portability
that
you
that
you're
experiencing
with
psyllium
at
the
kubernetes
layer,
then
you
still
have
things.
You
know
we're
working
on
a
product
that
was
getting
replicated
into
each
one
of
the
major
Cloud
providers
and
it's
like
yeah
psyllium
was
great
when
we
were
talking
about.
B
You
know
isolation
on
the
you
know
the
Pod
executions,
but
when
we
got
out
of
that
and
we
got
up
to
the
cloud
providers,
you
know
it's
there's
just
not
a
common
language
right
and-
and
you
don't
have
you
know-
I'd
love-
to
see
something
like
psyllium
identities
that
are
so
powerful
inside
of
a
cluster,
and
this
is
potentially
where
you
know
like
a
multi-cluster
motion.
Things
like
that
could
be
helpful
as
well,
but.
C
That
is
where
I
think
what
we
have
taken
approach
is
making
it
kubernetes
Centric.
So
as
long
as
I
think
it
is
kubernetes
first
developer.
First,
we
like
the
developer
first
model
of
kubernetes.
So
when
it
comes
to
that
model,
if
you're
able
to
annotate,
for
example,
things
that
are
being
generated,
the
the
Telemetry
and
other
things
that
are
being
generated
from
the
other
instances
in
Cloud,
if
we
have
the
similar
kubernetes
context
to
it,
at
least
it
solves
the
kubernetes
problems.
That
is
where
we
are
aligning
towards.
E
So
in
terms
of
looking
at
things
from
the
Pod
level
than
the
node
level
and
the
interconnect
level,
we
were
looking
at
Hubble
and
we
could
tell
that
if
the
Pod
was
on
the
same
node
as
the
what
appeared
to
be
a
broken
pod,
because
the
issue
was
that
the
the
IP
associated
with
the
Pod
would
be
dropped
at
Layer
Two
on
the
Amazon
side.
But
if
the
pod's
on
the
same
node,
then
psyllium
is
just
going
to
Route
the
traffic
and
it's
gonna,
it's
gonna.
E
You
know
the
flow
is
gonna
work
and
it
was
kind
of
like
we
actually
had
that
level
of
insight
where
we
could
look
at
the
node
and
luckily
we're
all
within
the
same
cluster.
So
these
things
had
like
consistent
identities
within
the
cluster,
and
so
what
was
my
point
it?
My
point
is
like
we
saw
like
earlier
today.
We
we
saw
that
the
next
version
of
Hubble
is
going
to
have
grafana
style,
metrics
integrated
into
it,
which
is
awesome.
E
Sometimes
you
look
at
Hubble.
You
show
someone
Hubble
for
the
first
time
and
they
don't
realize
how
powerful
it
actually
is
that
you're,
seeing
the
Flows
at
a
pod
level
annotated
with
these
identities
and
I,
think
that's
going
to
help.
Take
things
a
little
bit
to
the
next
level,
where
you're
going
to
be
able
to
correlate
yeah
metric
type
events
between
your
systems,
at
least
perhaps
visually
so
you're.
D
Going
to
see
on
how
much
trouble
I
am
from
observability
me,
I
have
to
think
about
communities.
Observability
with
eppf
and
I
have
to
think
about
a
5G
core
with
NW
daf
from
ggpp
that
doesn't
care
about
any
of
this.
They
have
their
own
model
I
end
up
with
a
residential
Gateway
that
does
TV
streaming
with
tr369
a
USP
model
which
has
yet
another
nut
observability
model
that
fits
so
anything
that
actually
gets
to
the
application.
Level
I'm
happy
because
that's
the
one
thing
I
don't
have
to
care
about
anymore.
D
It's
fixed
I've
got
a
bull.
I've
got
a
tetragon.
I've
got
open,
Telemetry
I
can
Jagger
trace
the
thing.
I
can
see
everything.
My
trouble
is
really
when
these
things
need
to
get
integrated
with
the
rest
I.
Now
my
my
stress
factor
goes
quite
up
because
I
have
way
more
work
there
than
in
the
cloud
piece.
So
for
me
that
that's
not
that's,
not
a
real
issue
as
of
yet
when
I.
My
issue
is:
when
you
look
at
all
that
ecosystem
and
out
and
I
need
to
have
a
correlation
around.