►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. 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.
Intro & Deep Dive: Kubernetes SIG-Storage - Xing Yang, VMware & Michelle Au, Google
Kubernetes SIG Storage is responsible for ensuring that different types of file and block storage are available wherever a container is scheduled, storage capacity management (container ephemeral storage usage, volume resizing, etc.), influencing scheduling of containers based on storage (data gravity, availability, etc.), and generic operations on storage (snapshotting, etc.). In this session, we will give an introduction to SIG Storage and then deep dive into some projects that SIG Storage is currently working on, provide an update on the current status, and discuss what might be coming in the future.
https://sched.co/ekHD
A
A
A
A
This
includes
provisioning,
a
new
volume
attaching
the
volume
to
the
node
and
mounting
it
so
that
the
part
can
use
it
augmenting
detaching
and
deleting
the
volume
when
it
is
no
longer
needed
taking
snapshots
so
that
it
can
be
used
to
restore
the
volume
if
the
original
volume
is
corrupted.
For
some
reason,
six
storages
also
looks
at
how
to
influence
the
scheduling
decisions
based
on
topology
information,
to
see
whether
the
storage
is
accessible
to
a
node
and
make
sure
volume
is
scheduled
to
a
node
which
can
have
access
to
the
storage.
A
A
We
have
a
storage
class
concept.
Surgical
class
provides
a
way
for
administrators
to
describe
the
classes
of
storage.
They
offer
different
classes.
Might
map
to
different
quality
of
service
levels
in
dynamic,
provisioning
search
class
is
used
to
find
out
which
provisioner
should
be
used
and
what
parameters
should
be
passed
to
the
provisioner
when
creating
the
volume
kubernetes
plugins
include
entry,
plugins,
auto-tree,
flex
volume
and
csr
drivers.
A
A
New
features
are
only
added
to
the
csi
drivers.
We
will
be
talking
about
the
status
of
a
cmsi
migration
in
later
slides
csi
is
supported
by
multiple
container
orchestration
systems
and
storage
vendors
other
than
persistent
volumes.
There
are
also
fmr
volumes.
F1
volume
is
specified
directly
in
a
pod
spec.
A
A
A
This
is
part
of
an
effort
to
move
entry
cloud
provider
plugins
to
output,
3
csr
drivers
to
use
this
feature.
User
must
also
deploy
the
equivalent
csi
driver
to
on
csi
migration
feature
flag
that
is
defaulted
on
in
1017
release
and
also
the
csi
migration
provider
feature
gate
for
the
corresponding
cloud
provider
in
1.19.
A
A
The
other
feature
got
promoted
to
beta
was
immutable
secrets
and
config
maps.
This
allows
secrets
and
config
maps
to
be
read.
Only
both
world
expansion
and
warling
snapshot
stayed
in
beta
1.19
release,
but
we
made
lots
of
improvements
forward
expansion
we
added
offline
world
expansion,
support
detection,
so
csi
driver
can
return
a
field
pre-condition
error
code.
If
only
offline
expansion
is
supported,
but
the
user
has
requested
a
expansion
when
volume
is
online.
This
way
kubernetes
csi
reset
the
sidecar
will
stop
calling
controller
expand
volume
for
the
snapshot.
A
In
1019,
we
also
introduced
a
few
new
aha
features.
We
introduced
this
csi
storage
capacity
tracking,
so
we
added
a
new
csi
study
capacity.
Api
object
in
kubernetes
core
api
in
the
storage
api
group.
Without
this
feature,
part
scheduling
was
done
without
considering
that
the
remaining
storage
capacity
may
not
be
enough
to
start
a
new
pod.
With
this
feature,
csi
driver
can
report
available
capacities
associated
with
node
topology
and
switch
class,
so
that
that
capacity
sees
a
function
and
kubernetes
scheduler
will
make
placement
decisions
when
choosing
an
order
for
a
pod.
A
Kubernetes
has
volume
proteins
whose
life
cycle
is
tied
to
your
pod
and
can
be
used
as
a
scratch
space.
For
example,
we
have
built
in
empty
dirt
volume
type
or
those
type
of
plugins
can
be
used
to
load
some
data
to
a
pod.
For
example,
we
have
the
building
config
map
secret
volume,
types
or
csi
inline
volumes.
A
A
All
the
parameters,
all
the
parameters
used
in
a
storage
class
for
the
volume
provisioning
are
also
supported
by
this
genetic
ethmoid
volume
and
all
features
supported
with
persistent
volume
cleanse
are
supported.
That
includes
the
storage
capacity,
tracking
snapshots
and
resizing
the
third
new
of
a
feature
introduced
in
1019
is
csi
volume.
Health.
A
A
B
All
right,
thank
you,
shane.
So
in
120
we
have
a
lot
of
good
things
planned
that
are
graduating.
First,
is
the
csi
volume
snapshot
feature?
We
are
targeting
ga
in
120,
so
this
feature
gives
you
the
ability
to
be
able
to
take
snapshots
of
a
persistent
volume
claim
and
then
be
able
to
create
new
pvcs
from
those
snapshots.
B
B
The
next
feature
that
we
are
planning
to
graduate
from
alpha
to
beta
is
non-recursive
volume.
Ownership
specifically
for
the
fs
group.
Setting
this
feature
gives
you
the
ability
in
your
pod,
to
specify
that
you,
you
only
want
to
change
volume,
ownership
of
a
volume
only
if
the
group,
the
fs
group
setting,
has
changed
so
this
is
an
important
performance
enhancement
for
if
you
have
a
volume
that
has
a
lot
of
files
on
it
and
the
ownership
doesn't
change.
B
B
The
third
feature
that
we
are
targeting
beta
in
120
is
is
sort
of
related.
It's
the
csi
driver
policy
for
fs
group.
This
is
the
ability
for
a
csi
driver
to
be
able
to
specify
if
they
support,
fs
group
modifications
or
not.
This
is
planning
to
graduate
to
beta
in
120
and
then
the
last
feature.
Graduation
is
azure
file,
csi
migration,
and
this
is
targeting
beta
in
1.20
and
after
I
believe,
after
this
feature,
azure
file
graduates.
B
And
that's
all
that
we
have
planned
for
1.20.
Moving
on
to
beyond
1.20
we
have
a
couple
of
a
number
of
different
features
in
the
pipeline.
First
are
the
graduating
features.
First,
is
volume
expansion?
This
has
been
long
in
beta
for
quite
a
few
releases
now
and
we
are
working
on
trying
to
iron
out
all
the
remaining
remaining
sort
of
design
issues
and
we're
hoping
to
be
able
to
target
a
ga
of
this
feature
in
1.21.
B
An
important
change
that
we're
making
is,
we
are
deprecating.
The
online
offline
volume,
expansion,
csi
plugin
capability,
the
online
and
offline
expansion
is
still
supported.
It's
just
that
the
actual
csi
capability
will
be
deprecated
and
instead
we'll
be
using
specific
error
codes
to
be
able
to
determine
if
a
plugin
can
support
online
or
offline
expansion.
B
B
This
is
also
still
some
of
it
is
a
little
bit
up
in
the
air,
because
there's
the
new
there's
a
new
effort
going
on
in
sig
windows
for
for
allowing
privileged
containers
in
windows,
so
that
might
adjust
some
of
the
timelines
here,
but
I
think,
for
the
most
part,
are
the
whole.
The
main
plan
we
have
right
now
is
to
target
ga
of
at
least
csi
proxy
windows.
Support
in
1.21.
B
B
B
Another
feature
that
we
are
currently
actively
designing
and
discussing
right
now
is
volume
groups,
and
this
is
sort
of
the
notion
that
a
group
of
pvcs
are
related
to
each
other
in
some
way,
such
as
they're.
All
all
the
pvcs
are
replicas
of
a
particular
stateful
set
as
an
example,
and
this
concept
is
going
to
enable
a
lot
of
various
use
cases,
some
of
which
include
being
able
to
have
snapshot
consistency
across
multiple
volumes
and
another
use
case
is
to
be
able
to
do
failure,
domains
spreading
across
volumes
in
the
same
group.
B
B
B
This
effort
is
currently
under
prototype
and
there
are,
there
are
weekly
design
meetings
for
these.
So
definitely,
if
you
are
interested
in
these
efforts,
please
join
us
in
in
six
storage
and
you
can
get
you
can
go
ahead
and
participate
in
these.
This
all
the
all
of
these
discussions
for
these
various.
B
B
So
that's
a
very
important
effort
that
we're
currently
under
design
and
prototype
right
now.
In
addition,
we're
working
with
sig
apps
on
a
number
of
features
related
to
stateful
sets.
First,
is
supporting
volume.
Expansion
for
stateful
sets
through
the
stateful
set
volume,
claim
templates
and
then
the
other
feature
we're
working
on
is
to
be
able
to
clean
up
pvcs
when
a
stateful
set
is
deleted
or
scaled
down.
So
these
are
both
efforts
that
we're
sort
of
co-working
on
with
us,
sig
apps,
so
be
on
the
lookout
for
those
and
then
with
sig
scheduling.
B
B
All
right,
so,
as
you
can
see,
there
are
a
ton
of
different
features
and
projects
that
we
are
working
on
in
six
storage
and
we
would
definitely
appreciate
all
the
help
we
can
get.
So
if
you
are
interested
in
getting
involved,
please
go
to
our
sig
storage
community
page
there.
You
can
find
the
details
for
our
bi-weekly
meetings,
every
9
a.m.
Pacific
time
every
other
thursday.
B
If
you
want
to
get
one
of
the
best
ways
to
start
getting
involved
is
to
just
just
start.
Looking
at
the
code,
one
of
my
favorite
methods
is
to
just
start
with
the
main
method
and
walk
down
it
until
you
get
to
the
part,
you
need
it's
a
great
way
to
run
through
the
code
and
sort
of
start
at
the
top
level
and
see
where
it's
going.