►
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.
Keynote: CI/CD Isn't Reserved for Software! - Erin Boyd, Distinguished Engineer + Director of Emerging Technologies, Red Hat & Matt Farina, Distinguished Engineer, SUSE
Speakers: Erin Boyd, Matt Farina
With more than 125 CNCF projects with various levels of maturity, the TOC is continuously evolving to meet the scale of project adoption and provide value to the cloud native community.This keynote will focus on how we are executing on our strategic objectives outlined in Valencia to improve the way we serve this community.
A
Well,
Matt
continuous
Improvement
isn't
A
New
Concept
derived
from
the
Japanese
business
philosophy
of
Kaizen.
It's
based
on
continuous
Improvement
of
working
practices,
personal
efficiency,
Etc
directly
translated.
It
means
good
change,
but
you
know
in
software
we
have
to
make
an
acronym
out
of
everything,
so
we
call
it
cicd,
but
the
idea
of
making
small
continuous
improvements
in
delivering
to
the
community
is
really
what
Toc
is
all
about.
B
And
you
know
the
TOC,
it
really
started
off
small
and
it
has
continuously
improved
over
time
when
the
cncf
started.
There
was
just
one
project
kubernetes
and
the
TOC
eventually
added
more
projects,
but
there
was
just
a
small
number
that
they
could
do
themselves
and
then
over
time,
as
things
grew
as
you
can
see
in
the
landscape
sliding
things
there
were
working
groups
added
special
interests,
Group,
which
became
technology,
advisory
groups
and
all
of
the
structure
scaled
with
it,
and
we
had
to
continually
change
over
time
as
we
scaled
up.
A
Great
so
the
TOC
represents
10
companies,
three
are
who
are
from
end
users,
not
vendors
and
the
TOC
members
work
in
small,
medium
and
large
companies.
They
all
come
from
four
different
countries
and
even
two
different
continents.
They
have
varied
backgrounds
from
expertise
and
observability
security
container
run
times
and
more.
As
you
know,
Kathy
Zhang,
who
just
presented
before
us
from
Valencia,
has
just
joined
since
then.
B
We
want
to
take
Cloud
native
Computing
everywhere
from
the
desktop
to
the
data
center
to
the
edge.
Our
mission
is
to
take
it
everywhere
in
the
world
into
every
industry.
The
todc
does
that
by
guiding
technical
decisions,
you'll
see
that
in
the
processes
surrounding
projects,
the
scope
of
the
technical
advisory
groups
and
more,
we
tried
to
do
this
with
both
Innovation
and
stability
in
mind.
A
B
A
So
the
TOC
is
a
group
of
people
who
not
only
want
to
help
grow
the
technical
community
but
listen
and
evolve.
The
systems
in
which
we
work
to
ensure
its
growth
is
positive
and
sustainable
for
the
future,
for
everyone
from
the
technical
advisory
groups,
to
the
TOC
to
ambassadors,
to
contributors
and
the
like,
we're
all
working
as
servant
leaders,
we
want
to
encourage
diversity
of
thoughts.
We
want
to
create
a
culture
of
trust.
We
want
to
have
an
unselfish
mindset
and
we
want
to
Foster
leadership
in
others.
B
A
So
at
Valencia,
if
you
were
there,
you
might
have
seen
the
same
slide
around
the
cloud
native
pillars.
Looking
at
the
evolution
of
the
CNC
landscape,
we
would
like
to
outline
the
main
pillars
that
got
us
to
where
we
are
today.
Open
governance
and
transparency
is
the
base
of
our
community,
while
technical,
Evolution
and
interoperability
created
the
vast
cncf
ecosystem
that
all
of
us
references,
you'll,
see
these
pillars
pillars
as
the
fundamental
underpinnings
of
servant
leadership
and
how
each
of
these
pillars
can
be
expressed.
A
So,
let's
go
dive
a
little
deeper
into
open
governance
and
transparency
outlined
in
crossing
the
Chasm
by
Jeffrey
Moore.
The
book
describes
the
different
phases
of
new
and
disruptive
Technologies.
One
key
function
of
the
TOC
is
shepherding
projects
through
the
three
stages
of
the
cncf
sandbox
incubation
and
graduation.
This
means
working
with
projects
doing
due
diligence
being
helpful,
sponsoring
them
and,
of
course,
ultimately
voting
on
the
projects.
We're
constantly
updating
the
process
to
make
it
more
efficient,
create
less
confusion
and
frustration
for
all
sides,
especially
the
projects
that
we're
trying
to
help.
B
To
date,
there
are
18
graduated
projects.
These
projects
include
what
you
need
to
schedule
and
run
containers
along
with
projects
for
security,
monitoring,
storage,
networking
and
more
and
some
of
the
incubating
projects,
some
that
were
shown
earlier
in
the
updates.
They
look
like
they're
ready
to
graduate,
so
this
list
May
grow
in
the
near
future.
B
The
37
incubating
projects,
an
81
sandbox
projects,
bring
us
to
more
than
130
total
cncf
projects.
This
has
grown
immensely
since
that
beginning
where
there
was
just
that
one
kubernetes
projects.
These
include
a
wide
range
of
projects
to
deal
with
immediate
concerns
like
security
and
things
we're
still
trying
to
figure
out
like
webassembly
and
so
much
more.
B
Today,
we
would
like
to
unveil
a
new
Sandbox
submission
process.
Sandbox
is
that
stage
where
most
projects
join
the
cncf
sandbox
projects
can
be
experiments,
projects
where
companies
want
to
start
collaborating
together,
and
so
many
other
things.
The
new
process
takes
place
over
on
GitHub,
where
a
majority
of
the
project's
maintainers
already
do
their
work.
It
uses
issue
based
templates.
Everything
is
tracked
in
the
open
and
feedback
from
the
different
groups
on
the
proposals
can
all
be
tracked
in
one
place.
B
A
B
With
so
many
projects,
many
of
which
work
in
the
same
space,
we
would
like
them
to
work
well
together,
both
in
collaborating
on
solving
problems
and
in
the
way
applications
communicate
with
each
other
to
help
the
TOC
manage
so
many
projects
and
technical
areas.
The
TOC
created
the
technical
advisory
groups,
which
we
refer
to
as
tags.
B
The
tags
cover
a
wide
variety
of
areas
and
if
one
of
these
areas,
which
we're
going
to
go,
walk
through
here
in
a
moment,
if
one
of
them
interests
you
or
you
have
questions
about
it,
consider
reaching
out
to
the
tag
to
learn
more.
Let's
take
a
look
at
the
tags
tag.
Security
is
active
in
many
ways.
They
maintain
a
cloud
native
security
white
paper
if
you're
looking
to
get
into
Cloud
native
security.
This
paper
is
a
good
start.
They
collaborate
with
projects
on
Security
reviews
and
supply
chain
security.
B
A
Tag,
Storage
storage
is
one
of
the
pillars
of
cloud.
You
need
it
in
just
about
everywhere
and
we
depend
on
it
to
just
work.
The
tag
storage
has
created
and
iterated
on
a
white
paper,
around
storage
architectures
in
the
cloud
native
native
ecosystem
data,
access
deployment
and
challenges
of
distributed
scale
of
these
systems,
as
well
as
in
white
paper
on
Disaster
Recovery,
which
is
particularly
complex
in
a
cloud
native
kubernetes
world.
B
Running
workloads
is
a
big
part
of
the
cloud
right.
You
have
your
infrastructure,
and
now
you
want
to
run
the
workloads
there.
There
are
concerns
around
running
them.
Updating
software
day,
two
operations
and
more.
This
is
where
Tag
app
delivery
comes
in
an
example
is
the
work
they
did
around
the
operator
white
paper
to
help
people
understand
what
they
are
and
how
to
navigate
them,
and
so,
if
you're
interested
in
working
with
apps
and
figuring
out
how
you
run
them,
how
you
build
those
platforms
that
they
talked
about
earlier.
A
So
tag
Network.
The
networking
tag
covers
a
wide
range
of
use
cases
in
the
cloud
Nico
native
ecosystem
Network
literally
touches
every
part
of
the
stack
you
will
notice
on
their
landing
page.
They
quote,
nothing
is
considered
out
of
scope.
The
team
looks
to
specifically
identify
the
aspects
of
networking
that
differ
from
the
traditional
data
center,
additionally
exploring
abstractions
to
enable
workloads,
both
in
and
outside
of
kubernetes.
B
Tag
runtime
looks
at
what
runs
your
workloads
at
a
low
level.
This
includes
projects
like
containerd
and
cryo.
It
also
includes
higher
level
projects
like
kubernetes
kubernetes
distros,
like
k3s
running
virtual
machines
in
containers
with
projects
like
Cube,
vert
and
running
edge
workloads
with
projects
like
Cube
Edge
operating
an
open
source
project
is
more
than
producing
code.
You
need
governance
so
that
project
is
developed
in
a
stable
environment.
A
And
we'd
like
to
announce
a
new
tag
that
has
just
been
formed,
called
the
tag:
environmental
sustainability
at
kubecon
Valencia.
It
was
announced
that
there
was
a
working
group
to
shed
light
on
the
challenges
and
opportunities
for
this
community
to
build
projects
that
lend
an
edge
on
the
responsibility
of
us
to
support
sustainability
and
I'm
happy
to
announce
that
it's
now
a
formal
tag.
This
tag
has
three
goals.
B
Knowing
what's
going
on
in
your
workloads
is
important
when
they
are
being
scheduled
on
various
nodes
and
that
can
change
at
any
time
it's
important
to
have
a
way
to
observe.
What's
going
on,
you
can't
just
SSH
into
a
server
and
look
at
the
workloads
and
what's
going
on,
like
you
used
to
do
tag,
observability
is
where
you
know
it's
there
to
help.
B
So,
let's
talk
now
about
sustainability
and
how
we
sustain
this
ecosystem
speakers
are
always
showing
the
landscape
on
stage
to
emphasize
the
size
and
complexity
of
the
cncf
ecosystem
for
the
TOC.
This
means
a
lot
of
things.
Priyanka
emphasized
that
we
are
the
fastest
growing
community
in
open
source,
and
that
means
that
we
need
to
keep
changing
and
adapting
to
our
new
size
constantly,
and
not
only
is
the
landscape
large
and
complex,
but
it's
growing
in
size
and
complexity
faster
than
ever.
B
A
But
you
can
help
going
back
to
the
title
of
this
talk
and
how
we
can
continuously
improve
our
community.
Let
me
have
you
think
about
for
a
minute
the
idea
of
one
percent.
There
have
been
numerous
books
around
this
concept,
but
my
favorite
story
is
about
Chris
Nikish,
who
about
two
years
to
ago
today
was
the
first
person
with
Down
Syndrome
to
complete
a
full
Ironman
Triathlon.
He
was
told
that
it
would
be
impossible.
A
Christy
tells
in
his
book
called
one
percent
about
how
small
incremental
process
in
the
support
of
a
community
towards
his
goal,
made
it
all
possible.
One
sit
up,
one
squat
one
push-up
one
mind
he
talks
about
measuring
our
improvements
and
not
just
our
successes
as
the
cloud
native
ecosystem
evolves
and
grow.
How
can
we,
as
a
community
embrace
the
journey,
make
the
small
incremental
improvements
to
the
impossible
possible
just
like
Chris?
We
need
a
strong
community
and
we
need
each
one
of
you.
B
As
the
landscape
grows
and
the
community
grows,
we
need
to
scale
all
of
the
different
parts
of
it.
If
you're
using
the
technology,
please
consider
contributing
to
it.
There
are
many
places
to
contribute
Docs
translations,
things
that
you
saw
earlier
just
helping
others
in
the
issue
queues.
If
you
know
how
you
know,
one
of
the
projects
works.
If
you
can
explain
that,
there's
always
people
asking
for
help
helping
others
just
learn
this
in
the
issue:
cues
and,
of
course,
code
and
reviews.
A
B
Every
year
the
TOC
has
an
election
for
about
half
the
members.
This
enables
there
to
be
continuity
across
elections
and
we're
coming
up
to
the
next
set
of
Elections.
Members
are
elected
by
different
groups,
including
the
governing
board,
the
end
user
members
and,
if
you're
interested
in
joining
the
TOC.
B
Now
is
the
time
to
learn
more
and
consider
running,
and
if
you
have
any
questions
about
this
or
something
else
for
the
TOC
there's
a
Toc
panel
tomorrow
and
you
can
come
by
and
ask
us
we're
open
to
discussing
it,
sharing
what
we
do
and
you
know
what
it
looks
like.
So,
if
you're
interested
Now's
the
Time
to
poke
interest
at
it.