►
From YouTube: Graduated Project Lightning Talk: Rook: Enterprise Storage for Kubernetes - Travis Nielsen, Red Hat
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. 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.
Graduated Project Lightning Talk: Rook: Enterprise Storage for Kubernetes - Travis Nielsen, Red Hat
All Kubernetes clusters require storage! But how do you configure and manage it? Come catch a glimpse of how Rook provides an enterprise storage platform to the community as an upstream and open-source project, available to any Kubernetes cluster, whether running on-prem or in the cloud. Rook was accepted as a graduated project by the Cloud Native Computing Foundation in October 2020.
A
Hello,
welcome
to
this
lightning
talk
presenting
on
rook
enterprise
storage
for
kubernetes,
I'm
travis
nielsen,
one
of
the
original
rook
maintainers,
and
I
work
for
red
hat
happy
to
be
here
with
you
today
virtually
and
hope
to
meet
you
soon
in
person
at
some
point.
So
let's
dive
right
in
all
right
so
who
needs
storage?
We
all
need
storage
right.
Applications
require
persistence,
that's
just
what
it
comes
down
to
now,
depending
on
where
you're
running
you
have
different
solutions
available
for
storage.
A
If
you're
running
a
cloud
provider
now
you
have
options
available
available
for
storage,
you
might
also
be
finding
limitations
with
them
or
each
cloud
provider
is
different.
You
don't
have
a
consistent
platform
there
or
if
you
go
into
your
own
data
center,
you
kind
of
fall
off
a
cliff
and
you
say
wait.
What
do
I
do
for
storage
now?
I
have
to
go
find
some
external
solution
to
provide
storage
to
my
kubernetes
cluster.
What
do
I
do?
Third
point?
A
Storage
is
traditionally
not
part
of
your
kubernetes
cluster,
it's
treated
as
an
external
plug-in,
but
why
really
should
storage
be
external?
To
kubernetes
shouldn't
we
be
able
to
manage
storage
as
any
other
kubernetes
application
inside
the
same
cluster
and
finally,
a
question
we
started
with
was
well.
If
you're
building
a
data
platform,
can
you
really
trust
a
new
data
platform,
something
built
from
scratch?
Or
is
there
a
way
we
can
bring
in
a
stable
data
platform?
A
Of
course,
it'll
be
consumed
like
any
other
storage,
plug-in
they'll
use,
storage
classes
and
pvcs
and
pvs,
and
all
that
goodness,
so
it
will
be
consumed.
The
same
with
the
same
patterns
that
you've
already
been
using.
A
second
storage
should
be
automated
and
it
should
be
done
in
a
way
that
is
native
to
kubernetes.
The
way
you
do
things
in
kubernetes
and
you
add
onto
kubernetes,
is
with
operators
and
with
custom
resource
definitions
or
crds.
A
We
looked
at
a
few
and
we
started
with
ceph.
We
said:
okay,
we
believe
in
ceph,
it's
been
around
for
a
long
time,
so
we're
going
to
take
sef
we're
going
to
bring
it
to
kubernetes
and
that's
where
rook
was
born.
But
now
rook
has
been
out.
For
a
few
years,
we've
declared
brook
stable
in
december
of
2018,
so
we're
yep
so
we're
just
over
two
years
with
production
deployments.
A
There
are
many
so
many
clusters
out
there
in
production.
I
frequently
hear
of
users
just
saying
how
glad
they
are
to
be
running
rook
in
production.
It
is
stable.
There
are
clusters
with
hundreds
of
nodes.
We've
got
clusters
of
many
petabytes
of
data.
We
have
some
large
clusters
out
there
running
production.
We
don't
know
about
most
of
the
clusters
honestly,
because
it
is
an
upstream
project.
People
are
free
to
use
it
and
they
don't
even
have
to
tell
us
about
it.
So
what
is
the
storage
platform?
A
A
Okay,
first
is
block
storage,
where
you
might
have
a
read,
read:
write
once
volume
a
pod
needs
to
write
to
his
storage
databases
and
whatnot,
just
a
simple
block:
storage.
Next
we've
got
shared
file
systems,
so
you've
got
multiple
pods
that
need
to
share
the
same
volume.
That's
you
know,
read,
write
many
stuff
provides
that
with
ffs
and
then
finally
object.
Storage
provides
an
s3
interface
with
buckets
gets
inputs,
and
all
that
so
ceph
has
has
all
three
of
these
provided
in
one
storage
platform.
A
So
let's
talk
about
the
community,
so
rook
is
a
cncf
graduated
project
where,
in
october
the
cncf
accepted
us
as
a
graduated
project.
We
believe
that's
a
great
testament
to
what
we've
been
building
and
the
community
we've
been
building
and
then
all
the
other
stats
are.
You
know
just
evidence
that
people
are
using
it
over
200
million
downloads,
that
just
kind
of
blows
my
mind
over
300
contributors,
we're
just
happy.
There
are
so
many
people
who
find
value
in
brooke
and
are
contributing
to
it.
A
Our
current
release
is
version
1.6
that
just
came
out
in
april,
so
try
it.
So
what
are
we
trying
to
accomplish
with
the
project?
I
mean?
How
do
we
make?
How
do
we
make
it
open?
What's
our
goal
with
it?
So
our
goal-
and
our
mantra
really
is
community,
is
first
we
want
to
build
something
that
the
community
finds
value
in.
This
is
why
we
donated
at
the
cncf.
This
is
why
we
progressed
became
a
graduated
project,
because
community
is
first
it.
The
project
is
completely
open
source
with
apache
2o
license.
A
We
have
a
cadence
of
quarterly
releases
for
minor
releases
with
regular
patch
releases.
You
know
we
tend
to
apache
leases
every
week
or
two
just
to
get
the
latest
fixes
out.
So
people
can
pick
those
up.
We
do
have
maintainers
from
four
companies
at
the
moment,
so
just
in
alphabetical
order,
claudical,
cybosu,
red
hat
and
upbound.
A
A
A
We
have
a
csi
driver
that
will
provision
a
mount,
the
storage
for
your
applications
and
then
finally,
as
already
mentioned,
ceph
provides
that
data
layer
for
block
shared
file
system
and
object
so
on
or
in
the
next
couple
of
days,
we'll
have
another
session
a
deep
dive
that
will
talk
more
in
depth
about
what
features
rook
has
what
what's
in
our
latest
release
and
show
a
demo
of
creating
a
cluster
with
local
pvs.
I
really
invite
you
to
check
out
that
demo
that
talk
that
we'll
have
for
you
later
so
get
involved.