►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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: Kubernetes Project Updates - Stephen Augustus, Head of Open Source, Cisco
A
Hello,
hello,
everyone
today
we're
going
to
do
a
little
speed
round
of
kubernetes
project
updates,
so
I
am
stephen
augustus
head
of
open
source
at
cisco
and
one
of
the
co-chairs
for
a
few
things
in
the
project.
A
So,
first
off,
I
want
to
start
with
the
code
of
conduct
committee,
one
of
my
favorite
governance
groups,
and
talk
about
some
of
the
things
that
they've
been
working
on
over
the
past
year.
So
first
off
the
transparency
report.
Transparency
report
is
a
as
an
effort
that
was
happening
between
both
of
the
code,
both
both
the
code
of
conduct
committee,
as
well
as
the
steering
committee.
So
project
transparency
report
is
a
critical
evidence
point
for
this
large
communities.
A
Members
to
understand
the
presence
of
the
code
of
conduct
is
it's
not
simply
a
token
or
something
hollow,
but
rather
a
representation
of
the
project's
culture
and
active
accountability
and
restorations
in
store,
ensure
a
safe
space
for
all
to
collaborate
in
the
project
right.
So
super
super
important.
What
this
means
for
the
end
users
of
the
project
is
that
is
that
their
supply
chain
right,
and
so
this
is
not
just.
This
is
not
just
the
software.
This
is
not
just
the
people,
but
the
supply
chain.
A
A
If
you
see
behavior,
which
is
contrary
to
the
code
of
conduct,
speak
up,
this
might
be
directly
in
the
moment
that
lee
that
feels
safe
to
you
to
the
the
the
special
interest
group
working
group
leads
in
the
area
to
your
co,
to
your
steering
committee
representatives
or
privately
through
the
code
at
kubernetes
dot,
io
email
address,
as
with
technical
debt
driven
bugs
in
software
engineering,
the
hardest
conduct
issues
aren't
typically
ones
where
something
was
done
deliberately
wrong,
but
rather
ones
where
we
together
allowed
a
situation
to
grow
into
something
larger.
A
A
A
So
steering
committee
next
up
so
also
the
transparency
report
seriously
go
read
that
we
also
had
annual
reports
for
all
of
the
all
of
the
governance
groups
within
the
kubernetes
community.
We
started
off
with
kind
of
trial,
running
the
annual
reports
with
working
groups
and
now
we've
kind
of
extended
that
to
all
of
the
governance
groups
within
the
community.
So
if
you
want
to
see
what
your
favorite
groups
have
been
up
to
and
haven't
had
a
chance
to
do
that,
yet
the
annual
reports
are
in
the
kubernetes
dot.
A
Io
excuse
me:
github
dot,
github.com
kubernetes
community.
The
steering
committee
election
is
imminent,
as
in
so
a
reminder
for
anyone
who
is
a
candidate
for
the
steering
committee.
Your
bios
are
due
today.
So
if
you
have
not
seen
that
notice,
please
submit
your
bios
today.
I
believe
the
elections
will
be
opening
up.
A
I
will
be
starting
more
of
the
preparations
next
week
and
finally,
there
is
a
governance
board
proposal
that,
if
you
were
part
of
the
sig
leads
or
working
group
leads
and
so
on
and
so
forth,
you
may
have
heard
from
paris.
So
please
talk
to
your
leads
and
talk
to
paris
about
things
that
you'd
like
to
see
in
the
community,
because
those
will
be
presented
to
the
cncf
governing
board
all
right,
so
I'm
gonna
go
a
little
faster.
A
Now
because
I
see
I
see,
I've
got
the
the
jack
bauer
24
situation
going
so
see.
So
sync,
security
security
is
one
of
our
newer
sigs.
Sync
security
has
a
few
sub
projects
that
you
should
definitely
check
out.
We've
got
docs
tooling
audit
coming
out
of
docs,
we've
got
so
sync:
security
works
to
improve
the
security
of
the
kubernetes
project
and
the
ecosystem
as
a
whole
by
building
bridges
both
internally
and
externally.
We're
providing
space
for
community
collaboration,
knowledge,
sharing
and
learning
and
raising
security
awareness.
A
The
horizontal
initiatives
include
cross-cutting
documentation,
tooling
development
and
facilitation
of
regular
third-party
security
audits.
So
if
you've
seen
some
of
the
security
audits
happening
in
the
past
in
kubernetes
we're
going
to
keep
that
train
rolling
now,
sig
security
is
a
community
effort.
It's
driven
by
the
people
who
show
up
and
do
the
work.
This
is
this
is
big
in
open
source
show
up.
Do
the
work.
Someone
will
give
you
the
hat.
A
The
sub
projects
have
started
with
interested
community
members
and
kind
of
like
moved
into
a
great
opportunity
to
see
a
lot
of
a
lot
of
again
interested
community
members
step
up
to
be
leaders.
So
this
is
a
really
great
opportunity
to
to
get
involved
in
the
community.
So
again,
docs
tooling
audit
we've
got
hardening
guides.
A
One
of
the
the
coolest
collaborations
that
we've
seen
in
the
community
so
far
is
the
the
deprecation
of
pod
security
policies
and
the
and
the
rise
of
the
pod
security
admission,
which
is
a
collaboration
between
sig
security
and
sig,
off
sig
release
it's
near
and
dear
to
my
heart,
but
I
again
I'm
in
the
speed
round.
A
So
a
vision,
a
road
map,
so
sync
security
now
has
excuse
me
sig
release
now
has
a
road
map,
a
vision
of
what
we'd
like
to
see
happening
in
the
project
as
it
relates
to,
as
it
relates
to
delivering
kubernetes
to
all
of
you.
Fine
folks,
we've
got
more
release
managers
than
ever
before.
We've
got
new
release
manager
associates,
we've
got
artifact
promotion.
Artifact
promotion
is
fun.
A
You
should
all
want
to
do
it
if
you've,
if
you've
gotten,
if
you've,
had
an
opportunity
to
work
on
image
promotion
for
any
one
of
your
sub
projects
within
the
community.
You
can
also
now
do
that
with
with
files.
Artifacts.Kates.Io
is
new
and
we're
still
kind
of
trialling
it
out.
A
But
if
you're
interested
please
talk
to
sig
release
and
we
will
help
you
get
started
with
pushing
you
know
your
tar
balls,
your
all
of
your
fun
artifacts
into
into
a
a
location
that
is
safe
and
secure
and
then,
finally,
we're
securing
that
supply
chain
delicious,
delicious
salsa.
So
we've
had
a
lot
of
chats
about
like
software
supply
chain
security
throughout
this
conference
and
we're
going
to
continue
to
hear
it.
A
This
is
a
pivotal
moment
and
I'm
not
going
to
go
into
I'm
not
going
to
go
into
some
of
the
spiels
that
you've
already
heard,
but
we
are
trying
to
lead
the
pack
by
by
working
through
and
working
kind
of
across
working
across
the
svdx
communities
working
with
folks
who
deliver
a
software
bill
of
materials,
we're
working
with
folks
who
work
on
provenance
and
attestation
and
all
of
these
fun
software
supply
chain
security,
buzzwords
that
you're
hearing
right
now.
Finally,
the
with
salsa.
A
So
these
this
framework
allows
us
to
kind
of
see
what
we're
doing
where
our
artifacts
are
going.
Who
has
control
of
them?
What
build
systems
they're
running
it?
That
is
we're
we're
going
to
be
partnering
directly
with
the
salsa
community
and
open
ssf
to
build
out
this
framework
over
time.
A
So
stay
tuned
for
that,
and
please,
if
you
have
this
kind
of
focus,
help
come
to
sig
release,
get
involved,
sig
storage,
sync
storage
is
responsible
for
ensuring
that
different
types
of
file
and
block
storage,
whether
it's
ephemeral
or
persistent,
local
or
remote,
it's
available
wherever
and
whenever
a
container
needs
it
right.
So
one
of
the
big
things
that
happened,
this
previous
cycle-
122
csi
windows-
moves
to
ga.
A
So
if
you
want
to
check
out
the
article
it's
right
there
up
on
the
screen,
give
you
a
second
to
take
a
picture
and
they
are
always
looking
for
new
contributors,
and
I
think
that
can
kind
of
echo
that
across
the
entire
community,
we're
always
looking
for
new
contributors
working
group,
api
expression.
Now
working
group,
api
expression
is
involved
in
improving
the
mechanisms
to
server
open
api
from
kubernetes
api
servers
and
apis
authoring
and
expressiveness
allow
apis
to
properly
and
programmatically
describe
their
mechanisms.
A
So
server
side
apply
has
been
something
that
has
been
has
has
been
in
the
works
for
quite
some
time
now,
and
it
goes
to
ga
in
122
or
it
went
to
ga
and
122.
A
the
the
ga
milestone
means
you
can
actually
depend
on
this
feature
and
and
its
api,
without
the
fear
of
you,
know
future
backwards
and
compatible
designs.
So
please
go
check
out.
Server
side
apply
working
group
naming
we
dissolved
working
group
naming
we
spun
it
up
and
we
spun
it
down.
If
you
are
because
we
did
what
we
came
to
do
when
we
initially
started
this
group,
the
idea
was
to
create
framework
and
a
process
for
the
kubernetes
community
to
change
language
that
is
not
inclusive.
A
What
that
gave
rise
to
was
the
inclusive
naming
initiative
of
which
myself
and
celeste
horgan
are
co-founders,
because
we
will
be
spending
more
time
in
the
inclusive
naming
initiative.
We'd
like
you
to
join
us
in
the
inclusive
naming
initiative
and
specifically
the
the
community
work
stream
which
focuses
on
delivering
these
changes
to
to
open
source
communities
as
well
as
it.
It
offers
the
same
function
as
say:
a
sig
contributor
experience
or
tag
contributor
strategy
on
the
cncf
level
working
group,
kate's,
infra,
strikethrough,
sig,
kubernetes
infrastructure.
A
They.
This
is
one
of
the
first
times
in
the
community
that
we've
seen
a
working
group.
This
is
the
first
time
in
the
community
that
we've
seen
a
working
group
transform
itself
into
a
sig.
A
A
few
years
ago,
we
set
off
on
a
journey
to
convert
all
of
the
infrastructure
that
was
currently
google
owned
into
kubernetes
community
owned
to
give
the
keys
of
that
castle
to
the
community.
So
here
we
are,
this
is
this:
is
the
proof
point
it's
so
important
that
it
needs
to
be
a
sig
working
groups
in
the
kubernetes
community
governance
wise,
if
you're,
not
familiar
working
groups,
are
meant
to
be
time,
bounded
efforts.
A
Now
it's
we're
not
necessarily
going
to
tell
you
how
long
it's
going
to
take
for
them
to
necessarily
spin
down,
but
we've
said
that
this
is
so
important
to
us
to
this
community
that
it
needs
to
be
a
sake.
It
needs
to
be
long-standing,
so
congrats
to
all
of
the
leads
of
both
the
chairs
and
the
technical
leads
of
working
group
working
group,
kate's
infra
for
driving
that
forward
for
the
community
and
all
the
contributors
involved.
There.
A
The
product
security
committee
is
now
the
security
response
committee.
Kubernetes
is
a
project
not
a
product
right,
so
this
is
just
a
little
name
change
to
reflect
that
work.
Thank
you
to
all
of
the
people
who
are
on
the
security
response
committee
who
protect
this
community.
There
are.
There
is
an
on-call
rotation.
There
is
lots
of
lots
of
work
that
happens
in
the
background
to
make
this
community
safe.
So
thank
you
to
the
product
to
excuse
me.
The
security
response
committee
and
sig
docs
can
has
help
one
higher
technical
writers.
A
Sig
docs
is
currently
we're
in
a
place
where
we
want
more
contributors
to
sig
docs.
This
is
an
awesome
opportunity
to
get
involved
in
the
community,
and
this
is
often
of
many
people's
entry
point
to
the
community.
This
is
actually
where
I
started
in
the
community:
sig
docs
and
sig
azure.
So
please,
if
you
are
interested
in
getting
started
in
this
community,
come
to
sig,
docs
and
hire
technical
writers
and
send
them
to
the
communities
that
you're
working
in.
A
And
finally,
a
general
join
us.
We
are
always
looking
for
new
contributors,
we're
always
looking
for
people
to
get
involved.
There
are
a
few
links
that
I
will
give
you
a
chance
to
to
snapshot
but
get
dot.
Kate
sadaya,
which
is
kind
of
our
github
short
name,
slash
community,
will
take
you
to
our
community
repo
and
you
will
have
a
full
rundown
of
all
of
the
the
various
governance
groups
and
how
to
get
involved.