►
Description
#Knative #OpenSource
WordPress on Knative by Evan Anderson, Software Engineer at VMware
One of the ways to learn about systems is by pushing their boundaries. The typical WordPress-on-Kubernetes demo uses a stateful WordPress server talking to a stateful database. WordPress seems like a great candidate to run as a stateless, scaleable service. What happens when we try to run a stateful WordPress on Knative? We learn a lot about WordPress and Knative!
A
Okay,
is
that
pretty
visible
for
everyone?
Yes,
yes
great,
so
why
am
I
here
and
why
am
I
talking
about
wordpress,
so
I've
been
working
on
canada
for
a
while
and
one
of
the
fun
things
about
k-native?
Is
that
it
and
kubernetes
both
are
designed
to
run
lots
of
different
software,
and
that
includes
running
software
that
maybe
wasn't
designed
with
kubernetes
in
mind
and
wordpress
is
a
great
example
of
that.
A
You
know,
there's
lots
of
places
you
can
go
and
you
can
pay
like
five
bucks
a
month
or
something
like
that
to
get
your
wordpress
site
hosted.
So
this
is
clearly
more
about
learning
than
it
is
about
being
the
strictly
most
cost-effective
option,
but
I
wanted
to
be
able
to
get
some
experience.
Actually
you
know
using
k-native.
A
A
I
wanted
to
be
able
to
run
real
software,
so
that
includes
stuff.
Like
upgrades-
and
I
learned
a
lot
of
stuff
about
kubernetes
upgrades,
including
scary,
etsy
d
surgery,
when
you
screw
up
your
quorum
and
you
have
two
nodes
down
that
you
re
reinstalled
and
you're,
trying
to
figure
out
how
do
I
get
quorum
for
x
for
etcd
when
it
expects
three
nodes?
And
I
have
only
one-
k-native-
has
not
been
the
painful
part
here,
which
is
great.
A
A
A
A
So
whoa
that's
a
pretty
simple
docker
file
and
I
just
downloaded
and
unzipped
the
nanospace
theme,
which
is
the
one
I'm
using
and
downloaded
installed
it
and
here's
where
we'll
show
the
final
product,
and
so
this
is
actually
cold
starting
over
there.
It's
actually
in
my
basement
running
off
my
dsl
line,
and
here
we
go
it's
up
and
running
and
if
you
wanted
to
see
the
cable
management
is
a
little
neater
now,
but
it's
basically
three
of
these
dell
thin
clients
with
about
eight
gigs
of
memory
on
each
one.
A
A
It's
pretty
boring
to
do
that,
but
copy
paste
and
you
know
you're
off
to
the
races.
This
is
actually
more
recent.
So
this
will.
This
is
hinting
a
little
bit
of
other
stuff.
I
needed
to
do
great
so
now
I'm
not
getting
logged
out
anymore
and
I
try
putting
together
that
first
post
and
I
upload
this
image
and
I
go
to
post
it
and
then
I
go
and
check
in
five
minutes
and
the
image
is
gone
which
doesn't
seem
right
so
yeah.
A
It
looks
like
wordpress
stores
images
on
local
disk
too,
and
since
we
want
to
be
able
to
scale
out
wordpress-
that's
probably
not
great
so
yeah.
What
can
we
do?
It
turns
out.
Other
people
have
had
this
problem.
They've
tried
to
run
wordpress
in
a
somewhat
more
automated
fashion
and
there's
a
couple
of
different
s3
plugins.
A
A
So
that's
awesome
and
at
this
point
I
realized
that
downloading
this
and
unpacking
it
and
everything
else
is
probably
not
the
awesome
thing
I
wanted
to
do,
and
so
I
go
and
make
a
two-stage
docker
file,
and
you
can
see
that
I'm
downloading
these
with
curl
and
unzip,
and
so
I
need
an
image
with
curl
and
unzip
and
I
didn't
really
feel
like
I
needed
those
in
wordpress.
So
here
we
go.
A
A
So
for
stuff
to
content
uploads,
I
rewrite
it
and
send
it
to
the
s3
service
and
for
everything
else.
I
rewrite
things
and
send
it
to
the
to
a
k
native
the
creative
external
service,
and
I
set
the
host
name
to
the
that
of
the
candidate
service.
So
I
could
be
using
domain
mapping
for
this.
But
since
I
want
some
pieces
of
the
url
to
go
to
one
service
and
some
pieces
to
go
somewhere
else,
I
use
the
contour
http
proxy,
and
so
this
is
working.
My
media
uploads
work.
B
A
A
A
A
A
A
And
a
little
bit
longer
and
a
little
bit
longer
and
eventually
you'll
get
upstream
request
timeout,
which
is
on
voice,
speak
for
it
took
more
than
the
15
seconds
I
expected,
and
eventually
it
will
start
up
and
it
will
work
and
then
everything
is
quick
and
so
forth
again,
so
you
know
going
and
loading
this
post.
You
know
everything
works,
quick
as
long
as
the
container
sticks
around
and
then
as
soon
as
the
container
goes
away.
A
So
it's
great
that
you
can
just
take
one
of
these
things
and
ship
it
in
here
and
then
you're
like.
Why
is
cold
start
so
bad
and
it
turns
out
if
we
actually
go
in
and
look
at
that
entry
point
every
time
it's
starting
up.
It's
discovering!
Oh
wait.
I
need
to
do
this.
Let
me
tar
up
everything
in
these
file
paths
and
copy
it
over
to
a
new
directory.
A
A
A
A
You
can
see
that
right
now,
I'm
sticking
with
wordpress57
and
we'll
pick
up
the
minor
versions.
There,
if
the
nanospace
theme
or
the
s3
uploads
theme,
has
a
newer
version.
I
need
to
go
in
there
manually,
but
the
nice
thing
is:
I've
got
git
tracking.
All
of
this,
so
there's
no
like.
Oh
what
happened,
how
do
I
go
back
and
yeah
and
it
scales
on
requests?
So
if
someone
wants
to
load
test,
my
blog,
it
should
work
just
fine,
and
actually
that
makes
me
think
of
one
more
thing.
A
A
A
A
A
A
A
A
A
A
B
B
A
A
A
A
A
A
A
A
A
If
you
want
to
actually
see
what
I'm
doing
it's
under
metrics,
I
have
a
fluid
bit
set
up.
The
one
extra
thing
is
that
the
collector,
I
also
have
a
little
log,
rotate
container
running,
because
otherwise
I
run
out
of
space.
I
put
like
you
know:
it's
a
40,
gig
volume
or
something
like
that,
and
so
log
rotate
is
how
I'm
getting
those
extra
things
and
it
doesn't
actually
work
great
with
nginx,
because
the
dot
log
it
recognizes
the
suffix,
but
all
the
other
ones.
A
A
Cert
manager,
the
circ
manager,
is
actually
for
external
ssl
internally.
I
think
it's
just
a
self-signed
cert
and
there
was
one
thing
I
needed
to
change
just
a
little
bit
so
you'll
see
there's
this
s3
endpoint
and
you
need
to
override
the
endpoint
parameter
to
get
it
to
point
away
from
s3
and
get
it
to
point
to
your
own
aws
host,
which
is
in
this
case.