►
Description
The ninth edition of our bi-weekly meeting to discuss Kubernetes as it relates to Drupal, WordPress, and the CMS space covers a round table discussion featuring DDEV’s K8s team.
Catch up with the group on GitHub: http://bit.ly/338dXC5
Learn more about our work with Kubernetes: https://bit.ly/3ii1xiD
B
B
B
So
one
of
the
things
that
we
tend
to
do
to
get
started
most
times
is
kind
of
go
around
the
room
and
introduce
everybody
I'll
go
ahead
and
start.
My
name
is
Jeff
Bridges
I'm
CTO
at
a
company
called
EDF.
We
use
kubernetes
in
production
and
focus
on
hosting
sites
so
that
developer
to
deployment
kind
of
workflow.
We
are
currently
doing
an
on
site
here
in
Denver.
B
So
having
a
lot
of
big
kubernetes
conversations
got
a
nice
demo
of
some
of
the
icd
process
that
we
just
went
through
with
a
product
called
Argos
PD
which,
on
the
18th,
we
will
have
a
lightning
talk
for
so
for
those
of
you
that
are
interested
in
learning
about
CICE,
as
it
relates
to
the
operators,
controllers
and
different
components
of
kubernetes
using
actions
in
Argos
CD.
That
might
be
a
good
one
to
attend.
B
D
E
A
B
F
B
C
G
B
E
E
You
know
as
usual
in
in
the
context
of
like
a
fruition,
you
know
we're
supporting
a
lot
of
different
CMS's,
tripoli,
wordpress,
bespoke
stuff-
and
you
know
my
focus
there
has
been
trying
to
you
know,
drive
some
change
and
modernization,
but
also
like
keep
things
simple
for
developers.
So
I
think
you
know,
that's
really
been
my
focus
and
something
recently
that
we've
been
trying
to
roll
out
is
is
like
a
uniform
way
to
even
just
handle,
like
log
logging
right,
because
I
think
a
lot
of
times.
E
Think
right
now
we
were
like
there's
all
these
flashy
things
and
there's
a
lot
of
VC
money
and
there's
all
these
products
with
yu-gi-oh
names-
and
you
know,
I
saw
her
Kelsey
connect.
Our
who
I
know
is
sort
of
a
high
profile,
kubernetes
guy
on
Twitter
and
he's
he's
kind
of
constantly
trying
to
like
pull
back
on
that
I
think
a
little
bit
and
just
be
like.
Let's
just
focus
on
like
a
good
API
and
pull
it
out
and
maybe
like
pump
the
brakes
on
on.
You
know
always
using
the
next
flashy
thing.
A
About
yeah
we've
been
pretty
busy.
This
been
at
that
conference
trouble
South.
Last
week.
We've
got
a
really
good,
deep
dive
into
skipper,
which
is
a
project
based
by
previous/next,
which
is
based
in
Sydney
in
Australia
and
yeah.
It's
a
really
cool
project.
It's
it's
definitely
something
worth
checking
out:
it's
basically
a
build
and
deployment
system
for
Drupal
and
kubernetes.
A
You
know
it
takes
a
lot
of
that
sort
of
paying
around
integration
with
kubernetes.
It's
just
a
CLA
based
tool
heavily
using
operators,
and
the
architecture
is
really
nice,
I
believe
so
it's
they've
kind
of
broken
that
up
into
two
different
operators
for
different
purposes,
and
we
were
able
to
actually
have
a
really
good
chat
about
how
we
can
collaborate
going
forward
which
is
really
exciting,
so
yeah
looking
forward
to
seeing
what
happens
there,
the
other.
The
other
big
news
is
that
Lagoon
the
projects
by
amazing
we're
we're
full
steam
ahead
for
native
community
support.
A
We've
got
customers
coming
on
board
with
managed
community
services
from
January.
So
yes,
okay,
if
you're
interested
in
and
that's
going
on,
we've
got
a
lot
of
stuff
up
on
our
gift.
Hug
page
and
yeah,
we've
already
got
a
pot
running
and
we
just
would
just
turn
those
final
tests
and
changes
to
to
make
sure
we
sort
of
dropped.
B
B
B
Cool
well,
there's
definitely
a
lot
going
on
in
the
kubernetes
world.
I,
don't
know
if
everybody
here
anybody
caught
it,
but
Ricardo
puts
it
a
very
interesting,
a
graphic.
It's
kind
of
a
summary.
Some
of
the
stuff
that's
been
happening
at
cube
con.
You
know
some
of
the
nice
things
that
have
been
happening
specifically
at
the
top
of
the
list
is
that
reading
launched.
Has
anybody
in
that
group
had
the
opportunity
to
use
it
yet
everybody's
head
down
trying
to
figure
out
this
kubernetes
things?
It's
totally
understandable,
but
I'm
hearing
good
things
about
it.
B
B
There's
a
lot
of
really
intelligent
people
with
a
lot
of
edge
cases
of
use,
cases
that
are
being
accounted
for
as
a
result
of
this
investment
in
this
work
to
Delaney,
&,
Investments
and
Edwin.
It's
our
now
old
members,
which
has
been
pretty
nice.
You
know
saying:
Dana
support,
Ranger
labs
announced
a
new
product
called
Rio.
I
haven't
had
the
opportunity
to
take
a
look
at
that,
but
I
think
it's
worth
checking
out.
B
Jade
frog
has
done
a
lot
of
different
things
in
the
Java
space
they're,
slowly
moving
forward
to
allow
more
and
more
utilization
inside
of
kubernetes
and
say,
they've
announced
a
frog
container
registry.
It
has
over
one
hundred
and
forty
eight
thousand
code
permits
so
far,
so
it's
definitely
worth
taking
a
look
at
and
I
might
have
mixed
that
statistic.
Just
a
little
bit
I.
B
Imagine
that
they
broke
it
out
and
modernized
it
a
little
bit,
but
that's
purely
our
Factory
is
a
very
old-school
workhorse.
That
does
amazing
things
when
implemented
properly.
It
can
be
a
bit
happy,
though
this
company
out
there
that
is
named
HPA.
They
have
made
an
announcement
that
was
worth
mentioning
a
cute
card
that
they
have
caged
all
of
the
source
solutions,
not
quite
sure
and
I'll
have
too
much
background
on
information
on
that
on
RedHat
made
an
announcement
that
they
launched
a
project
called
code,
ready
workspaces
to
point
out.
B
I'm,
definitely
take
a
look
at
that
and
then
two
more
announcements
de
midi
announced
spectra,
hybrid
cloud
solutions
and
mer.
Antis
launched
kubernetes
as
a
service
and
Miranda's
launching
kubernetes
as
a
service
is
particularly
interesting
because
mer
antis,
if
I'm
not
mistaken,
is
the
company
that
recently
purchased
the
docker
Composer
deployment
processes
from
docker.
So
docker
has
been
alleviated
of
that
and
that
dual
split
focus
and
are
focusing
primarily
on
the
local
development
environments
that
they
currently
work
on
so
curious
to
see
what
ends
up
happening
there.
B
B
The
statistic
that
I
I
misspoke
earlier
was
we're
sitting
at
a
hundred
and
forty
eight
thousand
code.
Myths
I
think
the
code
reading
workspace
has
roughly
35,000
contributors
in
it
and
then
collectively
a
coupon
represented
over
twenty
five
thousand
job
openings.
So
what
we're
seeing
in
the
industry
is
that
kubernetes
continues
to
accelerate.
It
continue
instituted
to
essentially
dominate
when
it
comes
to
the
orchestration
abilities
for
what
we've
all
been
working
on
so
I
think
it's
a
really
exciting
place
to
be
I
like
to
see
the
growth
and
I
think
it's
a
very
healthy.
B
As
far
as
that,
I
really
don't
have
too
much
to
talk
about
so
I
think
maybe
open
it
up
to
the
team
I
into
the
group
and
see
if
anyone
has
any
recent
challenges
or
celebrations
that
they'd
like
to
share.
Maybe
some
of
the
problems
that
you're
currently
facing
that
you
might
like
to
get
a
little
bit
of
feedback
on.
We
did
have
some
intelligent
people
on
line
so
feel
free
to
contribute.
There
I'll
just
give
it
a
second.
If
anybody
would
like
to
jump
in.
B
In
Cube
we're
exploring,
but
we
haven't
actually
taken
that
plunge
yet
I
understand
that
Magento,
when
we
were
at
a
type
of
free
conference
in
Germany
and
I,
believe
they
had
a
head
of
something
related
to
Magento
out
there.
I
am
not
sure
if
it
was
product
development,
but
you
know
we
did.
A
little
bit
of
exploration
sounds
like
it's
completely
possible.
B
Magento
tends
to
be
a
little
bit
heavier
as
far
as
disk
is
concerned.
Specifically,
it
does
a
lot
of
reading
and
writing
when
it's
in
a
development
mode,
but
it
also
has
a
nuttin
layer
mode
where
it
goes
eliminates
that
disk
I/o
largely
so
it
starts
to
become
more
acute,
capable
it's
definitely
not.
A
stateless
app,
so
I'd
be
ultra
curious
to
hear
of
any
success
stories
around
that.
E
Necessity
running
so
magenta
one
and
two
were
close.
Magenta
two
is
ended
or
excuse
me
magenta
one
is
end-of-life
light.
Eminently
magenta.
Two
is
actually
much
more
difficult
to
sort
of
containerize
for
some
of
the
reasons
that
you
just
expressed
and
the
fact
that
it's
I
think
brought
along
a
lot
of
interest.
Interesting
technical
debt,
I
guess
I'll,
say
I'm
very
much
like
a
scruple
commerce
guy
instead,
but
I
just
I
mean
we're
running
it
because,
basically
we're
just
we've
just
kind
of
done
a
legacy
application.
E
A
That's
definitely
something
we're
and
we're
looking
forward,
we've
just
actually
recently
edited
couple
of
on
the
framework,
so
civil
stripes,
a
big
one.
That's
a
new
zealand-based
CMS,
so
the
government
used
here
quite
heavily,
so
we've
been
working
on
that
support
just
last
week
and
well
yeah
we're
looking
at
remember
other
frameworks
just
to
provide
an
easy
onboarding
process
and
a
lot
of
them.
You
could
actually
just
get
going
straight
away
in
the
way
we
were
architected
on
platform.
A
However
I'm
just
wanting
to
give
like
an
example,
is
a
good
starting
point:
there's
a
good
set
up
and
here's
your
services,
they
should
arrive
and
one
of
the
things
with
Magento
I
remember
a
couple
of
years.
Back
was
a
but
sure
he
because
you
couldn't
you
couldn't
download
the
source
without
a
user
account.
Is
that
still
the
case.
E
Well,
that's
sort
of
more
like
a
build
time.
Consideration
you
use
still.
If
you
are
installing
with
composer,
you
still
need
to
have
like
a
credential
to
authenticate
against
Magento
repo,
although
like
it's
free,
if
it's
Community,
Edition
majestical,
has
that
same
problem
with,
like
you
know,
it's
not
GPL.
So
there's
a
lot
of
like
paid
paid
plugins,
but
we
just
addressed
that
by
like
injecting
you
know
the
right
credentials
and
stuff
at
Build
time.
But
my
the
challenge
is
that
we
have
more
with
Magento.
E
Is
that
on,
like
schema
change
and
like
code
deploy,
it
has
its
own
like
dependency
injection
and
like
sort
of
precompilation
some
system
and
all
of
the
Magento
people
that
we
have
because
I'm
not
one
basically
like,
say
that
it's
almost
unavoidable
to
have
like
up
to
15
and
20
minute
down
times
on,
deploy
which
I
just
can't
believe
but
nobody's
come
to
me
with
any
solutions.
There
I
think.
B
B
A
E
E
A
B
A
Yeah
and
yeah
I
haven't
actually
probably
looked.
It
looked
like
it
was
released
overnight
and
we've
just
been
asleep,
so
haven't
dug
into
it.
But
from
what
I
can
see,
it
seems
like
it's
kind
of
like
this
infinite
node
scaling
unit
thing,
so
you're
really
not
managing
nodes
anymore.
You
basically
define
your
workloads
I
need
to
find
the
resource
limits
within
each
pod,
and
you
let
Fargate
manage
how
it
gets
sort
of
deploying
and
manage.
So
it's
that
whole
I
know
there's.
A
You
have
also
been
going
down
this
path
for
a
couple
of
years,
which
and
I've
been
working
on
this
sort
of
infinity
node
project,
which
is
basically
a
node
which
Anton
either
an
aks
cluster
or
even
an
on-prem
cluster
that
you
can
actually
just
infinitely
scale
with
a
single
node
and
to
stop
the
need
for
having
to
manage
to
the
no
poles
and
resources
their
level.
There
was
also
something
Kelsey
brought
up,
I
think
when
it
was
announced
as
the
fact
that
hey
you
know
now
that
this
API
with
Cuba
Nidhi's.
A
B
A
Yeah
Jeff's,
obviously
being
pretty
hard
work
notice
he's
been
all
over
that
operator,
ACK
repository,
which
is
really
cool,
so
I
haven't
directly
used
that
operator
we
use
AWS
quite
heavily,
so
yes,
I
mean
the
idea
would
be.
We
use
the
old
way
to
deploy,
which
was
a
extranet
school
playbook,
because
it's
a
written
opponent
will
definitely
look
at
replacing
that
with
the
with
the
operator
from
Jeff,
because
that's
a
distance,
it's
just
a
pain
to
maintain
really
so
it's
incorporated
a
simple
CID
to
deploy,
iwx
and
manage
upgrades
and
things.
B
Yeah
I
said
just
a
general
kind
of
administrator
type
of
stuff,
I'm,
still
working
on
getting
a
little
bit
more
formalized
about
lightning
talks.
I
think
that
we're
going
to
have
a
good
one,
like
I,
said
on
the
18th,
that's
going
to
cover
our
go
speedy
and
github
actions,
and
some
of
our
deployment
processes
that
we
use
internally,
those
are
coming
along
pretty
well
we're
learning,
just
an
amazing
amount
of
knowledge
as
a
result
of
playing
with
some
of
these.
B
You
know
that
to
Brad's
point
earlier
about,
I
think
was
Brad
that
made
two
point
about
all
of
the
tools
that
are
popping
up
in
the
community
and
in
the
you
know,
ecosystem
it's
really
hard
not
to
just
pick
the
name
shining.
So
for
us,
we
started
off
with
a
product
called
code
for
us
that
we
were
using
and
it
originally.
B
Have
evolved
through
a
couple
generations
of
tools
and
I
think
that
we
found
a
nice
nice
sweet
spot
that
we're
looking
forward
to
sharing.
If
anybody
has
any
laning
talks
that
they'd
like
to
put
together
or
maybe
share
with
the
group,
you
know
feel
free
to
approach
me
and
I
will
get
that
on
schedule.
I
think
maybe
reaching
out
to
Knicks
Santos
I
believe
it
is
it's
to
get
an
overview
of
skipper
would
be
pretty
nice
because
it
sounds
like
a
neat
project,
but
I
don't
know
too
much
about
it.
B
A
We
great
to
have
them
on
bullet
to
really
go
through
it.
So
hopefully
I'm
not
gonna
totally
miss
this
up,
but
we
did.
We
did
do
a
deep
dive
in
a
box
last
week,
so
I
do
have
it
fresh
in
the
mind
but
yeah.
The
idea
is
that
it's
very
heavily
integrated
with
AWS,
which
is
actually
solves
a
lot
of
those
authentication
and
build
issues.
So
yes,
you're
right,
so
you
actually
build
out
your
project
locally
and
you
push
that
up
to
the
container
industry
with
an
aw.
It's
all.
A
Your
communication
is
all
managed
by
our
and
I
am
wrong.
So
it's
it's
basically
shared
across
a
project
or
anything
like
that.
So
you
indicated
already,
you
can
push
your
images
up
and
then
it
proceeds
to
deploy
out
to
eks
and
it
takes
advantage
of
a
lot
of
those
management
services.
So
cloud
watch
for
logs
out
front
for
CD
in
the
list
goes
on
the
service
ID,
it's
Aurora
for
database
and
all
of
those
are
little
mini
operators.
A
It's
on
the
on
the
single
Drupal
CID,
so
you
kind
of
have
a
single
place
to
know
exactly
the
state
of
the
whole
Drupal
site
that
you're
running
with
with
linking
off
to
all
the
operators
and
yeah.
It's
a
super
simple
super
easy
to
sort
of
manage
and
maintain
from
a
from
users
point
of
view,
I
guess
at
this
stage
it's
around
that
configurability,
so
extending
it
to
do
different
things
they
talked
about
rather
than
just
using
aurora
service.
A
A
Essentially,
so
it's
all
built
with
COO
builder,
so
all
go
based,
and
what
we've
discussed
is
the
fact
that,
because
of
a
they're,
all
very
integrated
into
a
single
and
operator
repository,
we're
really
trying
to
possibly
get
them
get
to
move
some
of
that
out,
because
these
are
really
generic,
tooling
type,
things
that
we
can
actually
share.
So
one
example
was
actually
having
development
container
images
so
what
they
they
have
a
concept
of
every
night.
A
They
go
and
snapshot
the
database
sanitize
it
and
push
that
into
a
database
image
and
and
then
release
that
and
so
developers
actually
every
day
just
pulling
down
the
latest
image
of
the
database,
which
contains
all
the
data
there's
no
SQL
syncing
or
anything
going
on
more
access
against
controlled
wire
by
your
normal
project,
access
all
the
sanitization.
It's
done
for
you,
so
they've
got
a
really
cool
tool,
called
mtk,
yeah
yep,
which
which
should
have
does
this
all
for
you
and
that's
actually
now
an
operator
within
skipper.
A
So
you
can
basically
send
the
cid
of
an
image
with
all
the
information
that
you
need
to
do
with
the
sanitization
instructions
when
it
goes
ahead
and
creates
that
sanitized
database
image
and
pops
a
summary.
So
that's
something
we
actually
use
a
GoSee
miss.
We
built
something
custom
for
that
purpose,
however,
really
came
to
sort
of
collaborate
on
that
sort
of
stuff
because
it
just
seems
like
it's
a
it's.
It's
a
great
solution
to
that
problem
and
it
might
as
well
be
a
generic
one,
which
is.
A
Sure
yeah
yeah,
it's
all
bleeding
edge
and
you
know
I
think
they've
made
the
right
decision
around.
You
know
managed
services
leverage
as
much
of
that
as
possible,
keeping
that
keeping
that
really
core
as
small
as
possible
and
then
only
they'll.
Look
at
you
know
extending
to
managing
some
of
that
stuff
inside
the
project.
Only
it
only
on
leads
basis,
they
simply
say
yeah.
It's
the
society
and
I
recommend
anyone
just
keep
an
eye
out.
Hopefully
they
can
actually
come
on
and
do
that
an
explanation.
Justice,
yeah.
B
B
Well,
you
know
it's
a
small
group,
so
I'm
gonna
keep
it
a
little
bit
shorter
than
normal
until
we
get
some
of
these
lightning
talks
lined
up.
So
thank
everybody
for
participating.
We
have
one
more
meeting
this
year.
That's
going
to
happen
on
December
18th
I
had
mentioned
that
a
couple
times
and
then
the
meeting
after
that
on
January
1st
is
going
to
be
canceled
because
of
New
Year's.
So
thank
you
for
your
participation
have
a
great
end
of
the
year
and
looking
forward
to
seeing
everybody
I.