►
From YouTube: K8s SIG Docs Meeting 20191203
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).
B
A
So
everybody
it
is
December
3rd
2019,
and
this
is
a
weekly
meeting
of
criminate
e-cig
docks.
We
are
now
being
recorded
thanks
to
Jim
angel,
really
I,
think
the
meeting
is
being
jointly
run
by
myself
and
Jim
and
Jared,
because
Jared
is
taking
notes.
Jim
is
running
the
recording
and
I'm
just
saying
the
words
until
other
people
can
be
persuaded
to
talk.
Do
we
have
any
new
contributors
with
us
this
week?.
C
A
D
And
I'll
bite
as
well.
My
name
is
Jamie
Duncan
I
was
at
Red
Hat
for
about
eight
years
and
recently
switched
over
to
VMware
and
and
looking
a
little
more
upstream.
So
instead
of
sort
of
focusing
downward,
I'm
focusing
upward
and
Doc's
are
it's
something
I've
done
a
fair
amount
of
writing
and
I
actually
enjoy
them.
So
a
little
a
little
sadism.
A
A
A
So
anyway,
welcome
or
welcome
to
both
of
you-
hey
well
just
go
quickly
through
the
updates,
a
reminder,
since
everybody
can
see
them
also
and
I,
don't
see
you
writing
on
the
call,
but
I
believe
there's
a
time.
Difference
pain
there,
so
she's
wrangling
this
week,
Jared
you're
on
deck
for
next
week.
Kids.
Thank
you
very
much
and
we
don't
have
anybody
assigned
for
the
last
two
weeks
of
the
year
for
what
I
assume
are
sort
of
obvious
reasons
and
please
check
that
PR
Wrangler
shifts.
A
E
E
B
Took
a
look
at
that
issue,
if
we
don't
have
anyone
from
the
release
team
here
president,
when
I
peeked
at
this,
it
looks
like
one
of
the
commits
for
a
master
got
merged
into
the
release
branch
and
in
part
of
that
somebody
didn't
sign
the
CLA
or
something
was
signed,
and
then
it
was
merged.
I,
don't
know
what
exactly
causes
it
but
we're
seeing
sorry
go
ahead.
B
No
problem
so
essentially
the
master
branch
was
copied
over
to
a
release
branch
as
part
of
the
release
process
and
on
Monday
they're
planning
and
cutting
the
new
release.
But
right
now
we
can't
merge
at
least
not
gracefully.
The
synchronization
between
the
branches
without
the
CLA
sign
signing
issue
resolved
that's
kind
of
the
background
that
I
caught
from
it.
A
I,
we
were
just
looking
at
this.
This
issue
with
a
117
really
and
I
have
a
vague
recollection
of
encountering
this
in
police's
past,
whether
it's
a
it's
an
artifact
broken
commit
histories.
I
might
be
having
that
wrong.
Also
Steve
I
thought
I
saw
you
on
the
call
and
I
wondered
whether
you
had
any
recollection.
A
A
It's
not
a
merge
conflict
so
much
as
there
is
at
least
one
commit
without
a
sea
of
valid
CLA
CLA
check,
and
this
just
looks
like
a
familiar
problem
when
there
wasn't
really
a
CLA
problem
from
releases
past
I.
Don't
know
that
we
need
to
necessarily
continue
to
flog
the
horse,
but
I
just
thought:
I'd
call
it
out
in
case.
There's
anybody
looting
Steve
on
the
call
who
remembers
what.
E
H
B
G
No
memory
of
this
problem,
so
I
won't
be
much
use
here.
What.
F
If,
if
the
branch
manager
or
someone
with
someone
working
on
that
like
in
the
actual
branch
itself
for
the
repo
rebase
is
all
of
those
like
makes
an
empty
commitment,
a
tree
bases
and
squashes
everything
that
I
mean
that's
a
ton
of
commits
to
squash
potentially,
but
that
will
resolve
the
conflict.
If
you
squash
all
of
the
previous
commits
into
like
a
nominal
into
an
empty,
commit
just
to
have
a
commit
space
there,
that
will
remove
the
CLE
conflicts,
but
it's
it's.
A
F
So
I
is
here
as
a
place
to
talk
about
well
to
thank
Jim
for
putting
together
the
contributor
day,
experience
for
docs
at
the
last
minute
and
doing
a
great
job
with
it.
Jim
stepped
in
when
our
original
organizer
just
had
too
much
going
on
and
saved
the
day.
So
many
thanks
to
Jim
for
setting
up
a
day
that
would
I
think
was
ultimately
pretty
successful.
We
had
been.
F
You
know,
as
as
one
does
at
these
contributor
days,
had
folks
kind
of
come
in
and
out,
but
I
think
like
Jim
pulled
off
the
first
time
that
I've
seen
this
in
multiple
years
of
coop
Kahn's,
more
people
came
in
as
the
day
went
on
and
the
like.
The
afternoon
session
was
more
well
attended
and
like
more
valuable
to
contributors
in
the
morning.
B
So
I
thought
that
was
pretty
valuable
and
I
think
there's
more
opportunities
for
that
type
of
presentation
that
type
of
kind
of
deep
dive
on
the
technical
side.
I
thought
it
was
definitely
worthwhile
and
something
it
was
spur-of-the-moment,
but
I
think
it
proved
to
be
more
valuable
than
originally
thought
even
for
myself.
So
that
worked
out
great
and
we
got
pretty
lucky
there.
In
the
early
morning
session
it
was
I
was
just
somewhere
in
the
middle
of
the
road
contributors.
B
There
was
only
one
brand
new
contributor
that
joined
us
for
the
morning
session
and
Luke
was
able
to
grab
them
and
do
a
one
on
one
training
session.
So
I
think
we
could
handle
that
a
little
bit
better
in
the
future.
If
we
do
have
somebody
that
is
brand
new
and
a
lot
of
intermediate
contributors,
there
needs
to
be
a
way
to
handle
that
dynamic
and
the
same
thing
as
if
it
were
to
be
flipped.
B
If
we
had
a
bunch
of
new
folks
to
kubernetes,
how
do
we
deal
with
the
intermediate
folks
that
are
that
are
attending?
So
overall
I
thought
it
was
a
pretty
good
success.
I
would
like
to
have
some
more
planning
involved,
but
got
the
other
cards
you're
dealt
and
I.
Think
we
had
a
very
successful
summit.
H
H
B
A
H
A
That's
okay,
yeah!
Thank
you
for
calling
it
out
anyway,
so
I
believe
it's
only
brought
on
myself
on
East
Coast
time,
but
Jim
is
only
an
hour
behind
us
right,
you're
in
Austin
yep,
so
I
think
you
know
taking
it
a
little
earlier
will
make
it
easier
to
spread
the
burden
of
running
also
because
there
was
a
bit
of
a
scramble
last.
It
was
last
week
right
Jim
when
you
said
that
you
would
run
it
and
because
I
said,
look
10
o'clock.
You
know
especially
right
before
what
turned
into
a
deranged
holiday.
B
Yeah,
no,
not
a
problem
at
all,
and
so
what
I
plan
on
doing
here
it
sounds
like
we're
all
pretty
much
in
alignment
is
I
sent
an
email
out
to
the
sig
Doc's
mailing
list
make
sure
it's
visible
for
everyone.
We
had
some
time
to
chew
on
this
for
a
little
bit
and
then
we'll
PR
that
change.
If
it
there's
no
major
objections,
perfect.
H
I
Okay,
now
Brad-
oh
thank
you
so
I
don't
know
if
it
was
about
a
month
ago,
or
so
we
had
a
team
that
built
a
new
tutorial
for
how
to
configure
kubernetes
microservice
Java
based
I
have
a
micro
profile
based,
and
they
did
it
just
like
all
the
other
four
tutorials
that
we
have.
They
built
it
all
on
cata,
Kota
and
I.
Think
we
even
gave
a
demo,
and
most
people
found
that
very
positive
and
then
one
of
the
action
items
was.
I
We
were,
as
a
group
gonna
have
a
discussion
to
think
about.
Well,
what
do
we
do
with
this?
Is
this
something
we
can
host
or
how
you
know?
How
could
the
team
move
forward
if
people
want
to
build
these
new
tutorials,
its
new
content,
that
would
bring
in
a
greater
audience
to
kubernetes
targeting
j2ee
developers,
but
we
never
really
told
the
team
how
we
move
forwards.
I
That
was
kind
of
the
discussion
like
I
said
it's,
like
all
the
other
kind
of
coda
tutorials
now
cow
Dakota
has
been
acquired
by
O'reilly
I,
assume
everybody
seen
that
I,
don't
know
how
that
affects
our
decision,
but
but
yeah.
This
was
to
try
and
get
sort
of
a
thought
process
or
an
idea
of
what
should
be
the
next
step.
With
this
type
of
tutorial,
I
mean.
Obviously
the
team
would
love
for
it
to
be
posted
with
all
the
other
tutorials
I,
don't
know
if
that's
an
option
or
not.
F
C
H
G
You
sorry
go
ahead,
I'll
post
these
links,
but
there
I
think
there
are
two
places
it
can
go.
It
can
go
in
our
Docs
under
tutorials,
kubernetes
basics.
We
could
just
add
a
module,
it
might
have
to
be.
You
know,
sort
of
ported
over
to
the
format
we
use
cuz.
There
was
some
back
in
the
day.
I
took
the
the
original
kata-kata
pages
and
did
some
you
know,
changes
on
to
make
make
them
so
they
just
fit
in
our
Docs
it
and
the
other
place.
I
suppose
it
could
go.
G
F
So
I
know
that
cata
Kota
has
a
strong
preference
to
host
in
kubernetes.
Do
so
Brad
my
concern.
My
only
concern
with
these
tutorials
is
that
we
not
run
into
the
what
we've
already
experienced
with
cata
Kota,
namely
that
we're
doing
all
of
the
infrastructure
hosting
and
they're
we're
also
doing
like
issue
triage
they're,
not
staying
on
top
of
triaging
their
own
content.
F
So
no
more,
no
more
white
elephants
if
they
want
to
host
this
content,
then
I
think
that's
great,
but
it
needs
to
be
clearly
theirs
and
if
it
does
not,
if
they
don't
maintain
it,
if
its
tail's
out
over
time,
if
we
start
getting
issues
for
it
that
aren't
addressed
stay
within
30
days,
then
it
goes
away
and
I
just
I
want
us
to
be
really
clear
about
that.
I
think.
I
I
Very
familiar
with
this
model
quick
funny
story
in
a
previous
open
source
land,
we
had
the
same
kind
of
thing
where
everybody
maintained
their
storage
drivers
and
the
person
who
was
supposed
to
maintain
it
left
IBM
and
the
bugs
went
too
long,
and
these
people
called
me
up
and
threatened
to
take
all
our
storage
drivers
out
a
tree
and
long
story
short
to
make.
That
group
that
was
the
cinder
group
and
OpenStack
happy
I
literally
gave
them
a
developer
for
a
full
year
to
make
amends
for
the
transgressions
and
my
cell
phone
number.
I
I
H
F
Sounds
reasonable
to
me,
with
the
caveat
that
I
will
be
out
at
that
time,
so
I
don't
so.
This
is
maybe
a
good
time
to
jump
ahead
to
the
wrapping
up
the
year
that
to
talk
about
vacations
and
who
will
be
who
will
be
around
in
who
won't
so
for
that
third
week
of
December
like
Jim,
do
you
will
you
be
around
yeah.
F
F
A
F
F
H
F
H
F
F
We've
been
wrangling,
all
of
the
boring
contractual
details,
in-house
and
hurting
all
of
those
cats
through
all
of
the
right
gates
has
been
a
challenge.
But
now
everyone
is
aligned,
so
I'm
going
to
reach
out
to
the
contractors
and
let
them
know
to
go
ahead
so
crossing
my
fingers
for
a
site
redesigned
by
the
end
of
the
year.
A
F
So
we're
on
track
to
pass
the
18,000
mark,
which
is
pretty
significant,
I
think
we
are
we're
the
second
in
terms
of
like
a
number
of
PRS
overall
NP
RS
per
year.
It's
kubernetes
k
kubernetes
at
the
top,
and
then
I
think
it's
a
two-way
tie
or
close
enough
between
us
and
cig
testing
for
the
volume
of
PRS
that
we
handle
per
year.
So.
F
F
A
F
I
want
to
raise
visibility
on
the
PR
Wrangler
schedule,
so
I
I
filled
when
I
created
the
schedule
for
q3
and
q4
I
added
a
slot
for
the
first
week
of
the
year,
but
that's
the
person
that
I
originally
allotted
to
it
is
misty.
Linville
and
Misty
has
moved
on
as
an
approver
and
no
longer
has
any
active
involvement
in
in
the
kubernetes.
So
we
need
to
find
a
replacement
for
that
particular
week
and
we
also
need
to
generate
the
PR
Wrangler
schedule
for
the
first
two
quarters.
F
A
B
A
A
You
know
I'm
happy
I'm,
just
not
quite
I'm,
not
quite
sure
I
mean
I'm
happy
to
make
it
a
larger
collective
effort,
I'm
just
not
quite
sure
how
much
informed
leadership
I
can
provide.
So
we
say
I
guess
the
question
that
I
have
and
we
can
finalize
an
answer
to
this
offline
too,
is
a
site
from
Misty.
Are
there
other
current
PR
Wranglers
who
should
be
taken
off
the
list
or.
A
A
F
F
A
F
Cody
Clark
I
think
I
yeah
Cody
hasn't
I
used
to
been
around
to
observe
from
time
to
time,
but
he
hasn't
actively
contributed,
PRS,
I
think
since
like
March
or
April,
so
yeah
we
need
to.
We
need
to
freshen
this
list,
but
I
know
that
Ryan
McGinnis
is
still
around
and
like
he
just
did
a
PR
shift
like
maybe
like
two
or
three
weeks
ago,
yeah.
F
A
A
A
B
Cool
one
quick
topic:
if
we're
ready
to
move
on,
go
for
it,
sorry,
just
more
I,
don't
fits
a
heads
up
or
I.
Don't
know
the
way
to
actually
phrase
this,
but
when
I
was
at
cube,
Conner
the
contributor
summit
there's
a
lot
of
intersections
from
docks
and
contributes
and
from
the
release
team
and
some
folks
doing
similar
initiatives
to
onboard
people.
And
what
does
that
process?
Look
like
I
know
contributes.
B
Has
the
non-coding
contributor
a
working
group
I
believe
it
is,
and
so,
for
example,
when
I
was
at
the
contributes
deep
dive,
they're,
currently
looking
at
like
a
markdown
linter
for
some
other
documentation
or
to
put
in
place
the
repo
and
that's
something
that
we've
been
looking
into.
A
cig
Docs
is
a
markdown
linter
and
there's
some
discussion
going
on.
It's
not
really
the
gist
of
this
conversation,
but
really
was
more
about.
I
would
like
to
work
with
some
of
the
other
chairs
and
the
other
SIG's
to
at
least
have
two-way
communications.
B
So,
as
part
of
our
meetings,
there
could
be
a
minor
contribute.
Some
data,
as
it
applies
to
Docs
or
release
or
kind
of
at
least
those
two
or
three
SIG's
that
have
some
overlap,
so
we
don't
run
into
the
situation
where
we're
all
isolated
working
on.
You
know
winters
or
closing
issues
a
certain
type
of
way,
so
I
wanted
to
open
up
the
discussion
open
it
up
here.
First
for
comments
before
just
cutting
down
people
on
slack.
F
A
Absolutely
and
I
think
that
that
that's
the
kind
of
really
focused
cross
cig
collaboration
that
can
foster
sort
of
more
Crossing
community
building
seems
like
we've,
got
to
a
point
where
there's
there's
a
certain
there's
a
there's,
an
interesting
kind
of
dance
that
I've
been
observing
between
well
contrib,
X
and
ducks,
especially,
and
that's
been
going
on
for
quite
a
while.
Now
that
dances
choreography
has
changed
slightly
just
to
continue
murdering
the
metaphor
and
I
think
that
doing
something
I
guess
that's
really
focused-
could
really
help
sort
of
keep
the
keep.
The
collaboration
flowing.
K
K
K
F
L
K
So
I
was
at
the
contributor
summit
and
Gwen
had
given
me
a
bunch
of
links
that
were
just
ripe
with
content
and
like
really
really
good
videos
and
datas
and
github
links
and
I
was
wondering
if
there's
a
way
to
distribute
some
of
this
really
good
content
on
the
blog
I
see
that
there's
like
links
for
contributors
summit,
San
Diego
scheduled,
announced
I'm,
just
wondering
if
those
like,
like
any
kind
of
a
follow
up
from
San
Diego
fur.
You.