►
From YouTube: Kubernetes Project Update - Stephen Augustus, KubeCon + CloudNativeCon Europe 2021 Co-Chair
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. 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.
Kubernetes Project Update - Stephen Augustus, KubeCon + CloudNativeCon Europe 2021 Co-Chair & Head of Open Source, Emerging Technologies & Incubation Division, Cisco
A
Hey
everyone:
my
name
is
stephen
augustus.
I'm
head
of
open
source
at
cisco,
I'm
also
one
of
the
kubernetes
project
leads
for
sig
release.
Today,
we're
gonna
be
chatting
with
you
about
kubernetes
project
updates,
one
of
our
favorite
projects
in
the
world
right.
So,
if
you
have
ever
joined
me
for
a
presentation,
you
know
that
I
value
deeply.
The
human
component
of
open
source
projects
and
and
kubernetes
is
a
project
that
is
near
and
dear
to
my
heart.
A
So
in
every
one
of
these
presentations
I
always
want
to
talk
about
the
human
component
a
little
bit
now,
if
you
have,
if
you
have
read
kubernetes
press
in
the
past,
you
will
know
that
a
lot
of
a
lot
of
our
spokespeople.
If
you
will
like
to
talk
about
project
maturity
and
and
kubernetes,
becoming
boring,
and
I
think
we're
I
think,
we're
moving
steadily
towards
that
point.
Now,
I'm
going
to
practice
a
few
numbers
with
you,
22
38,
34
42.
A
I
like
that
one
and
51.
so
okay
practice
is
over.
Why
did
I
choose
those
numbers?
So
if
we
look
back
into
the
release
cycles,
going
back
going
back
from
117,
those
are
the
numbers
of
enhancements
that
were
landed
for
each
cycle.
So,
if
you're
familiar
with
the
project,
you
know
that
enhancements
are
our
nate.
Are
our
designation
for
for
features?
Really
an
enhancement
is
meant
to
an
enhancement.
Is
a
designation
for
a
set
of
work
that
spans
across
multiple
release
cycles
right?
So
it's
not.
A
It's
not
easy
to
encompass
the
entire
scope
of
a
feature
in
in
a
single
cycle.
Often
it
takes
multiple
cycles
for
a
feature
or
a
set
of
features.
Components
to
move
from
alpha
to
beta
to
ga
or
stable,
so
enhancements
is
kind
of
that
bucket
that
we
put
all
of
those.
A
All
of
those
components
are
the
set
of
components
that
would
be
delivered
within
a
release
or
set
of
releases
now
so
again,
one
more
time
with
those
numbers
22
for
kubernetes
117
38
for
kubernetes
118
34
for
kubernetes
119
42
for
kubernetes,
120
and
51
for
kubernetes
121..
A
Now,
with
those
numbers,
you
can
kind
of
see
an
upward
trend
right,
we're
kind
of
we're
kind
of
going
up
up
into
the
right.
Roughly,
you
know,
with
the,
with
the
exception
of
of
of
the
difference
between
kubernetes
118
and
119,
we're
trending,
we're
trending
upwards
right,
and
that's
that's
that's
nice
to
see
in
terms
of
enhancement
delivery,
especially
the
the
number
of
enhancements
going
being
graduated
or
deprecated
we're
looking
at
like
13
from
from
kubernetes
121..
A
We
have
kind
of
iterated
over
different
approaches
for
several
different
things
and
we're
starting
to
find
a
fit
we're
starting
to
find
a
lot
of
things
that
work
for
us
we're
starting
to
find
a
lot
of
different
ways
in
crafting
conversations
to
be
more
effective
to
increase
the
reach
of
those
conversations.
A
So
the
first
one,
if
you
were
hanging
out
with
us
for
for
kubecon
n,
a
virtual
in
2020,
I
talked
about
the
release
cadence
and
again
the
human
component
of
the
kubernetes
project.
Now
in
119
we
slowed
down
the
kubernetes
release
cadence
or
we
elongated
the
the
one,
the
119
cycle
right.
A
That
was
kind
of
a
special
case
and,
following
that,
following
that
choice,
this
was
kind
of
like
the
peak
of
of
you
know,
of
kova
19,
as
well
as
protests
across
across
the
world,
and
we
thought
that
it
would
would
make
a
lot
of
sense
to
give
everyone
the
time
and
space
that
they
needed
to
really
process
to
be
able
to
do
good
work.
So
we
extended,
we
extended
that
release
cycle
after
many
many
discussions.
A
Now,
what
followed
were
were
several
questions
about.
Would
that
be
the
new
release
cycle
is?
Is
now
that
we've
extended
it
now
that
we've
elongated
that
cycle
it
effectively
moved
2020
from
the
standard
four
releases
a
year
down
to
three
releases
a
year,
and
we
got
several
questions.
A
Is
three
releases
a
year
going
to
be
the
new
norm?
So
when
I
chatted
with
y'all
last,
we
said
we're
gonna,
wait,
we're
gonna,
see
we're
gonna,
get
lots
of
feedback
from
people,
we're
we're
not
going
to
move
on
this
decision
until
we
feel
that
we
have.
We
have
had
an
opportunity
to
chat
with
a
bunch
of
different
people
and
and
get
their
takes
and
and
kind
of
incorporate
that
feedback
into
a
proposal
right.
A
So
if
you,
the
kubernetes
enhancement,
proposals
are
caps
as
they're
affectionately
called
so
the
so
sig
release,
along
with
sig
architecture
and
testing,
produced
a
proposal
for
changing
the
release
cadence,
and
we
recently
landed
that
proposal
during
the
the
120
or
towards
the
tail
end
of
the
120
release
cycle.
So
that
means
that
if
you
have
not
heard
the
news
yet
that
kubernetes
is
officially
after
much
discussion
moving
to
a
release
cycle
of
three
releases
for
the
year.
A
So
it's
roughly
15
week
release
cycles
with
some
breaks
in
between
some
breaks
that
we
try
to
try
to
have
considerations
around
kubecon
cloud
native
con
as
well
as
holidays
across
the
world,
and
and
what
that
allows
us
to
do
is
to
to
take
time
to
to
spend,
spend
some
effort
in
areas
that
that
at
times,
can
can
often
be
overlooked.
A
Right
areas
like
like
product
management,
pro
product
program,
project
management
being
able
to
do
triage
on
active
on
on
active
issues
and
pr's
being
able
to
bring
more
contributors
to
your
respective
cigs
or
sub
projects,
and
and
give
them
give
them
opportunities
that
may
may
not
have
existed
in
certain
areas
around
triage
around
the
the
product
program,
project
management
and
and
definitely
not
to
be
forgotten.
The
time
to
improve
tests
improve
test
coverage.
A
Fix
flaky
tests
have
discussions
around
the
proposals,
the
the
level
of
of
effort,
that's
required
and
the
the
amount
of
commit
that
sigs
are
going
to
to
to
to
to
have
for
for
the
next
cycle
right.
So,
overall,
I
think
that
we
are
we're
fairly
confident
in
this
being
a
quality
of
life
improvement
for
everyone
who
both
contributes,
contributes
to
kubernetes,
as
well
as
those
who
consume
kubernetes.
So
thank
you
to
everyone
who
is
involved
in
those
discussions,
they're
incredibly
thoughtful
discussions.
A
We
took
quite
a
bit
of
time
to
to
to
ship
this
because
we
wanted
to
make
sure
we
had
those
discussions.
So
as
a
result
of
this
this
I
want
to
go
back
to
those
numbers
really
quickly
right,
so
we're
looking
at
34,
42
and
51
right.
Those
are
the
numbers
again
for
kubernetes
119.,
the
enhancements
for
119
for
120
and
for
121.
A
So
already
there
is
a
there's
a
net
gain
in
terms
of
in
terms
of
the
the
the
enhancements
that
we're
able
to
deliver
with,
with
an
extended
slightly
extended
release
cycle
right.
We're
really
going
from
we're
really
going
from
about
a
three
month
or
quarterly
cadence
into
a
roughly
four
month
or
15
week.
A
Cadence
so
very
happy
to
see
that
very
excited
to
see
all
the
people
who
have
been
pushing
that
forward,
including
the
including
all
of
the
sig
sub-project
owners,
enhancements
enhancements
owners,
the
release
team
and
the
wider
community
for
communicating
this
message
out
to
to
downstream
consumers
as
well.
A
A
We've
also,
we've
also
started
to
talk
about
an
opt-in
process
for
the
releases,
and
I
think
the
opt-in
process
has
also
had
a
a
a
positive
effect
on
the
on
the
amount
of
enhancements
that
we're
able
to
deliver
for
a
cycle.
So
what
opt-in
is
is
almost
as
as
the
name
implies
for
a
sig
to
to
sign
up
for
the
release
cycle.
A
Essentially,
they
have
to
tell
the
release
team
what
they're
planning
on
committing
to
and
that
that
turns
the
release
team
model
for
the
enhancement,
sub
team
of
the
release
team
from
a
kind
of
a
pull
model
into
pushing
information
out
from
the
sigs
into
the
release
team.
So
we've
we've
seen
some
success
with
that
we
have
as
a
project.
A
Sig
testing
has
worked
on
the
removal
of
bazel
within
the
kubernetes
kubernetes
repo,
that
is
a
huge
quality
of
life
improvement
for
contributors,
especially
if
you
consider,
especially,
if
you
consider
new
contributors
or
contributors
that
are
just
recently
getting
engaged
with
the
project
having
to
learn
a
new
framework
essentially
for
for
doing
work.
A
You
know
when
you
may
be
used
to
say
using
mate
files
or-
or
you
know
your
handy
dandy,
shell
scripts,
so
I
I
believe
that
you
know
the
the
year
plus
of
work
that
it
that
it
took
to
put
together
that
proposal,
as
well
as
execute
on
it
from
sig
testing,
has
a
huge
quality
of
life
improvement
for
for
the
project,
so
hat
tip
to
them.
The
community
meetings
are
back,
we
have
been.
A
We
have
changed
cadence,
you
know
during
during
2020
and
and
moving
into
2021
we've
brought
the
community
meetings
back.
The
community
meetings
are
going
to
be
a
more
lively
forum
for
discussion.
There
will
be
discussions
around
enhancements
discussions
around
what's
happening
in
the
community.
What
what
you
need
to
be
aware
of
different
ways
for
you
to
get
involved,
so
I
think
so.
I'm
very
happy
to
see
the
community
meetings
coming
back.
Those
are
you
know.
A
Those
were
one
of
my
ingress
points
when
I
was
getting
started
with
kubernetes,
so
I
I
hope
that
they
are
as
fulfilling
to
new
contributors
and
to
ongoing
contributors,
as
they
were
to
me
when
I
was
starting
out
so
with
121,
with
with
121
with
1
20.
A
We've
had
some
interesting
deprecations
happen.
So
within
previous
cycles
we
deprecated
docker
shim,
and
you
may
be
aware
that
that
led
to
some
interesting
discussions,
kind
of
across
the
community
across
the
internet,
just
to
be
clear,
deprecating
docker
shim
is
not
defecating.
Docker
docker
shim
is
a
component
that
allows
us
to
interact
with
containers
within
the
kubernetes
ecosystem.
A
It
is.
It
is
something
that
is
widely
discussed
on
blogs
and
explained
in
great
detail.
Do
not
worry,
we
have
your
back
there
and
there
is
time
to
make
adjustments
as
needed
in
in
your
running
clusters
or
your
clusters
to
be
upgraded
in
addition
to
the
docker
shim
depreciation.
We
also
have
pod
security
policies
have
been
deprecated.
Pod
security
policies
have
been
in
it
have
been
in
kubernetes
since
near
inception.
A
It's
one
of
the
first
features
or
enhancements
introduced
into
the
project
and
we're
moving
on
we're
moving
on.
We
have
deprecated
pot
security
policies
in
favor
of
in
favor
of
some
new
functionality,
and
we
will
see
so.
The
deprecation
window
has
started
during
the
121
cycle
and
we'll
see
pod
security
policies
fully
deprecated
within
by
125..
A
Now
a
few
other
very
interesting
things
that
have
happened.
Kind
of
around
communicating
the
steering
committee
has
started
to
do
or
we're
continuing
to
do
now.
A
Annual
reports
for
sigs,
so
annual
reports,
we
piloted
the
annual
report
program
within
for
working
groups
and
now
for
2021
we're
reflecting
as
a
community
on
all
the
work
that
our
sigs
have
done
really
across
the
year
and
we'll
continue
to
do
that
every
year,
so
very
excited
to
see
that
work
happen,
as
you
know,
as
as
someone
who
doesn't
necessarily
get
to
touch
every
sig,
it's
great
to
be
able
to
go
back
and
and
read
information
about
all
the
the
great
work
that
other
states
have
been
doing.
A
Asynchronous
communications
is
another
thing
that
has
has
been
huge,
especially
as
we
we
look
at
our
our
global
situation.
121
was
the
first
time
that
we
had
that
we
had
a
release
team
lead
who
was
based
in
aipac,
and
that
has
led
to
that
has
led
to
a
lot
of
rethinking
of
all
the
processes
that
we
kind
of.
A
A
So
we
have
wrapping
up
lots
of
interesting
things
that
have
happened
across
the
last
few
cycles.
Structured
logging
is
now
in
beta
pod
resource
metrics
are,
are,
are
now
active,
being
able
to
defend
against
logging
secrets
via
static
analysis
for
so
hot
tip
to
sig
instrumentation
cron
jobs
are
now
stable.
Cron
jobs
have
been
in
beta
since
1.8
they're,
now
stabilized
of
121.
A
ipv4
ipv6,
dual
stack
support
has
gone
to
beta,
which
means
it's
on
by
default.
Graceful
node
shutdowns
are
now
in
beta
persistent
volume.
Health
metrics
are
now
in
alpha
lots
of
fun
things
to
check
out
in
the
community,
but
unfortunately,
that's
all
the
time.
We
have
so
when
you
have
a
chance
check
out
the
annual
reports
check
out
the
rundown
on
may
13th
for
the
121
release
and
check
out
the
kubernetes
community
repo
to
get
more
information
on
how
to
get
involved
in
kubernetes.
Thanks
for
your
time,.