►
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.
主题演讲: Kubernetes 项目更新 | Keynote: Kubernetes Project Updates - Jasmine James, Engineering Manager, Twitter
A
A
These
updates
might
seem
familiar
they're,
essentially
a
re-record
of
the
updates
that
stephen
augustus
head
of
open
source
at
cisco
and
former
kubecon
co-chair
gabe
at
our
los
angeles
event
in
person
in
october.
There
are
a
few
additions
that
I'll
be
also
talking
about
today.
So
let's
dive
right
in
first
up
code
of
conduct
committee,
the
coc
is
a
governance
group,
and
here
are
some
of
the
things
that
they've
been
working
on.
A
A
project.
Transparency
report
is
a
criminal
critical
evidence
point
for
this
large
community's
members
to
understand
of
the
presence
of
a
code
of
conduct
is
not
simply
a
token
or
something
hollow,
but
rather
a
representation
of
the
project
culture,
and
that
there
is
active
accountability
and
restoration
to
ensure
a
safe
space
for
all
who
collaborate
within
the
project.
A
Those
conversations
earlier
before,
what
might
be
just
a
simple
communication,
grows
into
a
negative
pattern
or
establishes
unprofessional
culture.
Also,
as
steven
mentioned
mentioned
in
his
address
in
october.
Thank
you
to
tasha
and
eva
who
are
now
emeritus
members
and
welcome
valerie
and
nabarron
to
the
code
of
conduct
committee.
A
All
right
steering
committee
updates
reiterating
read
that
transparency
report
also
go
and
check
out
the
annual
reports
for
all
groups
within
the
kubernetes
committee
community
to
see
what
they're
up
to
you
can
actually
access
it
at
the
kubernetes
community.
Github
steven
gave
the
update
that
the
steering
election
was
in
progress
in
october.
We're
happy
to
announce
that
it's
been
completed,
and
here
are
the
results.
Congratulations
to
the
new
steering
committee
members,
christophe
blecker
from
red
hat
stephen
augustus
from
cisco
paris
pittman
from
apple
and
tim
pepper
from
vmware.
A
A
This
is
a
newer
sig
and
it
works
to
improve
the
security
of
kubernetes
project
and
the
ecosystem
as
a
whole
by
building
bridges
both
internally
and
externally.
It
provides
a
safe
space
for
community
capital
collaboration,
knowledge
sharing
and
learning,
and
also
raising
security
awareness.
Horizontal
initiatives
include
cross-cutting
documentation,
tooling
development
and
facilitation
of
a
regular
third-party
security.
Audit
security
is
a
community
effort
driven
by
people
who
show
up
and
do
the
work.
A
The
sub-projects
have
started
with
interest
interested
community
members
showing
up
with
an
idea
bringing
other
contributors
to
do
the
work
coming
into
their
own
as
leaders
and
building
that
community
and
making
it
a
space
for
others
to
grow.
Sick
security
is
really
proud
of
their
updates
to
their
sub
projects.
A
Our
docs,
this
the
doc
sub
project,
has
been
improving
the
kubernetes
documentation
to
help
users
run
their
cluster
in
safer
ways,
and
it's
also
producing
a
hardening
guide
to
raise
adoption
of
practical
security
improvements
which
is
really
really
needed
by
the
community.
I'm
super
excited
about
that.
The
tooling
sub
project
is
helping
kubernetes
maintainer
ship,
safer
code
by
developing
tooling
and
procedures
to
find
and
reduce
common
issues
like
vulnerable
dependencies
or
data
leakages.
A
The
audit
sub
project
is
making
it
easier
for
security
and
auditors
to
engage
with
that
massive
kubernetes
code
base
and
is
finding
more
opportunities
to
improve
kubernetes
for
everyone.
These
are
all
great
opportunities
in
sub
projects
to
get
involved.
So
please
reach
out
to
the
sig.
If
you're
interested
end,
users
often
have
a
lot
of
questions
about
hardening
their
clusters,
so
the
sub
sig
is
very
excited
for
them
to
get
their
hands
on
the
docs
hardening
guide.
This
guide
gives
users
practical
advice
that
will
increase
their
understanding
about
how
to
make
their
clusters
more
secure.
A
So
pod
security
admission
gives
psp
users
a
path
forward
and
helps
kubernetes
be
more
secure
in
its
default
state.
As
I
mentioned,
security
is
always
looking
for
security-minded
contributors,
including
ones
who
are
new
to
the
kubernetes
project,
bring
your
gifts,
ideas
and
help
make
kubernetes
better
next
up.
Sig
release.
A
A
They've
also
started
to
look
into
securing
the
supply
chain.
Sig
release
is
trying
to
lead
the
pack
by
working
across
the
spdx
community
and
those
that
deliver
s-bombs.
The
salsa
framework
allows
them
to
see
where
the
artifacts
are
going
and
gives
more
insights.
Sick
release
will
be
building
up
that
framework
over
time.
A
Csi
windows
has
moved
to
general
availability
in
the
1.22
release.
Windows
does
not
currently
support
privileged
containers,
yet
so
to
solve
this
problem,
the
csi
proxy
enables
csi
node
plugins
to
be
deployed,
as
unprivileged
pods,
to
use
a
proxy
to
perform
privileged
storage
operations
on
the
node.
This
allows
end
users
to
use
the
csi
driver
to
provision
persistent
volumes
to
use
in
their
workloads.
A
Six
stores
always
needs
new
contributors,
so
I
will
echo
here
again
please
reach
out
if
you're
interested
in
contributing
working
group
api
expression,
so
this
group
improves
mechanisms
to
serve
open
api
from
kubernetes
api
server
and
api's
authoring
and
expressiveness
to
allow
apis
to
properly
and
programmatically.
Describe
their
mechanisms.
A
A
A
All
right
working
group
naming
working
group
naming
was
dissolved
because
the
initial
objectives
were
achieved
and
they
sought
out
to
create
a
framework
and
process
for
the
kubernetes
community
to
change
language
that
was
not
inclusive.
The
goal
was
to
change
all
of
those
names,
and
it
was
done
so.
Thank
you
to
steven
m
celeste,
who
are
the
co-founders
of
this
working
group.
Thank
you.
Thank
you.
Thank
you.
A
All
right,
working
group,
kubernetes
infrastructure,
has
transformed
itself
into
a
cig.
This
is
the
first
time
that
this
has
happened
as
stephen
mentioned
in
october,
and
the
journey
was
started
to
convert
the
infrastructure
owned
by
google
to
community-owned
infrastructure.
They
found
that
it
was
so
important
that
it
needed
to
be
a
sig.
So
if
you're
looking
to
get
involved
in
this
project,
please
reach
out
to
the
kubernetes
infrastructure
sig.
A
A
Sig
docs
is
a
place
where
we
need
a
lot
of
contributors
and
it's
a
fantastic
way
to
get
started
in
the
community
and
as
many
folks
entry
point
into
the
community,
we're
looking
for
help.
So
please
reach
out
if
you're
looking
to
write,
documentation
or
even
contribute
technical
writers
to
any
of
the
areas
that
you're
leveraging
from
the
kubernetes
project.