►
From YouTube: Kubernetes for Product Managers Part 3
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
Hi
it's
victor
again
and
based
on
popular
demand.
Now
I
have
a
part
three
of
the
kubernetes
for
product
manager
series.
A
One
might
say
this
should
be
part
one,
because
what
we
are
going
to
speak
about
are
the
basic
building
blocks
of
the
cloud
native
ecosystem.
So
to
say
that
is
terraform
kubernetes
and
docker
what
they
are,
what
they
are
and
how
do
they
fit
together
into
something
that
we
haven't
spoke
spoken
about
in
the
previous
videos,
so.
A
What
the
buzz
is
about,
first
of
all,
what
is
docker
docker
r
is
container
technology.
There
are
other
container
technologies
as
well,
but
docker
is
the
most
well
known
the
most
popular
and
the
one
that
kubernetes
and
other
tools
are
built
upon.
So
we
are
only
focusing
on
that
from
a
use
case
perspective.
A
The
package
stage
is
really
really
central
to
the
whole
devops
lifecycle,
because,
basically,
that's
where
the
development
team
handles
over
a
container
to
the
devops
team,
just
so
to
say
or
to
the
ops
part
of
the
organization
and
containers
are
the
standard
interface
that
from
the
outside,
it's
totally
standard,
while
the
developers
know
what's
inside
and
the
operators
don't
have
to
know
what's
inside
now.
What
kubernetes
is
kubernetes
is
a
programmable
api,
as
we
have
seen,
but
by
by
default.
A
This
is
a
container
orchestration
engine,
so
what
kubernetes
does
is,
if
you
have
microservices,
that
means
that
you
will
have
hundreds
or
thousands
of
containers
running
to
provide
your
services.
Managing
containers
at
that
scale
is,
is
a
problem.
It's
an
issue
and
that's
where
kubernetes
comes
into
the
play,
because
it
will
spin
up
new
containers
of
a
specific
kind
when
node
increases
it
checks.
Whether
containers
are
healthy.
If
they
are
not,
then
it
restarts
them
and
it
orchestrates
all
these
containers
based
on
load
and
requirements
again
going
back
to
the
application
developer
perspective.
A
A
How
this
is
done?
It
depends
on
a
company
by
company
basis,
but
that's
the
basic
idea
that
we
don't
want
developers
to
work
on
kubernetes.
We
want
them
to
work
on
the
application.
Logic
create
a
container
perhaps,
but
even
that
might
be
taken
over
by
the
platform
team
and
then
developers
just
get
the
metrics
and
the
logs
and
know
how
to
troubleshoot
things
when
needed.
A
The
third
topic
that
was
mentioned
as
a
question
was
terraform,
so
terraform
is
actually
used
to
set
up
the
basic
infrastructure
to
create
the
kubernetes
cluster
itself.
That's
what
you
can
use
start
from
for
you
can
create
any
anything.
You
can
run
any
action
with
trafform
that
has
an
api.
You
can
think
you
can
think
of
a
traffic
actually
as
a
layer
on
top
of
the
apis.
That's
why
gitlab
has
a
traffic
provider.
A
So,
if
you
want
you
can
manage
your
gitlab
instance
with
trafford.
You
can
create
gitlab
projects
set
up
gitlab
users
and
all
kinds
of
stuff
with
that.
But
the
same
is
true
for
aws,
you
can
use
star
form
to
start
a
new
vpc
to
start
a
new
kubernetes
cluster,
set
up
users
and
rows
within
aws
and
manage
those
attach
them
to
the
cluster.
To
everything,
and
once
you
created
this
cluster
using
trafform,
then
you
have
your
kubernetes
cluster.
A
Now
what
I
have
seen
that
application
developers
often
don't
even
know
what
terraform
is,
they
might
not
even
know
about
its
existence.
Actually
they
might
have
heard
about
cloud
formation,
which
is
an
alternative,
an
aws,
specific
alternative
for
for
the
same
functionality,
but
basically
platforms,
often
just
totally
unknown
to
them
as
a
technology.
A
So
this
is
how
these
things
get
together
and
seriously
what
I
think
it's
it's
nice
idea
to
know
what
the
different
users
know
about
these
technologies,
especially
as
git
labs
focus
is
on
the
developer
that
we
want
to
be
developer
first.
This
means
that
actually,
they
work
and
building
the
container
and
every
other
work
is
to
support
the
application
developers
so
that
they
can
focus
only
on
the
application
logic.