►
From YouTube: K8s ContribSummit Core Planning: SanDiego 20191202
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
everyone
welcome
to
our
last
edition
of
the
San
Diego
contributor
summit
retro
on
Paris.
As
always,
and
first
up,
we
have
Bob
with
finishing
out
registration
from
the
retrospective
I'll,
be
taking
notes
and
if
anybody
else
can
jump
in
and
help
take
notes,
that
would
be
great
too
Bob
kick
things
off
for
us.
Okay,.
B
The
last
thing
I
do
want
to
talk
about
registration
is
the
amount
of
no-shows
that
were
getting
for
the
new
contributor
workshop
and
I.
Had
this
idea
and
a
couple
other
groups
have
done
this
sort
of
thing
for,
like
meetups
and
I,
believe
the
CN
CF
have
done
this
for
some
of
their
other
events
and
that's
to
actually
charge
like
a
minimal
fee.
We're
talking
like
one
to
five
dollars
and
if
they
show
up
it
is
refunded
or
if
they
cancel
early.
C
B
A
A
E
E
G
A
All
right,
so,
let's
go
ahead
and
move
on
to
future
considerations.
Section
suggestions
for
next
time,
based
on
our
previous
experiences.
With
this,
let's
see
it
looks
like
I'm
up
first
with
some
two
quick
ones:
one
have
your
own,
then
you
don't
share
with
other
kolos.
We've
done
this
before
it
doesn't
work,
especially
registration.
A
The
other
suggestion
is
templating
is
cool,
but
don't
lose.
The
creativity
I
watched
us
several
times
during
this
summit.
Do
things
the
way
we
did
them
the
last
time,
just
because
that's
how
we
did
them
and
that
kind
of
losses,
I
think
the
creativity
of
the
event
itself,
like
especially
like,
for
instance,
shirts
swag
things
like
that.
So
just
my
advice
is
yes.
Templating
process
is
cool,
but
don't
lose
your
creativity,
Jeff
Bob,
burkas
you're
up
next.
E
Yeah,
so
this
is
something
that
we've
been
kind
of
tossing
around.
It
might
not
be
feasible
with
every
venue,
but
actually
having
a
completely
separate
wireless
network
that
people
can
connect
to
in
the
workshops
in
order
to
have
kind
of
a
not
congested
wireless
network.
Talking
through
the
harbor
box.
E
G
The
harbor
box
is
not
the
the
issue
here.
We
we
definitely
reached
capacity
on
the
Wi-Fi
and
had
a
bunch
of
people
not
being
able
to
follow
along
at
the
pace.
We
wanted
them
to
and
indeed
contributor
workshops,
because
the
internet
just
died
several
times
and
then
because
they
needed
to
download
a
bunch
of
stuff
that
we
didn't
have
in
the
harbor
box,
because
that
was
not
in
the
the.
A
G
You
know
Jeff
talked
to
me
about
this
as
well
at
the
conference
to
essentially
have
the
harbor
box
and
have
a
separate
Wi-Fi
network
around
that
one
and
then
have
the
the
harbor
box,
essentially
proxy
everything
that
would
help
us
a
lot
when
it
comes
to
removing
a
ton
of
traffic.
That's
going
from
the
internet
to
the
venue.
It
will
not
help
us
have
an
easy
way
to
set
up
Wi-Fi
for
everyone.
Yes,
we're
we're
splitting
this
across
several
rooms
right
and
and
several
larger
spaces
within
a
big
hotel
complex.
G
G
F
F
G
A
And
possibly
budget
yeah,
so
yeah,
Jeff
and
Deb
and
future
leads
make
sure
that
you
account
for
that,
because
that
means
you'll
probably
have
to
skim
somewhere
else.
Since
we
keep
since
we
hit
the
budget
most
events
so.
A
E
A
Well,
we'll
skip
Jeremy
for
right
now
and
then
anybody
else
with
new
contributor
shop,
future
considerations.
They're
gonna
have
their
full
retro
in
like
20
minutes,
so
we
can
either
punt
that
to
their
retro
or
speak
now
or
forever
hold
your
peace.
Anything
about
new
contributor
workshop
future
considerations.
E
We
can't
so
this
is
long
story
short.
We
had
people
that
were
trying
to
JIT.
Well,
they
were
just
grabbing
bags.
They
weren't
even
looking
at
their
names,
they're
just
grabbing
bags,
that's
kind
of
bad.
In
Seattle
we
had
a
single
point
where
people
would
come
in
and
pick
up
their
bags
if
we
are
going
to
have
that
kind
of
Welcome
Desk
slash
reg
like
touch
point
as
people
funnel
in
we
should
be
handing
on
their
swag
and
we
don't
need
to
give
it
to
them
with
that.
So
I
think
eliminate
the
whole
bag
process.
A
I've
mentioned
it
to
Jeff
already
the
only
way
that
that's
gonna
work.
Y'all
is,
if
you
have
a
separate
registration,
a
que
you're,
not
next
to
other
clothes.
You
can
see
that
there's
already
there's
already
issues
like
getting
into
the
event
itself,
so
that
would
get
back
that
giving
out
schwag
at
reg
would
only
further
that
issue.
So
that
is
why
it
is
absolutely
key.
You
all
have
your
own
registration
area,
you're,
all
your
own
entrance,
so
that
there
is
no
bottleneck
and
commotion
and
getting
people
through
the
door
in
like
a
thirty
minute
period.
E
G
Just
just
thinking
out
loud
here
if
we,
instead
of
having
the
the
two
table
setup
that
we
had
over
in
San
Diego
if
we
had
the
day
and
just
thinking
here
if
we
would
have
had
a
swag
slash
info
desk,
not
a
registration
desk,
because
people
can
register
everywhere
right.
So
just
a
swag
and
info
desk,
where
the
new
contributor
swag
was
I
and
we
could
had
that's
more
or
less
the
idea.
G
Yeah
cuz
it
really
tied
to
registration,
I,
think
that
will
just
become
a
ball
neck
and
I
would
rather
have
people
register
wherever
they
want.
You
gets
easy
a
ton
of
people
registered
at
the
airport.
It's
great!
Then
they
come
to
the
to
the
venue
and
they
pick
up
their
swag
instead
of
having
one
single
registration
point,
because
that's
gonna
be
a
yeah.
C
G
A
This
time,
though,
except
there
wasn't
like
someone
at
a
desk,
it
was
a
self-service
swag.
Pickup
I
feel
like
a
lot
of
the
complaints
that
I
heard
were
people
that
just
didn't
even
know
the
bags
were
there
so
I'm
wondering
if
that's
why
I'm
thinking
like
it
needs
to
be
near
the
door
where
people
come
in,
it's
like
a
first
thing
so
that
they
see
it
or
be
very
close
to
a
door
where
people
are
coming
in
so
that
they
say
it.
They
all.
G
A
III
I
don't
understand
the
complaint
that
people
didn't
see
the
bags,
but
I
definitely
think
we
can
be
a
little
clearer.
We
can
have
a
big
big
sign,
an
enormous
swag
sign.
Doesn't
people
know
that
they
should
pick
things
up
there,
but
yeah
we
can.
We
can
definitely
staff
it,
but
that
would
be
more
staff
true,
but.
E
I,
actually
I,
don't
think
that'll
be
difficult,
I,
don't
think
staffing.
It
will
be
that
difficult,
because
if
it's
the
same
place,
that
people
are
going
to
stick
their
bags
or
need
to
sit
down
or
essentially
do
what
they
did
in
the
booth
that
we
had.
There
was
there's
at
least
someone
there
all
the
time.
Yep.
A
I
Had
a
brief
discussion
with
Jeff,
but
it's
after
the
community
discussion.
So
the
point
there
was
that
Deb
was
technically
the
single
person
from
CN
CF
on
the
table
on
the
other
stuff
and
was
in
the
staffing
table
were
the
CNC
representative
could
be
only
they're
presented
hold
of
this
yet
CF
stuff.
A
H
A
lot
of
the
program
sessions
were
sparsely
attended.
You
know
large
part,
because
contributors
were
you
into
the
hallway
track,
like
I
had
times
when
we
had
less
than
20
people
less
than
25
attendees
in
the
big
room
and
like
a
hundred
people
outside
in
the
coffee
area.
Talking.
So
if
that's,
what
folks
want?
We
can
save
ourselves
a
lot
of
trouble
by
simply
having
fewer
concurrent
tracks
and
I
think
that's
the
way
to
go
and
will
be
less
planning
and
less
work
and
whole
bunch
of
other
things.
A
The
best
part
about
those
recordings,
though,
is
we
have
them
for
history
now,
like
especially
like,
like
the
practical
get,
even
though
some
of
even
though
some
of
the
sessions
were
sparsely,
attended,
they're
gonna
have
you
rates
of
thousands
at
this
point
yeah
it
doesn't
play
the
discussion
sessions,
though
yeah
yeah,
yeah,
I,
know
I
get
that
as
well,
but
to
me
and
what
I
would
I
told
a
lot
of
this
lot
of
the
presenters
myself
is
to
think
about
it.
A
H
Yeah,
that
was
just
a
communication
problem
in
that
I
wasn't
clear.
That
Deb
was
telling
me
that
we
didn't
have
the
budget
to
mic
and
record
all
rooms,
and
so
we
ended
it,
but
first
for
the
contract
that
said
that
some
rooms
would
be
recorded,
but
not
Mike,
which
me
all
right.
So
we
need
to
look
at
that.
Make
sure
it's
in
the
budget
ahead
of
time
and
all
obviously
be
less
of
a
problem
over
to
a
fewer
concurrent
tracks,
because
that's
less
of
an
expense.
A
We
make
it
a
best
practice
to
record
all
sessions
go
forward
unless
they're
on
conference
or
technical
discussions
I
feel,
like
I
mean
we've
got
people
flying
in
from
Poland
to
do.
Talks
like
I
really
think
that
every
session
should
be
recorded,
with
the
exception
of
on
conferences
and
technical
discussions.
I'd.
H
B
H
Why
already
did
that
for
content
for
this
contributor
summit,
because
we
had
a
number
of
submissions
for
things
that
were
basically
very
sig
specific
content
and
we
rejected
those
or
in
a
few
cases
where
it
was
borderline,
got
them
to
modify
it
to
make
it
more
inclusive
of
people
who
were
not
regular
participants,
in
that
sake
the
so
so
we
did
actually
push
people
to
to
look
at
hey.
You
know
this
really
sounds
like
a
seed.
You
know
deep
dive.
C
H
Yeah
so
one
problem
we
had
in
that
this
is
just
an
incidental
thing.
One
problem
we
had
in
the
morning
was
we
couldn't
find
some
of
the
room
facilitators
and
we
didn't
actually
have
cell
phone
numbers
for
people
so
that
we
could
find
out
because
they
were
actually
at
the
venue.
We
just
didn't
know
where
they
were
so
and
that's
just
something
I'm
suddenly
I'm.
So
we
should
just
do
for
all
staff
and
volunteers.
H
Right
is
make
sure
we
have
cell
phone
numbers
for
those
people
and
the
cell
phone
will
be
using
at
the
event
so
that
we
can
message
them.
If
we
don't
know
where
they
are,
the
let's
see
haven't
written
checklist
printed
schedule
for
wound
Proctor's
the
we
did
not
have
a
printed
list,
we
could
hand
them
on
the
day
of
the
event
we.
A
H
A
A
I'll
also
add
another
one
with
please
try
to
have
this
room
not
be
huge.
More
is
not
better
any
other
comments
about
restructuring
of
room,
facilitator
roles,
I.
A
Also
kind
of
think
that
every
shadow
should
take
a
room,
I
feel
like
you
between
this
core
group
of
people.
We
should
have
room
facilitators
covered,
that's
just
my
take
on
that
too
I
feel
like
if
we
have
forty
people
that,
like
we
don't
really
know
and
they're,
not
necessarily
in
the
community
yet
etc,
etc.
That,
like
just
adds
to
the
chaos,
it
would
just
be
so
much
better
if
that,
if
that
core
crew
of
people
could
be
shrunken
down
a
little
bit,
yeah.
A
Definitely
saw
shadows
that
were
not
listed
as
from
facilitators
or
any
any
kind
of
day
of
help.
I
mean.
E
I
took
four
hours
worth
of
rooms
in
San
Diego,
but
the
other
thing
is
oftentimes.
I
am
like
bouncing
between
the
room
and
some
other
task
because
want
Lake
once
once,
someone
is
in
the
room
and
actually
presenting
like
checking
in
every
10
minutes
is
appropriate.
You
don't
like
me
personally,
I
have
never
found
whenever
I've
proctored
a
room
either
at
cube
con
or
in
other
events
that
I
have
had
to
sit
there,
the
entire
time
so
being
able
to
bounce
between
the
room
and
then
something
else.
E
H
H
Yeah,
so
one
of
the
things
that
we
could
do
to
get
a
better
idea
of
no
show
or
showing
up
for
only
one
or
two
hours
rates
would
be
having
the
CN
CF
make
a
comparison
of
registrations
for
the
contributor
summit
against
other
events
and
letting
us
know
how
many
people
were
double
or
triple
registered.
H
C
A
good
question:
I,
don't
think
we
ever
counted
the
tables
I
think
we
assumed
that
there
would
have
to
be
some
combining
of
tables.
I
actually
think
that
next
time,
maybe
I
don't
know
if
the
suggestion
was
in
here
already
somewhere
else,
but
I
think
we
actually
need
to
count.
The
tables
have
like
a
map
and
have
some
organized
way
of
distributing
the
the
SIG's,
because
the
the
problem
with
having
it
be
super
successful
and
everyone
was
there-
was
that
it
turned
into
chaos.
C
H
G
E
So
I
have
mixed
feelings
on
that
it
from
like
a
top-down
perspective,
there
were
a
lot
of
things
happening,
but
at
the
same
time
the
karaoke
was
a
long-running
thing
where
you
could
like
pay
attention
or
not.
The
dogs
were
a
long-running
thing,
I
think
two
hours
for
you
to
pay
attention
or
not
in
it.
The
unconference
was
I
believe
the
only
like
short
thing
where
it
was
Markey
and
Paris
I.
E
Think
of
the
marketing
bears
carrying
around
the
whiteboard
like
sign
out,
sign
up
sign
up,
but
like
it
having
multiple
small
things
that
you
can
focus
on
means,
you
could
choose
what
you
did.
Okay
and
oftentimes.
A
lot
of
people
were
just
you
know,
doing
the
hallway
track
and
talking
with
their
birth,
anyways
I
I.
E
Think
this
is
where
you
and
I
are
gonna
disagree,
because
I
went
in
there
for
20
minutes
and
in
those
20
minutes,
I
saw
at
least
10
people
come
in
at
the
dogs
and
leave
and
I
always
saw
a
little
bit
of
traffic.
The
thing
was
the
the
area
itself.
Wasn't
that
big
and
I
don't
think
people
wanted
to
crowd
the
dogs,
which
is
good
but
I
do
think
they
they
got
utilized.
It
just
wasn't
like
a
mad
rush.
E
G
Yeah
I'm
with
Jeff
I,
got
mixed
feelings
here.
Yeah
there
was
a
lot
of.
There
were
a
lot
of
things
happening
at
once,
but
that
also
meant
that
you
could
be
doing
a
ton
of
things,
so
you
could
do
the
bingo
and
meet
with
people
or
you
could
listen
in
on
the
hilarious
and
wonderful
karaoke
or
it
could
go
at
the
dog
and
chill
for
a
bit.
It
gave
people
a
lot
of
options
instead
of
just
hanging
by
the
box.
Yeah.
C
G
J
Think
I
wanted
to
add
on
to
the
whole.
Yes,
there
was
a
lot
of
things
going
on
I,
don't
think
there
was
a
problem,
unlike
the
the
attendee
side
of
like
attendees,
like
being
like
this
too
much
stuff
I
think
it
was
the
things
going
on
which
required,
like
you
know,
high
kind
of
maintenance,
ish
well
for
me,
like
with
the
bingo
stuff,
I
felt
like
I
kind
of
underestimated,
a
lot
of
things,
because
it's
the
first
time
running
it.
J
E
C
C
Don't
know
if
there's
anything
more
explicit
that
we
can
do
about
just
making
sure
that
the
date,
and
not
just
saying
it's
on
Monday,
but
actually
saying
it's
on
Monday,
the
or
whatever
in
every
single
communication
that
we
do
I
think
we
just
need
to
be
really
clear
that
the
date
of
the
party
and
the
date
of
the
event
and
absolutely
every
communication
we
put
out.
Maybe
it
already
was
I,
don't
know
you.
D
C
A
C
A
Think
we
should
run
like
ke
dev
emails
weekly
about
like
a
certain
activity
that
we're
having
to
highlight
it.
It's
kind
of
like
contributor
summit
highlight
of
the
week
and
things
like
that
I
think
more
communication
is
actually
good
here,
so
+1
to
that
I
think
that's
it
for
that
section
and
I'm
back
y'all
Comcast
Internet.
What
a
bummer
three.
A
B
The
the
best
thing
that
went
the
best
for
the
NCW
was
having
people
in
the
room
to
do
hands-on
help
because
we
ran
into
a
bunch
of
issues
and
people
had,
especially
in
the
new
contributor
workshop,
had
a
lot
of
varying
levels
of
familiarity
with
any
of
the
tools
involved.
Like
some
people
didn't
know
how
to
use
get.
Some
people
didn't
know
how
to
use
go
so,
there's
combinations
of
those
things
and
I
think
having
people
in
the
room,
especially
we
had
several
three
or
four,
maybe
in
the
NCW
beginners
track.
B
I
think
that
was
super
helpful
and
made
it
successful
like
at
the
end.
Even
though
we
had
a
bunch
of
issues,
there
are
still
people
that,
at
the
end,
we're
like
able
to
make
a
change
to
coop
scale
and
build
it
and
see
that
it
worked
and
had
some
understanding
of
where
the
code
lived
and
I
think
that
was
really
useful
to
people.
B
The
ones
that
like
I,
saw
them
have
that
success.
We're
really
happy
that,
like
the
people
were
there
to
help
each
other
also
people
started
helping
each
other,
as
they
were
sitting
next
to
each
other.
I
think
we
definitely
should
encourage
that,
maybe
like
as
a
group
thing,
because
I
think
we
kind
of
broke
up
into
like
here's,
what
you
should
do
and
then
it
was
kind
of
like
a
free-for-all
and
we
wandered
around
help.
People
which
work
really
well
but
I
think
we
could.
H
B
A
Where
I
was
going
with
those
registration
questions
to
y'all
like
we
had
all
this
data
about
the
folks
and
like
their
skills
and
I?
Yes,
I
know
that
people
over
inflate
their
skills
or
maybe
even
under
inflate
their
skills,
but
at
least
it's
still
a
good
pulse
of
like
how
maybe
we
could
group
people
in
the
room
and
stuff
like
that.
I
just
wanted
to
say
that,
like
for
future
considerations
on
registration,
if
there's
specific
groupings
that
you
could
figure
out
ahead
of
time
use
it
I
can.
K
I'm
trying
to
get
context
here
and
know
so:
okay,
I
think
for
the
most
part,
people
self
selected
into
the
correct
groups
between
beginner
and
intermediate.
We
still
had
some
questions,
but
I
think
we
were
very
clear
on
who
should
be
in
which
room,
mainly
the
questions
I
had
were
from
folks
who
were
on
the
cusp
of
things:
they're
like
well,
I've,
sort
of
done
kubernetes
but,
like
I,
don't
know
anything
about
the
community
and
what
should
I
do.
I
K
Anything
on
that,
in
that
sense
we
did
well.
The
codebase
walkthrough
is
really
helpful
for
people
and
on
the
on
the
intermediate
workshop,
so
that
went
well.
The
reason
why
I
think
that
went
well
is
because
people
asked
good
questions
afterward,
they
didn't
ask
questions
like
where
are
things
and
they
asked
more
questions
on
like.
Why
are
things
this
way,
which
you
know
we?
None
of
us
have
good
answers
for
so
there's
that,
but
that's
just
the
way
it
is.
K
There
were
a
couple
people
on
the
intermediate
side
that
would
have
probably
done
better
on
the
beginner
side
of
things,
there
was
one
person
who
I'm
who
asked
really
specific
questions.
Very
they
weren't
really
questions.
They
were
more
like
demands
like
do.
You
have
a
diagram
of
like
the
kubernetes
repository,
and
that
was
really
funny
because-
and
the
best
part
was
that
one
of
the
other
participants
said
this.
K
B
B
K
All
right,
oh
one,
more
thing
that
went
really
well.
It
was
really
awesome
to
have
everyone's
getup
handles
beforehand
and
we
could
I,
don't
know
how
that
worked
out
in
the
beginner
track,
because
that's
where
we
do
the
playground
exercise-
and
we
don't
do
that
in
the
intermediate.
But
it
was
really
successful
to
have
have
it
set
up
beforehand.
Yeah.
K
A
Everyone
for
pounding
down
the
CIL
CLA
stuff
ahead
of
time,
yeah
finally,
Tim
says
as
well:
yeah,
that's
awesome
all
right,
so
our
favourite
section.
What
can
be
improved?
Let's
see
going
down
here,
new
contributor
workshop,
Jay
burkas-
you
actually
have
the
first
one
with
bunch
of
NCW
attendees
didn't
get
the
prep
email
for
whatever
reason.
H
A
So
you
know
something
something
along
the
lines
of
life
your
reg
is
done,
but
you're
gonna
get
a
ton
of
other
information.
So
look
out
for
it
or
something
like
that.
I,
don't
know
we
always
have
a
problem
in
this
area
y'all.
This
is
another
thing
about
put
the
doing
the
new
contributor
workshop
out
of
a
box.
Oh
we've
had
so
many
mixers
with
like
the
preppy
males
and
like
who
reads
them
and
like
who
actually
like
some
people
will
even
come
in
and
say
how
we
read
it.
K
We
did
some
of
that.
We
did
in
fact
paying
everybody
in
the
beginning
of
the
workshop
and
said:
hey.
We
just
realized
that
the
network
is
completely
trashed.
So
if
you
haven't
cloned
kubernetes
yet
start
it
now,
because
it's
gonna
take
you
half
an
hour,
so
we
do
have
reminder
slides
for
everybody,
and
we
don't
want
to
go
overboard
with
that,
because
we
also
don't
want
to
give
the
impression
that
this
is
like
the
expected
workflow
I.
A
B
Yeah,
so
we
in
the
beginner
workshop,
like
we
had
instructions
for
pulling
things
from
the
harbor
box,
and
that
was
we
didn't
actually
end
up
using
them,
because
we
didn't
have
time
I,
think,
and
that
was
useful
for
people.
But
then
we
had
some
people
who
were
trying
to
use
like
cloud
machines
there,
like
their
machines,
were
super
locked
down.
B
Having
worked
in
an
enterprise
before
that's
super
common,
like
I'm
gonna,
bring
my
laptop
that
Lockheed
issued
me,
but
I
can't
actually
install
anything
on
it,
so
I
would
use
like
any
AWS
instance
or
something
or
droplet
that's
what
people
were
doing
so
having
some
alternative
instructions
would
have
been
useful,
I
think
the
Wi-Fi
I
ended
up
kind
of
out
and
not
being
great.
So
it
was
not
helpful
like
at
some
point
because
of
the
Wi-Fi
but
I
think
when
the
Wi-Fi
was
still
working.
B
It
was
really
useful
for
people
that
be
able
to
pull
those
things
really
quickly
and
not
saturate
the
network.
The
next
one
is
the
instructions,
and
this
probably
plays
into
Chris's
point
about
this
team
being
thrown
together.
The
flu
there
were
some
instructions.
It
conflicted
like
we
had
people
check
out,
we
said,
install
go
1:13,
but
then
we
had
them
check
out
like
a
1/16
branch.
So
there
was
some
conflicts
there,
because
you
can
actually
build
116
with
NGO
113.
B
Also,
there
was
some
pauses
where
people
assembled
over
commands
or
didn't
really
understand
what
the
instructions
on
the
slide
said.
So
having
like,
maybe
a
little
bit
more
hands-on
approach,
there
would
have
been.
It
would
have
been
good,
especially
with
the
instructions
being
kind
of
not
validated
but
also
like
I,
think,
a
follow-on
to
that
is
maybe
like
have
a
week
week
before.
Have
the
content
done
so
that
we
could
validate
things
beforehand
and.
M
Then
I
think
we
part
of
it
is
the
the
shifting
of
staff
I'd
walk
through
it
with
marki
a
week
or
so
before
and
highlighted
each
of
those
things
as
a
potential
gotcha
to
decide
to
pass
which
go
in
which
Kate's
to
choose
to
build
and
fix
it
down
ahead
of
time,
one
or
the
other,
and
and
to
note?
Because
it's
in
flux
like
for.
K
M
A
F
K
K
We
have
been
moving
towards
modularizing
the
workshop
and
breaking
it
up
into
tiny
boxed,
focused
sections,
so
I
added
a
bunch
of
play
books
where
I
tried
to
break
out
all
the
content
by
topic,
put
a
time
estimate
on
them
and
put
suggestions
on
implementation
on
them.
One
of
the
main
things
that
was
hard
this
time
was
that
I
have
been
presenting
most
of
the
content
by
myself
in
previous
workshops
and
the
delegation
didn't
work
out
super
well
because
I
handed
people
slides
that
I
had
made
and
I
had
context
for
so
going
forward.
K
Having
unified
slide
topics
I
know
is
important
to
some
people,
but
I
think
it
is
more
important
that
you
own
your
own
content.
So
that's
one
of
the
things
and
then
I
put
like
some
really
specific
suggestions
with
the
so
going
back
to
having
people
be
more
engaged
rather
than
talking
at
them.
We
can
hide
some
like
fun,
Easter
eggs,
so
one
of
the
interactive
I
think
works
really
well
for
the
beginner
track.
Is
the
playground
exercise
I?
K
K
We
actually
spend
some
time
prepping
a
specific
channel
on
kubernetes
slack,
where
people
introduce
themselves
but
like
maybe
have
like
some
kind
of
Easter
Egg
hidden
like
the
first
person
who
finds
the
channel
on
kubernetes
slack
with
the
most
words
or
you
know
something
like
that
gets
a
prize
that
will
encourage
people
to
join
and
actually
stay
engaged
or
the
first
person
to
like
introduce
everyone
at
their
table
in
the
new
slot
right.
Something
like
that
and
do
something
similar
for
discuss.
What
was
the
other
thing
that
I
had
anyway.
K
K
D
K
Bring
my
own
if
I
from
home
people
are
like.
Why
don't
you
just
have
like
a
fake
set
up
and
I'm
like
eh,
because
it's
a
ton
of
work
B,
because
we
don't
know
what
everyone's
computers
look
like
and
see
because
that's
not
really
the
point.
The
point
is
to
work
with
kubernetes,
so
it
doesn't
really
worked
as
like
a
sandbox
solution.
I
think
we
want
our
own
network
I.
A
A
Last
minute,
comments
later
taters
for
everybody.
Dropping
I
also
have
to
drop
I've
got
a
Syrian
community
meeting,
but
y'all
can
still
chill
and
talk.
If
you
want,
please
feel
free
to
wrap
things
up.
Otherwise
it
was
awesome
event,
no
matter
the
Wi-Fi
issues.
Y'all
did
great.
You
worked
in
in
in
ambiguous
times
and
let's
rock
the
next
one,
so
much
work
loved
by
all
five.