►
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). 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 - Jasmine James, Senior Engineering Manager-Developer Experience; Ricardo Rocha, Computing Engineer, CERN; Emily Fox, Security Engineer, Apple
A
A
Awesome
awesome
so
happy
to
hear
that
we
have
exciting
day
two
planned
for
you,
but
first
I
want
to
ask
a
question:
show
of
hands
who
remembers
the
first
project
that
brought
them
into
the
cloud
native
computing
foundation
community
raise
of
hands.
Do
you
remember?
A
No,
no
one
remembers.
It's
been
a
long
pandemic,
so,
okay
for
me,
it
was
about
five
years
ago
and
that
first
project
was
kubernetes.
So
I'm
excited
to
be
here
now
on
the
keynote
stage,
sharing
with
you,
some
updates
from
the
kubernetes
project.
So
that's
the
first
thing
we're
going
to
do
today,
all
right,
so
I'm
jasmine
james.
I
lead
developer
experience
in
my
current
organization
and
it's
really
comprised
of
helping
developers
have
a
seamless
experience.
A
A
So
how
does
this
work
every
kubecon
we
reach
out
to
the
projects
and
ask
what
are
some
of
the
cool
things
that
you
all
are
doing
and
we
get
feedback.
So
this
is
a
result
of
the
feedback
that
we
were
provided.
This
list
is
not
exhaustive.
You
can
always
find
out
more
information
about
kubernetes
and
other
cncf
projects
via
kubernetes
io
or
the
cncf
website.
So
let's
get
right
into
it.
The
first
update
is
from
the
steering
committee.
So
what
even
is
a
steering
committee?
A
A
The
steering
committee
is
focused
on
growing
maintainers
right
now,
which
brings
me
to
that
program.
I
mentioned
they'll,
be
paying
special
attention
to
testing
infrastructure
and
further
community
building
and
they've
put
out
a
special
ask
for
reviewers
with
specialties
in
quality
and
security.
So
if
you're
interested
drop
them
a
line
in
the
kubernetes
channel,
other
things
in
flight
include
helping
folks
transition
into
an
owner
role
of
the
project
or
stepping
forward
to
be
a
project
leader.
A
The
one
thing
I
really
appreciate
about
kubernetes
is
the
easy
way
you
can
consume
their
documentation
and
the
clarity
on
how
to
contribute.
So,
if
you
work
at
an
organization
that
uses
kubernetes
reach
out
and
slack
and
get
more
information
on
how
you
can
become
an
active
participant,
all
right,
next
up,
sig
security.
So
yesterday
we
found
out
that
65
percent
of
you
here
today
at
cube
clown
cube
concours
native
cloudnativecon
eu.
A
It
was
your
first
time
so
I
thought
I'd
talk
about
what
a
sig
was
so
a
sig
is
a
special
interest
group
and
the
kubernetes
version
of
security
takes
the
community
building
approach
to
improving
security
for
the
project
itself
and
users
by
working
with
other
sigs
on
documentation
and
features
to
make
kubernetes
safer.
It
also
helps
with
security
self-assessments
for
kubernetes
and
the
sub-projects
and
periodic
third-party
code
audits,
third-party
code
audits.
A
In
this
version,
there
is
a
single
hierarchy
instead
of
a
different
one
for
each
controller
and
some
of
the
improvements
are
a
cleaner
and
easier
to
use
api,
safe
sub
tree
delegation
to
containers
and
new
features
like
pressure
stall
information
for
more
information
on
how
to
configure
c
group
v2
check
out
the
container
runtime
docs
on
kubernetes
dot,
io
all
right,
sig
storage.
Another
special
interest
group
update,
so
this
group
is
responsible
for
ensuring
the
different
types
of
file
and
block
storage
are
available
wherever
a
container
is
scheduled.
A
They're
also
responsible
for
storage
capacity
management,
influencing
scheduling
of
containers
based
on
storage
and
generic
operations
on
storage,
and
they
made
a
lot
of
things
available
in
1.24
version
of
kubernetes,
so
volume
expansion.
So
this
allows
users
to
increase
the
size
of
their
volumes
while
keeping
their
workloads
online.
This
feature
allows
the
users
to
increase
the
size
of
the
provision
volume
only
using
the
kubernetes
pvc
api
setting
a
larger
size
in
the
pvc
automatically
triggers
the
expansion
of
the
volume
that
backs
the
underlying
persistent
volume,
as
well
as
resize
resizing
the
file
system.
A
If
needed,
storage
capacity
tracking
takes
capacity
into
consideration
when
scheduling
pods
on
a
node.
This
feature
allows
a
csi
driver
to
report
storage
capacity
and
lets
the
kubernetes
scheduler
use
that
information
to
make
more
intelligent
decisions
when
choosing
a
node
for
a
pod
ongoing
for
many
releases.
Now,
csi
migration
allows
kubernetes
to
migrate
entry
volume
plug-ins
to
out-of-tree
csi
drivers
using
csi
drivers
allows
for
better
maintainability
and
reduces
the
support
for
the
opera,
reduces
the
opportunity
for
vulnerabilities,
big
difference.
A
Cluster
operators
can
also
only
select
the
storage
drivers
that
their
cluster
requires.
So
what
does
this
group
need
more
contributors
for
information
on
how
to
get
involved,
check
out
their
github
project
or
you
can
join
their
slack
channel
at
fig
dash
storage,
all
right,
sig
cluster
life
cycle.
So
this
special
interest
group
examines
how
we
should
change
kubernetes
to
make
it
easier
to
manage
and
operate
with
a
focus
on
customer
cluster
deployment
and
upgrades
it's
an
exciting
time
for
cluster
api
because
they
have
reached
production
readiness
with
the
1.0
release.
A
Cluster
api
enables
declarative
management
for
kubernetes
using
api
using
and
making
it
easy
to
create,
configure
and
update
clusters.
This
simplify
simplifies
the
ready,
the
repetitive
tasks
of
kubernetes
lifecycle,
while
maintaining
consistency
and
reliability.
The
whole
goal
of
this
special
interest
group
in
cluster
api
is
to
make
cluster
lifecycle
boring,
basically
not
think
about
it.
So
if
you're
interested
in
contributing
to
making
cluster
lifecycle
the
most
mundane
activity
ever,
you
can
reach
out
via
slack
at
sig
cluster
lifecycle.
A
Lastly,
sig
scheduling,
so
this
group
is
responsible
for
the
components
that
make
pod
replacement
decisions
in
kubernetes.
Recent
initiatives
include
performance
improvements,
including
pod
schedule,
latency
and
throughput.
There
also
was
launch
of
a
new
working
group
focusing
on
enhancing
batch
workloads.
This
is
relevant
for
hpc
aiml
data
analytics
ci,
among
others.
Finally,
the
scheduler
plugins
subproject,
which
now
includes
10
plugins,
addressing
features
like
co-scheduling,
load-based
scheduling
and
elastic
quotas.
A
The
most
relevant
impact
has
been
the
improvements
in
the
scheduling
throughput.
It
can
now
achieve
300
pods
per
second,
according
to
tests
conducted
by
sig
scalability
interested
in
learning
more
reach
out
to
sig
scheduling,
scheduling
in
slack,
and
that
is
it
for
the
kubernetes
updates
hope
you
have
a
great
rest
of
kubecon.