►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Because they offer many similar capabilities, it’s easy to confuse a Platform as a Service with a Kubernetes as a Service system, but they are fundamentally different, and that can have serious implications if you choose the wrong option. In this webinar, Mirantis’ Nick Chase explains the difference between the two and how to choose which will be better for your particular use case. Attendees will learn:
* How both systems generally work, and what they offer
* How to provide developers with ready access to the resources they need
* How to avoid hamstringing operators with too restrictive an environment
* How to determine which approach is more appropriate for you
A
All
right
we're
gonna
go
ahead
and
get
started.
I'd
like
to
thank
everyone
who
is
joining
us
today.
Welcome
today,
CN
CF,
webinar
Paz
vs.
calves
what's
different,
and
when
does
it
matter,
I'm,
Taylor
Wagoner
and
the
operations
analyst
for
CN,
CF
and
I'll
be
moderating
today's
webinar.
We
would
like
to
welcome
our
presenter
Nick
chase
head
of
technical
content.
Outrageous,
a
few
house
hi
Nick
a
few
housekeeping
items
before
we
get
started
during
the
webinar.
A
You
are
not
able
to
talk
as
an
attendee
there's
a
Q&A
box
located
at
the
bottom
of
your
zoom
screen.
Please
feel
free
to
drop
in
your
questions
there,
rather
than
the
zoom
chat
window
and
we'll
get
to
as
many
as
we
can
towards
the
end.
With
that
I'll
hand
it
over
to
Nick
to
kick
off
today's
presentation,
hello.
B
Thank
you.
Okay.
So
a
little
bit
about
me,
I
am
in
charge
of
technical
content,
former
antis,
which
means
that
I
write
about
this
stuff
for
a
living
and
I've
been
getting
pretty
deep
into
this
topic.
Lately,
I'm
also
a
former
member
of
the
kubernetes
release
team
and
I'm,
an
old-time
developer
and
the
author
of
a
bunch
of
books
and
a
slew
of
tutorials
and
a
bunch
of
stuff,
and
let's
be
realistic.
You
didn't
come
here
to
find
out
about
me.
So,
let's
just
kind
of
jump
right
into
the
topic.
Next
slide,
please!
B
Okay!
So
before
we
start,
let's
take
a
quick
look
at
what
it
is.
We're
gonna
cover
we're
gonna
start
out
by
talking
about
what
a
platform
as
a
service
and
a
kubernetes
as
a
service
actually
are
so
that
we
can
kind
of
make
sure
we're
all
on
the
same
page
so
to
speak
and
and
then
we'll
look
at
what
each
one
of
them
does
well
and
also
not
so
well.
B
Finally,
we'll
look
at
some
of
the
things
that
you
need
to
ask
yourself
before
deciding
which
one
is
going
to
be
best
for
you
next
slide,
please
all
right.
So
a
quick
word
about
who
I
had
in
mind
and
when
I
was
putting
this
together,
it's
geared
towards
helping
make
technical
decisions,
but
it's
not
necessarily
leading
with
a
bunch
of
technical
terms
and
concepts.
B
That
said,
if
you
are
technical,
you
shouldn't
be
bored,
because
these
are
things
that
you
need
to
think
about
as
well.
Finally,
if
you're
just
curious
about
what
this
is
all
about,
this
presentation
is
gonna
help
you
understand
the
lay
of
the
land
so
that
you
can
figure
out
where
you
want
to
go
next
when
it
comes
to
getting
more
information.
B
I
just
want
to
make
sure
here
for
one
moment,
though
yeah
okay,
that
was
just
my
view.
That
was
weird.
Okay,
all
right,
so
I'm
gonna
be
talking
about
Paz
and
Kaz
in
general
and
of
course,
every
product
has
different
capabilities.
So
one
thing
that
you
might
find
helpful
is
to
download
a
table
that
we've
put
together
of
where
different,
Kaz
and
Paz
products
stand.
B
When
it
comes
to
each
of
these
capabilities
and
to
be
honest,
a
bunch
more
capabilities
that
I
I'm
not
gonna,
have
time
to
cover
so
feel
free
to
go
ahead
and
grab
that
it
will
give
you
a
whole
wealth
of
information
all
right.
So,
let's
get
started.
The
first
thing
that
we
need
to
do
is
settle
on
what
it
is.
We
are
actually
talking
about.
Now.
It's
really
easy
to
get
confused,
because
there
are
passes
that
work
with
kubernetes
and
their
Casas
that
offer
application
catalogs.
B
Now
if
you've
been
awhile,
if
you've
been
around
for
a
while,
this
kind
of
progression
may
look
familiar
to
you
in
the
old
days.
You
know.
Like
five
years
ago
we
had
to
distinguish
between
a
ayahs
or
infrastructure-as-a-service
and
pass
or
platform-as-a-service
and
SAS
or
software
as
a
service
now
I,
as
is
a
system
that
lets
developers
and
other
users
request
infrastructure
such
as
compute
power
and
storage,
in
a
self-service
way.
B
Obviously,
that's
where
we're
going
to
spend
time
today
now
above
that
is
SAS
or
software
as
a
service
where
users
don't
actually
stuff,
they
just
use
the
application.
That's
provides
it's
provided
to
them.
You
know,
for
example,
salesforce
is
probably
the
best-known
SAS,
but
really
you
know
virtually
any
website.
These
days
is
also
assessed
when
you
come
right
down
to
it.
So
so
that's
what
we
used
to
look
at
now.
Things
are
a
little
bit
more
complicated,
so
casts
or
kubernetes
as
a
service
is
a
kind
of
hybrid
of
these
systems.
B
B
So,
let's,
let's
do
a
definition
here
so
platform-as-a-service.
It
is
a
system
that
it's
abstracts
away
the
hardware
and
software
deployment
and
it
enables
developers
to
just
mix
and
match
components
for
application
creation.
Now
this
is
not
the
same
as
like
low
code
or
no
code
environments.
If
you're
familiar
with
those,
if
you're
not
don't
worry
about
it,
forget
I
even
mentioned
it,
but
basically
it
gives
you
a
way
to
say:
I
want
a
database.
I
want
a
web
server
here.
Are
the
parameters
I
want,
and
it's
done?
B
Okay,
so
you
don't
have
to
think
about.
Oh
I
got
to
get
a
server
and
I
got
a
the
server
up
to
the
network
and
I
gotta
get
this
I'm,
not
gonna.
Get
that
and
you
know
it's
just
you
don't
worry
about
any
of
that
and
that's
a
pass.
Okay
now
next
slide,
please
so
some
passes
that
you
may
have
heard
of
so
making
it
a
little
bit
more
concrete.
B
Cloud
Foundry
in
many
ways
is
kind
of
the
grand
old
man
of
passes,
or
at
least
the
passes
that
are
around
today
and
today
a
lot
of
people
are
using
open
shift
in
the
public
cloud.
You've
got
Google
and
Amazon
and
Microsoft,
they
all
have
their
entries
and,
of
course,
there's
Heroku
and
force
com.
You've
got
Stratus
and
and
other
open
source
projects.
B
Do
your
thing
a
next
slide,
please,
and
so
now,
kubernetes
as
a
service
is
a
much
newer
category
relative
to
pass,
but
there
are
still
multiple
cast
products
out
there.
You
may
have
heard
of
rancher
and
platform.
9
and
Moran
says
just
announced
its
own
casts
a
couple
months
ago
and
maybe
a
little
less
well
known,
VMware
and
Rackspace
have
their
own,
and
then
there
are
the
public
cloud
versions
from
Amazon
and
Google
and
Microsoft.
So
there's
a
bunch
out
there.
B
Ok!
Now,
how
do
you
tell
them
apart
if
you've
used
any
of
these?
You
know
that
there
is
often
a
ton
of
overlap.
Openshift
is
based
on
kubernetes,
so
it's
often
mistaken
for
Kansas,
but
it's
really
a
pet
Rancher
offers
an
application
catalog,
but
it
offers
the
ability
to
create
new
kubernetes
clusters
and
operate
them
independently.
So
it's
really
a
cat
and
in
some
ways
it
doesn't
really
matter
which
is
which
it's
a
matter
of
what
you
need
and
can
the
software
you
choose,
give
it
to
you.
B
Basically,
in
this
case,
we're
going
to
draw
a
line
where,
on
one
side
on
the
cast
side,
we
have
do
you
create
kubernetes
clusters
for
for
developers
to
use
and,
on
the
other
side,
is
your
primary
purpose
to
provide
these
components
to
developers
for
them
to
use?
So
that's
where
we're
drawing
the
line?
Okay!
B
So
the
primary
pardon
me
so
the
primary
feature
of
platform-as-a-service
as
I
was
saying
is,
of
course,
that
application
catalog.
This
catalog
enables
users
to
create
a
project
by
basically
hooking
together,
different
components
rather
than
having
to
deploy
them
and
confirm
them,
configure
them
individually.
B
On
the
other
hand,
next
slide
please,
on
the
other
hand,
because,
as
assumes
that
you're
only
going
to
create
applications
by
putting
together
those
pre
provided
components,
that
can
also
be
a
problem
because
you
are
locked
into
the
applications
and
specifically
the
versions
of
the
applications
that
are
provided
to
you
for
development.
This
may
not
matter
for
production
systems.
This
may
be
a
much
bigger
deal.
Also,
you
have
to
ask
the
question
of
whether
these
applications
and
versions
are
going
to
be
supported
and
upgraded
into
the
future.
B
Now
what
some
companies
do
is
they
delete
the
existing
catalog
that
comes
with
their
past
and
replace
it
with
a
catalog
of
production,
approved
applications?
It's
extra
work,
but
you
get
the
benefit
of
having
the
catalog
without
potentially
exposing
anything
due
to
security
issues.
Next
slide,
please
now
it's
it's
also
simpler.
So,
on
the
strength
side,
it's
also
simpler
in
many
ways
for
developers,
because
they
don't
really
have
to
think
too
hard
about
what
pieces
to
use.
So
you
know
you
need
a
database,
you
grab
one.
B
Of
course,
you
could
also
think
of
this
as
a
weakness,
because
nobody
thinks
too
hard
about
what
they're
linking
together,
but
ok,
next
slide.
Please
all
right
strength
from
some
perspectives
is
that
a
PEZ
gives
the
operator
a
large
amount
of
control.
It's
the
operator
who
makes
the
architectural
decisions
for
the
past,
which
in
many
ways
makes
decisions
for
the
applications
being
built.
It's
the
operator
who
does
all
the
installation
and
maintenance
and
upgrading
it's
the
operator
who
also
controls
access
to
the
past.
So
that's
great.
B
If
you
are
an
operator,
centric
organization,
next
slide,
please.
On
the
other
hand,
if
you
are
not
an
operator
centric
organization,
for
example,
if
you've
been
leaning
heavily
into
DevOps,
this
can
be
a
problem.
Developers
who
may
be
used
to
making
a
lot
of
decisions
suddenly
find
that
those
decisions
are
not
available
to
them.
B
Next
slide,
please.
So,
on
the
strength
side
has
deployments,
typically
have
everything
you
need
to
get
started.
They
have
an
existing
application,
catalog
as
we
were
saying
to
which
you
can
likely
add
components,
and
some
of
them
will
also
have
additional
pieces,
such
as
jenkins
or
some
other
CI
CD,
or
I
am
for
authentication
and
so
on.
These
may
be
built
in
or
they
may
be
bolted
on
next
slide.
Please,
on
the
other
hand,
maybe
you
don't
want
the
pieces
the
panas
has
chosen
for
you.
B
B
But
on
the
strength
side
in
today's
world,
usually
a
good
thing
that
somebody's
thinking
about
security,
but
because
you
know
it's
usually
something
that's
handled
as
an
afterthought
by
developers,
yeah
I'm,
a
developer,
I
will
cop
to
this.
We
don't
usually
think
about
that
up
front
and
that's
not
a
good
thing.
So
a
lot
of
these
past
frameworks
have
various
security
decisions
already
made
to
help
out
in
that
respect-
and
you
probably
saw
this
coming,
but
that
could
also
be
a
problem
because
you
don't
necessarily
have
any
control
over
those
security
policies
and
restrictions.
B
Okay.
So
that's
platform-as-a-service!
Now
what
about
kubernetes
as
a
service?
So
let's
go
ahead
and
look
at
the
pluses
and
minuses
there?
Okay,
so,
as
you
probably
guessed,
we're
operators
are
kind
of
the
last
word
in
pass.
Kaz
gives
more
power
to
developers
because
Kaz
just
provides
the
way
for
you
to
spin
up
a
cluster,
it's
up
to
the
developer,
to
decide
what
applications
to
run
when
to
upgrade
or
update
their
clusters,
and
and
so
on.
B
But
you
know
generally,
it's
the
it's
also
the
developer,
who
controls
security.
So
you
don't
run
into
a
situation
where
your
developers
are
hamstrung
by
overly
restrictive
environments
and,
of
course,
there's
always
a
flipside
to
that,
especially
if
you're
an
operator
who
may
be
completely
horrified
at
the
idea
of
developers
making
all
of
those
choices,
they
may
be
using
applications
that
aren't
approved
or
creating
cluster
sprawl
or
not
updating
their
clusters,
though
I
should
say
as
I
mentioned
again.
You
know
some
of
these
Casas
to
have
automated
updates
built-in.
B
B
Okay,
another
good
thing
about
kubernetes
as
a
service
is
that
it
makes
scalability
a
little
bit
easier
and
when
you
have
a
pass
system,
you
typically
have
one
large
central
one
large
centralized
system
that
everything
runs
on
and
then,
if
you
need
to
scale
horizontally,
you
need
another
big
machine
or
three.
On
the
other
hand,
if
you
have
a
small
cluster
running
on
small
machines,
you
can
just
add
some
more
of
those
small
machines.
So
that's
easier
and
of
course,
as
I
mentioned
earlier,
you
do
have
to
watch
for
cluster
sprawl.
B
B
Another
thing
we
alluded
to
earlier
is
the
fact
that
developers
can
update
or
upgrade
clusters
themselves.
But
what
that
also
means
means
is
that
when
a
cluster
is
upgraded
or
updated,
it's
just
that
cluster
that's
affected
as
opposed
to
paths
where
potentially
everything
might
be
affected
all
at
once,
if
you're
upgrading
the
the
centralized
system
so
another
advantage
of
cash,
is
that
you're
just
using
the
cast
to
create
or
manage
your
cluster
and
then
the
at
the
actual
application
is
totally
dependent
on
the
kubernetes
api.
B
And-
and
that
brings
us
to
next
slide-
please,
yes,
and
that
brings
us
to
maybe
one
of
the
biggest
advantages,
which
is
that
you
can
create
apps
that
span
multiple
clusters
or
even
multiple
clouds.
Now
I'm,
not
saying
that
this
is
impossible
with
paths.
Ok,
it's
just
more
of
a
natural
process
with
cat's-eye
I
know
you
can
do
it
with
a
pass.
B
So
this
gets
us
a
lot
closer
to
to
cloud
native
here,
okay,
so
that
is
a
lot
of
pluses
and
minuses.
But
how
do
you
decide
which
one
is
right
for
you
now?
I
obviously
cannot
tell
you
specifically
one
way
or
another
for
a
lot
of
reasons.
First
off,
of
course,
you
know
that
every
case
is
different,
but
also
every
path
and
kaz
are
different
too.
So
you
need
to
ask
yourself
some
questions
and
then
look
at
the
specific
product
you're
considering
to
see
whether
it
does
what
you
need
it
to
do.
B
Okay,
so
let's
look
at
some
of
those
questions.
First
thing
you
need
to
think
about
is
to
decide
what
you're
trying
to
accomplish
in
the
first
place.
Do
you
already
have
applications
and
you're
just
focusing
on
deployment?
You
know
that
path
might
not
be
right
for
you
in
that
case,
you're,
probably
looking
for
more
of
a
chasm.
On
the
other
hand,
if
you
are
coming
at
this
more
of
a
Greenfield
thing,
maybe
path
sounds
like
a
better
idea.
B
Next
slide,
please,
on
the
other
hand,
if
you
are
dealing
with
developers
who
maybe
need
more
help
in
getting
things
set
up,
then
you're
more
likely
to
want
a
pen.
Maybe
you
have
specific
applications
that
you
would
like
them
to
use
now
that
doesn't
mean
that
you're
necessarily
going
to
go
with
pens,
because
you
could
use
a
cast,
but
a
cast
that
has
a
robust,
say,
image
directory
that
you're
going
to
require
your
developers
to
pull
from.
So
you
gotta
weigh
these
things.
B
Next
slide,
please
flexibility
is
another
issue.
Do
you
have
internal
systems
you
want
to
tie
into?
Are
you
married
to
a
specific
networking
infrastructure?
These
are
things
that
you
need
to
consider,
because
you
need
to
make
sure
that
whatever
system
you
choose
enables
you
to
do
what
it
is
that
you
need
to
do
next
slide,
please
same
thing
for
multi
cluster
or
multi
cloud
apps.
B
If
there's
even
a
chance
that
you
may
need
to
move
to
another
provider
at
some
point,
you
need
to
make
sure
that
that's
possible,
and
these
days
most
apps
are
multi
cluster
in
some
form.
So
that
is,
that
is
a
really
big
deal.
The
days
of
the
monolithic
application
are
well
I,
don't
think
they're
over,
but
they're
definitely
numbered,
especially
with
you
know,
edge
computing
coming
out
and
you
know,
coming
into
its
own
I
shouldn't
say
coming
out,
but
coming
into
its
own
there
are
you
really
need
to
take
that
seriously.
B
So
I
guess
what
it
comes
down
to
is
the
question
of
how
predictable
are
your
plans?
Where
do
you
think
you
may
need
flexibility
in
the
future
and
you
need
to
make
sure
that
that
flexibility
is
there?
Okay,
okay!
So
that's
a
lot
of
little
details,
but
what's
so
I
would
encourage
you
to
go
ahead
and
download
the
download
the
comparison
table
to
get
a
feel
for
what
products
are
gonna.
B
Give
you
what
capabilities,
because,
like
I
said
there
are
a
bunch
of
things
that
I
didn't
even
talk
about,
like
you
know,
can
you
deploy
on
bare
metal
and
how
long
does
it
take
to
deploy
Hauer?
How
is
multi-tenancy
handled
and
stuff
like
that?
You
know
what
kind
of
ingress
is.
You
know,
there's
just
there's
a
lot
of
stuff,
so
let's
so
I
would
encourage
you
to
go
ahead
and
grab
that
that
spreadsheet
all
right,
so
I
guess
that
we
can
now
go
ahead
and
move
on
to
questions.
B
B
Let's
me
see,
can
you
talk
more
about
why
you
consider
open
chef
to
be
more
of
a
pass
than
a
cast
all
right?
Let
me
preface
this
by
saying
that
I
am
NOT
an
expert
in
open
show
and
that
most
of
my
experience
with
OpenShift
has
been
OpenShift
3,
which
is
not
the
most
recent
version
and
that
OpenShift
4
does
make
a
lot
of
kind
of
CAHSEE
changes.
B
Openshift
2
to
my
understanding,
was
designed
to
be
more
of
a
pass.
It
was
designed
to
provide
these
I
want
to
say
they
were
originally
called
cartridges,
but
I
may
be
thinking
of
something
else:
I'm
pretty
sure
they
were
cartridges
and
they
were.
It
was
designed
to
provide
that
functionality
in
terms
of
you
know,
giving
people
this
ability
to
use
this
functionality.
B
A
B
B
Exploding
in
the
next
couple
of
years,
based
on
the
fact
that
kubernetes
is
exploding
and
people
need
to
need
to
be
able
to
use
it.
So
I
definitely
definitely
say
that
Kaz
is
something
to
watch
out
for
all
right.
Let's
see
if
the
applications
are
written
for
a
chaos
or
eks
or
PKS,
that
will
also
have
a
locking
with
the
respective
provider
API.
So
anytime,
you
are
using
provider
API
as
opposed
to
the
kubernetes
api.
B
You
are
locking
into
that
provider
that
that
is
sort
of
the
definition,
and
in
fact
that
is
that
is
part
of
the
why
these
providers
give
you
those
api's
I,
mean
think
about
it
for
a
minute.
If
your
Amazon
and
you
have
a
great
thing
to
allow
people
to
do
with
kubernetes,
you
have
two
choices.
You
can
build
it
and
contribute
it
to
the
kubernetes
community
so
that
anybody
using
kubernetes
can
use
it
or
you
can
make
your
own
API
and
you
know,
make
it
available.
B
B
B
B
This
caste
provision
nodes
across
a
cluster
or
even
multiple
pods
in
a
node,
okay,
so
I
think
we
need
to
make
the
distinction
between
provisioning,
kubernetes
and
provisioning
an
application
on
kubernetes
okay.
So
what
Kenz
does?
Is
it
provisions
the
actual
kubernetes
cluster?
So
Ken
starts
out
with
empty
hardware
nodes
well,
not
empty.
They
presumably
have
an
operating
system
on
them.
B
What
I've
got
is
an
empty
kubernetes
cluster
with
no
applications
no
pods
on
it,
except
you
know
the
ones
to
normally
run
it,
but
then,
when
I'm
going
to
provision
the
application,
that's
when
the
normal
kubernetes
scheduler
comes
into
play.
Now,
if
you
have
a
pass
or
a
Kaz
that
has
an
application
catalog,
for
example,
I
was
mentioning
some
of
the
Casas
do
have
application
catalogs.
They
may
go
ahead
and
spread
those
pods
over
multiple
nodes
that
have
been
provisioned
by
the
cats.
B
B
B
However,
and
we'll
say
that
would
be
a
good
topic
for
a
TCO
calculator.
I
just
published
an
article
on
TCO
assumptions,
and
there
are
so
many
things
that
you
have
to
think
about,
because
it's
it's
a
matter
of
resources,
you
know,
are
you?
Are
they
public
cloud?
Are
they
private
cloud
if
they're
private
cloud?
What
do
you
you?
You
have
to
pay
for
electricity
and
cooling
and
your
admins,
and
if
it's
public
cloud,
you
still
need
admins
to
to
help
your
internal
people
and
to
manage
everything
else
there.
B
Our
open
source
caz
solutions
out
there
or
do
most
people
resort
to
ansible,
Kumud
men
automation
to
stand
up
their
clusters.
This
may
only
be
relevant
to
organizations
that
run
kubernetes
on
Prem
yeah
I
think
it
is
probably
only
relevant
to
them
and
I
think
that
at
that
point
you
have
to
ask
yourself
what
what
you
consider
to
be.
B
B
Is
it
possible
to
have
a
pass?
That's
also
a
Kaz
yeah.
Certainly
in
fact
we're
saying
you
know,
OpenShift
probably
does
both
at
this
point
at
least
an
open
shift
for,
but
I
I,
don't
know
this
for
sure.
Like
I
said
most
of
my
experiences
with
three,
but
there's
no
reason
that
a
pass
could
not
deploy
kubernetes
clusters
as
if
they
were
other
applications
and
again,
there's
no
reason
a
caste
can't
offer
you
a
an
application
catalog
and
a
lot
of
them
do.
B
B
B
Yes,
mer,
anthis
does
have
its
own
cast
coming
out.
If
you
want
to
be
involved
in
the
private
beta,
certainly
let
me
know
and
chase
at
Miranda's
comm.
That
is
fine.
Let's
see
what
other
questions
we
have.
We
do
have
some
more
time.
So
if
you
have
any
more
questions,
please
go
ahead
and
drop
them
in
the
Q&A
and,
if
not
I,
think
we
are
going
to
going
to
give
you
back
the
next
14
minutes
of
your
life
Taylor.
What
do
you
think
sounds.
B
Do
we
do
does
openshift
support
coop
spray?
Oh
god,
I
have
I
I,
don't
know,
that'll
go
in
the
follow-up
that'll
go
in
the
follow,
will
grab
all
these
questions
and
now
we'll
put
them
in
the
follow-up
lock,
because
I
had
no
idea,
but
I
will
find
out
for
you
specifically
just
for
you.
Okay
I
do
want
to
thank
everybody
for
putting
up
with
my
rambling
thanks.