►
From YouTube: Intro to the Cloud Native Maturity Model - Danielle Cook, Simon Forster, Robbie Glenn & John Forman
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). 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.
Intro to the Cloud Native Maturity Model - Danielle Cook, Fairwinds; Simon Forster, Stakegy; Robbie Glenn & John Forman, Accenture
Since 2021, the Cartografos Working Group has produced the Cloud Native Maturity Model. In this session, the chairs will review the Cloud Native Maturity, discuss the latest updates and inclusions and solicit participation in the group.
B
So
the
cartographos
working
group,
just
to
give
you
an
overview
of
who
we
are.
We
were
a
group
that
came
together
last
year
to
try
and
provide
some
tooling
for
the
end
user
community
on
what
is
this
cloud-native
landscape?
How
do
you
navigate
it
and
where
a
group
that
works,
we
meet
regularly
to
talk
through
different
pieces
of
content
and
really
provide
as
many
tools
as
possible
to
get
people
into
cloud
native
and
using
it
successfully.
D
Yeah,
so
why
another
model
right?
We
have
the
landscape,
it's
very
good.
We
have
the
trail
map,
it
teaches
us
how
to
get
to
kubernetes
right.
Well,
the
landscape
is
very
hard
to
read
right.
We
have
an
interactive
model
where
we
can
dive
into
bits
and
pieces,
but
it's
constantly
growing.
It's
constantly
evolving.
How
do
we
keep
up
right
as
an
organization?
How
do
we
plan
over
two
years?
A
So
there
are
five
stages
to
the
maturity
model.
We
have
level
one
which
is
build
level,
two
operate
level,
three
scale
level,
four,
improve
and
level
five
to
optimize.
It's
important
to
recognize
that
at
level,
one
where
we
start
the
journey
is
not
a
baseline.
It's
not
a
baseline
of
zero
you're,
not
starting
with
nothing
rather
at
level.
One.
It's
pre-production!
A
It's
non-development,
we're
testing
getting
starting
to
understand,
kubernetes
and
related
cloud
native
technology
level.
Two
operate
is
the
first
step
into
production,
so
kubernetes
is
there
it's
implemented
level
three
is
for
scaling
out.
Okay.
This
is
where
you
really.
The
organization
is
committed
and
well
on
its
cloud
native
journey
level.
B
B
We
saw
a
theme
around
policy
like
what
do
you
need
to
put
in
place
for
compliance?
What
what
security
regulations
do
you
need
to
meet?
There
was
the
process
of
okay.
How
are
we
going
to
organize
our
workflows?
What
are
we
going
to
do
with
ci
cd,
and
then
there
was
the
business
outcomes.
Why
are
you
actually
doing
this
and
in
each
stage
like
what
should
you
be
able
to
demonstrate
to
your
business
leaders
to
your
board
to
your
c
level?
You
know
all
of
that
presented
itself.
C
All
right
so
robert
mentioned,
you
know
mature
models
and
frameworks.
All
those
great
things,
that's
nice,
but
what
we
want
to
talk
about
is
the
journey.
What
is
your
journey
to
cloud
native
right?
The
cncf
is
great,
with
doing
a
great,
you
know,
incubating
new
projects
right
to
to
production,
but
how
do
we
take
these
things
actually
do
something
with
it
once
which
is
out
there
in
the
world.
So
in
the
past
we
had
journeys
to
the
cloud
with
journalists
to
devsecops,
but
now
it's
turned
to
cloud
native,
and
this
has
to
be.
C
The
discussion
is:
how
do
we
get
the
cloud
native
you
know,
and
as
we
do
this,
though
one
important
aspect
is
technical
debt-
is
that
when
we
at
this
early
in
the
stage,
is
you
have
to
go
through
your
landscape?
Understand
what
tools
am
I
going
to
take
on
this
journey
in
my
new
luggage
and
what
luggage
am
I
going
to
leave
at
home?
I
only
take
what
I
need
otherwise,
it'll
get
more
complex
and
you
never
you're
going
to
get
to
the
next
journey
level.
C
Just
don't
go
straight
from
zero
to
hero,
it
won't
work.
Okay
and
then
you
know
also
in
the
early
stages
be
manual,
don't
go
crazy
in
automating
on
day
one
you'll
get
there,
but
right
now
you
have
a
lot
of
gaps
in
your
skills
in
your
environment.
So
don't
go
too
crazy.
Let's
just
begin
this
journey.
The
right
way.
D
And
by
level
two,
you
are
moving
into
production,
so
you're,
taking
all
of
that.
Those
skills
that
you've
built
in
level
one
all
that
governance
and
you're
really
trying
to
take
that
into
production
and
and
and
bring
some
some
value
that
you
can
show
to
your
business.
That
kubernetes
is
real.
We
have
the
this
competency
and
we
can
really
you
know,
change
our
business
with
this.
D
There's
gonna
be
a
focus
on
still
smaller
teams,
cross-functional
teams,
very
bright
people
right
and
you're
gonna
get
those
pockets
of
of
strong
skills
in
those
cross-functional
teams
that
you're
gonna,
you
know
build
your
competency
on.
That's
gonna
lead
you
to
level
three,
which
is
scale
right,
and
it's
not
talking
about
scaling
your
workloads,
because
you're
already
doing
that
you're
already
in
production
right,
so
we're
talking
about
scaling
your
teams.
How
do
we
replicate
the
this?
D
This
knowledge
that
we've
incubated
right
and
take
that
to
other
teams
within
your
organization?
How
do
we
grow
that
right?
And
so
that's
gonna
be
a
bunch
of
different
things,
but
a
lot
of
it
is
around
standardization,
those
very
bright
people
in
those
cross-functional
teams.
They're
going
to
you
know,
be
elevated
to
almost
a
center
of
excellence
and
they're
going
to
build
some
standardized.
D
You
know
tools
that
we
can
share
with
the
rest
of
the
organization
so
that
they
can
bring.
You
know
themselves
up
to
that
level
of
of
skill
very
quickly,
there's
also
going
to
be
a
heavy.
You
know
emphasis
on
the
business
side
of
it,
because
now
you
know
the
the
this
is
something
that
we're
able
to
use
as
our
primary
you
know,
driving
force
behind
our
compute
and
the
business
has
to
be
on
board
and
really
buy
into
that.
D
C
C
My
staff
is
getting
their
skills
in
place,
they
feel
more
comfortable
with
new
technologies
and
we're
really
moving
ahead
where
we
need
to
be-
and
at
this
point
I'm
beginning
to
kind
of
level
off,
I'm
very
comfortable
we're
at
this
level
we're
able
to
scale
at
this
point
and
really
go
full
production
with
full
devstock,
ops
and
everything
else.
That's
going
on.
You
can
kind
of
consider
this.
You
talk
with
state
when
we
talk
to
people
out
there
in
history.
This
is
kind
of
where
they
want
to
hit.
C
This
is
their
goal
is
to
be
at
this
level
and
during
the
process
you
can
even
do
things
now.
You
know
I
can
manage
my
things
now
I
can
match
kpis.
I
really
measure
things
to
see
where
we
are.
Are
we
really
improving?
You
know
is
cloud
native
worth
it?
Why
am
I
here?
I
can
actually
measure
these
things
now
and
the
really
cool
things
that
I'm
saying
right
now
at
this
level
is
you
know
in
the
past?
I
would
go
to
cxos.
They
go
john
open
source
get
out
right,
but
today
it's
changing.
C
They
are
not
becoming
the
thought
leaders
now,
where
the
ceos
the
cxos
have
watched
corporations
are
the
thought
leaders
for
cloud
native
because
they
went
on
this
journey
and
and
adapting
this
today,
and
so
it's
kind
of
from
the
base
period.
Now
it's
gone
to
the
water
room
completely
at
this
level,.
B
So
in
level
five,
it's
about
optimization,
so
you
have
gone
through
the
journey.
You
have
made
a
bunch
of
decisions,
you
have
improved
those
decisions,
but
now
you've
reached
your
master
level.
Your
team
is
skilled.
Everybody
knows
what
they're
doing,
but
you
might
have
made
some
decisions
that
aren't
necessarily
the
right
decisions
that
you
want
to
revisit.
B
You
might
want
to
be
looking
at
or
you
will
be
looking
at.
How
do
I
automate
as
much
of
this
as
possible
you'll,
also
at
that
point,
be
figuring
out
what
the
new
tools
are
in
the
market
like
we
are
rapidly
evolving.
There's
new
projects,
all
the
time,
so
you'll
be
revisiting
those
and
looking.
What
do
you
need
to
add
to
your
system,
your
environment
and
really
here
like
this-
is
where
we
want.
You
know
everybody
to
reach,
and
hopefully
many
of
you
are
like
I'm
doing
that
now.
B
Everything's
good,
and
this
is
where
we
want.
You
know
contributions
back
to
the
community.
What
have
you
developed
in
your
environment
that
you
can
give
back
to
the
cncf
or
you
know,
add
to
a
new
project
join
this
working
group.
There's
plenty
of
things
to
get
involved
in,
like
the
experience
you
have
at
this
optimization
phase,
this
level
five
is
vital
to
join,
to
share
with
the
community.
A
A
A
We
really
need
to
keep
making
sure
that
the
that
the
model
stays
relevant
and
changes
and
then
finally
we're
pushing
we
try.
We
want
to
keep
up
with
the
leading
edge
of
technology
and
what
the
cncf
has
as
its
mission,
and
this
means
that
we
need
to
have
contributions
from
people.
We
need
to
keep
it
fresh
and
we
would
really
like
to
encourage
and
invite
all
of
you
within
the
cloud
native
community
to
contribute
to
this.
A
A
We
have
a
number
of
published
artifacts.
Everything
that
we've
done
within
the
working
group
is
within
the
cartograph
repository
in
the
cncf
organization
and
github,
and
we
do
have
a
series
of
reference
documents
there
that
you're
very
welcome
to
read
and
we
encourage
pull
requests
and
issues
as
well.
We'd
love
your
feedback
on
that.
A
C
So
with
that,
there's
also
called
for
action
as
well.
You
may
be
thinking
you
know,
john
robbie
danielle
simon,
I'm
never
technical,
but
I
do
want
to
contribute
the
beautiful
thing
about
this.
Is
it's
documentation?
It's
not
coding
to
build
this
model
out,
so
everybody
here
in
this
room
and
whoever's
listening
from
the
interwebs
can
also
contribute
to
this,
and
we
invite
you
to
do
that.
You
know
we
have
some
new
members
as
well
to
introduce.
C
D
C
D
B
We've
just
done
a
whistle-stop
tour
like
the
fastest
speed-dating
version
of
this
maturity
model.
There
is
a
lot
of
material
behind
this,
so
you
can
go
onto
our
github
page
and
there
are
right
now
it's
separated
into
the
prologue,
the
people,
the
process,
the
tech
you
can
dig
through
it.
We
added
business
outcomes
to
it
this
year,
so
that's
new
in
the
model
and
we
have
been
refining
it.
So
there
are
a
ton
of
links
available.
A
C
Did
I
mention
I'm
an
author?
Have
they
mentioned
that
once
or
twice?
Well,
so
is
everybody
else
on
the
stage?
So
during
this
process
we
also
wrote
a
book
about
this
betrayal
model
to
make
it
more
fun
and
it
may
be
a
friend's
adventure.
Definitely
go,
go
buy
the
book
at
this
bookstore
and
maybe,
if
you're
lucky
enough,
we
got
to
show
up.
He
may
be
signing
the
book
for
you
as
well.
C
A
We
do
have
a
booth
here
at
kubecon,
it's
within
the
cncf
project
area
and
we'd
love
to
see
you
afterwards.
We
do
have
extra
printed
copies
of
the
model
for
those
of
you
who
didn't
receive
them
when
you
came
in,
we
have
stickers
and
of
course,
if
you
have
a
copy
of
admiral
bash's
island
adventure,
we'll
sign
it
for
you
as
well.
E
E
C
So
remember
back
in
the
day
when
everybody's
just
say,
nobody
got
fired
for
buying
ibm.
Remember
that
well,
I
started
to
say
nobody
ever
got
fired
for
buying
kubernetes
and
they
said
kuberwoodies.
I
said
kubernetes
and
I
started
the
conversation
with
them,
trying
to
position
it
at
that
level.
It
was
in
the
beginning.
It
was
very
difficult.
In
the
beginning,
the
developers
were
making
this
stuff
fun
in
the
basement
and
on
top
they're
like
open
source,
we
don't
want
it.
It's
dangerous.
It's
scary,
we're
very
comfortable
doing
this.
C
F
E
B
That's
why
we
added
the
business
outcomes
to
the
section,
so
we
could
each
each
area
we
could
say.
This
is
how
you
need
to
be
communicating
the
benefits
of
this,
so
that
it
isn't
it's
some
guidance
that
can
inspire
some
ideas
so
that
when
you're
starting
on
your
journey,
you
know
it
might
be
one
person,
two
people,
a
few
people
who
have
played
around
with
some
cloud
native
tools
and
now
they
want
to
take
it
to
the
business.
We
have
provided
that
language
in
it.
A
Specific
to
the
point
of
our
relationship,
so
the
charter
of
this
group
is
that
it
does
not
in
any
way
attempt
to
dictate
to
the
cncf
any
technical
decisions
or
any
decisions
around
projects.
So
we
explicitly
do
not
participate
in
that.
It's
not
a
role
of
of
this
group.
It's
rather
to
assemble
artifacts,
to
help
in
communicating
that
so
so
we're
there
to
to
help
provide
what
the
cncf
already
does
and
in
the
format
that
might
be
helpful.
C
C
D
And
I
think
we
you
know,
draw
from
the
group
the
the
different
either
working
groups
and
sigs
and
and
the
projects
themselves.
I
mean
we
invite
members
of
the
project
teams
to
to
tell
us
how
to
you
know,
incorporate
you
know
the
the
pieces
of
of
your
project
that
are
going
to.
You
know
really
bring
value
to
to
the
to
the
customer.
So
I
mean
again
we're
not
making
any
kings,
but
if
there's
something
new-
and
you
know
valuable-
that
that
we
can
incorporate
as
a
a
feature.
D
G
C
I
think,
if
you
look
at
those
models,
they
were
not.
They
were
not
poor
in
the
cloud.
This
is
board
in
the
cloud.
That's
the
difference.
So
if
you
take
that
those
initiatives
you
can
have,
it
could
be
very
clunky
and
you
can
make
a
wedge
fit
in
a
round
hole
or
a
square
pick
a
round
hole,
that's
going
to
go
versus
something!
That's
that's
built
for
the
cloud
already
right,
so
it's
kind
of
like
you
know,
that's
one,
that's
one
from
the
other
frame
story.
C
C
B
And
the
way
the
model
was
built,
so
the
reason
it's
it's
us
sitting
here
is
we'd
all
put
together
different
maturity
models,
looking
at
it
from
different
points
of
view,
and
so
we
came
together
from
our
skills
at
our
organizations
having
built
environments
for
companies
and
scaled
them
and
said
like
well.
What
are
the
common
things
that
have
happened
so,
with
all
of
the
three
different
models
we
were
able
to
pull
together
this
kind
of
one
umbrella
from.
H
So
obviously,
software
security
is
a
big
hot
topic
right
now
and
there's
a
lot
of
different
efforts
going
on.
So
there's
like
the
open,
ssf
and
the
supply
chain
stuff
and
there's
this:
how
much
do
you
all
talk
to
each
other
and
sort
of
try
to
dovetail
your
recommendations
versus
each
working
on
your
own
piece
and
getting
your
own
assessments.
C
So,
two
years
ago
I
I
led
the
group
to
create
the
cks
exam.
I
actually
I
I
spearheaded
the
development
for
cks
because
of
all
the
knowledge
I
have
based
on
these
things,
and
so
I
worked
obviously
with
I.
Let
them
speak
as
well,
but
we
kind
of
used
that
dialogues,
along
with
our
best
knowledge,
to
create
that
end
of
the
day.
Your
security
supply
chain
is
very
critical.
Security
is,
is
never
a
first-class
citizen.
Even
today
we
speak
to
clients,
they
think
about
security.
It
is
never.
C
B
As
part
of
our
process
we
reached
out,
so
we
did
our
initial
launch
of
the
cloud
native
maturity
model
and
then,
over
the
last
six
months,
we
met
with
all
the
tags
and
presented
it
to
them
and
invited
feedback,
help
us
out
you're
the
expert
in
security
you're,
the
expert
in
storage,
whatever
the
tag
group
was,
and
so
we're
trying
to
get
as
much
feedback
from
the
tags
as
possible,
because
we
aren't
the
tag
on
security.
So
we
need
that
input
and
what
we
want
to
do.
B
The
goal
is
to
have
the
cloud
native
maturity
model
linked
to
all
of
the
content
that
the
other
organizations
or
the
other
groups
within
the
cncf
are
creating
so
that
as
a
user,
you
can
go
and
go
okay.
I
understand
that
this
is
where
I
should
be
on
my
journey.
Here's
this
paper
from
the
tag
security,
here's
this
paper
from
the
tag,
storage
group
and
it's
this
kind
of
master
repository.
If
you
will.
H
My
actual
my
question
was
actually
slightly
different
than
within
the
cncf.
It's
that
there
seems
to
be
a
variety
of
different
linux
foundation,
foundations
which
are
all
tackling
aspects
of
the
security
model,
and
so,
for
example,
if
you're
trying
to
do,
reproducible
builds
and
things
like
that,
maybe
having
features
in
a
cluster
make
that
easier
or
harder.
A
B
So
well
so,
within
what
we're
trying
to
say
within
the
model
is
there's
all
these
cloud
native
technologies
out
there.
You
know
amongst
the
people,
the
process,
etc,
and
so
we're
saying
you
need
to
look
into,
for
example,
cicd.
So
you
will
need
tooling
there,
or
you
know,
kubernetes
is
absolutely
mentioned
in
the
model.
Helm
is
absolutely
mentioned
in
the
model.
A
D
You
might
try
different
ways
to
to
secure
your
supply
chain
right
you're,
you
have
your
very
you
know
your
your
center
of
excellence,
trying
out
different
things
to
to
figure
out
how
best
to
get
to
that
next
level
of
of
spreading.
You
know
of
kubernetes
being
the
way
that
you
deliver
all
of
your
workloads.
C
C
You
know
I've
seen
over
the
years,
people
struggle
with
kubernetes
quite
a
bit.
They
don't
get
it
right,
the
first
time
they
they
try
different
tools
until
they
get
it.
You
know,
but
end
of
the
day.
It's
about
industry,
best
practices,
industry,
best
solutions.
What
are
they?
Who
knows
what
that
even
means
right?
C
It's
an
opinion,
but
it's
about
the
process.
If
you
follow
the
process,
most
of
the
tools
could
be
very
similar
and
in
the
day
anyway,
during
this
journey
right
as
I'm
calling
this-
and
it's
about,
you
know
again
the
cncf
great
job
of
creating
this
ecosystem.
But
now
how
do
we
manage
this
ecosystem?
How
do
we
go
from
zero
to
hero?
How
do
we
actually
implement
it?
We
need
some
kind
of
toolbox
to
do
that.
Some
kind
of
run
book
which
I'm
hoping
what
this
will
be
and
become
a
standard.
C
E
B
So
it's
definitely
early
on
in
the
development
of
you
know,
implementing
this
and
people
being
able
to
find
it
and
use
it,
and
all
that
right,
that's
part
of
us
making
sure
you're
all
aware
of
it.
I
think
what
we
all
can
say
is
we
have
been
using
it
at
organizations
and
that's
why
we
created
it,
because
we
realized
that
there
were
certain
steps
that
an
organization
needs
to
take
to
get
to.
You
know
a
mature
phase
of
this
model.
C
F
Thank
you.
My
question
is,
if
I
understood
it
right,
target
audience
is
business
in
the
end
right
and
because
things
like
a
scoring
model
and
everything
like
that
is
more
targeting
to
cios
ctos
and
those
technical
management
area
more
or
less
probably.
But
in
the
end
business
wants
to
leave
a
little
value
and
right
then,
if
they
see
benefit
out
of
it,
they
want
to
deliver
value
faster
and
so
on
and
so
on.
But
it
often
seems
that
that
the
optimize
phase
is
never
ending
right
because
there's
yeah.
A
B
So
the
target
I
we
want
this
to
be
useful
to
a
broad
range
of
audiences.
So
if
you
are
reading
the
in-depth
information,
there's
a
lot
on
the
tech
side,
there's
a
lot
on
the
process
side
so,
depending
on
the
areas
you're
reading
like
it
is
meant
for
a
number
of
different
stakeholders
within
the
organization.
C
One
problem
that
I
say
clients
is
that
they'll
start
with
one
version
of
something
maybe
open
shift
to
give
you
an
example,
and
then
next
year
they
go
maybe
eks
next
year,
how
about
aks
and
then
next
year,
how
about
rancher
right?
You
can't
do
that
right.
You
got
to
go
on
this
journey
every
time
you
do
that
you
stop
and
you're
off
from
number
one
again.
C
One
thing
I
can
say
to
everybody
is
that
what
I've
seen
and
I've
seen
this
a
lot
out
there
is
that
people
keep
going
back
to
level
one
again
right.
They
start
kubernetes,
they
start
playing
native.
They
start
going
on
the
journey,
but
then
some
yahoo
in
the
company
says
hey.
I
want
to
replace
this
tool
with
that
tool
and
now
the
drop
in
the
maturity.
Now
that
doesn't
work,
you
can't
stay
in
that
you
really.
C
You
have
to
be
able
to
understand
what
is
my
my
future
look
like
what
is
my
future
direction
right
and
if,
if
I'm
on
kubernetes,
that's
great,
let's,
let's
make
it
happen,
but
you
have
to
be
able
to
understand.
How
can
I
keep
my
maturity
going
and
not
go
backwards?
That's
something!
I'm
hoping
that
this!
You
know
this
betrayal
will
help
to
give
you
that
path.
There's.
D
Also,
like
the
the
challenge
that
I
don't
know,
I'm
sure
that
you've
faced
as
well,
but
that
we
face
is
that
there's
our
clients
want
to
be
at
a
certain
maturity
level
that
they're
not
at
right
but
we're
in
production.
They
say
and
we're
like
yeah,
but
you
missed
all
of
these
steps
before
then,
so
this
tries
to
bridge
that
gap
and
makes
those
conversations
a
little
bit
easier
so
that
they
have
something.
We
have
a
frame
of
reference
to
to
point
out
and
point
to
so.
B
And
you
might
you
know
one
thing
that
we
didn't
mention
earlier
was
you
might
have
with
one
application
reached
maturity,
and
then
you
decide
you
want
to
bring
another
application
along
and
you're
like
yeah
we're,
starting
from
you
know,
maybe
level
two
maybe
you've
like
advanced
it,
but
you're
gonna.
You
know,
as
you
migrate,
everything
it's
going
to
evolve
and
you
might
be
at
different
phases
at
different
times.
A
We
started
drafting
this
a
year
ago
and
then,
over
that
period
of
time,
we've
seen
a
significant
amount
of
change
within
the
cloud
native
landscape.
So
again
on
that
point,
we'd
love
to
invite
your
involvement,
and
specifically,
for
those
of
you
too,
who
don't
feel
that
you're
technical
enough
to
contribute
to
a
cncf
project
but
may
have
a
a
lot
of
skill
on
the
people
process
or
policy
side.
We'd
really
love
your
input
too.