►
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
Open
service
mesh
is
a
lightweight
extensible
cloud
native
service
mesh
that
you
can
utilize
to
quickly
secure
the
communications
of
your
services
running
in
the
kubernetes
environment.
Osm
takes
the
approach
of
providing
a
simple
way
to
get
the
core
features
and
functionality
needed
without
over
complicating
the
operational
experience
to
secure
your
cloud
native
workloads
in
the
following
demo.
We're
going
to
show
you
how
you
can
easily
enable
the
osm
add-on
to
an
aks
cluster
and
configure
it
to
protect
existing
services
running
in
the
cluster.
A
A
A
A
And
we
already
had
this
in
the
config
file,
so
we'll
just
simply
overwrite
it,
and
then
we
will
check
our
current
context
to
ensure
we're
on
the
brand
new
cluster
which
we
are
and
then
next
what
we'll
do
is
we'll
just
list
all
of
the
aks
add-ons
again.
This
is
a
brand
new
cluster,
so
we're
not
expecting
anything.
A
So
this
should
come
back
as
null
and
now
we're
on
to
deploying
the
bookstore
apps.
We
got
three
manifests
or
yamls
that
we're
going
to
deploy
the
first
one
is
going
to
be
the
book.
Buyer.
A
Next,
we'll
just
take
a
look
at
all
of
the
components
in
our
bookstore
namespace
and
we're
just
verifying
that
we
do
have
pods
up
and
running
with
services
here
and
then.
What
we're
gonna
do
is
we're
gonna
trail,
the
logs
of
the
book
buyer
pod
here,
so
we'll
go
ahead
and
query
to
get
it
and
then
what
we're
going
to
do
is
just
tell
the
logs
coming
out
the
book
buyer
to
ensure
that
it
is
talking
to
the
bookstore
service.
A
And
here
we'll
stop
the
log.
And
you
see
that,
yes,
we
are
connecting
to
the
bookstore
service
and
we
have
our
200
okay
and
you'll
notice.
The
server
is
in
a
and
so
when
we
deploy
the
envoy
sidecar
proxy
you'll
see
that
change
to
envoy
next
thing
we'll
do
here
is
we'll
go
ahead
and
enable
the
osm
aks
add-on.
A
And
that's
been
enabled,
and
what
we'll
do
is
we
will
just
query
for
that
specific
add-on
to
ensure
that
it
is
installed
onto
the
cluster
which
we're
going
to
true
back
and
so
the
next
steps.
What
we're
going
to
do
is
do
a
light
test
just
to
see
and
ensure
that
the
osm
add-on
is
correctly
installed
and
functioning.
A
Also
we're
going
to
take
a
look
at
the
pods
for
the
osm
controller.
It's
up
and
running
we'll
then
take
a
look
at
the
services
here
in
the
coupe
system.
Namespace
and
you'll
see
that
there
are
three.
We
have
an
osm
config
validator,
an
osm
controller
as
well
as
the
osm
injector
or
part
of
the
osm
add-on
service
and
then,
finally,
here
we're
going
to
query.
There's
a
configuration
config
map
and
one
thing
to
notice
here-
is
the
permissive
traffic
policy
mode
setting.
A
We
will
be
changing
that
setting
showing
how
the
access
works
for
the
osm
service
mesh
next
thing
we'll
do
is
we
will
need
osm
to
manage
the
namespaces.
A
A
A
And
now
you
see
that
it
has
a
ready
state
of
two
of
two
meaning
that
that
envoy
sidecar
has
been
injected
next
to
our
application
container.
And
we
can
quickly
view
that,
let's
query
to
get
the
book
buyer
again
and
then
we'll
do
a
describe
on
it
and
we'll
look
at
both
of
the
containers
that
make
up
that
pod.
A
And
then
again,
since
we
are
in
permissive
mode,
let's
go
ahead
and
just
check
to
see
that
the
book
buyer
can
still
communicate
to
the
bookstore
service,
which
it
can
and
so
we're.
Seeing
now
the
envoy
setting
here
that
that
communication
is
being
transversed
through
the
envoy,
sidecar
proxy
and
then
we'll
take
a
look
at
the
config
map,
configuration
and
we'll
go
ahead
and
actually
change
the
permissive
traffic
mode
policy
to
false.
A
A
A
So
now
we're
gonna
showcase.
The
traffic
split
first
thing
that
we're
gonna
need
to
do
is
actually
deploy
that
additional
bookstore
v2
service,
so
there's
just
an
additional
service
out
there
and
that
will
all
automatically
contain
the
smi
traffic
access
policies
as
well,
and
then
we
will
deploy
our
traffic
split.
A
So
we
will
apply
that
smi
traffic
split
policy,
and
now
what
we
can
do
is
we
can
tell
the
logs
specifically
looking
for
the
identity.
So
this
is
the
the
identity.
Property
is
going
to
actually
show
us
which
service
that
we
are
talking
to
and
what
you're
seeing
here
is
the
output.