►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Running MySQL on Kubernetes - Patrick M. Galbraith, Oracle
MySQL is the world's most popular open source database and there are a number of ways to run it on Kubernetes. This talk will explain and demonstrate how running a complex stateful application such as a database is made easier using Kubernetes. MySQL deployment patterns covered will start with simple MySQL asynchronous replicated master/slave MySQL and Galera synchronous multi-master replication both deployed as StatefulSets using a Helm charts. Following the simple patterns, a detailed discussion and demonstration will showcase the MySQL Operator which uses group replication and the MySQL router and makes creating MySQL clusters, backups, and restorations trivial. Next to be covered will be the Vitess Clustering system and its operator for horizontal scaling of MySQL which has numerous benefits such as built-in sharding and shard management, connection-pooling, query sanitization.
To learn more: https://sched.co/Grb4
A
A
Just
some
things
about
me:
I've,
been
in
this
industry
for
quite
a
while
I've
started
out
in
tech.
Well,
1986
on
electronics,
but
I
got
into
you
know,
working
in
software
and
systems
administration
around
1993
94
found
about
this
new
OS
called
some
guy
called
it
Linux
at
the
time,
and
it
was
I
spent
a
weekend
downloading
Slackware
onto
26
floppies
on
my
Packard
Bell
and
I
never
could
get
extra
on,
but
it's
been
a
wild
ride
and
it's
kind
of
interesting
being
back
in
Seattle,
because
I
really
started
my
tech
career.
A
Here,
though,
I
live
in
New
Hampshire.
Now
there
used
to
be
these
meetings
in
Ballard
at
talki,
Pizza
run
by
Phil
Hughes.
He
started
the
Linux
Journal,
so
those
were
the
sweet
days
and
now
we
come
full
circle
and
you
know
I've
been
at
all
any
number
of
companies.
I
am
now
at
Oracle.
I
was
at
hewlett-packard
prior
Packard
Enterprise
blue
gecko,
which
was
a
database
company
here
in
Seattle,
minus
QL
I
was
there
for
three
years
classmates
Slashdot
in
the
u.s.
Navy.
Interestingly,
we
were
talking
about
MySQL
and
kubernetes.
A
In
1999,
I
worked
at
Andover
dotnet.
They
had
a
company
that
owned
Slashdot,
and
there
were
these
two
guys,
one
from
Finland,
one
from
Sweden
David
axe,
mark
Monti
fit
in
dias,
and
they
came
to
talk
to
us
about
this
thing
called
replication
that
we
need
really
direly
needed
for
Slashdot
and
that's
how
it
all
began
with
MySQL.
For
me,
some
things
about
me:
I
won't
get
into
it
too
much
because
there's
a
lot
of
material
I
have
to
cover
and
I
want
to
touch
on
Vitesse
too
I've
got
so
many
slides.
A
My
big
problem
is
I.
Just
always
worry
do
I
have
material
to
cover
in
a
talk.
Well,
that's
not
a
problem
so
about
my
team.
I
Brisa
I
was
at
Oracle
dying
for
the
last
year,
and
I've
recently
moved
to
minus
QL
as
a
service.
We're
building
a
MySQL
service
on
Oracle's
cloud,
I'm
very
excited
to
be
starting
on
that
work.
On
MySQL
again
and
working
with
many
former
colleagues
from
MySQL
days.
A
The
what
is
this
presentation
about?
Well,
how
many
of
you
are
kubernetes
users,
kubernetes
administrators,
okay,
how
about
MySQL,
DDA's,
ok,
so
kind
of
a
mixed
group,
sometimes
I
give
this
talk
and
I
have
to
kind
of
explain
what
containers
are
so
I
won't
get
into
that
as
much.
But
there
is
this
kind
of
this
misconception
with
MySQL
on
containers,
people,
databases
on
containers.
Oh
that's
really
scary!
A
So
it's
about
my
running
MySQL
in
containers
and
in
particular,
MySQL
and
kubernetes,
is
about
stateful
applications
and
in
particular,
stateful
sets
operators
MySQL
operator,
which
there
were
there,
are
two
of
them.
That
I
will
show
you
and
I'm
really
going
to
try
to
get
to
my
the
test.
Slides
though
there
have
been
many
great
talks
on
the
tests
here,
so
I
I
can't
touch
the
quality
that
sugu
can
do
on
talking
about
it.
A
It's
such
a
great
system,
it's
hard
to
cover
it
all,
but
anyway,
so
I
get
a
lot
of
material
and
time
permitting.
If
we
have
questions
I
have
a
number
of
demos
I
could
play,
but
there
are
two
primary
ones
that
I
want
to
show
you
so
we'll
see
how
it
goes
so
I
won't
get
into
this.
We
know
what
containers
are
I
often
explain.
You
know
the
thing
I
see
have
seen
in
numerous
places.
Is
you
see
people
who
start
using
containers
and
to
them
it's
this?
A
It's
another
type
of
VM
you'll,
see
them
rum,
things
like
supervisor,
D
and
they're
all
kinds
of
processes
running
on
the
container
and
they're.
They
might
even
be
running
chef,
I,
I,
won't
say
where
I've
seen
that,
but
they
might
be
running
a
bunch
of
chef
cookbooks
inside
the
container
anti-pattern.
But
you
know
it's
a
learning
process.
I
did
the
same
thing,
so
it's
often
an
education
thing
and
dm's
versus
containers.
This
is
a
slide.
A
I
always
show
people
to
kind
of
hammer
home
what
the
difference
is
and
when
you
look
at
this,
you
can
kind
of
see.
Okay,
we're
actually
running
on
the
host
OS.
There's
no
hypervisor
layer,
there's
a
little.
You
know
there's
some
layers
that
you
have
to
go
through,
but
it's
much
more.
You
know
it's
part
of
the
OS,
it's
not
so
much
virtualization
as
much
as
it
is
isolation.
I
mean
that
is
a
type
of
virtualization,
but
it's
different
than
a
virtual
machine
and
I
won't
go
into
VMs
versus
containers.
So
this
is
a
slide.
A
I
I
enjoy
I
I
liked
this
graph
that
it
kind
of
explained
because
you
just
you-
can
see
the
whites
in
people's
eyes
when
they
start
debate
sort
of
container.
Oh,
no,
it's
more
of
a
misconception
than
reality
and
I
firmly
believe
that
containers
and
in
particular,
kubernetes
makes
it
easier
to
run
databases
on
it
makes
it
easier
to
run
any
application
on
I.
A
Believe
testing
is
made
easier,
no
emulation,
layer,
databases,
it's
always
kind
of
this
question
of
pets
versus
cattle,
the
in
databases
you
think
of
them
more
as
pets,
a
part
of
multiple
databases,
database
instances
or
one.
This
was
something
that
I
discovered
when
I
first
started
using
Cabrini's
I
thought:
okay,
pods
are
one
or
more
containers
on
a
machine.
I
thought
I
really
don't
want
to
run
a
bunch
of
MySQL
containers.
So
what
does
this
mean?
A
Because
I
always
try
to
understand
a
new
technology
by
how
can
a
database
run
on
it
and
in
the
documentation
kubernetes
pods
are
immortal.
That
strikes
fear
into
the
heart
of
a
DDA
in
a
database
is
a
very
complex
stateful
application
you
with
a
database.
You
want
stable
access.
You
want
a
plication
x'
to
always
get
the
same
database
handle
you
don't
want
any
surprises
and
safety.
You
don't
want
to
scale
if
it's
unhealthy,
that's
the
persistent
storage,
obviously
persistent,
sticky
storage.
A
So
really
it
boils
down
to
this.
For
me,
it's
the
way
I
can
have
explained
it.
Database
containers
are
the
containers,
are
the
cattle?
The
data
is
the
pet
and
here's
a
graphic
that
this
all
I'll
explain
this.
So,
first
of
all
you
have
your
data,
that's
the
pet.
Then
you
might
have
a
config
map
or
secrets.
Then
you
have
your
container
and
the
container
runs
and
it
sets
things
up.
It
runs
if
it
crashes.
Well,
we
have
a
femoral.
We
have
persistent
storage,
we're
using
block
storage
or
even
on
the
host
system.
A
That
container
might
go
away,
but
we
run
another
container.
It's
the
same
thing
as
before,
and
if
you're
using
a
stateful
set
as
I'll,
show
you
it
is
the
same
thing:
it's
just
it's
like
restarting
mysqld,
it's
just
it
it's
within
a
container.
So
this
is
something
to
help
people
understand
and
not
be
afraid
of
it.
A
So
with
kubernetes
and
MySQL
I.
Think
of
it
as
a
tale
of
two
open
source
projects,
MySQL
its
world's
most
popular
open
source
database,
2bic
widgets
in
around
20
plus
years,
and
then,
of
course,
there's
kubernetes.
The
new
person
on
the
block.
It's
the
fastest
growing
open
source
project.
It's
application.
We
know
all
the
things
we
I
don't
have
to
preach
to
the
choir
here
and
the
board
papers
there
for
your
convenience.
A
When
you
download
the
slides
later,
which
I
put
the
most
current
version
up
last
night,
I
won't
say
how
not
ready
they
were
so
kubernetes
ingredients
for
stateful
acylation
applications.
These
are
some
things
that
I
always
think
about
that
really
make
it
much
more
feasible
to
run
databases
and
other
stateful
applications
on
kubernetes.
We
have
labels,
I
mean
that's
kind
of
a
basic
thing
with
kubernetes.
It's
what
allows
discovery.
It
allows
things
to
associate
know
where
the
stable
thing
is
that
you
need
whether
it's
stores
your
network,
there's
services.
A
Obviously
it's
the
abstraction
that
lets
you
connect
to
an
underlying
pod,
there's
cube
dns,
which
is
you
know,
I
worked
at
Dyne
I
still
work
it.
There's
we're
part
of
the
same
company
and
DNS
is
something
people
take
for
granted
until
it
doesn't
work,
and
you
want
it
to
work
right,
and
this
is
something
that's
built
within
kubernetes
with
cube.
A
I
really
should
kind
of
have
sidecar
containers
under
there,
because
what
I'm
going
to
show
you
later
utilizes
this
pattern,
then,
of
course
we
have
operators
which
takes
domain
knowledge
and
encodes
it
into
a
controller,
an
application
that
does
something
for
you
that
you
no
longer
have
to
repeatedly
do
the
painful
way
and
then
they're
there.
There's
all
want.
Also
one
thing
you
have
node,
selector
and
affinity.
A
So
originally
my
one
of
my
first
contributions
to
to
kubernetes
was
I
created.
A
I
submitted
an
example
of
how
to
run
Galera
and
what
it
was
is.
It
was
three
pods
and
each
one
of
those
pods
had
a
you
know.
There
was
also
a
service
and
it
was
hard-coded.
You
know
this
right
here
was
the
pod.
This
here
was
the
the
service
for
the
given
node,
and
then
this
was
an
overall
service
for
all
of
the
nodes.
A
It
was
very
unflexible,
and
this
was
you
know,
a
basic
way
of
understanding.
This
is
a
way
of
seeing
how
far
kubernetes
has
come
and
how
much
easier.
It
is
now
to
run
things
like
this
and
much
more
dynamic.
It's
not
this
thing
where
you
have
to
think
about
it.
Then,
of
course
we
have
another
simple
way
of
running
MySQL
is
to
run
through
helm,
and
there
are
a
number
of
different
flavors
of
MySQL
and
forks
of
MySQL.
You
can
run,
and
these
are
three
of
them
right
here.
A
That's
the
simplest,
but
there's
so
many
more
advanced
ways
of
running
MySQL
and
easier
ways
of
running
node
selector
as
I'm,
and
this
allows
you
to
specify
some
affinity
and
what
sort
of
node
you
want
to
run
it
on.
You
can
have
hard
and
soft
affinity.
I
haven't
used
this
myself,
but
it's
something
that's
I
find
really
intriguing
and
it's
an
incredibly
useful
part
of
kubernetes.
A
Now
we
all
get
onto
stateful
sets
so
what
our
stateful
sets.
You
know
we've
heard
a
lot
of
discussion
as
to
what
they
are
and,
if
you
don't
know,
they
provide
guarantees
about
ordering
and
uniqueness
of
pod
resources.
Anything
that's
related
to
that.
Pod
has
a
stable
name,
a
sticky
name
throughout
restarts,
and
it
allows
you
to
also
connect
directly
to
the
pod.
A
You
don't
necessarily
need
a
service
to
connect
to
the
pod
if
like,
for
instance,
if
you
have
three
minus
QL
servers
running
a
master,
two
slaves,
you
can
connect
directly
to
the
master
for
reads
and
writes
and
to
the
slaves
you
can
connect
read-only
and
you
can
specify
those.
It
also
ensures
ordinality.
When
you
start
it
up,
it's
not
like
a
deployment
where
it's
random
there's
also
one
pod
per
index
and
they're,
not
interchangeable,
and
they
won't
it
attempt
to
run
with
the
same
name.
They
have
a
stable
network
identity.
A
A
They
have
the
service,
basically
is
creating
a
thing
of
it
as
creating
as
own
a
domain
name
for
your
internally
for
your
service
and
they're,
stable
across
restarts,
also
stable
storage
and
stateful
resources.
You
know
across
restarts,
you
know
if
your
container
underlying
container
dies,
it
comes
back
up
and
reattaches
to
the
the
storage
that
was
associated
with
that
member
of
the
stateful
set
and
safety.
It
won't
scale
if
it's
unhealthy,
that's
very
good!
That's
something
we
want!
So
here's
a
good
here's,
some
animations
to
explain
to
you
kind
of
camera,
hone
the
difference.
A
Here's
a
deployment
so
deployment
you
have
of
a
replica
set
creates
one
pod
creates
another
pod.
You
notice
these
aren't
in
any
order
and
they're
not
names
with
a
you
know.
Each
one
doesn't
have
an
ordinal
name.
Third,
one
could
come
up
and
in
this
order-
and
then
of
course
you
could
have
a
crash.
Well,
there's
nothing
to
prevent
another
one
from
popping
up
so
but
then
we
have
a
staple
set.
So
we
this
one's
called
mysql'
first
node
comes
up.
Second,
node
comes
up.
Third,
node
comes
up.
A
A
So,
of
course,
I
mentioned
headless
service,
and
this
would
I
mentioned
is
like
creating
a
domain
name
for
what
you're
running
and
you
basically
specify
them
without
having
a
cluster,
IP
and
whoops.
I
didn't
want
to
go
there
yet
and
for
read-only.
If
you
want
to
do
read-only,
you
create
another
service.
If
you
like,
or
you
can
correct,
connect
directly
to
the
pod
since
they're
consistently
named,
and
then
we
have
storage
class
in
volume,
clang
Timbits.
A
In
this
example,
we
define
a
storage
class
name
OCI
and
it's
using
oracle
clouds,
block
storage
and
then
within
our
state
'full
set.
We
have
a
volume
claim
template
where
we
have
an
annotation
kind
of
referring
to
that,
and
then
the
storage
class
name
OCI,
and
so
that
when
the
the
pod
comes
up,
it'll
use
that
block
storage.
A
At
the
simple
here's,
a
simple
example
of
a
stateful
set,
this
was
an
example
that
anthony
a
had
put
together.
I
keep
it
around
it's
it's,
not
something
you'd
necessarily
use
for
production,
but
it's
a
very
it's
a
pattern.
You
often
see
and
one
of
the
one
of
the
operators.
I
show
you'll
see
this
pattern.
You
know
it's
three
nodes,
you
have
a
master
and
then
two
slaves
and
there's
a
read
service
that
it
connects
to
and
then
for
rights
you
can
connect
directly
to
the
master.
A
The
way
it's
built
is
there's.
There
are
two
init
containers.
One
init
container
sets
up
a
config
map
and
in
Detroit
sets
up
a
ma'idah
MySQL
CNF
file,
a
comp
file
for
MySQL.
If
it's
ordinal
0
it
sets
it
up
as
the
master.
If
it's
anything
above
0,
it
sets
it
up
as
the
slave
and
then
there
are
two
app
containers:
one's
a
sidecar
container
that
runs
backups
and
again,
if
the
or,
if
it's
ordinal,
zero.
A
If
you
look
at
that
slide
and
look
at
it,
you
can
explain
to
you
how
a
lot
of
MySQL
operators
are
done
and
how
the
approach
that
they're
taking
operators
now
this
as
I
mentioned,
takes
domain
knowledge
that
the
things
you
do
as
a
DBA
or
as
a
DevOps
engineer,
it
takes
those
patterns
that
you
do
repetitively
even
within
kubernetes
prior
to
their
being
operators
and
allows
you
to
it,
builds
it
into
the
app.
If
it's
you
know,
as
I
as
I
show
you
here,
there
will
be
setting
up.
A
There
were
two
things
that
I'm
gonna
show
you
one
is
setting
up.
I,
know
DB
cluster
with
group
replication.
The
the
steps
that
you
manually
do
that
it's
a
little
bit
of
work,
but
it
does
that
for
you,
you
don't
have
to
think
about
it.
It's
encoded
into
the
application
and
another
operator
which
uses
Orchestrator,
which
press
labs
built.
That
does
the
same
thing.
A
A
Operators
extend
the
crew
brunetti
api,
they
create
custom
resource
definitions
such
as
you
know,
here's
some
examples
here
at
CD
cluster
Prometheus,
my
minus
QL.
It's
not
supposed
to
be
a
space
there,
backup/restore
oracle,
weblogic
so
on
and
so
forth.
I'm
kind
of
doing
this
out
of
order.
It
leverages
kubernetes
primitives,
like
replica
sets
and
stateful
sets
and
services
they,
as
I
mentioned,
they
execute
common
application
tasks
and
they're
usually
installed
as
add
appointment.
A
Here's
a
good
example
of
what
operators
do
they
observe
analyze
and
act,
so
the
observed
stage
is
to
look
at
what
there
currently
is.
In
this
example,
there's
two
running
pods
there's
one
is
three
one:
one
one
is
three
to
10
and
then
it
analyzes
it
says
what
are
the
it
does
a
diff
on
it.
Basically,
it
says
what
are
the
differences
from
desired
config
to
running
config?
Well,
we
should
be
three
to
ten
and
there
should
be
three
members
and
then
there's
act.
A
So
act
is
going
to
get
the
desired
config
it's
going
to
recover
one
member
and
that
it's
going
to
recover
any
of
those
that
need
to
be
updated
to
three
to
ten
to
that
version.
I
won't
play
this
demo,
it's
a
it's.
A
pretty
cool
demo,
I
took
doing
a
CD
cluster
and
bringing
it
up,
and
it's
it's
probably
about
a
minute.
A
I
sped
it
up
quite
a
bit,
but
it
kind
of
it's
a
good
example
of
how
the
operator
pattern
works
and
you
can
abstract
you
can
extrapolate
that
farther
for
other
types
of
things:
more
advanced,
stateful
applications,
here's
a
list
of
my
SQL
operators
and
two
of
these
I'm
going
to
demonstrate.
There's
the
Oracle
MySQL
operator
and
then
there's
the
press
labs
MySQL
operator.
The
Oracle
Oracle
MySQL
operator
is
your
able
to
deploy
highly
available
MySQL
instance
on
a
kubernetes
with
a
single
command.
A
It
watches
the
API
server
for
custom
resource
definitions
related
to
MySQL
cluster
and
acts
on
those
resources,
there's
backup
and
restore,
and
there's
also
backup
schedule
that
utilizes
MySQL
8.0
group,
like
replication
and
I,
know
DB
cluster
has
automated
backup
and
restore
to
and
from
object
storage
s3
compatible
in
the
demonstration.
I'll
show
you
it'll,
be
Oracles,
block,
storage,
object,
storage,
here's
a
kind
of
an
overview
of
what
the
operator
does.
A
You
have
the
kubernetes
api
in
the
operator
and
it
interacts
with
a
stateful
set
running
the
mysql
cluster
and
then
within
each
each
one
of
the
pods.
It's
basically
set
up
like
this.
You
have
the
kubernetes
api.
The
operator
creates
CR,
d's,
mysql,
cluster
and
so
on
and
so
forth,
and
then
it
ends
up
running
a
stateful
set
and
within
each
one
of
those
stateful
sets.
There's
the
pod
has
an
agent
and
a
MySQL
database.
A
The
operator
is
acting
on
what
needs
to
happen
and
updating
the
kubernetes
api,
and
then
the
agent
also
is
talking
to
the
kubernetes
eye
api,
observing
what
it
needs
to
do
and
whatever
it
needs
to
do
it.
It
does
those
tasks
such
as
cloning,
doing
a
backup
doing
a
restore
setting
up
the
cluster,
and
then
the
agent
also
as
I
mentioned,
does
the
the
restore
and
the
backup,
and
it
does
that
through
streaming
to
object,
storage.
A
There
are
some
simple
examples:
I
since
I'm
gonna
do
the
demo.
I
won't
go
into
this
scheduled
backup,
that's
the
one
thing
I
do
when
I
show
it
it's
pretty
cool
you
such
a
schedule
and
a
cron
like
entry
for
it.
When
you
went
around
the
backup
and
set
up
which
storage
provider
you
want
to
use
connecting
to
the
Oracle
MySQL
operator,
there's
a
couple
patterns
you
can
utilize,
you
can
write
directly
to
a
single
pod
because
it
is
a
stateful
set.
A
You
can
do
a
read/write
only
service
if
you
like,
and
then
of
course,
there's
the
MySQL
router
pattern
which
you'll
see
in
the
demonstration
MySQL
router
is
a
new
feature,
a
new
piece
of
software
and
what
it
does
is
it's
intelligent
about.
You
can
tell
it
which
is
going
to
be
the
primary
and
the
secondary,
and
if
you
want
to
pick
a
node
in
the
cluster
to
write
to
and
then
specify
which
ones
you
want
to
read
from
it'll
do
that
for
you
and
proxy,
your
minus
QL
traffic.
For
you
and
often
what
you
do.
A
A
I'm
also
going
to
show
you
running
external
DNS
oracle
clouds,
dns
service.
I
have
a
domain
kubernetes
cluster
comm
and
the
website
will
be
set
up
as
that
automatically
so
I'll
go
ahead
and
oh
good.
It's
full
screen
I'm
in
presenter
view,
so
it
doesn't
look
the
same
as
over
there.
Alright.
So
the
initial
state
we
have
nothing
running,
just
checking
out
helm.
A
A
Last
year
somebody
said
you
need
to
resize
this
and
edit
and
I
said
I
almost
started.
I
said
no!
No!
No!
You
get
totally
off
track.
So
we've
created
the
operator
we're
looking
at
the
logs.
So
now
we're
going
to
look
at
the
cluster.
We
have
a
convict
map,
we're
gonna
use
the
default
authentication
plug-in.
We
have
our
password
in
a
secret.
Now,
here's
our
cluster
with
three
members
and
we're
the
storage,
and
now
we
have
also
we
have
to
create
a
service
account
for
this.
A
The
maniacae
well
agent,
sidecar
container,
so
we're
gonna,
create
we're
gonna,
create
a
namespace
called
WordPress
WordPress.
We're
gonna
use
that
namespace
for
all
subsequent
operations,
so
we're
gonna
create
that
service
account.
Now
we're
going
to
create
the
cluster,
so
you
can
see
the
operator
churning
into
action
there.
A
So
we're
looking
at
the
agent
logs
for
the
first
node
I
have
that
running
and
the
other
the
window
to
the
left.
That's
showing
the
the
PVCs
being
bound
on
Oracle
blocks
to
Oracle
cloud
block
storage,
so
I'm
just
going
to
log
in
to
kubernetes
dashboard
and
take
a
look
around
here.
Well,
things
are
coming
up.
You
can
see
the
deployments
occurring
see
the
containers
are
starting.
It
looks
looks
good
thus
far,
so
now
we
can
see
that
the
third
node
coming
up
and
now
the
cluster
should
be
there.
A
So
the
way
backups
work
is
that
the
operator
determined,
picks
out
one
of
the
secondary
notes
to
perform
the
backup
from
the
backup
is
MySQL
dump.
Currently,
only
we
are
working
on
enterprise
backup
and
we
do
have
an
architecture
that
allows
you
to
have
different
types
of
backup
providers.
So
here's
the
the
the
WordPress
container
pot
I
mean
deployment
and
we're
going
to
specify
the
DD
host.
It's
localhost
6-4
4-6.
We
also
are
going
to
create
an
external
DNS
deployment.
This
is
going
to
connect
to
the
Oracle
cloud.
A
Dns
service
and
I'm
also
going
to
load
a
secret
from
a
file
here,
I'm,
not
showing
you
that
file,
so
we're
gonna
create
that
now
and
I'm
going
to
watch
the
logs.
This
will
be
interesting
because
you
can
see
when
we,
as
as
the
the
deployment
for
WordPress
comes
up,
you'll
see
it's
connected
to
Oracle
cloud
service.
Now
now
we're
going
to
create
the
WordPress
deployment
as
I
mentioned,
this
is
going
to
run
MySQL,
router
and
WordPress,
and
it
also
sets
a
domain
host
name
for
the
WordPress
service.
We're
running
wwq,
Bernese
cluster
com.
A
So
at
this
point,
I'm
gonna
look
at
just
kind
of
confirm
that
it's
there
there
it
is
there's
a
text
record
in
any
record
that
was
created
that
was
kind
of
fast
sorry
about
that.
But
I
was
trying
to
squish
things
down
so
that
we
would
have
time
so
we're
going
to
create
our
WordPress
site
and
I
promise.
This
is
gonna,
go
really
fast.
That
was
really
typing
fast.
When
I
did
this.
A
A
A
We're
creating
the
backup
now
we're
gonna
go
back
to
the
other
screen
watch
this.
So
if
you
see
in
the
lower
right
window,
you
can
see
that's
where
the
backup
happened.
That's
on
node
that
that's
on
the
the
third
node
in
the
cluster.
It
could
have
been
any
one
of
the
secondaries
so
yeah.
This
is
where
I
got
really
fast.
I
drank
a
lot
of
coffee,
yerba
mate
day
and
I.
Just
went
to
town.
A
A
A
A
A
A
That's
cool
I
mean
it
it's
so
much
easier
than
the
olden
days
back
when
we
were
at
slash
dot,
somebody's
calling
up
sweating
bullets
because
things
are
broken.
That's
the
beauty
of
kubernetes
so
to
keep
it
going.
I'm
gonna
bring
this
back
up
here
and
go
into
presenter
view
this
better,
not
go
back
to
the
first
slide.
A
Good,
sometimes
it
does
that
it's
really
annoying
so
is,
as
I
was
going
to
show
you
this.
This
is
the
operator
dimmer,
that's
what
it's
basically
doing,
but
for
this
time
sake
we're
gonna
move
on
to
the
press
labs
my
SQL
operator,
so
this
press
Labs
is
a
company
based
out
of
Romania.
They
build
WordPress
websites
and
they
have
a
ton
of
data.
I
just
really
started
looking
into
this
in
the
last
few
weeks,
and
it's
pretty
interesting,
it
uses
MySQL
or
github
x',
MySQL
Orchestrator.
A
It
uses
asynchronous
replication.
It
makes
it
makes
use
of
the
percona
utility
user,
which
allows
it
to
manage
the
the
cluster
it
uses.
Paconne
extra
DB,
5.7,
there's
a
backup,
actually,
there's
no
restore
that's
a
slide
cut
and
paste
thing,
but
it
does
backup
they're
working
on
restore
and
it
uses
the
custom
resources
for
that.
There
are
a
number
of
containers
with
this.
A
The
operator
itself
has
two
containers:
there's
the
operator
container
itself
and
there's
also
the
orchestrator
container,
and
that
connects
to
every
note
every
MySQL
instance
within
the
state
full
set
so
that
I
can
manage
it.
There's
two
init
containers,
there's
init
minus
QL,
which
sets
up
the
configuration
files
kind
of
like
that
pattern.
I
showed
you
with
the
real
basic
master-slave
replication
and
then
there's
also
clone
MySQL.
That,
of
course,
it's
pretty
obvious.
What
that
does
it
clones
based
off
of
the
first
node
and
does
the
restores
then
there's?
A
Of
course,
the
application
container
is
a
pre
Kona
container,
Picone
a
database
and
then
there's
some
sidecar
containers.
There's
there's
a
sidecar
container,
which
does
a
lot
of
the
work
just
like
the
the
MySQL
agent
did
in
the
previous
example,
I
showed
you
it.
It
takes
care
of
maintaining
running
the
clustered
running.
Various
actions
within
the
state
will
set
there's
also
PT
heartbeat,
which
just
provides
information
back
to
Orchestrator
and
there's
also
a
metrics
Explorer
container
to
Prometheus
here's
kind
of
a
diagram
I
put
together
to
explain
how
this
works.
A
You
can
see
that
the
two
init
containers
taking
care
of
talking
to
object
storage
to
do
the
clone
the
sidecar
container,
interacting
with
Orchestrator.
Actually,
it's
not
sidecar.
It
connects
to
MySQL
that
arrow
is
wrong.
Something
I
did
right
before
the
talk
and,
of
course
we
have
the
operator
and
then
PT
heartbeat
and
the
Prometheus
exporter.
A
The
do
a
demo
of
the
press,
labs
operator
right
now,
and
what
this
is
going
to
do
is
show
you
a
three
node
cluster
created
by
the
MySQL
operator.
It's
going
to
show
you
each
of
the
components
the
MySQL
Orchestrator,
the
MySQL
operator
container
and
in
each
pod,
with
in
with
the
MySQL
and
sidecar
containers.
A
A
And
we're
going
to
add
the
repo
for
it,
then
we're
going
to
install
the
operator
at
this
point.
The
operator
will
be
coming
up,
don't
go
all
right,
so
this
is
the
name
of
the
cluster.
It
has
three
Brad
Lopes
and,
of
course
it
uses
secrets,
because
the
sidecar
container
also
needs
to
be
able
to
talk.
Also
Orchestrator
needs
to
be
able
to
talk
to
the
nodes,
we're
going
to
create
a
namespace
to
run
the
syn,
so
we're
gonna.
Look
at
the
logs
for
the
operator
looks
like
things
are
working
well.
A
The
next
thing
we're
going
to
do
is
look
at
the
orchestrator
logging.
You
can
see
that
it's
also
connected
to
every
instance
that
comes
up
subsequently.
We
also
going
to
do
a
port
forward.
This
is
really
nice
about
orchestrators.
It
has
a
really
nice
UI
for
managing
your
topology
there's
nothing
at
first.
As
things
come
up,
you
will
see
more
nodes
come
up
also
watching
the
the
persistent
volumes
as
they
get
bound
just
kind
of
knowing
what
what's
going
on
and
when
it's
going
to
be
ready
to
start
operating
on.
A
A
A
A
Now
we're
gonna
go
into
the
master
I'm
going
to
look
at
the
I'm
gonna
confirm
that
it
is
indeed
a
master,
and
it
is
it's
just
kind
of
neat
to
see
this
work
for
me
that
this,
like
ultimate
all
the
the
times
I,
had
to
manage
masters
and
slaves
and
write
scripts
and
chef
cookbooks
chef
cookbooks.
It's
all
automatically
done
for
you,
so
you
can
see
that
we
have
a
master
and
a
slave.
What
does
the
slave
connected
to?
It
should
be
connected
to
node
0
sure
enough.
It
is.
A
A
A
Now
we're
gonna
shut
it
down.
That's
just
wrong:
oh
no!
It's
black!
That
means
it's
broken
and
also
the
slaves
are
unhappy
not
to
fear
orchestrators,
doing
its
work.
It's
bringing
a
backup
also
kubernetes
is
doing
its
work
in
bringing
the
pod
back
up
and
it's
happening
so
quickly
that
it
it's
still
maintaining
being
master.
In
some
cases
it
might
take
a
little
bit
longer
and
what
will
happen
is
Orchestrator
will
promote
one
of
the
other
ones.
That's
kind
of
neat.
A
A
Wow.
Look
at
that
we're
at
the
bit/s
slide.
I
made
it
so
I
got
the
editing
view
presenter
view.
Okay,
so
I've
updated
the
graphics.
The
test
is
now
accompanied
by
the
way.
The
test
is
a
wonderful
thing.
It's
what
I
consider
sharding
on
a
silver
platter.
How
many
of
you
have
written
your
own
sharding
systems?
It's
a
lot
of
fun.
Isn't
it
yeah
yeah.
A
A
A
A
A
A
A
Anyway,
I
wish
I
could
cover
everything.
It's
it's
very
difficult
there.
You
know
my
my
takeaway
in
this
is
that
kubernetes
makes
it
possible.
Do
a
lot
of
really
cool
things
with
databases
and
running
the
databases
is
made
easier
with
kubernetes
people
would
think.
Oh
no
I
don't
have
that
complexity,
but
it
makes
it
easier
to
run
it.
You
don't
have
to
do
all
of
these
manual
steps
and
go
through
the
pain
that
you
used
to
go
through
in
previous
times
back
in
the
dark
ages.
Thank
you
for
coming.
I'm
very
sorry.
I
went
over.