►
Description
Meet-up number eight of the CMS/Kubernetes SIG! In this session, we review the TYPO3 community’s work with Kubernetes, discuss a recent K8s presentation from DrupalCon, and share our work on Buildpacks.
Check out our work: http://bit.ly/3iamOLe
Watch the DrupalCon Kubernetes talk: https://bit.ly/2XItqH7
Catch up with the group on GitHub: http://bit.ly/338dXC5
A
All
right
so
we're
recording
this
is
the
November
20th
I,
believe
a
meeting
of
the
CMS
group
that
we
started
to
basically
started
with
Drupal
to
help
solve
some
of
the
problems,
or
at
least
collaborate
on
some
of
the
problems
that
people
that
are
using
kubernetes
and
production
are
actually
dealing
with.
So
you
know
everything
from
file
systems
and
networking
to
DNS.
Those
are
all
great
topics,
the
premise
being
that
there's
a
lot
of
common
and
shared
functionality
and
issues
that
we're
hitting
across
the
spectrum
and
in
the
spirit
of
open
source.
A
Those
need
to
be
talked
about
and
brought
to
surface
brought
to
light
so
that
people
can
understand
them
and
help
collaborate
on
solving
them.
The
company
that
I'm
associated
with
that
makes
Dee
dev
is
particularly
interested
in
taking
those
concepts
and
those
problems
and
applying
them
to
other
communities
as
well.
So,
for
example,
we
do
a
lot
of
work
with
the
Drupal
community.
A
B
I
work
in
aqueous
7i,
my
first
Linux
installation
when
is
in
1994
I,
think
that's
like
where
it
was
good,
never
mind
anyway.
I
did
my
first
presentation
on
docker
I
think
it
was
was
in
2013.
Maybe
it
was
yes
on
Drupal
con,
just
just
after
so
so.
Kevin
was
with
me.
His
is
to
blame
because
it
was
it
with
me
in
in
Acquia,
and
he
started
to
talk
about.
This
thing
called
occur,
at
least,
oh
god.
No.
B
This
is
the
same,
so
I
I
started
like
mixing
alex
c
with
with
talker
and
sea
routes,
and
by
by
that
time,
doctor
was
really
not
that
useful
in
terms
of
security,
and
but
it
was
fun.
We
ended
up
using
docker
as
the
measure
sink
for
program
for
the
drupal
CI
testing,
which
actually
runs
on
top
of
that.
So
we
have
several
containers.
We
have
the
base
container
and-
and
we
have
the
my
sequel
container,
all
of
the
PHP
containers.
On
top
of
that
after
we
finished
that
work,
there
was
a
small
group.
C
D
E
A
It's
a
small
group
today,
so
welcome
everybody.
We
don't
have
any
lightning
talk
setup
so
basically
figured
we
kick
it
off
by
maybe
going
through
some
of
the
recent
events
that
ended
up
occurring
and
talk
about
some
of
the
interest
that
we've
gotten
from
different
areas
and
some
of
the
things
that
have
happened
at
these
events,
one
of
the
earlier
ones
just
before
Drupal
con
was
a
type
of
recon
event.
And
for
me
you
know.
The
type
of
three
community
is
very
interesting.
A
If
you
go
through
and
do
a
composer
install
of
Drupal
you'll
see
typo3
libraries
come
into
core
drupal
a
during
the
core
drupal
install,
but
oddly
enough
you
don't
see
any
drupal
packages
going
back
the
other
way.
So
one
of
the
things
that
I'd
like
to
see
you
know
over
the
long
term
is
those
two
communities,
maybe
working
a
little
bit
closer
together
to
solve
some
of
the
PHP
problems
that
they're
having
because
I
think
that
there's
a
more
collaborative
way
to
do
it.
A
I
on
the
hosting
side,
the
typo3
community,
they
have
different
requirements
than
the
Drupal
CMS
does
because
it
tends
to
be
less
of
a
intensive
installation.
They
do
a
lot
of
things
in
files.
So
it's
more
disk
I/o
intensive,
there's
a
lot
of
read/write
actions
happening
when
they
do
an
installation
and,
throughout
the
course
of
their
update
cycles.
A
So
what
that
means
is,
you
know,
is
showing
them
ways
of
integrating
some
of
the
local
development
environments
that
are
currently
out
there
with
hosting
providers
upstream,
making
that
handshake
a
little
bit
more
friendly
back
and
forth
to
open
up
not
only
competition
but
open
up
the
ability
for
their
developers
to
have
more
access
to
good
quality
hosting,
and
so
far
that
message
has
been
resonating.
We've
got
a
lot
of
interest
from
some
of
the
larger
hosting
groups.
Jay
Weyland
net
is
one
I,
and
the
names
of
the
others
are
currently
escaping
me.
A
But
there
was
a
lot
of
interest
there
around
solving
this
problem
moving
forward
in
a
way,
that's
open
to
the
community
and
I've
talked
quite
a
bit
about
build
packs
in
the
past,
but
we're
using
that
as
one
mechanism
to
be
able
to
help
enable
their
engineers
to
be
able
to
define
what
their
software
does
on
something.
That's
doc,
arised
essentially
or
made
to
run
contain
so
that
could
be
a
local
development,
environment
or
hosting
platform.
A
A
Next
up
we
ended
up
having
to
book
on
Amsterdam
I.
Think
Drupal.
Con
Amsterdam
was
a
really
great
event.
I
definitely
enjoyed
being
there.
Luckily,
we've
had
you
know
you
it's
a
little
difficult
talking
about
kubernetes
in
the
space
of
Drupal,
because
most
drupal
engineers
aren't
going
to
pay
a
lot
of
attention
to
the
deeper
systems
work
that
needs
to
happen
to
support
kubernetes
or
support.
Drupal
I
I
mean
on
communities,
so
we
weren't
able
to
get
as
much
content
as
we
probably
wanted
related
to
kubernetes
inside
of
Drupal.
A
A
A
It
was
standing
room
only
and
very
well
done
and
definitely
appreciate
being
a
part
of
that
we
had
another
gentleman
there,
Brad
Jones
from
a
company
named
fruition,
that's
in
Denver
we
had
Thomas
and
I
am
neglecting
to
remember
Thomas's
last
name
right
now,
I
believe
he's
from
New
Zealand
I
eating
great
personality,
lots
of
good
information.
Some
of
the
questions
that
we
went
over
with
things
like
you
know:
when
do
you
decide
to
implement
kubernetes?
When
does
it
actually
make
sense?
As
far
as
a
business
is
concerned
to
implement
something
as
complex
as
kubernetes?
A
Why
is
it
worth
taking
over
that
effort?
What's
the
difference
between
managed
and
unmanaged
kubernetes,
do
you
really
want
to
run
your
own
clusters,
or
do
you
want
to
maybe
go
to
gke
or
AWS,
or
one
of
the
provided
services
out
there
eks
to
manage
the
upgrade
cycle
and
kind
of
the
dependencies
for
kubernetes
itself?
We
talked
a
little
bit
about
security,
talked
about
some
of
the
mistakes
that
we've
made
over
the
course
of
implementing
kubernetes
and
each
of
our
own
respective
businesses,
and
you
know,
there's
a
lot.
That's
been
learned
there.
A
You
know
one
of
the
common
things.
I
think
that
came
up
a
lot
was
dealing
with
rate
limits
dealing
with
CPU
limits,
making
sure
that
you
really
really
understand
what
you're
doing
there,
because,
depending
on
what
you're
running,
we
had
a
database
or
a
static
HTML
site,
there's
significant
differences
that
can
cost
you
over
the
long
run.
So
very
good
conversations.
We've
got
a
link
there
inside
of
the
meeting
notes
to
the
YouTube
video
of
the
case
panel
and
highly
highly
encourage
everybody
to
take
a
look
at
that.
A
We
also
had
a
Boff,
which
I
think
was
really
really
nice
I'm,
not
quite
sure
that
the
recording
came
out
with
a
high
enough
quality
to
be
useful
for
most
people,
but
the
conversations
and
the
groups
of
people
that
we
got
together
were
very
nice,
starting
to
really
get
the
sense
that
there's
a
lot
of
a
lot
of
embracement
of
kubernetes
in
the
drupal
space
happening.
There's
a
lot
of
people
that
are
constrained
by
the
existing
hosting
providers
that
are
out
there
in
that
they
need
to
run
internal
systems.
They
need
to
run.
A
You
know,
sovereign
systems.
They
need
to
be
able
to
have
a
bit
more
control
over
their
what
they're,
implementing
so
we're
finding
a
trend
of
shops,
of
agencies,
of
larger
enterprises
that
are
starting
to
take
on
the
kubernetes
challenge,
starting
to
really
appreciate,
what's
out
there
and
starting
to
hit
a
lot
of
the
challenges
that
this
group
was
put
together
to
try
and
solve.
You
know
a
lot
of
the
questions
that
we
had
were
very
common
ones
that
we
have.
You
know
how
do
you
deal
with
files?
How
do
you
deal
with
databases?
A
That's
that
completely
focused
on
digital
ocean
right
now,
which
you
know
digital
oceans,
offering
of
kubernetes,
is
a
managed
service
and
I
think
that
there
aren't
a
really
really
nice
thing
there.
The
combination
of
flight
deck
and
and
digital
ocean
seems
to
be
really
powerful,
any
others
that
I
missed
that
you
guys
have
in
mind
or
would
like
to
recommend.
A
Yep
yeah
so
drug
SIG's
CMS,
we
have
one
called
skipper
which
is
out
there
and
I
believe
that
was
done
by
Nick
and
I
I'm,
not
very
good
at
his
last
name.
But
skipper
is
a
pretty
neat
posting
system.
It's
I
believe
it's
coming
out
of
Australia,
but
it
looks
like
it's
maybe
designed
to
focus
on
building
your
containers
locally
and
then
running
those
in
production,
exactly
as
they
are
so
definitely
take
a
look
at
that.
If
you
get
a
chance
and
they
move
the
github
repository
so
I
don't
have
a
link.
That's
immediately
available.
E
I
just
got
an
email
about
it
cool.
Can
you
talk
a
little
bit
about
that
I?
Think
digitalocean
has
seen
probably
a
lot
of
growth
like
they
they're,
always
a
popular
VPS
provider,
but
I
think
they've
been
trying
to
grow
into
like
hosted
services
and
they're
there
kubernetes
offering
is
pretty
good
and
pretty
simple,
but
they
were
missing
a
few
things
that,
like
on
Amazon,
it's
easy
to
set
up
the
whole
ecosystem
for
kubernetes
because
they
had
an
ECR
for
a
registry.
E
So
they
they
just
added
I,
don't
see
it
in
their
listing,
though
the
registry
set
up
it
and
I'm
not
seeing
it
in
here,
but
but
that
way,
instead
of
having
to
like
build
your
own
docker
registry
and
run
it
either
like
in
a
cluster
or
somewhere
else,
or
some
people
I've
seen
that
used
digitalocean,
they
actually
use
an
ECR
registry
just
because
it's
easy
to
set
that
up
where
they
use
something
else.
A
hosted
registry
somewhere
and
pay
money
for
that
digital
oceans,
registry
I
think
is
a
little
cheaper.
A
They
have
recently
accepted
funding
and
have
kind
of
changed
their
business
model
a
little
bit
so
I
think
that
they're
offloading
most
of
their
dr.
Enterprise,
Composer
type
of
systems,
work
and
I'm-
probably
slaughtering
that
that
completely,
but
to
another
company
called
mer
antis,
which
purchased
that
division
of
their
company.
So
it
sounds
like
Dockers
starting
to
focus
more
exclusively
on
the
local
development
environments.
The
dr.
A
dev
desktop
seems
to
be
kind
of
where
they're
trying
to
to
rally
behind
and
I
think
it's
been
a
very
interesting
road
that
they're
on
you
know
historically
I
think
that
they
kind
of
made
the
wrong
choice.
Around
2012
I
think
they
were
approached
by
Google
to
to
kind
of
be
the
Shepherd's
of
kubernetes,
and
at
that
time
they
were
a
bit
of
a
unicorn
and
came
up
with
the
idea
of
competing
against
kubernetes
and
it
doesn't
seem
like.
That's
working
out
very
well
for
them
any
thoughts
on
that
yeah.
B
I
have
a
question,
so
it's
then
gently
related
to
that,
because
I
think
what
we're
talking
about
here
is
we
have
a
series
of
links,
or
at
least
ideas
where
to
actually
get
some
really
cool
information
about
what's
going
on
in
this
sector
of
tech,
but
we
don't
have
a
centralized
place
to
actually
do
that.
Did
we
think
that
we
already
think
about
the
possibility
or
the
opportunity
to
act?
B
We
use
the
six
immense
repo
to
actually
start
a
series
of
dynamic
listing,
for
this
is
even
like
news
that
that
come
out
or
even
interesting
moves
or
interesting
tools,
blog
posts
that
we
want
to
call
attention
because
I
well,
you
created
the
repo
which
is
great,
but
it's
it
stopped
like
it's
now.
Two
months
is
and
yeah
what
about
like,
creating
like
like
a
blog
post,
MV
or
resources
and
the
or
whatever
and.
E
D
A
B
A
Iiii
would
definitely
appreciate
that
as
well
as
the
community
would
I'm
sure
did
there.
Let
you
know
a
the
nice
thing
about
what
I
was
exposed
to
in
the
Amsterdam
was
really
understanding
that
you
know
we're
all
accustomed
to
Drupal
being
a
global
phenomenon,
but
but
kubernetes
really
is
and
the
audience
of
interest
is
significant
and
it
spans
you
know
all
time
zones.
A
So
while
we
have
this
particular
one,
we
try
to
alternate
them
every
two
weeks
to
be
a
little
more
appealing
to
people,
maybe
in
Australia
or
time
zones
that
are
a
bit
more
offset.
But
I
think
that
really
the
success
of
this
group
is
going
to
be
related
to
being
able
to
get
things
into
a
format
where
people
can
access
the
information
at
their
own
pace
and
at
their
own
time,
so
appreciate
help
there.
You.
E
Yeah
I
also
about
the
docker
situation
I
put
in
the
chat
something
about
pod
man
and
bilder.
No,
no,
who
who's
familiar
with
those
things,
but
it's
they're,
basically
like
drop-in
replacements,
for
docker
we're
to
the
point
where
you
can.
You
can
alias
docker
to
Padma
and
run
docker,
build
and
dock
or
whatever
and
pod
man
will
do
it
for
you
and
the
reason
I
know
about
those
is
because
over
in
the
fedora
and
Red
Hat,
community
they've
switched
completely
over
and
they
don't
even
have
docker
in
their
default
repositories.
Anymore,
intros,
various
different
reasons.
E
So
it's
it's
interesting
because
I
think
long
term,
long
term,
I
I,
don't
care
if
it's
docker
or
whatever,
but
the
key
is
to
make
sure
that
you
have
containerized
infrastructure
and
a
good
build
process
and
all
that
kind
of
stuff,
but
I
as
the
years
have
gone
on,
I've
been
less
and
less
optimistic
on
docker
in
particular.
There.
This
wholesale
is
interesting
because,
like
Enterprise
is
the
only
thing
that
I
could
imagine
generating
profits,
whatever
profits
there
were,
which
probably
wasn't
astronomical
like
they
were
hoping,
and
so
they
sold
that
off.
E
And
now
it's
like
docker
the
open
source
stuff
and
like
are
the
open
source
stuff
like
docker
hub
there's,
no
way
that
thing
can
make
money
with
private
repositories,
because
there's
500
other
private
repos
setups
that
all
are
I've,
seen
in
more
use
than
docker
hub
for
private
registries,
but
they
have
billions
of
terabytes.
Probably
of
public
registries
on
there
and
that's
a
lot
of
bandwidth
to
eat
up
I
do.
B
Agree
with
that,
especially
because
for
one
project
I,
don't
know
what
is
a
project
internally,
but
we
used
systemd
and
spawn
containers
and
those
were
actually
much
lighter
and
much
easier
to
actually
work
with
instead
of
docker
and
one
wincing
we
really
saw.
Was
you
probably
seen
that
the
docker
service
sometimes
goes
down
and
the
system?
These
service
is
actually
really
much
strong
in
terms
of
that
it's
much
resilient
in
terms
of
failures.
So
in
that
project
itself
we
use
that,
and
we
were
quite
happy
with
with
the
situation
there
so
so
yeah
so
they're.
B
A
Have
a
lot
of
interest
in
the
Oprah
can
open
container
initiative,
which
is
another
specification
kind
of
in
line
with
what
Jeff
was
mentioning,
and
that
for
us,
is
what
we're
you
know
as
long
as
the
outputs
containers,
we
don't
care
what's
generating
it,
we
just
need
to
be
able
to
run
it
efficiently
and
that's
kind
of
the
focus
that
we're
starting
to
take
as
well.
Yeah.
B
And
and
resilience
to
be
honest
like
since
we
created
a
sorry,
you
know
Korea,
it's
like
the
real,
the
whole
reliability.
Think
it's
a
major
topic
like
we.
We
talk
all
the
time
about
not
having
failures
or
learning
from
failure,
and
one
of
one
of
the
scenes
we
see
is
like.
If,
if
you're
pushing
too
much,
the
system
like
docker
sometimes
does
because
it's
not
really
lightweight
it
gets
it
gets
it
gets
burned.
It
gets
you.
B
You
back
is
very
important
right
now,
especially
when
we're
moving
to
have
every
scene
in
production
and
want
to
scale
up
to
the
point
that
yeah,
you
know
what
the
customer
is
happy
and
nothing
is,
is
going
down
because
of
that
I
think
there
are
a
couple
of
things
that
fail
in
kubernetes,
booming
wise,
like
I,
said
docker
service
going
down
and
all
that
it's
it's
pretty
much
related
to
the
way
that
containerized
service
is
built,
not
not
kubernetes.
It's
so
kubernetes
has
a
lot
of
problems.
B
A
Of
the
nice
things
from
our
perspective,
you
know,
because
we
are
involved
in
some
of
the
local
development
tools-
is
that
docker
has
suddenly
become
responsive
in
the
issue
queues.
You
know
as
a
result
of
these
issues
that
are
happening
with
them.
You
know:
we've
had
complaints
for
the
longest
time
about
open
issues
with
docker
that
they're
not
responding
to
in
any
way
shape
or
or
form
they
actually
care.
A
We'd
like
to
see
more
of
that,
you
know
I,
you
know
if
doctor
can
come
around
and
actually
be
a
good
shepherd
of
open
source
and
and
and
participate
in
the
communities.
I
think
there's
a
lot
of
potential
for
them,
but
I'm
not
going
to
lie.
I
mean
we've
had
to
already
start
evaluating
different
solutions
over
the
long
term.
For
what
some
of
these
local
development
tools
can
do
and
it'd
be
a
real
shame
if
we
lost
the
momentum
with
solving
some
of
the
development
problems
that
we've
happened
as
a
result
of
something
like
dr.
A
going
out
of
business
or
going
away.
So
that
should
be
very
interesting
and
Jeff
dropped.
Another
link
in
here
CRI,
oh
I
Oh,
which
seems
to
be
container
runtime
for
kubernetes
as
well
definitely
worth
they
can
look
at
yeah,
so
good
stuff
lots
of
change
in
the
industry,
lots
of
fun
things
going
on
and
I,
don't
know
so
Ricardo
you
and
you
were
at
Drupal
con
Amsterdam
did
you
have
any
favorite
sessions
or
anything
that
you
picked
up.
B
Panelists
they
were
at
the
end
saying
yeah
yeah.
You
did
good
because
we
want
to
focus
on
the
discussion,
not
really
the
people
standing
up,
but
anyway
the
discussion
there
was
actually
under
containers.
That's
what
I'm!
That's
why
I'm
pulling
this
in,
and
it
was
more
so
I
really
liked
the
kubernetes
panel.
But
the
dev
tools
panel
was
like
going
more
deeper
into
the
container
thing,
because
what
we
are
talking
about
there
was
everything
what
everything
goes
one
on
docker
and
everything
is
on
docker
and
right
now,
they're
there
it
seems
like.
B
B
B
As
we
were
talking
here,
we
still
need
to
figure
out
what
are
the
options
and
what
are
the
best
solutions,
solutions
that
for
develops,
work
on
the
Mac
works
on
Windows
works
on
Linux
and
whatever
opens,
or
whatever
system
were
talking
about
and
that's
a
difficult
answer,
especially
because
I,
don't
know
what
you
guys
think
about
this,
but
when
I
asked
docker
and
I've
seen
that
claim
on
the
doctor,
docker
and
issues
say
Oh
docker
doesn't
work
correctly
on
a
man.
Well,
the
Mac
kernel
doesn't
support
what
the
Linux
kernel
supports
to
be
able
to.
B
Actually,
you
know,
have
user
spaces
and
have
all
the
things
that
come
from
Solaris
already
in
the
past.
They
were
basically
it
was
knowledge
that
was
moved
to
win
us
right
and
this
knowledge
that
was
moved
to
Linux
I,
think
Apple
doesn't
care
about
if
their
kernel
is
going
to
support
those
kind
of
sales
right,
they're,
not
they're,
not
it's
not
their
target
right,
so
asking
docker
when
they're
going
to
fix
it
for
a
Mac.
B
It's
like
saying,
oh,
how
do
you
go
about
changing
that
kernel
that
it's
not
your
own
saying
and
then
putting
it
back
on
a
cannot
do
that?
That's
that's
not
that's
not
possible
unless
they
could
actually
contribute
to
that
and
I
don't
think
I
was
going
to
do
that,
be
able
to
whatever
what
other
solution
could
happen.
Nothing
right
well,.
A
D
A
There's
a
lot
of
people
that
are
saying
now
that
you
know
it's
just
a
matter
of
time
until
we're
all
using
Windows
machines
instead
of
Mac's,
because
you
know
I'm,
hearing
rumors
that
the
new
windows
builds
are
actually
run
on
Linux
kernels
in
their
testing
that
so
in
the
next
couple
of
years,
it
should
move
to
more
of
a
Linux
based
kernel
than
the
NDP's
kernel,
which
I've
been
very,
very
interesting,
Microsoft's,
a
smart
company.
You
know
they've
got
their
eyes.
A
To
be
so,
hopefully
Matt
catches
up
but
I.
You
know
they
just
developers,
developers
developers
it
works.
You
know
you
appeal
to
the
developer
and
you
appeal
to
just
a
world
of
influence
as
a
result
of
that,
I
think
that
you
know
the
developers
we
we've
changed
the
world
with
the
Internet
and
we're
continuing
to
do
it
so
I
add
the
more
that
we
can
empower
the
developer,
that
better
off
everyone's
going
to
be
hopefully
Apple
catches
up
with
that
less
and
hopefully,
docker
has
the
ability
to
to
help
resolve
some
of
these
problems.
A
A
Cool,
so
just
moving
along
with
the
agenda,
you
know
coupons
happening
now.
It's
in
San,
Diego
I
definitely
wish
that
I
would
have
been
able
to
attend,
but
I
have
not
been
able
to.
So
we
have
a
link
to
the
live
stream
in
the
documents.
For
anybody.
That's
interested
in
checking
that
out
cube
cons
are
absolutely
amazing.
The
community
around
kubernetes
is
fantastic.
A
A
Another
thing-
that's
really
nice
to
note-
is
that
helm
three
is
actually
out
there
now
for
people
to
start
using
and
playing
with
we've
seen
some
pretty
good
results
so
far
from
poking
at
it
we're
a
little
hesitant
to
embrace
it
completely
because
of
some
of
the
pain
that
we've
gone
through
with
previous
versions
of
helm.
But
I
I
hear
really
good
things.
I
have
as
anybody
on
the
call
heard
anything
you
no
well.
If
you
have
the
opportunity,
I'd
definitely
check
it
out.
A
I
know
that
that's
moving
along
pretty
well
and
one
thing
that
I
am
going
to
mention
is
I.
Believe
next
call
we
will
have
an
actual
lightning
talk,
lined
up
getting
a
little
bit
more
formalized
about
lining
these
up
in
advanced,
so
I
think
that
there's
going
to
be
some
additional
content
that
people
are
going
to
be
able
to
get
out
of
these,
which
I
think
is
good
and.
A
I
guess
next
we're
on
to
you
know
recent
challenges
or
celebrations
that
people
like
to
share
what
problems
are
you
working
on?
Can
we
help
give
feedback
on
projects
for
upstream
projects
for
us,
Minoo,
I?
Think
really
focusing
on
our
CI.
Cde
pipelines
has
been
kind
of
where
we're
we're
paying
a
lot
of
attention
right
now
we're
doing
a
lot
of
work
with
Argos
CD,
which
I
think
has
been
pretty
useful,
have
worked
with
a
couple
of
different
providers
to
help
from
more
of
a
kubernetes
native
space,
and
our
ago
seems
to
be
coming
out.
A
Pretty
well
see
you
later
Jeff
yeah.
So
that's
been
a
good
one
for
us
really
getting
nailed
and
said
to
some
of
the
testing
that
needs
to
happen
to
validate
the
system
and
we're
finding
that
you
know.
Testing
kubernetes
itself
is
pretty
hard
so
going
and
stepping
back
to
more
of
a
user
kind
of
behavior
driven
testing
through
the
CL
is
that
we
exposed
to
customers.
We
find
is
kind
of
a
good
way
of
going
about
and
testing
the
entire
system
without
having
to
write
really
deep
integration
tests.
B
B
Rani
play
on
the
dev
tools
panel,
because
you
guys
are
doing
a
great
job.
Like
truth
is
well
it's
carrying
the
flag.
A
few
other
companies
may
do
right
now,
but
it's
it
needs
to
be.
It
needs
to
be
carried,
it
needs
to
be
move
forward
and
the
result
is
like
this.
This
meeting
and
some
other
things
like
setting
up
the
repo
I
hope
I
do
hope.
B
We
bring
more
people
in
I'm
going
to
talk
about
this
in
places
that
I
know
we're
going
to
have
a
Drupal
day
on
Friday
here,
sold
out
and
I'm
going
to
talk
about
that.
But
I'm
going
to
do
a
presentation
there
and
I'm
going
to
talk
about
this,
making
small
pitch
one
minute
or
two,
because
we
need
we
need
to
get
more
people
involved
in
it.
That's
the
way
to
do
this.
A
Anyway,
we're
doing
spending
a
lot
of
time
focusing
on
bad
camp
as
well
next
year,
so
we're
we're
going
to
look
at
some
fresh,
a
bit
of
a
fresh
perspective
on
on
the
DevOps
track
for
a
bad
cam,
so
any
ideas
people
might
have
to
help
us
kind
of
move.
This
conversation
forward
with
that
for
would
be
greatly
appreciated
as
well.
Okay,
cool
well
as
far
as
next
steps,
looking
forward
to
pull
requests
from
Ricardo
no
pressure
there,
no.
B
A
I,
like
I,
said
we
will
be
doing
a
little
bit
more
work
to
give
more
formal
about
some
of
the
Lightning
talks,
we're
going
to
reach
out
to
some
non
drupal
people
specifically
and
get
some
deeper
understanding
of
kubernetes
itself.
So
look
forward
to
that
and
in
the
next
meeting
and
outside
of
that
I
guess.
That's.