►
From YouTube: OpenShift Coffee Break: DBaaS Series - CockroachDB
Description
Get your espresso ready for the OpenShift Coffee Break for another episode of the Database-as-a-Service (DBaaS) on Kubernetes at ease series with Red Hat OpenShift! Today we welcome Mike Bookham, Solutions Engineer at CockroachDB, to show how create cloud-native applications with CockroachDB Dedicated and Red Hat OpenShift Database Access (RHODA).
A
B
C
A
That
I
will
present
in
in
a
in
a
moment,
but
before
everything
welcome
everyone
for,
for
those
of
you
who
don't
know
us,
we
are
openshift
TV
and
web
TV
talking
about
openshift,
kubernetes,
Cloud
native,
and
my
name
is
natala
bitum
I'm,
a
product
marketing
manager
for
openshift,
and
this
show
talked
mostly
about
architecture,
kubernetes
and
coffee.
So
I
hope
you
had.
Your
coffee
show
to
start
the
journey,
because
I'm
gonna
introduce
my
guest
today,
which
is
Mike
bookcamp
from
cockroach
TBA,
hello
Mike.
How
are
you.
A
Good,
fantastic
Mike,
so
the
idea
we
invited
Mike
and
thank
you
for
joining
us
today,
Mike,
because
we
would
like
to
talk
about
how
to
use
how
to
consume
databases
in
kubernetes
is
a
not
topic
and
also
how
to
connect
kubernetes
to
databases
and
services.
So
this
this
was
the
idea
of
the
show,
and
in
openshift
we
have
an
integration
in
order
to
do
that.
So
Mike
today
is
gonna.
Do
a
quick
introduction
about
what
is
cockroachdb?
B
B
It
sure
so
I've
got
a
bit
of
a
presentation
that
I'll
run
through
give
us
a
bit
of
background.
So
if
you
could
just
bring
that
up,
I'll
hit
the
presentation
mode
here
and
we'll
and
we'll
go
through
through
it
from
there.
So,
first
of
all,
just
a
little
bit
of
background
really
about
cockroach
labs
and
and
how
they
were
formed
and
and
the
size
of
the
company
Etc,
so
cockroach
Labs
itself
has
been
around
since
2015..
B
We
were
established
by
3x
Google
engineers
and
basically
the
idea
for
cockroachdb
was
born
out
of
some
frustrations
that
that
they
experienced
at
their
time
Google
around.
You
know
the
complexities
of
scaling
out
relational
databases,
but
we'll
talk
about
that
in
a
little
bit
more
detail
as
we
go
through
the
presentation.
B
B
So
why
is
there
a
need
for
another
database?
There's
lots
and
lots
of
databases
out
there,
so
why
do
we
need
another
one?
So
if
we
think
about
you
know
the
rise
of
the
internet,
an
online
e-commerce
platforms
and
trading
these
types
of
platforms,
you
know
come
with
some
pretty
explicit
requirements.
First
of
all,
you
know
they
require
massive
concurrency,
but
at
that
massive
concurrency
they
require
you
know,
consistency
and
reliable
data,
and
that
can
be
quite
a
challenge
to
to
kind
of
achieve
that.
B
Secondly,
you
know
it's
about
a
significant
scale
and
distribution.
I,
often
think
in
this
scenario
of
cut
type
that
that
Black
Friday
event,
you
know
if
you've
got
an
e-commerce
platform
or
a
gaming
platform
and
there's
some
kind
of
massive
event.
That's
going
to
drive
a
considerably
large
amount
of
users
to
your
platform.
You
want
that
platform
to
kind
of
scale
out
horizontally
seamlessly.
You
know
ensuring
that
you
know
that
service
isn't
interrupted.
B
Although
you've
got
a
large
number
of
users,
you
know
connecting
to
your
platform,
you
don't
want
to
see
any
kind
of
disruption.
You
know
you
want
to
take
advantage
of.
That
kind
of
you
know
massive
marketing
event
that
you've
you've
invested
in
you
don't
want
the
platform
to
kind
of
collapse
in
a
heap,
as
a
large
number
of
users
are
flooded
to
your
you,
your
you
know
your
e-commerce
or
gaming
platform
and
then
thirdly,
always
on
availability
and
low
latency.
B
You
know
I
often
think
about
you
know
the
the
rise
of
the
iPad
had
my
children.
In
this
scenario
you
know
when
they
pick
up
their
iPad.
You
know
they
go
on
an
app.
You
know,
no
matter
where
they
are.
You
know
whether
they're
at
home
on
holiday.
They
expect
that
same
user
experience,
no
matter
where
they
are
in
the
world,
you
know,
and
if
they
don't
get
that
user
experience,
you
know
we're
all
the
same.
B
B
You
know
we've
been
able
to
do
that
with
applications
for
some
time.
You
know
those
goals
haven't
changed.
You
know
we
want
to
be
able
to.
You
know,
deploy
applications
seamlessly.
You
know
at
scale
across
regions
and
relatively
straightforward.
Well,
when
I,
when
I,
if
I
think
back
to
my
time
at
you
know
working
as
a
platform
engineer,
you
know
we
used
to
find.
You
know
that
very
easy
from
the
application
tier.
You
know
we
used
to
be
able
to
take
advantage
of.
You
know
many
of
the
cloud
providers.
B
You
know
services
for
us
to
be
able
to
kind
of
you
know,
deliver
those
applications
at
scale,
but
where
the
complexity
came,
you
know
is
that
that
data
tier
you
know
we
often
find
it
extremely
challenging
to
you
know
to
deliver
those
same
goals
you
know,
but
at
the
database
level
you
know
it
often
resulted
in
you
know
very
complex
Solutions
trying
to
replicate
data
across
regions.
You
know
maybe
complex
manual
sharding,
these
types
of
things.
So
really
you
know
the
database
hasn't
really
kept
up
with
the
evolution.
B
B
We
basically
take
the
best
of
like
the
three
worlds
we
see
of
the
database
world,
so
we've
got
the
relational
database,
so
you
know
you
still
need
that
kind
of
consistency.
You
know
that
the
relational
database
gives
you
you
know
if
you're
dealing
with
financial
transactions,
you
know
order
Management
Systems
you're,
going
to
require
that
kind
of
reliable,
consistent
and
familiar
language
that
those
relational
databases
give
you.
But
we
also
combine
that
with
the
scalability,
the
resiliency
and
the
flexibility
of
nosql.
B
So
as
obviously
people
started
to
adopt,
you
know
the
public
Cloud,
you
know
Distributing
their
applications
globally.
You
know
we
saw
this
massive
shift
to
nosql
databases,
but
it
doesn't
really
solve
the
challenge
of
consistency.
You
know
some
of
the
cloud
providers
have
attempted
to
achieve
that
by
taking
some
of
these
more
Legacy
relational
database
Technologies
and
try
to
put
a
wrapper
around
them.
You
know
in
their
Cloud
platforms
to
try
and
help
with
the
distribution
and
orchestration,
but
they
haven't
really
solved
that
that
problem.
B
That's
where
kind
of
cockroachdb
comes
in,
you
know,
we've
take
the
best
of
those
all
of
those
worlds.
Combine
them
together
to
give
you
those
guaranteed
transactions,
the
inherent
resiliency
and
scalability,
but
all
with
a
familiar.
You
know,
SQL
front
end
that
you
know
people
are
gonna,
be
familiar
with
and
be
able
to
consume
easily.
C
Look
at
the
color
of
the
cup
may
I.
Ask
you
whether
you
speak
about
obviously
consistency
or
granted
transaction
I
I.
Don't
want
to
anticipate
anything
in
from
your
presentation
how
you
can
I
cockroach
B
can
support
guard
and
transaction
in
a
highly
distributed
environment
which
could
be
in
general
kubernetes
and
more
specifically,
open
shift
yeah.
You.
B
B
So
the
way
that
we
do,
that
is,
although
we
look
and
feel
like
a
SQL
database
at
the
front
end,
because
we've
implemented
the
postgres
wire
protocol
under
the
hood,
we're
actually
a
key
value
store
and
we
store
the
rows
and
Columns
of
all
of
the
tables
in
a
lexographically
organized
key
value
store.
We
then
carve
that
key
Value
Store
up
into
smaller
chunks,
which
we
call
ranges
and
it's
those
ranges
that
are
written
in
triplicate
across
the
cluster.
B
So
each
range
is
actually
part
of
a
raft
group
and
we
actually
use
the
same
raft
algorithm.
That's
used
inside
xcd,
which
you
know
anyone
who's
familiar
with.
Kubernetes
will
be
familiar
with,
and
it's
at
that
range
level
that
we
use
raft
to
coordinate
the
right,
the
reads
and
rights
of
each
range.
So,
if
you
think
about
it,
when
a
Right
comes
in
to
the
raft
leader
of
that
range,
that
RAF
leader
then
coordinates
those
rights
with
other
replicas
which
would
live
on
other
nodes
within
the
cluster.
B
So
a
transaction
would
come
in
for
that
raft
leader.
That
rough
leader
would
commit
that
right
to
itself.
It
would
send
it
out
to
the
other
members
of
the
RAF
group
in
the
default
case.
That's
three!
So
as
long
as
it
got
a
acknowledgment
back
from
a
majority
of
the
RAF
Group,
which
would
be
itself
and
one
other
in
the
instance
of
three
replicas.
It
would
then
communicate
back
to
the
client
that
that
transaction
had
been
committed
successfully.
B
So
that's
how
we
kind
of
coordinate
those
rights
across
nodes
in
the
cluster
and
also
how
we
keep
that
latency
down,
because
we're
not
waiting
for
all
of
the
replicas
to
acknowledge
that
the
right's
been
committed
just
the
majority.
We
can
then
go
back
to
that
client
in
a
timely
fashion,
resulting
in
you
know,
quick,
reads
and
writes,
and
keeping
that
latency
down
to
a
minimum.
B
So
we
we
don't.
We
could
we
don't
necessarily
need
to
scale
out.
You
know
within
a
single
openshift
cluster
or
within
a
single
kubernetes
cluster.
We
can
scale
out
across
regions
and
although
we've
scaled
out
across
regions
or
across
kubernetes
clusters,
they
still
appear
as
one
single
logical
database.
The
only
requirement
there
is
that
all
of
the
pods
can
communicate
with
each
other
at
an
IP
level
and
also
be
able
to
resolve
DNS
queries
as
well.
B
So
as
long
as
you've
got
DNS
in
place,
and
you
can
have
pod
to
pod
communication
across
kubernetes
clusters,
then
cockroachdb
will
function
as
that
single
logical
database,
they're
Distributing,
your
data
across
multiple
kubernetes
clusters
across
multiple
regions,
which
is
pretty
unique
in
itself,
and
it
doesn't
have
to
stop
there.
It
doesn't
have
to
be
you
know
a
single
openshift
cluster
or
it
could
be
across.
You
know
multiple
different
Cloud
providers.
B
You
could
have
an
open
shift
cluster
on
premise,
coupled
with
a
a
kubernetes
cluster
running
in
gcp
and
an
AKs
cluster
in
Azure,
and
they
as
long
as
they've
got
that
network
connectivity
in
place.
They
can
function
as
one
single
logical,
relational
database
serving
your
data
to
those
apps
in
those
different
Cloud
providers.
B
Next,
we
talk
about
being
able
to
survive
anything
so
because
of
our
the
way
that
we
are
architected.
You
know
made
up
of
a
number
of
different
nodes
and
with
the
resiliency
that
provides.
If
you've
got
enough
nodes
in
each
of
those
regions,
then
you
can
actually
facilitate
a
complete
Regional
failure.
B
A
B
B
This
can
obviously
you
know
we
can't
beat
the
speed
of
light,
so
it
will
introduce
you
know
latency.
So
what
can
we
do
to
kind
of
overcome?
That
or
kind
of
you
know,
increase
the
performance
to
you
know
take
account
for
the
the
distributed
nature
of
the
database.
So
what
we
can
do
is
we
can
look
at
where
data's
being
accessed
from.
B
So
you
know
I
think
I
often
think
about
you
know
if
you've
got
a
globally
distributed
application,
you
know
maybe
like
uber,
you
know
if
I'm
sat
at
home
in
the
UK
looking
for
a
taxi
in
Uber,
you
know
querying
certain
rows
and
tables
in
a
specific
column.
I
don't
need
to
know
about
where
the
taxes
are
in
the
USA.
B
So
I
could
kind
of
pin
that
data
about
the
the
taxes
in
in
the
UK
to
nodes
that
are
based
in
the
new
in
the
UK
or
in
the
you
know,
the
the
near
vicinity
and
that's
just
going
to
help
increase
my
my
user
experience
a
side
benefit
of
that
as
well.
Is
it
can
help
you
kind
of
comply
with
you
know,
regulations
like
data
protection
gdpr.
If
you've
got
specific
geographies,
you
know
that
don't
allow
data
to
leave.
You
know
the
the
country
boundaries.
B
A
B
Excellent,
so
you
know
why:
why
is
cockroachdb?
You
know
architected
for
kubernetes.
What
what
benefit
do
we
have
of
running
cockroachdb
within
kubernetes?
So
you
know
if
we
think
about
the
kind
of
inherent
resiliency
the
kubernetes
brings
to
Applications.
You
know
cockroachdb,
because
it's
been
architected
to
running
kubernetes
can
take
advantage
of
those
types
of
things.
So
you
know
in
the
event
of
a
pod
failure
when
kubernetes
you
know
respawns
a
pod
to
replace
it
because
of
the
way
that
cockroach
is
architected.
You
know
that
new
pod
will
just
seamlessly.
B
You
know,
reconnect
to
the
the
existing
cluster
and
start
participating
in
the
database
and
then
from
a
scalability
point
of
view.
You
know
because
we're
running
cockroachdb
in
a
stateful
set
inside
kubernetes.
If
we
want
to
increase
the
number
of
replicas,
you
know
we
can
just
you
know
edit,
that
stateful
set
increase
the
number
of
replicas
and
let
kubernetes
or
openshift
just
take
care
of.
You
know
spawning
at
the
the
relevant
number
of
PODS.
B
So
really
you
know
we're
just
piggybacking
on
the
kind
of
orchestration
capabilities
of
kubernetes
to
make
managing
and
administering
cockroachdb.
You
know
that
much
easier
and
then,
if
we
talk
about
you
know
what
Fabio
and
Natalie
were
talking
about
earlier.
You
know
about
their
databases
of
service
element,
so
recently
openshift
have
launched
their
Red
Hat
openshift
database
access
or
Rota,
where
this
gives
you
the
ability,
inside
your
openshift
container
platform,
to
create
connections
out
to
third-party
database
as
a
service
Partners
like
cockroachdb.
B
So,
for
example,
if
you're
running
you
know
some
application
inside
your
openshift
cluster,
that
requires
connectivity
to
a
relational
database
like
cockroachdb,
then
you
can
now
do
that
through
Roda,
reaching
out
into
cockroachdb's
Cloud
platform,
creating
a
database
and
connecting
that
database
to
your
applications
that
are
running
inside
your
open
shift
cluster,
so
I've
got
a
little
demo
that
I
will
share
with
you.
That's.
A
A
B
B
We're
going
to
click
on
ADD
and
what
we're
going
to
do
is
we're
going
to
import
our
application
from
from
a
git
repository
I'm,
just
going
to
grab
this
URL
here
and
then
I'm
just
going
to
paste
that
in
the
box
there
and
that's
going
to
just
go
out
and
validate
that
that
GitHub
repo
is
actually
an
application
that
that's
got
some
of
the
correct
components
in
to
allow
openshift
to
build
it
and
deploy
it
into
our
cluster.
So
I'm
just
going
to
hit
create
there.
B
So
what
that's
doing
now?
It's
it's
pulling
down
that
code
from
that
GitHub
repo,
there's,
actually
a
build
it
inside
that
repos
there,
which
is,
which
is
just
happening
now,
which
is
just
building
our
Pac-Man
container
image.
What
will
happen,
though?
The
first
time
around
is
because
we
don't
have
a
database
at
the
moment
this
will
actually
fail.
B
B
A
Yeah
and
yeah
I
in
the
while
I
shared
in
the
chat,
the
link
to
the
repository.
If
the
people
want
to
just
you
know,
try
it
out
and
also
I
shared
the
link
for
the
developer
sandbox
for
openshift,
which
is
a
free,
openshift
cluster
that
you
can
use.
You
can
register
for
frame,
developer.com
and
and
start
using
this
cluster,
so
they
can
run
basically
the
same
demo.
A
B
A
B
B
Back
to
add
here
and
we
can
scroll
down
to
the
bottom-
we
see
we've
got
this.
This
box
here,
Cloud
hosted
database,
so
now
we're
going
to
click
on
there
and
you
get
the
three
different
options.
Obviously,
in
this
scenario,
we're
going
to
use
cockroachdb
cloud
so
we're
going
to
click,
add
to
topology,
and
then
this
is
using
a
set
of
API
keys
that
I've
pre-configured.
This
is
now
communicating
with
cockroach
cockroachdb
Cloud.
B
And
we'll
hit
create
and
what
that's
doing
now
is
using
those
API
Keys,
then
to
reach
out
to
cockroach
Cloud,
create
that
database
instance
for
us
and
and
then
that
will
be
within
our
topology,
then
so,
okay,
so
it's
created
the
the
database
instance.
Now
we
can
add
that
to
our
topology,
you
can
see
there,
it's
the
one
that
we've
we
asked
it
to
create,
and
it's
going
to
pop
that
into
our
project
cool.
B
So
you
can
see
now
we've
got
the
two
different
resources
now
within
our
project.
So
what
we
have
to
do
is
we
have
to
create
a
service
binding
between
the
two
of
them.
So
what
we'll
do
is
if
we
grab
this
Arrow
drag
it
into
this
box,
then
openshift
is
going
to
create
that
service
binding
between
the
application
and
the
database,
and
that's
going
to
contain
all
the
information
required
for
the
application
to
connect
to
the
database.
A
That's
pretty
cool
bike,
so
we
can
see
now
that
the
application
is
not
restarting
all
the
time,
because
now
it
can
connect
to
the
cockroachdb
that
you
created
from
this
openshift
cluster.
Thanks
to
the
Roda
integration,
I
I
put
in
the
link
in
the
chat
the
link
to
the
service
binding.
So
this
is
a
kubernetes
operator
that
lets
you
connect
the
application
with
databases
or
or
other
resources.
A
So
you
don't
have
to
write
stuff
yaml
manually,
it
can
be
done
automatically
and
the
openshift
topology
has
this
mechanism
to
you
know
help
you
doing
this
bind
so
everyone
is
looks
connected
nicely
Mike.
You
can
create
your
container.
You
can
create
a
database
on
the
cockroachdb
cloud,
so
it's
a
database
as
a
service
and
then
you
can
connect
it
with
a
you
know,
pulling
a
line
under
the
Hooters,
the
technology,
but
it's
all
kubernetes.
But
this
is
a
nice.
It's
a
ux
workflow!
Isn't
it
yeah.
B
Also
as
well,
those
credentials
are
kind
of
you
know,
they're
kind
of
hidden
from
those
developers
as
well.
They're
no
longer
need
to
know
the
connection
string,
the
username
and
password.
All
they
need
to
know
is
that
service
binding
that
they
that
they
need
to
use
for
their
application,
and
it
will
give
them
access
to
the
right
database,
so
you're
kind
of
securing
those
credentials
as
well
and
limiting
the
the
access
to
them
to
preventing
anybody
who
doesn't
necessarily
need
them
getting
visibility
of
them
right.
B
So
now
we've
got
our
Pac-Man
app
whoa
and
let's
play
Natalie,
has
shared
the
link
in
the
chat
as
well.
So
you
can
all
have
a
go
on
that.
So,
what's
going
to
happen
is
as
you
play
the
game,
you
know
you're
going
to
generate
a
score
and
that
high
score
is
going
to
be
held
in
in
a
database
table
inside
your
cockroach
DB.
So
I
was
very
poor
there
and
didn't
get
a
very
high
score,
but
I'm
going
to
hit
save
there
and
hit
you
high
score
list.
B
B
So
I'm
going
to
connect
to
this
that
when
you
in
cockroach
Cloud,
when
you
hit
connect
you're
given
like
this
flash
screen
here,
that's
got
a
number
of
settings
on
there
and
and
I'm
talking
you
through
how
to
connect
your
you
know
your
CLL
eye
tool
or
or
any
other.
You
know
tool
that
you
have
to
connect
to
your
database.
B
The
first
thing
that
you
need
to
do
is
you'll
have
to
download
this
CIA
certificate
and
it
and
that,
and
if
you
click
that
down
over
there,
we
give
you
just
this
curl
command
and
that's
going
to
put
that
certificate
in
the
right
place
on
your
local
machine.
So
I'm
just
going
to
copy
that
and
I'm
going
to
download
that.
B
Next,
because
I'm
going
to
be
using
the
cockroachdb
client,
which
I'll
switch,
the
screen
share
to
in
a
moment
I'm
just
going
to
change
that
drop
down
arrow
there.
And
that's
going
to
give
me
the
connection
string
and
the
command,
along
with
the
connection
string,
to
connect
my
CLI
terminal
to
that
database.
So
I'm
going
to
copy
that
and
then,
if
I
switch
to
my
terminal
window.
B
A
B
B
A
C
C
B
A
B
A
The
flow
is
really
nice,
Fabio
Mike,
at
least
from
a
developer
perspective.
I
can
try
my
stuff
I
can
with
a
database
that
I
don't
have
to
set
up.
So
this
complexity
is,
you
know,
is
it's
not
to
the
developer
I
I
order,
a
database
I
deploy
an
app
I,
create
a
container
from
the
source
code.
I
connect
them
with
a
nice.
You
know
UI
action.
Of
course.
Not
everyone
loves
the
full
UI,
you
know
experience,
but
their
service
binding
is
available.
Also,
it's
a
kubernetes
object.
B
Okay,
cool,
so
I
found
I
found
the
password
which
is
just
held
within
the
secret
inside
kubernetes
I
was
just
held
within
that
service.
Binding
object,
so
I
just
clicked
on
that
service.
Binding
object
within
there
there's
a
secret
and
in
that
secret.
One
of
the
Fields
is,
is
the
password
for
the
connection
string,
so
just
copied
that
pasted
that
into
my
terminal
window
and
now
I'm
connected
to
my
cockroach
Cloud
DB
cluster
I
did
a
show
tables
and
you
can
see
there
that
we've
got
our
high
score
table.
A
Well,
Mike,
it's
fantastic
I.
Can
you
do
so?
I
I
played
a
little
bit.
I'm
sure
everyone
attending
is
playing
and
keep
please
keep
keep
playing,
because
this
will
fulfill
the
the
data
again.
The
repo
is
the
one.
That's
sharing
the
chat.
If
you
want
to
try
the
same
demo,
that
Mike
did
you
can
try
by
using
the
repo
I'm
gonna
put
again
in
the
chat,
so
the
Cockroach
BP
team
made
this
demo
and
you
can
use
it
on
for
developers
and
books
for
openshift,
which
is
an
operative
cluster.
A
You
can
introduce
it
for
free
and
then
you
have
the
Cockroach
DB
operator
installed.
You
have
the
road
operator
installed,
so
you
can
either
test.
You
know
the
operator
for
in
cluster
database
or
connecting
to
a
database
as
a
service.
So
those
are
the
two
experience
now
you
can
try
it
out
for
free
Mike
cockroachdb
has
a
trial,
I
guess
any
free
trial.
Okay,.
B
A
Cool
and
I
I'm
gonna
put
in
the
chat
the
link
to
the
prior
cluster.
So
you
want
you
want
to
try
the
same
demo,
get
a
trial
from
cockroach
to
be
get
the
trial
from
the
free
upper
shift,
developer,
Center
cluster
and
get
the
repository
on
GitHub
for
for
the
Pacman
demo,
which
is
really
cool
thanks
Mike.
For
for
that
demo,
do
you
have
any
other
thing
to
show
Mike
in
the
yeah
for
slides
or
any
other.
B
Yeah
there's
just
a
couple
of
slides
left
just
talking
a
little
bit
about
the
different
versions
that
we
have
I
can
talk
about:
okay,
cool,
perfect,
so
just
hit
on
there.
Like
we've
just
touched
on
so
we've
got,
we've
got
what
we
call
cockroach
DB
core,
so
that's
our
free,
open
source
version
that
you
can
download
and
use
completely
free.
B
B
Maybe
if
you
wanted
to
run
it
across
different
Cloud
providers,
for
example,
maybe
you've
got
a
hybrid
environment
where
you
want
to
run
some
openshift
clusters.
On-Prem
combine
that
with
some
kubernetes
or
openshift
clusters
in
the
public
Cloud,
then
our
self-hosted
version
would
be
the
one
that
you'd
be
able
to
do
that
with
and
then
we've
got
cockroachdb
serverless
there
on
the
left.
So
this
is
what
we
actually
use
for
that
demo.
B
That's
what
Rhoda
reaches
out
and
connects
into,
which
is
our
serverless
offering
currently
and
that's
basically,
a
pay-as-you-go
cockroachdb,
multi-tenanted
environment,
where
you
can
kind
of
really
deploy
cockroachdb
in
a
matter
of
seconds
and
and
get
up
and
running
really
really
quickly.
That's
currently
in
a
single
region
in
a
single
Cloud
at
the
moment,
but
as
we
get
further
to
GA
you
you'll
see,
you
know
the
capabilities
it
increase
over
time.
And
finally,
this
is
for
really
for
production,
workloads
and
that's
cockroachdb
dedicated.
B
B
Looking
after
those
clusters
for
our
customers
and
that's
currently
deployed
in
AWS
or
or
gcp
today,
then
you
know
what
would
you
use
cockroachdb
for
so
we're
a
general
purpose,
relational
database
for
system
of
record
workloads,
so
whether
you're
kind
of
you
know
modernizing
your
existing
application
estate,
you're
migrating
to
the
cloud
or
you're
building
Greenfield
applications
inside
kubernetes
that
require
a
relational
database.
You
know
cockroachdb
is
a
really
good
fit
for
that.
B
You
know
we're
not
restricted
to
one
specific
vertical,
although
we
do
work
well
in
things
like
Financial
Services,
you
know,
gaming,
retail,
we've
seen
use
cases
across
all
different
sectors
and
that's
just
a
kind
of
list
of
some
of
our
kind
of
current
customers.
There
yeah
so
and
then,
if
you
want
to
kind
of
reach
out
to
me,
there's
there's
my
kind
of
email
address.
A
Thank
you
Mike,
so
the
email
is
bootcamp
at
cockroachlabs.com.
If
you
you
can
see
in
the
screen,
yeah
and
good,
you
also
put
the
our
partnership
team
as
cockroach
CBS
Reddit
partner,
and
we
that's
why
we
have
this
integration
that
you
can
find
in
inside
operator.
Hub
inside
openshift,
but
Mike
I
was
looking
also
on
operator
habayo,
which
is
the
community
Upstream
hub
for
operators
and
I
found
the
Cockroach
to
be
operator
based
on
the
helm
chart.
A
B
Correct
yeah
yeah,
so
there's
a
there's
like
if
you
want
to
deploy
cockroach
into
openshift
cluster,
there's
kind
of
three
ways
to
do
it,
depending
on
like
what
your
configuration
is.
So,
for
example,
you
know
if
you've
got
a
single
cluster
where
you
want
to
deploy
it,
you
can
use
the
operator.
We've
got
an
operator
that
you
can
use
to
deploy
it.
That's
got
one
custom
resource.
You
know
you
define
your
cluster
characteristics
in
a
yaml
file.
B
Then
you
can
deploy
that
via
the
operator,
we've
got
a
Helm
chart
and
then
we've
just
got
some
kubernetes
manifest
as
well,
so
where
the
kubernetes
manifests
come
into
play
is
when
you're
doing
things
like
multi-region.
So
if
you've
got
multiple
kubernetes
clusters
and
you
want
to
deploy
cockroach
across
all
three
of
them,
then
you
can
use
the
kubernetes
Manifest.
That's
the
kind
of
easiest
way
to
do
that.
Multi-Region
deployment.
A
A
B
B
You
know
you,
it's
not
that
we
don't
work
in
a
two
data
center
configuration,
but
it
doesn't
really
give
you
that
survivability
that
you're
after
because,
obviously,
if
you
lost
one
data
center,
then
you'd
lose
a
majority
of
all
of
your
ranges
and
you'd
lose
your
whole
database,
so
it's
really
kind
of
intuitive
to
have
to
so
yeah.
Certainly
we
say
like
three
data,
centers
or
three
regions.
You
deploy
your
nodes
across
those
three
regions,
and
that
would
give
you
the
resiliency
how
it
does
that
is.
B
Obviously
your
ranges
would
then
have
one
replica
in
each
of
those
regions.
So
if
one
region
went
down,
you
would
only
lose
one
replica
from
your
range,
so
you'd
still
have
a
majority
for
all
ranges,
and
and
your
data
would
continue,
continue
to
be
served
so
those
regions
could
be
made
up
of.
You
know
three
different
open
shift
clusters
in
three
different
data:
centers
there
could
be
an
open
shift,
cluster
on-prem,
AKs
and
gke.
C
C
Right
that
fits
perfectly
with
a
multi-open,
hybrid
Cloud
approach.
I've
read
that
when
we
are
going
toward
the
a
pattern
where
you
can
have
open
shift
everywhere
and
managing
that
upper
shift
from
on-premise
or
some
place
in
the
club,
okay
may
I.
Ask
you
just
one
question:
if
there
is
any
specific
solution
from
cockroach
B
for
Edge
deployment,
when
you
need,
for
example,
I
I
mean
when
you
have
to
deploy
something
with
a
small
footprint
on
a
single
upper
shift,
node
or
remote
notes.
Something
like
that.
If
there
is
something.
B
C
B
If
you
wanted
to
deliver
a
single
database
across
them,
you'd
just
have
to
make
sure
that
you'd
have
sufficient
connectivity
between
all
those
nodes
at
the
edge
to
be
able
to
accommodate
those
those
rights
and
make
sure
that
you
know
there
was
a
and
a
low
enough
latency
to
make
it
practical
to
do
that.
No.
A
B
Up
so
from
a
single
site
perspective,
you
know
it's
distributed
across
the
availability
zones
within
that
region,
okay,
but
you
can
also
select
a
multi-region
deployment
as
well.
So
if
you
wanted
to
be
able
to
survive
a
region,
failure
with
cockroach
clouds,
you
can
select
a
you
know,
a
three
region,
multi-region
deployment
and
you
can
distribute
your
data.
You
know
more
widely
across
multiple
geographical
regions,.
A
Yeah,
cool
cool,
interesting
I
think
it's
a
very
nice
feature.
Also
as
a
developer
I
can
select,
you
know,
I
can
deploy
the
app
I
can
connect
it.
I
can
select
the
level
of
available,
they
need
for
tests.
Maybe
just
single
it's
it's
okay,
then,
when
things
goes
to
prod
and
the
traffic
increase.
Maybe
it's
good
another
question
about
the
traffic
increasing.
Do
we
have
any
relevant
metrics?
We
can
use
inside
the
cluster
kubernetes
operative
cluster.
Let's
say
we
have
the
operator
and
then
we
the
database
are,
is
hitting
hard.
B
So
cockroachdb
has
its
own
admin
console
and
within
there
there's
lots
of
metrics
that
are
being
exposed,
so
you'd
be
able
to
kind
of
go
there
and
investigate
you
know
what
those
metrics
are
and
and
whether
they're
you
know,
the
throughput
that
you
have
is
sufficient.
You
know
whether
you're
seeing
any
kind
of
bottlenecks,
but
also
you
know
we
expose
those
same
metrics
via
a
Prometheus
endpoint
as
well.
A
A
B
Yeah,
so
that
that
is
basically
that
there
are
a
there's,
a
number
of
resources
that
get
deployed.
You
know,
like
a
you,
know,
service
accounts,
and
you
know
these
types
of
things
along
with
the
the
stateful
set,
but
the
stateful
set
is
really
where
you
know.
Cockroachdb
is
running.
That's
where
you
know
the
the
applications
specifically
run
in
yeah.
So
it
would
be
that
resource
that
you
scaled
out
and
yeah.
One
thing
with
scaling
is
obviously
you
know
it
is
still
a
database
there's
like
lots
of
data
involved.
B
So
you
know
it's
not
as
easy
to
scale
out
as
an
application.
You
need
to
put
some
additional
thought
into
it,
because
every
time
you
kind
of
scale
out
the
number
of
PODS
there's
a
kind
of
a
data
movement
activity
that
has
to
go
on
so
maybe
do
it
a
little
less
aggressively
as
you
would
that
application
tier
you
know
giving
the
database
time
to
kind
of
redistribute
that
data
across
those
new
nodes.
As
you
scale
out,
you
know,
you
don't
want
it
to
be
still.
B
You
know
trying
to
move
ranges
around
into
those
new
pods
and
you
decide.
Oh,
you
know:
we've
gone
past
the
peak
in
there
in
the
in
the
traffic
and
we
want
to
scale
it
back
in
and
you
start
trying
to
scale
it
in
when
it
hasn't
already
finished.
You
know
moving
data
around
so
just
do
it
with
a
little
bit
more
caution
because
of
you
know
the
the
data
that's
involved,
that
has
to
be
moved
around
the
cluster
when
you
perform
those
scaling
operations
right.
A
Thanks
and
I
was
thinking
Mike
another
use
case.
Very,
it
could
be
very
common
in
which
the
kubernetes
stateful
said
help,
which
is
the
upgrade
you
know
in,
for
instance,
auto
ship.
We
have
the
over
the
upgrades,
so
it's
basically
automatically
upgrading
the
cluster
draining
the
nodes
automatically.
It's
all
made
by
this
logic,
this
rail,
Corollas
and
openshift,
when
we
need
to
upgrade
the
nodes
where
cockroach
DB
is
running
I,
guess
it's
important
to
have
the
stateful
set.
So
kubernetes
knows
that
this
object
need
to
be
moved
as
a
single
entity.
A
You
know
because
there's
also
data
attached,
do
you
have
any
recommendation
for
upgrades
and
also
hot
question,
which
kind
of
storage?
Do
you
recommend
for
running
cockroach?
To
be
it's
okay,
any
software
defined
storage
for
in
your
opinion,
or
do
you
recommend
any
you
know
more
close
to
Bare
Metal
solution.
B
So
we're
not
really
bothered
about
what
storage
that
you
run.
You
know
cockroach
DB
on
you,
don't
need
to
have
any
kind
of
replicated
storage
because
we
deal
with
the
replication
with
inside
cockroachdb.
So
you
know
we
write
the
data
in
triplicate
across
the
cluster,
so
you
don't
need
any
kind
of
fancy
storage
underneath
that's
doing
any
kind
of
additional
replication
we're
more
specific
about.
You
know
the
number
of
iops
that
that
storage
can
provide,
and
you
can
find
that
information
in
our
docs
to
let
you
know
how
many
iops
per
vcpu.
B
We
recommend
you
to
have
so
it's
more
about.
You
know.
What's
the
throughput
of
the
storage
as
opposed
to
what
type
of
storage
it
is
or
we're
using
kubernetes
is
just
a
a
PV.
You
know
with
a
PVC
right,
it's
just
simple:
straightforward,
kubernetes,
Concepts!
You
know
we're
not
really
concerned
about
what
that
storage
is
underneath
as
long
as
it
provides
us
with
the
required
amount
of
iops
right.
B
Instance,
correct
correct
and
that
that's
a
that's
a
great
point
for
me
to
kind
of
plug
our
Cloud
report,
so
we've
just
kind
of
released
a
cloud
report
where
we've
done
different
benchmarkings
against
the
different
instant
types
from
all
the
different
Cloud
providers.
And
if,
in
that
cloud
report,
you'll
find
you
know
which
instant
types
provides.
The
best
performance
for
running
cockroach,
DB,
nice.
A
Nice
and
cool
to
mention
in
openshift.
If
you
need
to
change
the
instance
type,
you
can
go
to
the
machine
set
and
add
a
new
machine
set
for,
for
the
instance
tab
you
wanna
use.
So
it's
really
easy
with
the
machine
API
implementation
in
openshift
for
the
kubernetes
cluster
API
to
change
the
instance
type
to
other
newest
Center
to
scale
it
up
the
cluster.
A
C
A
So
folks,
please
go
to
this
link
to
download
the
demo,
the
Pac-Man
demo
for
cockroach
to
be
go
to
developer
sandbox
for
openshift
to
try
it
out
and
go
to
the
trial
of
cockroach
to
be
to
to
try
the
Cockroach
to
be
Cloud,
so
you
can
plug
easily
the
same
demo
flow
that
Mike
was
doing
today
and
the
recording
is
at
the
same
link.
You
are
watching
now,
either
from
twitch
or
YouTube.
If
you
wanna
review
what
Mike
did
you
can
watch
it
for
this
bike?
A
We're
gonna
end
the
show
with
some
reminder
of
what
we
have
today
in
the
shadow
Fabio,
because
today
we
have
an
open
shift
TV.
We
have
the
level
up
hour
and
then
ask
an
admin,
and
we
will
come
back
next
Wednesday
with
the
Red
Dot
access
office
hour,
again
talking
about
real
for
Edge
and
microshift
and
all
their
open
source
for
that
technology
for
the
edge
with
Andrea
and
all
the
red
that
access
the
team.
A
With
that
thoughts,
Mike
I.
Thank
you
very
much
for
joining
us.
It
was
a
really
pleasure,
I
hope
to
have
you
back
in
the
show
in
the
next
future.
For
another
awesome
demo
with
cockroach
to
be
and
openshift,
and
thank
you
for
joining
today,
nice
background
and
thank
you,
everyone
for
joining
and
attending
today
and
see
you
next
Wednesday
ciao.