►
From YouTube: Kubernetes SIG Docs Update Meeting 20190702
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
B
Well,
I'm
actually
just
kind
of
starting
off
on
my
kubernetes
learning
path,
so
obviously
that
entails
going
through
a
whole
bunch
of
documentation
and
blog
posts
and
all
kinds
of
stuff
like
that
and
trying
things
out
so
as
I've
been
trying
things
out
and
notice,
various
things
that
didn't
work
or
things
that
didn't
quite
fit
I've
been
going
and
trying
to
contribute
to
the
documentation
and
stuff
like
that.
So
that's
how
I
kind
of
got
involved,
and
hopefully
I
can
continue
to
do
that
kind
of
contribution
and
and
clean
some
stuff
up.
Awesome
well,.
A
B
A
C
Hi
Renee
yeah
I'm
new
to
this
one
and
I
I
got
the
details
from
Pat
and
I
got
this
meeting
in
red
too
I'm
looking
forward
to
contribute
more
to
this
committee,
especially
to
the
RAM
here
and
I
am
start,
and
today
a
beginner
level
at
the
Covenant.
It
also
but
I
hope
I
will
be
able
to
learn
and
be
able
to
contribute
back
to
the
community.
Awesome.
A
A
A
Yes,
sorry,
PR
English,
the
PR
regular
schedule
for
q3
q4
is
up.
Please
if
you
were
an
approver.
Please
take
a
look
at
that
schedule
and
if
that
does
not
look
correct
to
you
or
if
you
see
some
sort
of
schedule,
conflict
like
now
is
the
time
to
fix
that
now,
like
early
is
better
than
trying
to
do
it
last
minute,
so
please
go
over
and
take
a
look.
A
Caitlin
was
our
PR
Wrangler.
Last
week,
Thank
You
Caitlin
are
PR
regular.
This
week
is
Coty
Clarke
and
our
regular
for
next
week
is
Zack.
Arnold
and
I'm
gonna
put
a
footnote
there
to
talk
about
our
PR
q
when
we
get
there
so
I
announced
this
last
week,
but
I
also
want
to
boost
visibility
on
it,
I'm
happy
to
say
that
Jim
angel
is
shadowing
for
the
role
of
Doc's
chair.
Everybody
would
like
if
you've
worked
on
any
of
the
past
three
releases.
A
You've
worked
with
Jim
in
some
capacity
and
Jim
is
awesome
folks,
and
he
is
yeah
he's
coming
up
in
the
world,
and
so
we
are
not
really
teaching
him.
So
much
is
just
showing
him
what
he
can
already
do
to
be
a
chair.
So
please
congratulate
working
dull
or
and
support
him
as
he
grows
into
this
new
role
and
if
you
are
interested
in
being
a
chair
as
well,
that's
let
one
of
us
know
that
myself
or
Jennifer
or
Jarrod,
but
he
gets
back
from
sabbatical
and
if
that's
something
that
you're
interested
in
as
well.
A
That's
that's
a
conversation
we
can
have
okay.
So
our
cue
to
review
and
q3
planning
meeting
is
on
Thursday
July
25th
and
we've
scheduled
that
from
5:00
to
8:00
p.m.
Pacific
time.
I
know
that
it's
not
a
perfect
time
for
everyone.
There
is
literally
we
have
a
global
saying.
There
is
a
little
literally
no
perfect
time
when
we
can
have
everyone
there.
So
if
that
time
doesn't
work,
I'm
sorry.
A
A
A
So
I
want
to
ask
folks
to
start
thinking
about
what
are
the
things
that
you
would
like
to
see
better
in
documentation
in
q3.
What
are
the
things
that
we
can
meaningfully
do?
What
are
the
things
that
we
can
accomplish
so
start
thinking
about
that
about
what
you'd
like
to
see
better
in
q3
for
Docs
and
be
prepared
to
discuss
that
in
our
q3
planning
meeting,
and
that
also
reminds
me.
A
Sorry
one
second:
this
is
the
the
joy
of
a
life
of
a
DD
awesome.
J
I,
see
that
you
have
got
you've
already
put
down
one
specific
proposal:
I
just
dropped
a
link
to
a
Google
Doc
in
the
agenda
and
that
should
be
open
to
everyone.
But
that's
doc
is
the
placeholder
sort
of
the
shell
for
our
agenda
for
the
q3
planning
meeting.
So
if
you
have
proposals
that
you'd
like
to
make
I'd
ask
that
you
drop
them
in
that
Docs
so
that
we
can
aggregate
them
all
in
one
place.
E
A
So
of
the
three
pieces
left
to
do
be
the
top
top
level
controllers
concept
guide.
I
know
that
we
have
one
PR
open
for
that
from
a
septum,
a
KA
Tim
banister
and
the
last
update
I
saw
from
Tim
was
about
two
weeks
ago.
Waiting
for
the
1.15
released
a
drop,
so
I
left
to
know
for
them.
Hey
Brad
can
I
ask
you
to
you.
Please.
A
A
The
other
piece
update
deployment
concept
topic
shabih
has
a
PR
open
to
update
some
deployment
information.
It
would
be
awesome
if
we
could
get
that
merged.
I
think
there's
more
to
do
there,
but
we've
got
some
solid
work
that
just
needs
review
and
when
I
say
we
that
it
needs
review,
I
need
to
go
review
it.
So
this
is
my
call
to
accountability.
I
will
go
review
that
today,
so
the
other
piece,
that's
still
kind
of
outstanding,
is
Q
baby
and
ox
Jennifer.
Do
you
want
to
talk
about
human
DM
ducks.
D
D
D
B
F
Just
wanted
to
comment
from
my
personal
experience
using
a
cube
ATM
and
have
a
high
interest
in
the
cluster
API
project.
Speaking
as
a
consumer
of
kubernetes
and
enterprise,
we
don't
have
any
plans
of
abandoning
cube
ATM
in
the
near
future.
Cluster
API
just
way
to
alpha
right
now,
it's
really
exciting
what
they're
doing
it's
really
cool
and
it
seems
like
the
community
is
really
shifting
focused
in
that
direction,
but
as
far
as
the
short
term,
without
alpha
that
is
I,
don't
see
it
being
widespread,
but
I
don't
want
to
be.
F
D
Maybe
I
don't
have
to
do
so
much
homework
if
cluster
API
last
I
knew,
which
is
really
probably
cluster
AP
I
was
very
alpha,
sounds
like
it's
still
very
alpha
from
a
user
perspective.
It's
still
the
entry
point
that
we
want
to
help
people
with,
and
so
that
is
in
fact
the
right
place
to
focus
our
energy
and
attention,
and
it
can
only
have
stabilized
further
in
the
intervening
six
months
so.
E
Yeah
and
it's
add
to
that
I
think
it's
fair
to
say,
yeah
I,
don't
think
the
cluster
API
has
stabilized.
Is
that
the
other
folks
impression
that
I'm
watching
it
seems
like
from
the
meetings
I
was
at?
It
was
still
kind
of
in
flux,
I,
don't
know
if
everybody
else
Jim,
if
you
got
that
impression
or
not
I
also.
B
D
F
It
sounds
like
kind,
is
more
for
CI
for
kubernetes,
so
there's
no
real
intent
for
the
end-user
to
run
it
there's
a
lot
of
value
there,
but
really
it's
a
lot
of
testing
and
moving
fast
for
our
infrastructure,
really
quick
ways
to
test.
If
you're
doing
your
own
CI,
you
could
use
kind,
but
you're
not
really
building
net
new
clusters
with
kind
that
still
seems
to
be
cube,
ATM
so
to
thumbs-up
on
continuing
cube,
ATM
docs.
D
A
A
A
But
then,
as
we
moved
through-
and
this
still
looks,
pretty
good
I
mean
who
steals
like
two
weeks
for
the
first
40,
but
then
from
40
to
60,
I
start
seeing
this
spike
to
where
we're
getting
close
to
a
month
old
and
then
even
older
than
that
back
to
the
middle
of
May,
and
some
of
these
some
of
these
things
I,
like
you,
know,
I,
look
here
at
14
for
29,
there's
no
CLA
agreement
attached.
So
you
know
the
folks
who
are
wrangling.
A
If
you
see
somebody,
if
you
see
excuse
me,
if
you
see
an
open
PR
after
like
a
week
with
no
CLA
assigned,
please
feel
free
to
close
it
and
like
remind
the
person,
hey
feel
free
to
reopen
this
as
soon
as
you're
willing
to
to
sign
the
the
CLA
but
there's
yeah.
There's,
there's
really
no
good
reason
for
no
CLA
PR
to
be
open.
A
This
long-
and
you
know
things
like
14
3:30
without
looking
at
it,
I
don't
know,
what's
going
on
same
for
14
331,
but
if
you're,
if
it's
just
that
they're
getting
feedback
and
then
not
implementing
it
also,
please
feel
free
to
close
these
PRS
again
with
a
gentle
reminder.
Hey
feel
free
to
reopen
this
as
soon
as
you're
going
to
respond
to
the
feedback.
D
A
And
then
we
sort
of
get
down
to
I,
don't
I,
don't
know
what
to
gracefully
call
it.
When
we
get
down
to
like
the
problematic
stuff
we
get
down
to
the
to
the
the
you
know
like
the
last
10
or
so
PRS
that
are
difficult
to
wrangle,
for
whatever
reason,
so
these
aren't
always
closeable
for
various
set
of
reasons.
A
But
if
we
can
close
PRS
I
would
ask
that
we
do
so
because
our
total
is
pushing
up
to
we've
got
a
hundred
and
ninety
eight
pull
requests
open
right
now
and
that's
a
little
high
I
would
like
to
see
us
again.
You
know
with
knowing
that,
like
40
of
our
PRS
are
open
in
the
last
two
weeks,
I'm
not
that
concerned,
but
I
would
like
us
to
get
that
number
down
to
a
more
reasonable
level.
I.
G
E
E
E
If
this
is
the
right
time
sure
yeah
go
for
it?
It
went
very,
very
well.
So
what
we
did
again,
I
I
did
a
little
bit
of
what
I'd
call
death
or
glory,
because
I
really
really
needed
a
vacation,
but
at
the
same
time
I
really
needed
to
have
some
content
available
and
thank
goodness
for
VPNs,
because
I
was
able
to
get
there
on
Sunday
and
get
a
nice
chart
done.
Chart
deck
done
with
a
lot
of
visuals
and
really
was
great
about
translating
it.
E
So
we
had
a
full
day
there
on
Sunday
to
get
really
well
prepared
with
the
content
that
people
could
take
away
in
both
English
and
Chinese,
and
so
what
I
end
up
doing
is
we
I
did
present
the
new
contributors
workshop,
which
went
very
very
well,
and
then
we
used
the
same
content
with
more
content
for
the
deep
dive,
and
we
had
a
lot
of
folks
that
we
had
a
couple
folks
from
the
Indonesian
translation
team,
which
was
wonderful.
They
had
a
lot
of
questions
really
great.
E
You
know
they
had
a
lot
of
questions
and
then
we
had
the
China
team
there,
which
had
all
the
experience
in
the
world
for
the
same
types
of
questions.
So
that's
what
I
noticed
is
you
know.
We've
got
a
lot
of
knowledge
there
of
well,
you
know
how
do
you
handle
you
translate
a
page,
and
then
you
know
what?
E
If
how
do
you
know
when
it
changes,
for
example,
and
we
are
seeing
a
little
bit
of
I
guess
the
Korean
team
built
their
own
kind
of
tooling
for
that
and
the
Chinese
thing
that
they're
a
little
chewing.
So
we
have
to
watch
that,
and
maybe
maybe
perhaps
when
I
suggested,
that
maybe
one
of
the
teams
honestly
submit
pull
requests
to
actually
make
that
part
of
what
we
have
available
into
our
scripts
folder
yeah.
That
would
be
a
good
idea
just
so.
E
How
many
folks
showed
up?
Do
you
think
for
the
the
deep
dive
more
than
I
thought?
You
know
we
had
to
sort
of
circle
tables
were
so
it
seemed
like
total.
We
had
about
18
people,
20
people,
and
we
used
her
time
wisely.
We
did
a
lot
of
the
intro
stuff
and
then
got
sat
down
and
covered
a
lot
of
whatever
the
Indonesian
team
needed
or
the
Chinese
who
needed
we
made
the
most
for
time.
A
D
A
B
B
E
E
The
reason
in
dots
we
have
a
nice
culture
because
we
typically
something's
a
little
on
the
complex
side.
We
do
both
a
technical
review
and
obviously
that
the
doc
style
type
review
so
we're
typically
very
comfortable
at
reaching
out
to
the
difference
to
communities
and
asking
for
that
review.
So
I
know
from
our
culture
and
exacting,
you
know,
add
to
that
we're
very
comfortable
going
to
the
SIG's.
Now
we
have,
we
have
a
couple
people
in
each
sig.
We
find
them.
E
A
A
C
A
Recycled
PR
reviews,
or
something
like
that,
and
if
you
add
mentioned
that
PR
review
alias
for
that
team
into
into
a
comment
on
a
particular
PR
teams,
are
usually
really
good
about
getting
folks
on
to
that
within.
Like
I,
don't
think
I've
had
anybody
like
unless
I
did
it
on
a
Friday
afternoon,
usually
doesn't
take
more
than
24
hours
to
get
it
mentioned
or
together
to
get
eyes
on.
B
A
A
A
All
right,
Simon,
Forester,
I
notice,
you
were
with
us
and
I,
wanted
to
follow
up
from
a
discussion
two
weeks
ago,
Simon
you
had
mentioned.
Tell
me:
if
I'm
remembering
this
correctly,
you
had
had
the
idea
of
putting
together
a
review,
a
review
pool
for
internationalization
questions
in
English.
Did
you
did
you
want
to
follow
up
on
that?
Do
you
want
to
say
any
more
about
that.
G
A
A
We
have
a
like
a
fair
number
of
of
our
localization
teams
are
also
highly
fluent
in
English.
So
that's
that
kind
of
a
kind
of
a
demand
is
usually
met
within
the
team
itself,
but
I
would
absolutely
encourage
you
Simon.
If
you
see
opportunities
to
step
in
and
and
like
contribute
clarity
to
any
of
the
discussions
that
you
see,
don't
wait
for
permission.
A
A
H
You
know
the
bullet
points
under
that
list
and
was
wondering
if
at
some
point
we
may
want
to
put
in
not
a
requirement,
but
just
maybe
mention
a
suggestion
once
you
know,
if
we
can
figure
out
a
tool
to
use
and
say
hey
if
you
update
a
page
that
has
links
on
it,
maybe
run
this
thing
and
check
it
out.
You
know
to
at
least
kind
of
get
ahead
of
that
before
we
figure
out
what
automating
that
process
looks
like.
A
This
it's
one
thing
to
ask
folks
to
like
check
their
links,
but
because
we
run
the
spectrum
of
technical
knowledge
and
technical
comfort
with
like
we
have
folks
were
like
oh
yeah,
I
run
my
own,
like
I've,
got
my
only
check,
whereas
a
cron
job
at
the
background
of
vo2,
like
people
go.
What's
a
link
checker,
so
I
think
the
more
specific
that
we
can
be
with
those
kinds
of
recommendations
for
quality,
the
better
off
that
our
source
is
going
to
be
so
yeah
I.
Think
that's
a
great
idea
set
awesome.
H
A
A
We
had
someone
report
that
they
were
having
difficulty
running,
that
hugo
locally,
with
the
commands
that
we
offer
and
my
initial
admittedly
on
charitable
impulses.
I
it's
just
somebody
who
hasn't
got
set
up
right.
Well,
then,
I
I
called
refreshed
and
I
tried
to
run
it
locally.
It's
not
working
for
me
either.
A
A
F
A
quick
comment
on
the
link
checker
if
I'm
not
mistaken,
link
checkers
are
more
for
validity
and
in
this
case
it's
a
resource
that
is
external
when
you're
running
it
locally
without
internet.
So
almost
beyond
a
link
checker,
maybe
a
link,
checker
plus
or
extended,
would
be
a
link,
checker
and
then
also
a
external
resource
checker.
If
we
did
care
about
maintaining
this,
the
ability
to
run
the
site,
offline,
I'm.
H
H
B
F
H
A
A
A
B
B
So
a
lot
of
this
issue
is
obviously
going
to
be
around
the
integration
of
all
of
the
end-to-end
testing
and
upstream
testing
stuff
and
that
uses
the
cluster
set
up
scripts
cube
up
and
that
kind
of
stuff.
However,
there
is
a
good
chunk
of
work
that
needs
to
be
done
to
remove
references
within
the
documentation
itself
to
those
scripts
and
things
like
you
know,
logging,
configuration
and
stuff
like
that
from
from
the
docs
itself.
B
So
I've
already
started
on
some
of
the
logging
extraction.
There
is
a
list
of
pull
requests
in
in
that
issue,
but
there
are
plenty
of
other
places
that
reference
various
links
into
the
cluster
scripts
and
that
kind
of
thing.
So
the
idea
from
Tim
Sinclair
is
obviously
long
term.
We
want
to
just
get
rid
of
the
cluster
directory
entirely
and
so
the
two
main
pieces
there
are
getting
rid
of
the
integration
with
various
testing
pieces
and
then
anything
that
references
it
in
the
documentation.
B
B
I'm
just
saying
that
so
Tim
Hakan
mentioned
on
I
think
it
was
the
kubernetes
dev
mailing
lists.
Maybe
two
months
ago
it
was
like
right
before
coop
con
Barcelona
mentioned
cleaning
up
a
bunch
of
stuff
in
the
cluster
directory
and
the
hack
directory
for
backlinks
sort
of
random
bash
scripts
that
have
kind
of
accumulated
over
the
years
and
Tim
created
this
issue
to
kind
of
track.
All
that
kind
of
work.
What's.