►
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
Welcome
to
network
segmentation,
let's
go
over,
how
you
would
analyze
the
health
of
your
network
security
for
a
payments
application.
So
in
this
case
I
have
all
my
name
spaces
in
the
square
box.
As
you
see
here,
and
each
of
the
dots
represents
a
set
of
pods
and
deployments
running
within
that
namespace
and
the
line
between
these
represents
the
active
connections
and
what
I'm
concerned
about
is
my
payments
namespace.
So
I'm
going
to
look
at
and
hover
over.
A
My
mastercard
processor,
which
I
can
immediately
see,
has
an
ingress
flow
over
tcp
and
port
8080
from
my
gateway.
My
gateway
has
three
egress
flows,
one
a
couple
to
my
coop
system:
namespace
one's
going
to
my
api
server.
I
can
also
see
my
api
server
talking
to
cube
dns,
and
these
are
all
things
that
I
would
expect
now.
If
I
click
on
allow
connections.
A
However,
I'm
going
to
notice
a
couple
things
one,
my
mastercard
processor
doesn't
have
any
network
policies
on
it
and
neither
does
my
gateway,
meaning
anything
is
allowed
in
my
environment
and
any
connection
is
allowed
for
ingress
and
egress.
Traditionally
this
is
hard
to
answer,
but
one
of
the
things
that
stack
rocks
is
able
to
do
is
help
you
generate
a
network
policy
ammo
that
you
can
directly
apply
to
kubernetes
based
on
the
behavior
of
the
network.