►
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.
How to put a Database in Kubernetes - Jeffrey Carpenter, DataStax
The idea of running a stateful workload in Kubernetes can be intimidating, especially if you haven’t done it before. How do you deploy a database? Where is the actual storage? How is the storage mapped to the database or application that uses it? In this talk, we’ll demystify the deployment of databases and stateful workloads in K8s by showing that databases are just applications composed of compute, network and storage. We can deploy them like any other Kubernetes application and take advantage of resources that K8s provides including Storage Classes, Persistent Volumes, Persistent Volume Claims, and Stateful Sets. We will demonstrate how to make it all work by deploying a relational database (MySQL) and a NoSQL database (Apache Cassandra).
A
A
So
I'm
not
going
to
talk
for
five
minutes
about
myself.
Just
so
you
know
where
I'm
coming
from
software
engineer
got
into
architecture
after
that,
and
then
I've
been
worked
in
defense
and
in
hospitality
and
for
some
reason
I
always
try
to
get
myself
on
whatever
the
project
is
that
the
company
is
betting,
the
business
on.
So
that's
where
I
seem
to
end
up
that
has
led
me
into
some
interesting
spaces,
a
lot
of
distributed
systems,
so
that
got
me
into
apache
cassandra
and
kubernetes
and
then
now
putting
them
together.
A
So
that's
kind
of
the
genesis
of
how
I
got
involved
in
this
kind
of
thing.
So,
on
the
way
over
here
I
was
grabbing
a
snack
and
I
went
outside
to
the
coffee
station
and
I'm
walking
past
a
table,
and
I
don't
I
don't
recognize
anybody
here.
So
maybe
I'll
be
okay,
so
I'm
walking
past
the
table
and
there's
a
group
of
folks
and
they're
like
hey.
A
Did
you
see
that
data
stacks
is
going
to
be
doing
a
talk
about
how
to
put
a
database
in
in
kubernetes
and
one
and
one
guy
goes?
Why
would
you
do
that?
That's
what
oh,
there
is
still
skepticism
out
here
around
this
now.
You
know
I'm
in
a
world
where
I'm
used
to
this
and
I've
already
bought
into
it.
This
is
an
article
that
I'm
showing
up
here
that
a
colleague
of
mine,
chris
bradford,
wrote
about
his
personal
journey
from
being
very
anti.
A
You
know
running
databases
and
containers,
just
even
that
idea
to
how
he
kind
of
went
through
that
progression
of
running
databases
on
kubernetes.
So
what
I
thought
I
would
do
is
this
is
not
the
why
you
should
run
a
database
in
kubernetes
talk
it's
more
of
the
assuming
that
you
agree
with
the
premise
of
doing
it.
How
do
we
actually
go
about
doing
it,
that's
kind
of
where
I'm
coming
from?
A
If
you
want
to
ask
me
questions
about
why
at
the
end,
let's
do
it
there's
a
whole
community
of
people
that
are
working
on
putting
stateful
workloads
on
to
kubernetes
it's
the
data
on
kubernetes
community.
We
had
a
great
full
day
of
sessions
here
on
tuesday
you
can
go
and
watch
a
lot
of
those
sessions
online.
A
One
of
the
things
that
I
learned
recently
is
a
survey
that
the
dok
community
commissioned
I'm
talking
to
a
lot
of
developers:
architects,
cios,
you
know
kind
of
all
range
of
the
the
I.t
workforce
looking
at
who
is
adopting
kubernetes
for
stateful
workloads
and
it's
kind
of
encouraging
and
a
little
bit
surprising.
These
numbers
that
that
were
that
were
able
to
come
through
now,
who
knows?
Is
there
confirmation
bias
from
people
who
are
willing
to
fill
out
a
survey
about
data
on
kubernetes
yeah?
It
may
be
okay,
but
look
at
this.
A
A
So
how
do
we
get
there?
I
want
to
be
clear,
and
you
know,
set
expectations,
and
you
probably
saw
this
when
you
were
looking
for
sessions.
This
is
an
introductory
level
session,
so
I'm
hitting
the
wave
caps
and
what
I
want
to
present
to
you
is
a
way
of
thinking
about
how
you
put
databases
and
possibly
other
stateful
workloads
onto
kubernetes.
So
I've
tried
to
break
it
down
into
a
few
simple
steps
and
it
starts
with
making
sure
that
you
understand
the
kubernetes
primitives
for
stateful
data,
including
the
persistent
volume
subsystem.
A
You
want
to
pick
a
storage
provider
because,
ultimately,
your
data
needs
to
end
up
somewhere
unless
you're
just
doing
caching,
you
need
to
pick
a
database
and
then
I'm
going
to
highly
recommend
that
you
find
an
operator
assuming
that
you're
using
a
pretty
common
or
popular
database.
So
those
are
the
steps.
A
What
we'll
begin
with
is
making
sure
that
we
understand
these
kubernetes
primitives
and
especially
the
ones
for
managing
state
for
stateful
workloads,
but
actually
we're
going
to
look
at
some
some
of
the
other
primitives
as
well,
that
are
not
exclusively
for
managing
state
they're,
all
involved
in
putting
a
database
on
kubernetes.
So
here
we
go.
A
I
want
to
start
with
demystifying
something.
Now
when
I
was
a
junior
developer,
I
was
afraid
of
databases.
Okay
database
was
like
there
was
one
guy
on
the
team
that
knew
how
to
interact
with
the
database
to
be
the
dba,
create
the
tables
and
manage
all
of
that.
You
wanted
anything.
You
went
to
the
guy
and
this
was
a
bad
thing,
because
mitch
got
stuck
there
for
a
while,
like
he
got
pigeonholed
and
he
was
the
only.
He
wanted
to
go
and
do
other
things,
but
he
was
the
database
guy.
A
He
was
the
only
one
that
knew
how
to
do
it.
So,
let's
demystify
a
database
is
an
application
in
applications
when
we
deploy
them
in
kubernetes
or
anywhere
else,
they're,
really
an
assemblage
of
compute
network
and
storage.
Those
are
their
needs
right.
It's
code.
It
needs
somewhere
to
run.
It
knows
how
to
talk
to
other
things,
and
it's
got
to
have
some
place
to
put
its
data
that
fits
a
database
just
as
well
as
any
other
application.
A
Okay.
So
let's
look
at
what
kubernetes
gives
us
and
break
it
down,
organize
the
community
kubernetes
primitives
in
terms
of
compute
network
and
storage?
Okay.
So
we
have
these
primitives
for
running
pods
on
worker
nodes.
We
have
replica,
sets
and
deployments
that
we
can
use
to
run
multiple
copies
of
things
we
have
now
stateful
sets
that
kubernetes
gives
us
to
run
stateful
workloads
for
exposing
our
capabilities
as
services.
A
We
have
a
kubernetes
service.
We
have
things
like
kubernetes
ingress,
so
these
are
primitives
that
kubernetes
gives
us
for
allowing
things
to
find
each
other
and
talk
to
each
other
and
then,
in
terms
of
storage.
We
have
a
whole
persistent
volume
subsystem
that
you
know
we're
definitely
going
to
focus
on
those,
but
in
order
to
deploy
a
database,
we
just
need
to
pick
the
right
pieces
from
kind
of
this
grab
bag
of
resources.
That
kubernetes
gives
us
I'm
going
to
show
you
some
code
here.
A
A
A
Okay,
so
I
want
to
talk
about
the
persistent
volume
subsystem
portion
of
kubernetes,
so
our
pods
can
mount
volumes
and
then
the
volumes
can
be
of
various
types
now
in
production
systems.
What
we
see
most
commonly
is
the
use
of
persistent
volume
claims.
So
that's
a
a
pvc
mount
is
the
most
most
common
type
of
volume
that
we
see
mounted
for
an
application.
That's
doing
something:
that's
stateful,
okay,
so
the
way
this
breaks
down
is
I
create
my
pod.
A
I
create
a
persistent
volume
claim.
That's
gonna
basically
represent
a
request
for
storage
that
my
pod
has
and
then
the
kubernetes
is
going
to
leverage
a
storage
class
which
is
managed
managing
a
section
of
storage
in
order
to
create
persistent
volumes
and
then,
when
we
create
pods
and
replicas
sets
and
stateful
sets,
then
that's
when
the
process
of
creating
those
persistent
volumes
and
associating
with
them
with
persist.
Volume
claims
happens
generally.
A
A
A
So
this
is
an
example
of
a
persistent
volume
declaration.
It
references
a
volume
size,
it
references
allowed
access
modes,
so
you
can
have
read
only
read
write.
You
can
have
volumes
that
can
only
be
written
by
a
single
writer
at
a
time
these
kinds
of
parameters
now
this
particular
definition
is
an
example
of
a
local
volume
that
is
mapped
to
a
specific
kubernetes
worker
node
using
node
affinity
and
again.
A
This
is
something
that
would
typically
be
configured
by
someone
who's
responsible
for
for
the
administration
of
your
kubernetes
cluster,
so
more
on
the
op
side
than
the
app
dev
site.
Once
a
persistent
volume
has
been
made
available
for
application
use
either
manually
or
they
can
be
dynamically
created
by
storage
classes.
As
we'll
see,
we
can
reference
the
persistent
volume
in
our
pod
specifications
through
creating
a
persistent
volume
claim,
and
this
provides
a
really
good
separation
of
concerns.
A
This
allows
us
to
as
an
app
developer,
just
ask
for
the
storage
that
we
need
and
the
characteristics
that
it
should
have
without
having
to
have
the
knowledge
about
the
specific
provider
that's
in
use.
This
also
makes
our
applications
more
easily
portable
so
that
they
can
run
in
a
different
environment.
As
long
as
we,
the
persistent
volume
claim,
can
be
satisfied
by
some
persistent
volume
that's
available
in
the
target
environment,
then
we
should
be
good
to
go.
A
A
A
So
on
the
right
side,
you
see
a
pod
that
has
been
defined
to
reference
that
particular
pvc,
so
pods
linked
to
pvcs,
which
link
to
persistent
volumes
which
are
created
by
storage
classes,
all
right.
So
speaking,
of
storage
classes.
This
is
where
the
idea
of
picking
a
provider
comes
into
play.
So
we
understand
the
kubernetes
primitives
at
this
point
now
we're
ready
to
take
what
we've
learned
and
assemble
things
to
deploy.
Applications.
A
Okay,
so
storage
class
is
responsible
for
the
dynamic
provisioning
of
storage
on
persistent
volumes.
In
order
to
help
satisfy
our
pvcs,
so
the
storage
class
handles
the
details
of
interfacing
with
our
requested
provider
or
the
provider
that
we've
configured
so
that
the
requested
amount
of
storage
can
be
set
aside.
A
I
didn't
I
did
like
sort
of
like
an
informal
survey.
I
didn't
count
on
my
fingers
or
anything,
but
as
I
was
going
through
the
kind
of
the
solution
showcase,
there
are
a
lot
of
storage
providers
here
at
kubecon.
This
is
a
rich
area
of
you
know,
competition
and
innovation,
and
and
so
there's
a
lot
of
options
that
are
available
and
that's
just
even
from
third-party
vendors.
I'm
not
even
counting
the
the
what's
available
from
our
standard
public
cloud
providers.
A
So
one
of
the
things
that's
pretty
cool
is
this
little
tool
recently
discovered
new
to
me
at
the
bottom
of
the
slide
here,
the
kubester,
which
is
a
tool
that's
going
to
allow
you
to
see
what
storage
classes
are
already
available
in
your
cluster
and
make
sure
that
they
are
configured
correctly.
So
that's
a
that's
a
pretty
fun
way
to
educate
yourself.
A
The
example
that
I'm,
showing
here
of
declaring
a
storage
class
is
a
really
simple
example
of
a
free
storage
provider
from
you
know
open
source
from
rancho
labs
that
basically
just
allows
you
to
provision
your
your
desktop
or
laptop
computer
as
a
storage
provider,
if
you're
just
running
kubernetes
on
your
desktop
kind
of,
for
you
know
local
dev
purposes,
so
I
use
this.
I
use
this
one
all
the
time.
A
A
You
can
use
csi
compliant
storage
providers
on
other
container
orchestration
platforms
as
well,
but
this
provides
a
specification
and
basically
an
api
for
providing
cloud
native
storage
and
most
of
these
cs,
csi
providers,
not
necessarily
all,
but
most
of
them,
actually
implement
their
control
plane
on
kubernetes.
So
I
think
it's
really
cool
that
you
know
you
can
have
your
storage
actually
managed
on
the
kubernetes
platform,
and
so
anyway,
I
love
geeking
out
peeking
under
the
covers
for
just
a
second
okay.
A
So
now
that
we
know
about
the
primitives
that
we
have
and
the
the
storage
providers
that
we
have
available
to
us,
so
we
pick
a
storage
provider.
Now
we're
gonna
pick
a
database
and
I'm
gonna
give
you
two
options
here
of
different
deployments
for
databases,
we're
gonna,
look
at
a
single
node
deployment
of
my
sql.
Now
I
understand
that
multi-node
deployments
of
my
sql
are
possible,
so
don't
get
us
up
with
me.
A
A
That
is
a
multi-node
deployment,
maybe
compare
and
contrast
and
look
at
using
some
of
the
different
application.
Compute
primitives
that
we
introduced
earlier,
namely
replica
sets
and
deployments
and
staple
sets
okay.
So
here's
a
sample
deployment
of
sequel-
and
this
is
based
on
an
example
that
you
can
find
in
the
kubernetes
documentation
I've
kind
of
forked
it
on
our
our
repo
that
I
shared
with
you
earlier
that
that
data
on
kate,
kate's
book,
repo
or
github
org,
and
so
very
you
know,
relatively
minor
modifications
to
that
standard,
kubernetes
documentation
example.
A
What
this
does
is
deploy
wordpress
a
single
node
of
wordpress
on
top
of
a
single
node
of
mysql,
and
one
thing:
that's
that's
kind
of
interesting
around.
This
example
is
that
it
shows
not
only
my
sql,
creating
a
pvc
and
getting
some
storage
allocated
to
it,
but
then
also
wordpress
is
using
mysql
and
also
on
top
of
that,
getting
its
own
volume
where
it
wants
to
store
some
configuration
data.
A
So
it's
a
good
demonstration
of
the
idea
that
applications
can
use
databases
which
use
persistent
volumes
and
applications
can
also
assign
volume
or
acquire
volumes
directly
themselves
so
because
we
are
only
deploying
a
single
node
of
mysql.
In
this
example,
a
kubernetes
deployment
is
a
good
choice.
Now
a
deployment
is
a
compute
construct
that
is
going
to
sit
on
top
of
replica
sets,
so
deployments
manage
the
life
cycle
of
replica
sets,
which
in
turn
create
pods
according
to
a
number
of
replicas
that
we
request.
A
So
this
is
better
than
just
running
a
database
in
a
bear
pod
by
itself,
because
when
you
create
it
as
part
of
a
deployment,
kubernetes
is
going
to
take
on
responsibility
for
that
life
cycle.
For
making
sure
that
your
desired
number
of
replicas
in
this
case,
one
is
running
so
we're
gonna
this.
This
might
not
be
super
high
availability,
because
we
could
have
some
downtime
if
a
pod
dies
and
has
to
be
recreated
we're
down
from
a
database
perspective
during
that
restart
period,
but
it
is
going
to
give
us
some
measure
of
availability.
A
The
other
thing
that's
curious
to
note
here
is
you
see
on
this
slide
that
there's
two
replicas
that
are
created
by
this
replica
set
they're
both
pointing
to
the
same
pvc?
So
this
is
a
characteristic
of
these
replica
sets.
Is
that
there's
only
one
pvc
that
is
defined
in
the
replica
set
if
you
create
multiple
replicas
they're
all
pointing
to
that
one?
Pvc
now
this
is
a
great
config.
This
is
a
great
configuration.
A
The
first
thing
is
on
the
left:
there
is
you
see,
security
credentials
now,
one
of
the
things
I
love
about
working
with
kubernetes
is
that
things
are
secure
by
default
right.
You
can't
get
out
of
port
unless
you
expose
it.
So
we
want
to
apply
these
same
principles
when
we're
talking
about
databases,
so
the
mysql
that
we're
deploying
has
a
administrator,
username
and
password.
We
can
actually
control
what
that
is
by
defining
it
in
a
secret
which
we
will
then
pass
into.
A
A
Okay,
so
again,
we're
not
creating
an
individual
pod,
we're
creating
a
deployment
that
wraps
it,
and
so
part
of
this
definition
is
not
the
actual
pod,
but
a
template
for
a
pod.
So,
every
time
the
deployment
is
going
to
create
an
additional
pod,
it's
going
to
use
this
template
or
kind
of
the
recipe
for
creating
that
pod
and
again,
you
see
in
there
the
reference
to
the
single
pvc
that
we
declared
earlier.
A
All
right,
the
next
piece
that
we're
going
to
talk
about
is
how
do
you
actually
make
a
database
accessible
to
your
applications?
Again,
it
would
kind
of
be
lame
to
address
our
applications
to
a
single
pod
instance,
a
kind
of
a
hard-coded
instance
or
ip
address,
because
that
pod
could
die
and
get
restarted.
So
we
want
to
stick
a
kubernetes
service
in
front
of
that,
and
this
is
going
to
abstract
the
details
of
where
that
database
instance
is
actually
living
on
the
network.
A
We
have
different
types
of
services
that
are
defined
in
the
kubernetes
world,
so
you
have
a
cluster
ip
service,
which
is
only
within
the
scope
of
that
cluster.
You
can
use
load
balancers
and
those
are
services.
Typically,
you,
typically
implementation
of
a
load.
Balancer
is
tied
to
your
cloud
provider,
so
incoming
calls
might
be
round
robin
to
different
instances
behind
that
service.
You
might
find
that
useful.
A
We
have
other
things
like
external
ports.
We
have
ingress
that
can
be
defined
and
what
we
see
most
often,
if
we're
talking
about
a
database
tier,
is
the
use
of
a
cluster
ip
service
or
maybe
a
load
balancer.
That's
that's
what
I
tend
to
see.
Most
often,
usually
you
have
an
application.
That's
sitting
on
top
of
your
database
and
the
application
is
what
is
providing
an
interface
outside
of
kubernetes,
so
not
that
you
couldn't
expose
the
database
directly,
but
I
just
don't
see
that
very
often.
A
A
So
what
this
does
is
when
you
do
the
dns
lookup,
based
on
this
name
of
a
wordpress
mic
sql
service,
what
you
would
get
back
is
the
ip
addresses
of
everything,
that's
sitting,
underneath
it
and
again,
in
this
case
it's
just
a
single
ip
address.
So
headless
service
is
a
great
way
to
go.
To
put
in
front
of
your
database
instance.
A
All
right,
so
that
was
a
quick
fly
through
of
a
mysql
deployment
example
again,
I
want
to
refer
you
to
the
github
repo
in
the
book.
If
you
want
kind
of
the
more
blow
by
blow
detailed
description,
we
try
to
go
through
all
the
the
various
options
kind
of
at
a
high
level
and
then
refer
you
to
the
the
points
in
the
kubernetes
documentation
where
you
can
deep
dive
and
get
the
lower
level
details
so
just
hitting
the
wave
caps
for
you
right
now.
A
We
want
to
talk
about
deployment
of
cassandra
now
so
the
way
that
cassandra
works
is
it's
a
multi-node
architecture.
No
one
runs
one
node
of
cassandra
in
production,
not
very
many
people
run
three
nodes
of
cassandra
in
production.
Generally,
you
have
a
lot
of
data
if
you're
using
cassandra
and
those
are
organized
in
there's
two
different
ways
to
think
about
how
cassandra
organizes
itself
and
the
data
that
it's
storing
so
there's
two
viewpoints
on
this
slide.
They
both
refer
to
the
same
cluster.
A
A
A
If
you
have
some
familiarity
with
stateful
sets
the
way
that
what's
shown
here
is
a
cassandra
deployment
that
has
three
racks,
so
one
data
center
consisting
of
three
racks
and
there's
a
single
pod-
that's
shown
here
in
each
rack,
and
so
we
have
a
stateful
set
that
is
managing
each
of
the
racks
and
then,
as
you
can
see
here,
there's
a
there's,
a
key
difference
from
the
my
sequel
example
that
we
saw
before
in
that
each
pod
is
actually
getting
its
own
persistent
volume
claim.
So
this
means
each
cassandra.
A
So
this
is
probably
our
most
complicated,
complicated
yaml
that
we're
going
to
see
so
trigger
warning
for
anyone
who
doesn't
like
reading
yaml
on
slides,
possibly
including
me,
but
this
is
better
than
me-
scrolling
through
a
terminal
window
and
screwing
it
up.
So
this
is
a
the
definition
of
a
stateful
set
for
for
a
cassandra
cluster.
It's
going
to
span
a
couple
slides,
we'll
just
walk
through
it
a
little
at
a
time
and
I'll
try
to
to
guide
you
through.
So
the
left
side.
A
Also,
on
this
left
side
we're
looking
at
we're,
defining
which
policies
we
want
kubernetes
to
use.
There
are
some
options
for
how
it
manages
the
life
cycle
of
the
pods
as
it's
as
it
spins
them
up
and
down
to
scale
up
and
and
destroys
pods
in
order
to
scale
down
in
the
stateful
set.
So
the
options
that
I've
specified
here
are
actually
the
defaults
and
they
represent
a
more
conservative
approach
to
to
managing
the
stateful
set
in
that
they're.
A
Going
to
start
one
note
at
a
time
and
they're
going
to
wait
for
each
node
to
to
report
that
it's
ready
before
starting
to
spin
up
the
next
note
and
the
the
restart
policy.
That's
here
is
it
functions
in
a
similar
way,
so
restarting
a
single
node
at
a
time
when
you,
so
the
the
stateful
set,
does
support
the
idea
of
a
rolling
update,
so
you
can
deploy
updates
to
the
to
the
stateful
set
that
will
be
rolled
out
individually
to
the
pots.
A
There's
other
things
that
we
see
here
on
the
right
side
of
the
slide:
exposing
ports
for
the
different
interfaces
that
cassandra
has
for
client
access
with
this
with
cql
cassandra,
query
language
management,
apis
interfaces
for
talking
to
other
nodes
and
so
on,
and
the
last
little
thing
on
the
bottom
right
there
is
is
kind
of
cool,
defining
a
pre-stop
command.
This
helps
us
have
each
cassandra
node
be
a
good
citizen
in
instead
of
just
ghosting
the
rest
of
the
cluster.
A
When
we,
when
we
scale
down
the
cluster,
it's
going
to
actually
communicate
and
offload
its
data
nicely
to
other
nodes
within
the
cluster.
So
there
are
other
hooks
that
we
can
define
in
terms
of
we
can
we
can
customize
the
liveness
and
readiness
probes
that
are
used
on
each
node
as
well
as
this
pre-stop
that
you
see
here:
okay,
we're
halfway
through
the
yaml
all
right.
So
what
we
see
here
on
the
left
side
is
overriding
some
environment
variables.
A
The
particular
cassandra
image
that
we're
using
in
this
example
actually
allows
configuration
by
providing
a
yaml
file,
which
you
can
swap
in
and
override
cassandra's
built-in
yaml
configuration,
or
you
know,
there's
also
several
environment
variables
that
are
supported,
that
you
can
kind
of
override
the
the
location
of
various
things
and
and
some
different
properties,
and
then
finally,
we
need
storage.
So
we're
going
to
define
a
pvc
template
and
every
time
the
stateful
set
is
going
to
stamp
out
a
new
pod.
A
It's
going
to
create
a
new,
a
new
pvc
according
to
the
template
that
we
have
defined
here
and
this
functions
much
the
same
way
as
the
other
pvc
definitions
that
you've
seen
in
the
previous
slides.
So
that's
that's.
The
great
thing
about
stateful
sets
is
that
it's
going
to
manage
the
the
creation
of
these
pods
and
the
creation
of
the
storage
that
they
need.
At
the
same
time,
one
of
the
things
that
they
do
not
do
is
when
you
scale
down
a
cluster
and
nodes
are
eliminated
from
the
stateful
set.
A
A
A
You
may
or
may
not
so,
and
that's
just
all
I've
shown
you
here
is
some
brief
talk
about.
You
know
initial
deployment
of
the
database
and
then
maybe
a
little
bit.
We've
talked
about
scaling
up
and
scaling
down
or
kind
of
hinted
at
that.
Now.
What
about
things
that
databases
need
care
and
feeding
tuning?
A
A
So
this
is
a
great
quote
from
tuesday.
This
is
very
likely
a
paraphrase
of
what
was
actually
said,
but
I
remember
rick
vasquez
from
western
digital
saying
something
like
this
and
a
great
panel
discussion
that
was
part
of
that
dok
day
and
his
his
words
of
wisdom
were
basically
yeah.
If
you're,
you
know
deploy
if
you're
going
to
deploy
a
database
in
kubernetes,
you
should
use
an
operator,
and
that
was
like
a
word
to
everyone.
A
A
So
cast
operator
manages
the
provision
and
running
of
your
nodes,
but
you
also
need
other
things,
and
this
is
a
common
thing
for
other
databases
as
well.
You
need
to
manage
backup
and
restores.
Maybe
you
need
secure
provisioning
of
keys
or
different
access
credentials,
there's
a
lot
of
things
that
go
into
it
right.
So
an
example
of
something
innovative
that
we're
doing
in
the
cassandra
community.
Is
this
kate
sander
project
in
which
we're
actually
building
an
ecosystem
of
things
around
the
core
cassandra
project?
A
What
we're
basically
doing
with
that
is
a
lot
of
the
technology
that
that
runs
that
goes
into
stargate
and
the
kate
sander
projects.
So
when
people
ask,
are
you
you
know,
can
you
run
a
database
on
kubernetes?
Well,
I
mean
that's
what
we're
doing.
We
have
a
whole
database
as
a
service
business
that
is
running
in
kubernetes.
A
So
if
you
want
to
hear
more
about
this
kind
of
stuff,
there's
a
talk
that
my
colleague
chris
bradford
is
is
co-presenting
with
tai
from
google.
This
afternoon
I
recommend
checking
that
talk
out,
especially
if
you
want
to
talk
about
multi-cluster
going
having
a
database
that
spans
multiple
kubernetes
clusters.
This
is
a
really
interesting
and
innovative
area
and
there's
a
lot
of
work
going
on
here.
A
This
is
the
book
plug
that
I
promised
that
you.
I
know
that
you
really
wanted
to
see
the
first
three
chapters
are
out
and
available.
If
you
have
an
o'reilly
account,
you
can
see
them
on
the
learning
platform
and
I'm
really
grateful
to
portworx
who
have
agreed
to
sponsor
the
book,
and
you
can
actually
get
the
first
three
chapters
for
free,
that's
what
the
first
three
that
are
available
from
them
right
now,
they've
been
handing
out
cards
and
I'm
giving
you
an
address
here
that
you
can
use.
A
This
is
something
that
I
don't
we're,
not
the
world
class
experts
like
no
one.
There
is
no
one
that
has
all
of
the
knowledge,
so
I'm
really
happy
to
be
corrected
and
fault
to
be
found
with
things
that
we
have
written
and
things
that
can
be
made
better.
So
I'd
love
to
have
feedback
from
people
that
are
looking
at
the
early
release
of
the
book
and
I'm
going
to
go
hang
out
at
the
datasacks
booth.
A
So
I
know
that
you
want
to
hear
my
colleague
rags
come
and
give
some
demos
he's
going
to
be
doing
some
hands-on
stuff
with
kate
sandra
at
the
booth,
and
I
think
he
also
has
a
couple
of
t-shirts
to
give
away.
If
we
have
folks
to
that,
want
to
ask
questions
and
I'm
sorry,
virtual
people,
I
cannot
send
you
a
virtual
t-shirt.
Okay,
so
I'm
ready
for
questions.
If
we
have
time.