►
From YouTube: Evolving the Cloud Native Maturity Model - John Forman & Robert Glenn, Danielle Cook, Simon Forster
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe in Amsterdam, The Netherlands from April 17-21, 2023. 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.
Evolving the Cloud Native Maturity Model - John Forman & Robert Glenn, Accenture; Danielle Cook, Fairwinds; Simon Forster, Stackegy
Speakers: John Forman, Danielle Cook, Robert Glenn, Simon Forster
Am I doing this cloud native stuff the right way? The Cloud Native Landscape is a great resource for users to see the technology in the cloud native space. But it can lead to uncertainty and constant second guessing if you are doing cloud native right. The Cartografos Working Group developed the Cloud Native Maturity Model, a five phase framework to help those new to cloud native and those deep in the trenches understand where they are in their journey and what they should be considering or doing. In this session, panelists from the Cartografos Working Group will discuss the maturity model and its phases. They’ll give an overview of what you should expect out of the people at your organization, the processes and policies to put in place, and where CNCF projects fit in. The session will also dive into how the Cloud Native Maturity Model should evolve with the ever-changing CNCF landscape. Audience members will be encouraged to join the group and offer suggestions on ways to improve the Maturity Model.
B
A
C
All
right,
so
you
guys
may
or
may
not
be
familiar
how
we
started
the
project
kind
of
graphics,
working
group.
It
all
started
with
initiative
where
all
of
us
had
different
models
that
we're
working
on
separately
and
then,
together,
we
kind
of
came
together
from
the
cncf
to
create
choreographers
that
you
see
today,
but
what
I
really
have
seen
beyond
that
was
the
current
you
know
journey
to
Cloud
native,
where
first
we
had
the
big
way
for
devops.
You
guys
remember
that
no
I'm,
sorry
back
up
one
second
turn
to
clouds.
C
First
right,
Journey
Cloud,
whatever
J2
say
everybody's
going
to
the
cloud.
You
know
we'll
save
money,
it's
all
worth
the
cloud
and
then
it
was
water
in
the
cloud
that
developed
the
whole
devops
journey
began.
Right
was
a
big
culture,
change
for
everybody
right
that
we've
also
develops,
and
the
third
one
was
when
Cloud
native
was
started
to
become
born
kubernetes
when
there
was
a
Russian
kubernetes
to
the
cloud.
But
when
we're
doing
this,
though
there
was
no
handbook
right.
Just
in
this
life,
the
Hayward
everybody
kind
of
crashed
into
the
cloud.
C
D
So
why
did
we
need
a
maturity
model?
We've
already
talked
on
or
touched
on
it
a
little
bit
before
we
have
the
landscape.
We
have
the
trail
map
they're,
very
technology
Centric
and
that's
not
the
whole
piece
of
the
puzzle.
You
know
who's
actually
developing
these
stuff
who's
actually
implementing
it.
It's
a
lot
of
people.
How
are
they
doing
it
process
and
and
what
are
they
doing?
What
are
they
allowed
to
do?
D
We
also
you
know.
On
the
left
side,
we
are
trying
to
avoid.
You
know
crowning
any
King
make
being
a
king
maker
in
the
industry
or
anything
like
that.
So
we
try
and
be
very
technology
agnostic
or
as
high
level
as
we
can.
We
do
have
to
you
know,
make
some
references
to
cncf
projects
in
some
cases
so
that
we
have
something
to
to
you
know
a
frame
of
reference.
B
So
the
maturity
model
covers,
as
we
were
developing
it.
We
realized
that
there
were
some
key
themes
that
were
coming
out
and
throughout
this
conference
so
far,
we've
been
hearing
a
lot
about
people,
process,
policy,
technology
and
business
outcomes.
I
think
is
a
major
Point
that
we
cover
within
each
of
where,
within
the
model,
we
talk
through
these
five
themes
throughout
every
level.
Looking
at
like
what
do
your
people
need
to
do?
How
do
they
need
to
shift
culturally?
B
What
processes
do
you
have
in
place
today
and,
as
you
move
to
Cloud
native
what
it?
What
does
that
look
like
what
sort
of
cicd
pipelines
do
you
need
to
put
in
place?
What
workflows
with
policy
we
dig
into
what
compliance
standards
need
to
be
put
in
place?
How
are
you
going
to
automate
this
policy
technology,
of
course,
is
you
know,
there's
this
whole
ecosystem.
B
We
do
not,
as
as
Robbie
said,
we
don't
make
recommendations
of
use
this
technology
or
that,
but
we
do
say
you're
going
to
need
tools
like
this
and
then
business
outcomes
and
something
that
came
up
as
we
were.
You
know
we
were
involved
in
a
CTO
Summit
yesterday,
looking
at
what
should
you
be
communicating
to
your
bosses
or
the
business,
the
board
and
whatnot
like?
Why
are
you
doing
this
journey?
So
the
model
covers
all
of
these
these
five
areas
and
then
the
levels
of
the
maturity
are
around.
B
You
know:
there's
five
different
levels,
so
build
is
all
about.
You
are
in
pre-production,
you're
figuring
this
out,
you're
trialing
it
a
lot
of
proof
of
Concepts
in
this
stage
operate
is
level
two
and
that's.
When
you
get
to
production,
usually
that's
around.
You
know
one
application
you're,
trying
it
out
you're,
maybe
not
doing
something
that
is
business.
Critical
scale
is
when
you
are
now
scaling
up
looking
at
how
you
can
get
more
applications
in
the
cloud
native
space.
B
Improving
is
where
you're
looking
at
decisions
you
made
around
security
and
policy
and
compliance
and
and
revisiting
them
and
looking
at
well.
Maybe
we
need
to
do
this
a
little
bit
better
and
then
optimize
is
really
when
you
figured
it
all
out,
which
is
the
Holy
Grail
and
there's
not
many
of
us
who
are
here
and
you're
now
going
well.
B
What
tools
have
I
created
that
I
could
perhaps
give
back
to
the
cncf
or
where
are
there
areas
where
just
a
small
little
optimization
will
really
help
us
out,
so
there
is
and
I'm
just
going
to
mention
it
here,
the
link
to
our
GitHub
repo
that
goes
into
this,
and
you
can
get
all
the
details
and
read
through
it
at
length.
So
what
we
wanted
to
do
next
was
instead
of
kind
of
just
go
through
a
PowerPoint,
slides
and
details.
B
B
C
Thanks
well,
in
the
past,
everything
started
where
everyone's
in
the
basement
right,
Cloud
native
star
in
the
basement
and
most
companies
were
developers,
got
geeked
up
on
kubernetes
on
the
cloud,
all
those
great
things,
but,
as
you
get
real
good
stuff
to
go
to
production,
to
be
serious
about
this,
a
level
one,
we
want
to
take
it
from
the
basement
to
production
at
least
begin
the
journey
anyway,
automation
at
least
later
on.
When
they
first
get
there.
It's
baby
steps
it's
a
marathon
to
Sprint.
What
do
you
want
to
call
it
right?
C
It's
one
day
at
a
time.
What
you
expect
in
the
beginning
is
just
a
lot
of
training
leveling
up
bringing
in
the
right
resources
a
lot
of
times
our
clients.
Will
you
know
trade
up
the
current
resources
or
hire
from
outside
to
bring
in
the
resources?
So
what
you
expect
from
the
team
is
you're
building
the
team,
basically
in
level
one
it
builds.
It's
built,
the
team,
build
the
process
but
build
the
processes.
B
D
D
You
want
to
automate
those
things
quickly,
things
that
you're
going
to
do
often,
certainly
you
know
a
lot
of
times,
especially
on
in
the
in
kind
of
the
build
phase,
you're
going
to
focus
more
on
automating
your
deployments,
rather
than
like
some
kind
of
integration
step,
because
you
know
a
lot
of
times,
you're
a
small
team
and
you
might
not
really
have
any
kind
of
integration
to
do
really.
But
you
want
to
make
sure
that
you
know
the
managing.
You
know
you
don't
want
to
be
running.
Cube
CTL
apply
all
the
time.
D
B
A
A
A
Than
we
potentially,
we
would
have
assumed
with
level
one
where
we
are
building
attempting
to
build
Cloud
native
applications
and
we
are
in.
We
are
not
in
production
yet,
but
we
still
do
require
kubernetes,
we'll
still
be
considering
our
source
control.
Many
of
these
things
we
may
already
have
we'll
also
need
to
be
thinking
about
what
are
what
about
our
Network
zones,
our
infrastructure,
our
firewalls,
because
for
many
organizations,
particularly
if
they
are
using
public
cloud
service
providers,
they're
going
to
need
to
get
all
of
that
access
in
place.
B
And
I
think
the
final
point
in
level
one
before
we
go
on
is
around
what
you
should
be
communicating
to
the
business,
and
this
is
where
I
think
as
an
industry
and
as
technologists
like
we
don't
always
do
a
great
job
at
so
here
in
level
one.
We
really,
you
know
in
the
maturity
model
talks
about
setting
kpis
that
the
business
understands
so
they're
not
going
to
get
the
nitty-gritty
of
why
you
chose
to
pick
this
Tech
over
that,
but
they
should
understand.
B
A
So
this
we're
in
production.
Now
this
is
the
very
first
step
where
we
re,
where
our
application,
potentially
a
very
small
use
case,
will
be
live
within
production.
We
will
need
to
have
CI,
obviously
in
place
and
a
means
of
releasing.
We
may
still
be
using
imperative
Cube
control
commands,
particularly
if
it
is
a
very
small
installation,
but
you
may
wish
to
be
raising
your
eyes
towards
get
Ops
even
at
this
point.
So
will
you
be
considering
a
good
Ops
operator,
for
example,
or
one
of
the
cncf
projects
that
occupy
this
this
space?
B
D
Yeah
so
you're
going
to
have
more
policies.
You
know
it's.
It's
you're
going
to
see
actually
over
kind
of
the
the
full.
You
know.
Journey
you're
gonna
see
a
big
explosion
as
you
get
to
like
level
three
right
of
Technologies
of
tools
of
code,
and
then
you
know
over
time.
You're
gonna
start
whittling
that
down
making
it
a
little
bit
more.
D
You
know
streamlined
so
at
level,
two
you're
you're
piling
on
the
policies
you're
adding
in
you
know,
maybe
something
like
a
policy
controller
of
some
sort
and
there's
tons
of
policy
types
out
there.
We
won't
don't
need
to
go
into
all
of
them,
but
I
would
say
that
you
know
the
more
that
you
know
the
better
right.
So,
of
course
you
want
to
be
adding
your
monitoring
Tools
in
as
well,
but
having
those
policies,
at
least
even
in
in
you
know,
kind
of
a
dry
run
mode.
D
B
And
so
in
terms
like
related
with
process,
so
you
know
what
what
is
part
of
the
process
like?
What
are
you?
What
should
you
be
scanning
for
as
you're?
You
know,
you're
doing
Change,
Control
you're,
doing
logging
you're
doing
all
these
things,
but
like
what
is
there
things
you
should
be
scanning
for
in
stage
two
level,
two.
C
B
C
Level
one's
but
upscaling
right
what
you
have
level
two,
it's
about
become
more
of
a
master
of
your
domain,
really
understand
the
technology
very
well
to
become
more
affluent
with
it.
We
are
now
you
know
in
stage
one
you
are
becoming
right,
a
cloud
native
engineer
at
level
two.
You
are
a
cloud
millionaire.
You
got
to
be
towards
that
level
to
to
believe
you
are
at
that
level
to
achieve
these
goals.
C
The
biggest
thing
with
this
also
is:
do
technology
is
always
coming
out
right,
there's
always
a
new
version
of
kubernetes
new
version
of
istio
and
everything
else
out
there
in
level
two
Support
also
to
see
what's
new,
that's
out
there
with
the
new
things
coming
out,
I'm
prepared
for
those
as
well-
and
we
know
the
landscape.
Ccf
is
evolving
every
day
to
stay.
On
top
of
that
alone
is
his
own
job
but
level
two.
Is
you
really
want
to
begin
focus
on
that
as
well?.
B
D
D
So
you
know,
if
you
have
you
know
all
the
all
the
the
pieces
you
know
in
place,
except
for
your
policies
or
something
like
that,
then
you're
never
going
to
you're,
never
going
to
get
to
level
three,
that's
for
sure,
you're
never
going
to
be
able
to
scale
you're,
never
going
to
find
you're,
never
going
to
be
able
to
to
see
what's
even
available
to
be
able
to
scale.
So
you
know
putting
those
things
in
place.
Early
is
important.
D
B
B
D
One
one
point
I
guess
to
to
finish
on
that
is
like,
for
example,
we're
at
we're
at
production,
maybe
with
one
app
right
by
the
time
we
get
to
level
three.
We
want
to
be
scaled
or
to
start
scaling
right,
be
prepared
to
scale
right.
So
it's
not
going
to
be
just
enough.
Okay,
we
got
one
app
to
production,
we're
at
level
two.
B
A
We
look
at
scale
within
this
model
as
being
I.
Both
is
a
simple
answer
within
level
2
we're
really
focusing
on
a
single
application
or
a
certain
center
of
excellence
within
your
organization
already,
with
with
level
three
we're
looking
at,
can
we
scale
out
individual
application,
our
applications
horizontally
or
vertically?
Can
we
bring
in
the
load?
Have
we
developed
the
level
of
trust
and
confidence
in
our
Cloud
native
platforms
to
be
able
to
do
that?
Secondly,
we
may
be
scaling
out
to
multiple
applications
as
well,
and
that's
a
really
vital
part
of
it.
B
D
So
one
thing
that
we
talk
about
with
the
the
people
aspect
is
you
know:
now
is
the
time
that
you're
going
to
really
start
thinking
about
a
center
of
excellence.
I
think
John
brought
that
up.
You
really
want
to
take
that
knowledge.
Capital
that
you've
built
you
don't
want
to
have
not
everybody's
going
to
be
a
security
expert
I
mean
a
kubernetes
experts.
Not
everybody
at
your
organization
needs
to
have
the
cka,
for
example.
At
some
point
you
know
you
really
just
need
operators
or
people.
D
You
might
have
even
abstraction
layers
that
you
know
keep
things
very
simple
for
your
end
users
at
at
this
stage.
So
how
do
you?
How
do
you
manage
that
that
complexity,
I
think
part
of
it
is
just
you
know,
centralizing
a
lot
of
that
that
knowledge
capital
in
something
of
a
center
of
excellence?
It
doesn't
have
to
be
a
formal
role
or
a
formal
group.
It
can
just
be.
You
know
a
a
designation
of
of
individuals
who
really
provide
that
thought.
Leadership
within
the
organization.
B
Well-
and
there
was
one
end
user
that
we
were
talking
to
yesterday
and
what
they
do
at
the
organization
is
they
provide
these
Pathways?
So
as
you're,
you
know,
you
want
your
developers
using
kubernetes
coding,
all
of
that
they
put
this
path
together
and
you
can
choose
I
want
path,
A
or
B
or
C,
but
you
have
to
stay
on
that
path.
There's
guardrails
established
around
it.
B
A
As
much
as
you
possibly
can
it's
really
vital
as
we
as
we
have
a
lot
more
complexity
within
our
estate.
We
realize
that
not
one
single,
individual
or
one
single
group
is
able
to
to
continue
to
do
everything
because
of
the
increasing
level
of
maturity
that
we,
we
hope,
you'll
be
seeing
within
your
platform.
You'll
be
able
to
really
take
advantage
of,
for
example,
the
operator
ecosystem,
that
we
have
Within,
kubernetes
and
good
examples
of
making
sure
that
we
take
advantage
of
that
for
our
applications
as
well
as
our
platforms.
A
So
are
we
taking
advantage
of
of
operators
for
applications,
but
what
you
is
absolutely
vital
is
that
senior
people
and
decision
makers
are
aware
of
this
and
what
this
means
there's
a
as
I'm
sure
we've
all
experienced
when
we've
taken
a
very
complex
application
and
done
traditional
installations
of
it.
It's
been
a
very
long
drawn
out
project.
If
we're
able
to
take
advantage
of
the
capabilities
of
the
platform
a
good
example.
Let's
say
the
strimsy
operator
off
the
top
of
my
head
for
Kafka.
B
Well
and
I
think
there
there
was
another
session
that
we
attended
where
it
was.
If
you
think,
you've
communicated
the
business
value,
you
should
communicate
it
eight
more
times,
at
least
like
people
need
to
hear
it,
and
it's
super
important
so
moving
on.
So
there's
going
to
be
a
ton
of
tech
that
you
have
in
place
at
this
stage.
But
what
are
two
things
that
you
might
not
have
had
in
place
that
you
really
need
in
this
stage
and
I
can
throw
that
over
to
any
of
you
yeah.
C
I
think
at
this
point
you
want
to
get
to
create
template
for
things
to
begin
that
process
of
actually
putting
things
to
code
right
level.
Four,
at
that
point,
I'll
get
there,
but
at
level
three
I
could
be
putting
the
C's
to
create
my
templates,
whether
it's
for
a
terraform
or
my
policies,
Oprah
or
maybe
I-
think
starting
that
process
right
now
for
the
policy
is
code.
C
113
is
critical
to
begin
to
that
level
of
the
skill,
also
what
I
have
multiple
fleets
or
if
my
sorority
is
multi-cloud,
which
every
client
today
every
couple
today
is
multi-cloud
nobody's
One,
Cloud
anymore
right.
So
now,
if
I
have
multi-cloud
that
makes
things
complicate
2x
more
so
would
it
be
kind
of
cool
to
have
policies
where
everything's,
driven
from
one
area
that
could
push
out
to
multiple
clouds
so
level
three
as
I'm
scaling,
doing
scaling,
I
gotta
think
about
multi-clut
as
well.
What
was
my
multiple
strategy?
That's
critical
level,
three
as
well.
B
C
C
B
C
At
level,
two
more
also
between
seriously
between
one
and
two
today,
but
they
want
to
get
to
a
four
to
five
to
really
become
at
that
level.
Level
four
was
on
permanent
things.
I
still
have
to
do
more
things
at
scale.
I
could
take
my
deployments
now
and
begin.
My
blue
green
Canary,
or
my
blue
blue
at
that
point,
also
doing
a
multiple
strategy
again
at
scale
to
be
able
to
push
more
policies
across
multiple
ones.
What
it
means
to
prove
at
level
four
is
to
be
able
to
get
much
curious
code
up
to
par.
C
B
And
so
when
you,
you
know,
you
were
talking
about
policy
code
and
level
three
and
this
this
question
is
for
you
Simon
and
it's
round
so
now,
if
I
have
some
policy
in
place
like?
Could
you
give
me
maybe
an
example
policy
or
maybe
not
and
talk
about
how
you
enforce
it
at
this
stage,
because
I
think
that
becomes
really
important.
A
We
would
hope
that
by
the
time
that
we've
reached
level
four
we're
really
taking
advantage
again
of
the
automation
that
we
have
within
the
platforms
we
do
have
projects
within
the
cncf.
We
know
a
vapor,
we
understand
gatekeeper.
We
have
all
of
the
the
admission
controller
ecosystem
within
the
kubernetes.
To
take
advantage
of.
We
would
expect
to
to
make
sure
that
nothing
that
doesn't
meet
our
policy
requirements
is
able
to
Simply
into
production.
We
would
be
enforcing
this
and.
D
It
actually
helps
us
improve.
It's
actually
part
of
the
improving.
You
know
process,
because
then
we
can
unlock
things
like
self-service,
like
I.
Just
think,
if
you
could
not
have
to
pay
a
bunch
of
Engineers
to
build
your
tools,
you
can
just
have
them.
You
know
your
engineers
fill
out
a
form
somewhere
and
and
something
automatically
takes
care
of
it.
And
it's
all
you
know,
within
your
security
and-
and
you
know,
compliance
so.
B
One
that
you
know
I'd
like
to
think
about
that
as
kubernetes
guard
rails
right,
so
we're
giving
we're
letting
devs
safely
develop
within
the
guard
rails
that
we're
giving.
So
you
know
I
always
like
the
picture
of
bowling
where
you
have
the
guard
rails
and
you
can
get
the
ball
down
and
it
gets
there.
B
So
it's
a
good
good
thing
to
make
sure
you
have
those
in
place
when
you're
here
so
now
we're
gonna
go
we're
gonna,
we're
cruising
through
level,
four
to
level
five
around
optimization.
So
you
know
you
have
people
in
place
and
you
have
gone
through
all
this
like
what
do
I
expect
of
my
people,
how,
if
my
team's
evolved
open
to
anyone.
C
I
guess
open
to
me
level:
five
is
where
I
fully
mature,
again
Electro
action
by
people
and
our
experts
and
then
I
smes,
so
I
think
about
experts
at
this
level.
Now
there
are
smes
graduating
from
level
one
to
level
five
at
that
level.
So
you
expect
at
that
point.
You
know
for
your
yourself
to
be
experts
in
Cloud
native
to
take
things
to
scale
anything
new
being
developed
is
now
Cloud
native.
B
A
Our
Hope
and
our
aim
is
to
be
able
to
see
both
internal
and
external
regulations
really
reflected
within
the
policies
and
the
compliance
that
we
have
within
our
Cloud
environments.
We
wish
that
we
want
to
be
able
to
see
all
of
the
yeah
I
think
that's
probably
the
most
important
takeaway
and
we
would
like
to
see
regulation
in
code.
B
And
kind
of
final
question
on
this
stage
is
around:
you
know
how
the
tech
stack
has
evolved,
and
you
know
we
talk
about
how
here
you're
revisiting
decisions
you
made,
maybe
in
level
one
and
level
two.
So
are
you
contributing
codes
to
projects,
or
are
you
selecting
new
vendors
what's
happening
here
and
that's
open
to.
C
Anyone
I
think
one
of
the
biggest
things
any
corporate
today
is
technical
debt.
Technical
debt
will
study
growth
to
be
Cloud
native.
We
all
know
that
it's
reality,
but
yet
we
have
four
10
20
tools
that
do
the
same
thing
in
our
Landscapes.
So
when
it
comes
to
Tech
Evolution
within
my
process
of
one
to
five
at
level,
five
I'm
gonna
get
very
lean,
I'm
gonna
start,
you
know
cutting
that,
throw
trying
to
out
the
old
technology.
Basically
in
other
levels,
a
level
five
technical
debt
should
be
none.
C
It
should
be
at
the
level
where
I
have
you
know
the
only
the
best
for
tools
running
my
environment.
So,
as
my
thing
evolved,
I
need
to
get
to
that
point
and
also
keep
in
mind
that
most
clients
will
not
be
a
level
five
I'm.
Sorry
to
say
that
if
of
Spotify,
important,
Cloud
native
technically
so
I'm
at
level
five,
but
most
companies,
today
most
clients
say
go
into
Cloud
native.
They
are
live
between.
C
You
know
four
and
five
right
and
possibly
even
closer
to
four,
because
you
still
have
the
Legacy,
in
the
background,
doing
certain
daily
certain
processes
to
really
not
give
you
like
that
entire
level.
Five.
But
at
the
same
time
you
have
different
work
streams,
so
applications
could
be
level
five.
Some
may
be
a
level
two
and
three
and
four:
don't
think
that
you
know
it's
all
or
nothing.
It's
not
like
if
I'm
level,
five
everything's
a
level
five.
Okay,
those
are
a
mix
with
my
environment
as
well.
A
So,
for
us
we've
we,
this
is
an
open.
This
is
a
cncf
initiative.
We
are
a
group
within
the
cncf
and
we
would
like
first
off.
We
would
love
contributions.
We
are
looking
at
publishing
of
the
artifacts
right
now,
they're
in
GitHub,
within
our
GitHub
repo,
we're
looking
at
incorporating
them
into
the
cncf
website.
A
We
will
also
be
continuing
our
partnership
with
the
tags
in
order
to
go
and
reflect
their
work
within
the
model
and
also
assist
them
where
they
wish
to
go
and
Baseline
their
Technologies
processes
and
and
people
and
as
well,
and
we
would
also
like
to
get
to
a
stage,
if
possible,
of
implementing
scoring
in
code
we'd
like
to
take
our
ourselves
to
level
five.
If
we
possibly
can.
B
Well
and
I
think
what's
really
here:
if
any
of
you
are
on
a
tag
or
whatnot,
we
want
to
make
sure
that
the
maturity
model
becomes.
This
repository
of
I
can
go
here
and
I
can
access
all
the
amazing
content
that
everybody's
working
on,
because
I
think
sometimes
within
the
cncf.
We
think
people
know
that
something
exists,
but
it
it
doesn't.
B
A
So
we'd,
really
like
you
to
check
out
the
repository
it's
on
GitHub,
we
would
love
to
see
your
issues
and,
if
there's
anything,
you'd
like
to
see
changed,
feel
free
to
submit
a
pull
request.
We
also
hold
Community
meetings
every
second
Tuesday
at
1
pm
U.S
eastern
time,
and
we're
also
on
cncf
slack
we'd
love
to
continue
the
conversation
with
you
as
well,
and
if
you
don't
already
have
one
we've
got
a
pile
of
brochures
up
here
and
we
also
have
a
booth
in
the
Pavilion
area
in
the
project
Pavilion.
Thank
you,
foreign.
C
One
more
thing:
if
everybody
adopts
kind
of
Graphics
in
their
environment
and
actually
have
it
running
successfully
right,
we
invite
you,
the
FSM
with
us
to
present
it
and
then
really
super
cool.
Somebody
can
do
that
right.
I
would
love
to
see
it
happen,
actually
do
a
use
case
of
this
model
in
real
life.