►
From YouTube: K8s SIG Docs Meeting for 20210518
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
This
is
the
kubernetes
sig
docs
meeting
on
the
18th
of
may
2021
and
we'll
be
following
a
cncf
code
of
conduct
for
online
meetings
and
so
forth.
Everyone
be
good
to
everyone,
please,
okay,
so
do
we
have
anyone
new
on
the
call
who's?
Someone
who
hasn't
joined
a
weekly
meeting
wants
to
introduce
themselves
to
sigdocs.
B
If
so,
just
hello.
C
A
Okay,
there
is
a
google
doc
where
you
can
make
notes,
but
very
welcome.
If
you
are
on
the
kubernetes
slack,
there
is
a
channel
called
sig
docs.
I
guess
you've
seen
that
already.
C
A
I
feel
very
welcome
to
ask
questions
there
and
we
we
will
do
our
very
best
to
help
you
get
going
and
and
also
to
feel,
welcome
there
too.
Okay
on
to
updates
reminders.
Vivioni
is
this
week's
pr
wrangler?
Next
week's
is
jim
angel
and
the
usual
reminder
about
knowing
your
upcoming
shifts
is
important
and
on
to
the
next
bit
of
the
agenda
upcoming
release
I'll
hand
over
to
you,
I
believe,
ray.
E
No,
it's
great
victory.
I.
D
No
worries
so
since,
since
the
13th,
which
was
enhancement
freeze
where
we
started
to
basically
pink
enhancement
owners
right
now,
we
are
tracking
54
enhancements
with
50
with
another
one,
which
is
basically
55,
another
exception
that
was
granted
today
out
of
66.
Basically,
so
that's
that's
home.
We
have
55
55
that
need
docs.
D
For
the
time
being,
we
have
one
one
draft
pr
and
seven
that
are
ready
for
review.
That's
it.
A
It
sounds
like
you,
you
wouldn't
want
any
help
there.
You
wouldn't
need
any
help.
Is
that
fair
to
say
you're
not?
Would
you
give
a
traffic
light
color
at
this
stage.
D
I
think
we're
green.
I
wouldn't
say
that
we're
blocked
on
anything
or
have
any
issues.
The
only
problem
is,
I
didn't,
do
the
branch
sync,
so
I
don't
have.
I
can't
improve
on
on
dev
122
branch
and
I'm
gonna
take
care
of
it
by
the
end
of
the
week.
A
Next
I'll
move
on
to
issues
and
pr's
who
wants
to
talk
about
the
rename
from
masters
the
primary
branch
to
maine,
I'm
not
sure,
who's
added
this
agenda?
You
think
I.
F
Think
it
was
jim,
he
already
sent
the
broadcast
through
the
emails
and
he's
still
waiting
for
whether
we
have
any
thoughts
about
this
or
disagreement
or
comments.
A
Or
yeah,
let
me
grab
that
url
and
just
open
it
elsewhere.
A
D
Yeah,
so
for
us
I
didn't
check
all
of
the
the
scripts,
but
I
can
tell
you
that
the
only
thing
that
we
need
to
take
care
of,
at
least
for
the
dev
branch,
is
to
have
the
config.tomo
point
to
main,
instead
of
master,
how
it
is
right
now
and
I
will
check
the
rest
of
the
scripts
to
see
if
there's
anything
wrong
there.
I
wouldn't.
D
Basically
I
don't
mind
if,
if,
if
we
do
it
during
this
time,
so
there's
there's
no
objection
on
my
part
from
there.
However,
I
need
to
check
the
the
scripts
to
see
if
there's
any
major
changes
that
need
to
be
done.
D
Scripts,
yes,
the
ones
that
we
run.
I
think
I
believe
it's
the
api
reference
docs,
which
I
don't
think
that
that
is
related.
I
just
want
to
check
before
before
committing
to
to
anything,
basically
that
that's
it,
I
don't
think,
there's
any
major
there
wouldn't
be
any
major
issues
anyway,.
A
What
I
think
this
does
need
is
it
needs
a
champion
we
would
we'd
need.
I
would
benefit
a
lot
from
having
someone
who
is
going
to
take
this
piece
of
work
and
drive.
It
forward,
coordinate
help
and
so
on,
arrange
dates,
because
you
know
there
will
be
some
pieces
involved.
A
A
A
Fine,
fantastic,
even
better,
I
just
didn't,
read
it
properly,
any
any
comments
on
on
this
before
we
move
on,
I
think
it's
pretty
uncontroversial,
actually.
A
Okay,
analytics
dashboard
pr,
I'm
guessing
abigail.
You
want
to
talk
about
this.
G
Yes,
that
was
from
me,
so
I
opened
this
up
at
the
end
of
last
week.
I
just
wanted
to
raise
it
if
people
had
time
to
review
and
give
any
thoughts
yeah
it's.
G
Basically
what
we've
been
talking
about
a
link,
it's
a
new
page
added
into
the
contributing
section
of
the
kubernetes
site
and
I'll
link
out
to
the
dashboard
that
people
can
see
see
the
analytics
if
people
have
a
better
place,
a
better
idea
of
where
they
should
live
instead
of
on
the
site,
let
me
know
otherwise
you
know
that's
the
latest
of
that
project.
A
So
I
see
you've
marked
this
as
hell.
I
I
don't
see
the
need
to
hold
this
up
like
the
normal
review
process
applies,
but
nothing
more.
Are
you
happy
to
to
unhold
it.
G
I
can,
I
think,
that's
from,
I
think,
did
karen
add
that
label.
I
didn't
add
that
later,
I'm
not
sure
what
that
label
is.
Oh.
A
Yeah,
sorry,
yes,
it
was
karen,
as
I've
had
in
lg
team.
Already
I'm
gonna
unhold
it
okay.
G
I
should
probably
post
a
link
to
this
in
the
localization.
They
have
a
separate
chat
right
in
the
slack
they
have
a
separate
channel
since
they
were
the
requested.
A
Cool
the
way
I
see
it
this
this
is
ready
to
review
and
and
let's
get
reviewing,
I'm
gonna
move
on
anything
more
on
analytics
before
I
do.
A
Cool:
let's
carry
on
a
discussion
from
last
week
about
reference
docs,
which
was
me
and
and
jim
my
view
is
that
sig
talks
as
a
group
should
focus
on
you
know
as
a
as
a
longer
term
task
on
reducing
the
toilet
around
publishing
reference
docs.
I
guess
that's
still
my
view,
I'm
not
sure
anyone's
going
to
object,
but
I'd
like
to
hear
from
people.
E
It's
it's
been
a
little
bit
of
a
speed
bump,
slash
hurdle
to
generate
the
the
reference
stocks,
just
because
it's
there's
tasks
of
knowledge
that
there
that
isn't
that
wasn't
passed
on
or
that
needs
to
be
passed
on
in
terms
of
generating
the
reference
stocks
as
the
the
past
few,
including
myself,
and
no
anna's
on
the
call
as
well,
that
we've
had
issues
generating
the
reference
stocks
and
I'll
just
be
helpful
to
have
a
like
a
better
guide.
E
A
E
A
Okay,
I
think
that's
that's
something
that
we
could
could
reasonably
suggest
and
make
possible
so
there's
a
container
image
either
it's
published
it's
not
a
secret
or
you
build
it
locally,
and
that
provides
the
mechanism
that
you
can
use
today
and
generate
docs.
A
D
I
mean
given
that
I'm
the
docslead,
it
would
benefit
me
a
lot
to
to
fix
this
before
I
actually
have
to
run
it.
So
I
could.
I
could
pick
it
up.
A
Cool
well
victor,
do
you
feel
able
to
log
that
issue
and
to
kick
things
off
start
the
ball
rolling,
yep
cracking
leave
that
with
you
then
yeah.
It
is
mainly
around
the
generation,
but
there's
also
pieces
of
work
around.
We
eventually
want
to
deprecate
the
or
we
have
kind
of
deprecated.
We
want
to
move
away
from
the
single
page,
api
reference
we
have
now-
and
I
guess,
there's
some
pieces
of
work
that
related
to
this
that
aren't
in
that
issue.
A
A
I
guess
really
that
the
people
who
are
chairs
and
and
tech
leads
if
he
included
and
the
others
not
on
today's
call.
A
We
are
really
keen
to
provide
mentoring,
provide
what
it
takes
to
help
people
become
more
of
a
contributor.
A
Now
that
can
be,
you
are
literally
brand
new
you've
never
contributed,
and
you
want
help
one
of
the
things
that
a
chair
or
a
tech
leader
or
someone
else
will
will
will
do,
will
benefit
signal
by
doing
is
by
helping
new
contributors,
so
that
kind
of
onboarding
help
guidance
coaching.
It's
a
really
valid
way
to
a
really
valuable
way
to
contribute
to
kubernetes,
and
I
just
want
to
make
it
make
it
clear
that
whatever
the
stage
in
your
sort
of
contributed
journey,
that's
something
that
that
chairs
and
leads
we're
really.
A
You
know
focusing
on
keen
to
to
make
that
available
and
make
it
clear
that
we're
we're
here
to
help
if
anyone
wants
to
find
us
on
slack,
send
send
direct
messages.
If
you
want
or
ask
in
public
either's
fine,
you
don't
have
to
hold
your
hand
up
in
public
and
say
I
want
help
if
you
don't
want
to,
but
we're
here
any
questions.
A
Cool
moving
on
to
the
cubicle
docs,
I
don't
think
we've
got
eddie
who
joined
last
week's
call,
so
we
won't
be
able
to
talk
about
that.
Eddie
is
from
the
six
cli
group
and
we're
working.
We
have
a
piece
of
work
around
merging
the
cli
docs
handbook,
the
cli
handbook,
the
cooperative
handbook,
sorry
and
the
main
documentation.
A
But
yeah,
so
I'm
not
gonna
talk
much
more
about
that
and
victor.
Let's
talk
about
feature
gate
stock
generation
from
source
code.
D
Yeah,
so
about
this
we
missed
a
lot
of
them
and
really
you
you
can't
blame
anyone,
because
they're
a
bit
hard
to
find
when
they
they're
they.
Basically
when
they
change.
So
you
need
to
really
navigate
when
you
get
assigned
as
a
shadow
or
or
as
a
docs
lead.
You
need
to
navigate
the
cap
and
check
out
what
the
feature
gate
itself
is
and
if
it
gets
promoted
and
so
on.
D
Currently
there's
all
of
this.
All
of
this
resides
in
cube,
underscore
features,
dot
go
as
I
think
someone
mentioned.
Let
me
actually
show
you
this
pasta
link
here
with
the
issue,
and
I
would
I
would
like
to
work
on
this
because
now
I
have
to
for
for
all
the
shadows
or
I
have
to
double
check
and
see.
D
If
something
happened,
I
guess,
if
a
feature
gate
changed
and
and
make
sure
that
the
documentation
really
reflects
that
it's
a
bit
hard
to
to
have
to
explain
to
everyone:
hey
you
need
to
go
to
the
cap,
and
then
you
need
to
read
the
cabin
and
see
the
feature,
gate
and
check
out
the
the
latest
changes
to
the
cap
to
see
if
it
was
promoted
and
so
on.
So
it's
a
bit
hard
to
to
explain
that
to
everyone
continuously
and
after
I
leave
someone
else
will
come
and
it
will
be
the
same
problem.
A
I
I
have
a
branch
where
I'm
working
on
this
and
actually.
C
A
Someone
had
said
I
wanna
put
my
hand
up,
and
you
know
I've
gotta
give
me
a
project.
I
said
great.
I've
got
some
starting
points
for
you,
here's
the
thing.
Would
you
like
to
help
move
it
forward?
So
I'm
going
to
take
that
as
you'd
like
to
move
that
forward.
D
Yes,
yes
very
much,
but
my
question
is:
how
would
you
like
to
do
it
because
I,
from
what
they
see
in
in
k
website,
most
of
the
scripts
are
python
based
and
the
way
that
I
see
this?
Maybe
it
would
be
easier
to
do
it
in
in
go
somehow,
but
at
the
same
time
you
would
always
need
to
because
this
way
you
just
pull
in
this,
this
cube
feature
file,
and
then
you
you
import
it
basically.
D
So
that's
kind
of
all
you
need
to
do
and
you
can
just
generate
the
yaml
file
or
whatever
from
it.
I
don't
know
how
you
could
do
that
in
in
python.
You
would
probably
need
to
parse
the
file
or
keep
it
separate.
I'm
not
sure.
A
I
don't
really
mind
what
language
is
used
to
generate
the
ammo
file.
I
actually
haven't
worked
on
that
bit.
I've
worked
on
the
templating
to
to
turn
the
yaml
file
into
you,
know,
markdown
and
eventually
rendered
html.
A
So
sure
that
sounds
like
a
good
compliment
like
that
can
split
by
the
way.
If
one
person
wants
to
work
on
the
generation
tool
and
another
person
wants
to
work
on
the
templating
and
generation
from
yaml
of
the
page,
that
can
be
two
people,
so
there's
room
for
collaboration
here.
If
anyone's
interested.
A
D
Sure
I
would
ask
you
also
to
please
share
what
what
you've
done
when,
whenever
you
have
the
time.
A
Yeah
yeah,
it's
it's,
it's
pretty
early
work,
but
I
will
share
push
a
draft
pr
and
share
it
with
you.
Victor
absolutely
I'll
mention
that
in
the
minutes
too,
thanks.
A
H
I
I
have
a
quick
question.
There
was.
H
Last
week
about
scheduling,
preemption
and
eviction,
and
it
moved
into
slack
and
I
wanted
to
join
in,
but
if
it
looks
like
it's
about
to
wrap
up,
I
don't
want
to
like
stop
the
flow
if
it's
ready
to
go,
but
I
I
do
have
some
things
I'd
like
to
maybe
contribute
there.
So
is
it
your
impression
it's
about
ready
to
publish-
or
you
know,
or
is
it
okay
to
still
contribute
there?
H
H
Okay,
well
well
I'll
jump
in
then.
If,
if
there's
nobody,
if
nobody
thinks
it's,
you
know
if
it's
about
to
publish,
I
don't
like
to
stop
things
that
you
know
everybody's
in
agreement
on
so
but
otherwise,
then
I
will
try
to
go
contribute
I
mean
I
would.
A
I
would,
I
think
I
try
to
do
where
I
can
and
I
think
I'd
speak
for
a
few
of
the
the
other
leads
as
well.
For
the,
for
the
sake
is
I'll,
do
a
review
and
I'll
say:
okay,
here's
some
feedback.
This
is
not.
This
comma
is
in
the
wrong
place
and
here's
some
some
more
feedback.
A
We
actually
write
configmat
with
capital,
c
capital
m
lgtm,
because
it's
good
enough,
so
you
get
an
lgtm
and
things
can
move
forward
and
sometimes
I'll
actually
do
lgtm
approve,
because
I'm
improv,
I'm
an
approver
and
then
hold
and
I'll
say
to
the
the
person
whose
code
it
is
I'll
say.
Your
contribution
is
good
enough
to
merge.
A
You
can
decide
whether
you
unhold
it
in
which
case
they
unhold
it
and
it
merges
or
if
they
really
like
the
idea
of
that
feedback,
and
they
actually
think.
Oh,
my
gosh,
I
wish
I'd
put
that
comma
in
it
changes
the
whole
sentence
sense
of
the
sentence.
Then
they
can
do
that
and
it'll
go
through
another
cycle,
so
that
approving
with
feedback
review
is
the
kind
that
I
want
to
promote
and
favor.
A
And
if
that
fits,
what
you
want
to
do,
chris,
I
think
that
that's
going
to
be
really
good,
like
give
it
an
informal
or
a
formal
lgtm.
At
the
same
time,
as
you
say,
and
by
the
way
I've
spotted
these
things.
A
Cool
I'll
put
a
note
in
about
that
in
the
discussion.
Let's
see,
what's
in
the
chat,
okay,
nothing!
Nothing
super
exciting!
I
will
just
put
that
note
in
our
forget
it.
Otherwise,
sorry.
A
Cool
any
more
discussion,
any
anyone
got
another
thing.
They
want
to
talk
about,
bring
up
right
now.
Any
questions.
A
Okay,
no
not
hearing
any
questions
right
now.
If
you
do
have
anything
that
you
want
to
talk
about
later,
find
us
in
in
slack
on
the
signox
channel
and
and
ask
gonna
count
you
down
five
four,
three,
two
one:
that's
a
sig
meeting
folks,
thanks!
Very
much
bye
cheers.