►
From YouTube: Kubernetes SIG Storage Introduction and Update - Xing Yang, VMware & Michelle Au, Google
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 SIG Storage Introduction and Update - 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.
A
B
A
A
A
A
A
A
A
A
A
The
reclaim
policy
is
retained.
This
means
the
pv
will
remain
along
with
the
physical
volume
on
the
study
system.
When
the
user
deletes
the
pvc,
if
the
reclaimed
policy
is
deleted,
the
pv,
along
with
the
physical
volume,
will
be
deleted
when
the
user
deletes
the
pvc
a
low
volume
expansion
is
true,
so
water
expansion
can
be
requested
by
the
user
here
and
volume.
Bending
mode
is
immediate.
In
the
sturdy
class,
immediate
means
volume,
binding
and
dynamic
provisioning
occurs
once
the
pvc
is
created.
A
A
A
A
A
A
Here's
an
example
of
the
downward
api
volume.
It
makes
downward
api
data
available
to
the
applications
it
amounts
to
directory
and
writes
the
requested
data
in
plain
text
files
in
the
support
yaml
file.
You
can
see
that
the
pod
has
a
downward
api
volume
and
the
container
amongst
the
volume
at
a
specified
location,
each
element
and
items
is
a
downward
api
volume
file.
The
first
element
specifies
that
the
value
of
the
pods
metadata
labels
field
should
be
stored
in
a
file
named
labels.
A
In
this
example,
here
we
set
volume
type
to
csi
in
part,
inline
definition
and
specify
the
driver
name
and
volume
attributes
for
a
csr
driver
to
support
csi
admiral
volumes.
It
must
be
modified
or
implemented
specifically
for
this
purpose,
a
csi
driver
is
suitable
for
csi
ethmoid
inline
volume
if
it
serves
a
special
purpose
and
needs
custom
per
volume.
Parameters
like
drivers
that
provide
secrets
to
your
pod,
the
secret
store
system
driver,
is
a
good
example.
A
Next,
I'm
going
to
talk
about
generic
ethmoid
volume.
The
generic
ethmoidal
volume
feature
allows
any
existing
study
driver
that
supports
dynamic
provisioning
to
be
used
as
an
ethernet
volume.
With
the
volume's
lifecycle
bond
to
the
pod,
it
can
be
used
to
provide
scratch
storage
that
is
different
from
the
root
disk.
For
example,
persistent
memory
or
a
separate
local
disk
on
that
node.
A
A
A
A
A
Here
is
an
example
of
a
csi
deployment.
It
shows
various
kubernetes
components,
the
css
driver
and
the
3d
system
that
is
used
to
persist.
The
data
here
we
have
cube
controller
manager
on
master
cc,
driver
controller.
Plugin
is
deployed
together
with
kubernetes
csi,
external
provisioner,
external
attacher,
external
resizer
and
external
snapshot
or
sidecars.
A
Note
that
css
driver
controller
pod
does
not
have
to
run
on
the
same
node
as
the
kubernetes
master,
but
is
recommended
to
run
on
dedicated
control,
plane,
nodes,
the
kubernetes
csi
side.
Cars
are
watching
kubernetes
api
objects
such
as
pvcs,
pbs
volume,
attachments
volume,
snapshots
to
detect,
create
volume,
attached
volume,
word,
expansion
and
volume
snapshot.
Requests
said
course
called
the
csr
driver
and
the
cset
driver
communicates
with
the
solid
system
to
complete
those
volume
operations
on
kubernetes
worker
nodes.
A
A
A
A
B
Thank
you
shing.
So,
for
the
six
storage
update,
I'm
going
to
deep
dive
into
a
couple
of
major
efforts
that
have
been
going
on
in
the
sig
for
the
last
couple
of
releases
and
then
I'll
give
a
summary
of
of
projects
that
we
have
promoted
in
the
122
time
frame
and
talk
about
things.
Some
things
that
we're
working
on
in
1.23
and
also
things
that
are
currently
in
design,
prototyping
phases
and
then
other
projects
that
we
are
working
with.
Other
sigs
on.
B
B
Currently,
the
following
entry
volume
types
have
a
beta
implementation
of
csi
migration
that
you
can
enable
today
in
your
clusters,
and
the
plan
is
for
these
specific
plugins
csi
migration
features
to
be
g8
in
1.24,
so
we
have
aws
ebs,
azure
disk,
azure
file,
openstack
cinder,
gcepd
and
vsphere
volumes,
all
right.
So
moving
on,
what
do
you
need
to
do
to
actually
turn
on
csi
migration?
B
So
if
you're
using
a
managed,
kubernetes
distribution,
you
will
need
to
double
check
the
documentation
for
your
distro
to
see
how
they're
handling
the
csi
migration
and,
if
there's
any
steps
they
might
require
you
to
do.
But
in
most
cases
actually
the
distro
should
be
taking
care
of
everything
to
enable
the
feature,
including
installing
the
csi
driver,
so
you
for
those
for
it.
So
if
you're
using
a
managed
distribution,
you
very
likely
won't
have
to
do
anything
to
enable
the
feature,
but
it's
good
to
double
check
just
to
be
sure.
B
B
B
B
Right,
so
that's
most,
that's
mainly
csi
migration.
In
a
nutshell,
I
think
yeah.
Basically,
this
is
coming
soon
over
the
next
release
or
two.
So
please
take
a
look
if
you're
in
a
working
in
a
cloud
environment
and
using
a
cloud
volume
plug-in
and
please
reach
out
to
us,
if
you
have
any
questions
or
concerns
about
the
feature
all
right.
B
The
currently
it
supports
operations
for
ntfs
based
file
systems,
samba
and
then
iscsi
support
is
available
in
alpha
as
well
and
there's
a
couple
of
drivers
known
drivers
that
have
already
implemented
support
for
the
csi
proxy
api.
I
put
a
so
I
did
put
a
little
asterisks
next
to
the
mention
about
no
privileged
containers,
support
in
windows.
B
B
So,
if,
if
you
are
writing
a
csi
driver
and
you
want
to
support
windows,
I'm
sorry
if
you're
riding
a
csi
driver
and
you
want
to
support
windows,
please
take
a
look
at
csi
proxy
and
also
go
go
ahead.
And
if
you
have
questions,
there's
a
csi
windows,
slack
channel
where
you
can
you
know,
ask
questions
or
you
know
if
you
want
to
help
out
with
the
project.
That's
also
great
too.
B
B
This
is
a
very
important
feature
for
any
csi
driver
authors
out
there,
as
this
allows
csi
drivers
to
authenticate
on
behalf
of
the
pod.
So
this
feature
allows
you
to
be
able
to
support
per
pod
apples
on
your
volumes
or
whatever
data
that
your
csi
driver
is
accessing
and
it's
already
being
used
in
some
ephemeral.
Csi
drivers
like
the
secret
store
csi
driver
that
we
mentioned
earlier.
B
Another
interesting
feature
that
we've
done
in
122
is
the
read,
write
once
pod
access
mode,
so
this
feature
went
alpha
in
122
and
this
basically
fixes
a
common
misconception
about
access
modes
and
kubernetes.
So
the
current
read
write
wants
access
mode.
That's
available
today
indicates
that
a
volume
can
be
attached
to
one
node
at
a
time,
but
it
doesn't
actually
indicate
how
many
pods
on
that
node
can
mount
that
volume.
So,
with
read,
write
once
pd's
today
you
can
actually
have
multiple
pd's
or
sorry.
B
B
This
feature
improves
the
time
that
it
takes
to
mount
volumes
that
have
a
lot
of
files
in
them
by
only
updating
the
ownership
of
the
files
when
the
top
level
directory
owner
doesn't
match
what
the
fs
group
says
so
for
volumes
that
have
thousands
of
files
in
them.
We've
seen
in
in
some
cases
that
this
feature
is
able
to
bring
them
out
time
down
from
something
that
originally
took
more
than
30
minutes,
and
it
brings
it
down
to
seconds.
B
This
feature
allows
a
csi
driver
to
explicitly
opt
into
supporting
fs
group
previously,
without
this
kubernetes
uses
a
heuristic
to
determine
which
drivers
will
have
fs
group
applied
with
them,
and
the
heuristic
is
a
bit
flawed
in
certain
scenarios.
So
this
feature
allows
csi
driver
to
opt-in,
explicitly.
B
B
In
addition
to
these
features,
we
are
also
working
with
other
sigs
in
kubernetes
to
co-develop
some
other
things,
so
we
have
in
the
data
protection
work
group
we're
working
on
design
for
change,
block
tracking,
and
this
is
pretty
important
for
enabling
the
ability
to
do
efficient,
backups
of
volumes
and
then
in
sig
apps.
We
are
collaborating
with
them
to
make
some
improvements
to
the
stateful
set
pvc
lifecycle
and
then
sig
node.