►
From YouTube: K8S SIG Docs Meeting for 20220405
Description
For more info see https://git.k8s.io/community/sig-docs
A
A
A
A
Alrighty,
if
any
new
contributors,
if
we,
if
they
if
they
come
online-
and
we
want
to
say
hello
or
feel
free
to
jump
in
the
chat
as
well-
that's
also
completely
fine
thanks
so
much
for
introducing
yourself
analog
and
we
will
get
on
with
the
rest
of
the
agenda.
So,
firstly,
what
I
wanted
to
do
is
go
into
some
of
the
reminders
that
we
have
just
I'm,
also
taking
notes
at
the
same
time
trying
to
multitask
so
for
in
terms
of
PR
Wranglers.
A
We've
got
a
brad
who's,
our
PR
Wrangler
for
this
week
and
for
next
week
team
is
going
to
be
our
PR
Wrangler
for
all
Wranglers
who
are
on
the
call
and
who
are
listening
to
the
recording.
After
the
fact,
please
check
the
pr
Wrangler
shifts.
We
have
recently
updated
that
I
will
get
into
that
in
the
discussion
points
later
on,
but
approve
is
make
sure
you
know
your
scheduled
Wrangler
shifts.
So
thanks
so.
D
A
A
C
Everyone
week,
13
docs,
ready
for
review
day
is
today
and
I
think
we
are
once
they
were
quite
green,
but
we're
a
very
greenish
sort
of
yellow
for
the
for
the
for
the
release
for
the
docs
section.
All
the
numbers
here
are
very
much
in
flux.
Today,
we've
still
got
two:
they
don't
have
a
PR
placeholder
we're
four
with
a
draft
PR
and
then
12
ready
for
review,
which
is
great.
C
C
We
are
I
think
in
a
good
spot.
We've
got
quite
a
few
ready
for
review
in
that
as
well
and
there's
nothing
that
has
been
there's
only
a
couple
of
things
that
are
currently
unassigned
and
I.
Don't
think
that
those
will
be
assigned-
and
there
is
nothing
in
the
unassigned
OR
currently
assigned,
but
without
a
PR
that
is
a
a
blocker
for
the
release.
C
C
A
Great
thanks
so
much
Nate
I've,
just
added
that
update
in
there
too,
but
yeah
there's
a
lot
of
chatter
around
in
in
the
a
Deadman
list,
as
well
as
slack
so
that
folks
can
keep
abreast
of
that
that
ongoing
issue,
but
yeah,
hopefully
not
too
many
days
in
terms
of
a
delay.
So
thank
you
so
much
for
that
update
great
with
that
being
said,
I
love
the
description
by
the
way
of
greenish,
yellow
I.
A
B
Hi,
everybody
so
timid
flagged
this
a
few
weeks
back
and
it
was
a
problem
with
some
of
the
mermaid
diagrams
experience.
The
syntax
failure
when
they
were
rendered
with
Firefox,
did
a
little
bit
of
digging
into
this
and
I
think
further
down
in
the
issues
right
up.
What
were
my
conclusions
at
this
point
in
time?
I'm
not
sure
how
to
move
forward
with
next
steps.
I
figured.
B
B
B
D
D
D
Oh
thanks:
Christopher,
that's
really
appreciated
and
I
think
I'm
subscribed
to
the
issue.
So
if
you
update
that
to
say,
if
that
didn't
help,
I'll
see
that
and
I'll
try
and
take
a
look.
Okay,
a
little
bit
short
of
copious
free
time
at
the
moment.
But
it's
it's
something
that
that
I
think
is
important
and
I
use
Firefox
as
my
daily
driving
browser
as
well.
D
A
A
Also
worth
pointing
out
that
you
know
we
as
Sig
docs
in
terms
of
General
third
party,
anything
try
to
be
as
neutral
as
possible,
so
purposely
saying
please
use
Chrome
could
mean
that
we're
preferencing
that,
as
opposed
to
trying
to
troubleshoot
the
issue,
so
I
think
it's
yeah.
A
team
suggestions
that
are
really
great
and
worthwhile
I
would
also
say
as
well.
B
A
B
A
A
Never
it's
never
a
bad
idea
to
be
transparent
when
we
have
found
bugs
and
things
that
we
need
to
fix
either
so
I,
don't
think
we
need
to
announce
it
all
from
the
from
every
Hill
and
every
and
every
every
pathway,
but
at
the
same
time
I,
don't
think
I,
don't
think,
hiding
it
or
purposely
trying
to
hide
it.
That
way
is
a
good
idea
either.
B
A
A
Great
thanks,
Chris,
and
thanks
also
for
kind
of
taking
the
lead
in
troubleshooting.
This,
like
you
mentioned
it
may
not
be
an
issue
to
that
many
people,
but
we
want
to
make
sure
that
that
our
docs
and
our
diagrams
are
actually
working
for
everyone
in
all
kind
of
use
cases.
So
that's
that's
really
great
that
you're
taking
this
on.
A
F
A
Great
thanks,
thank
you.
Ray
I
know,
we've
got
we've
you've
actually
done
two,
a
PR
regular
shift
scenario.
So
really
appreciate
that
you,
you
did
a
lot
of
lab
work
on
the
on
the
reviews
there
for
folks
who
are
reviewers
or
previous
on
the
call
jumping
into
those
PR
so
that
we
can
get.
The
second
review
would
be
really
great.
D
The
lgtm
thing
I
want
to
say
that
there's
two
different
potential
causes
for
having
lots
of
things:
LGT
I'm
waiting
for
approval,
one
of
them's
good
one
of
them
is
bad.
The
the
the
sort
of
the
bad
story
is
that
people
who
are
approvers
and
who
are
possibly
like
a
chair
of
the
Sig
at
doing
all
the
reviews-
and
that's
probably
the
case
that
we're
in
and
that's
kind
of
a
bit
bad
because
it
concentrates
the
reviewing
in
in
if
it
means
that
the
reviewing
is
too
concentrated
and
I.
D
Think
that's
the
the
case.
But
there
is
another
case
where
we
have
kind
of
the
same
large
number
of
things
that
are
lgtm
and
that's
okay,
and
that
can
happen
where
there
are
lots
of
people,
doing.
Reviews
who
aren't
approvers
and
it's
okay
to
be
a
become
a
reviewer
and
not
have
moved
up
to
being
an
approver
yet
or
to
say
I'm
happy
to
review.
D
But
I
don't
want
to
be
on
the
pr
Wrangler
schedule
and
if
people
who
are
doing
that
are
doing
lots
of
reviews-
and
it
creates
a
bit
of
a
bottleneck
for
the
approvers.
That's
good
because
we're
kind
of
it's
kind
of
the
right
thing
we
want
that
there
are
plenty
of
people,
doing
reviews
and
approvers
come
along
and
go
yeah.
Everything
all
looks
good
I,
see
no
reason
not
to
approve
this
put
the
stamp
on
slash
approve,
that's
kind
of
an
efficient
use
of
approval
time.
A
Yeah
absolutely
agree:
I've
also
just
put
that
note
in
the
agenda
that
when
we,
when
we
share
that
also
in
the
channel
to
kind
of
emphasize
that
it
can
be
folks
that
don't
have
reviewer
status,
if
you
want
feel
free
to
put
on
an
unofficial
look
good
looks
good
to
me.
Any
help
appreciated
to
kind
of
get
that
moving
so
that
it
isn't
in
that
concentrated
group
of
realism,
approvers.
So
that's
a
great
call
out
thanks,
Tim.
C
A
A
All
right
I'm
going
to
take
that
as
a
no
and
we'll
we'll
move
on
so
we're
on
to
the
next
discussion.
Items
and
I've
got
a
quick
one
that
I
just
wanted
to
update
everyone
on
myself
and
Ray
and
Divia
had
chatted
about
how
we
were
wanting
to
make
sure
that
a
we
were
supporting
our
contributor
Community
by
making
our
kind
of
that
pledge
to
keep
our
open
PRS
to
a
certain
number.
A
So
what
I've
done
is
I've
reached
out
to
a
few
Wranglers
and
approvers
in
the
community
to
make
sure
that
they
wanted
to
stay
on
the
schedule
or
or
or
maybe
drop
off,
as
well
as
a
couple
of
folks,
myself
included?
Who
who
weren't
on
the
actual
schedule
in
the
first
place?
And
so
we've
been
able
to
clean
up
the
schedule
a
little
bit.
We've
had
a
two
folks
step
down
from
wrangling
and
then
two
of
us
myself
and
Zach
step
into
those
into
those
Wrangler
shoes.
A
So
we
technically
haven't
lost
numbers
on
the
Wrangler
side.
Yet
but
at
the
same
time
we
have
been
able
to
update
the
list
so
that,
hopefully,
the
Wrangler
schedule
is
up
to
date
with
folks
who
are
available
and
able
to
contribute
so
I
just
want
to
put
that
out
there
for
anyone
who's
on
the
call
that
is
interested
in
wrangling
in
general
and
you're
wondering
what
that
is.
A
Definitely
take
a
look
at
the
pr
Wrangler
schedule,
because
we've
got
this
really
great
initiative
around
shadowing
PR
Wranglers
and
that's
where
you
can
for
the
week
of
a
of
a
certain
time
when
a
Wrangler
is
scheduled,
you
can
work
with
them
at
a
time.
That's
a
agree
to
by
yourselves
to
understand
how
do
you
do
wrangling?
What
are
your
tips
and
tricks?
What
are
you
looking
for?
A
And
and
what
does
that
entail
in
terms
of
keeping
up
with
the
open
PR's
and
the
contributor
Community?
So
everyone
for
for
those
who
are
really
interested
in
in
knowing
what
PR,
ringling's
all
about,
feel
free
to
contact,
Brad
or
myself
or
Ray
or
Divya,
and
we
can
pop
you
on
the
on
the
list
for
wrangling
or
for
shadowing
a
Wrangler
in
the
near
future.
A
G
Hello,
everyone,
so
so
the
thing
I'm
talking
about
today
is
our
doc
Sprint
that
we
were
hoping
to
run
for
kubecon
in
Europe.
That's
coming
up
at
the
end
of
May,
we're
still
hoping
to
hold
that
event
and
Natalie.
Thank
you.
So
much
for
has
contacted
folks
putting
on
the
schedule
and
have
reserved
a
room
for
us.
G
G
G
Yes,
that
is
a
great
point,
so
a
doc
Sprint
is
where
we
all
come
together
in
we're
going
to
be
doing
it
in
person,
but
it
could
also
be
done
virtually
and
we
all
come
together
and
ask
folks
to
come
and
focus
on
a
particular
area
of
docs,
a
particular
topic
that
we
have.
So
we
can
kind
of
get
through
a
larger
area.
G
A
couple
hours
in
the
afternoon
on
Monday
I,
don't
think
I
actually
wrote
in
I
didn't
put
down
the
actual
daily
event,
so
that
would
be
probably
helpful
for
folks,
and
this
should
be
Monday,
which
is
I,
think
the
contributor
Summit
is
happening
Monday.
So
it's
before
the
con
conference
starts
the
the
day
before
the
actual
conference
events,
presentation
start.
A
Yeah,
that's
right:
it
is
a.
There
is
a
announcement
that
just
went
out
to
communities
Dev
and
announcing
the
contributor
Summit
as
well.
So
that's
a
really
great
timing
and
there
is
the
desire
to
have
a
unconference
talks
there
and
everything
as
well,
but
we
will
be
concentrating
the
event
in
the
afternoon
just
for
all
sorts
of
Staffing
purposes.
I
personally,
don't
get
there
until
midday,
so
I'll
be
hard
to
hard
to
run
a
document
without
a
lot
of
stuff.
So
thanks
so
much
thanks.
A
G
Was
also
a
question
in
the
chat
about
virtually
streaming
the
dark
Sprint.
We
were
not
planning
on
doing
it
for
this
event,
just
for
logistical
reasons,
but
it
is
something
we're
thinking
about
doing
in
the
future,
if
that's
like,
just
outside
of
a
kubecon
having
a
virtual
doc
Sprint
that
we
can
get
more
people
involved
who
are
not
able
to
travel.
Obviously,
that's
an
issue
for
a
lot
of
folks.
G
A
Yep,
that's
a
great
point.
I
also
want
to
point
out
that
also,
unfortunately,
the
contributor
Summit
is
also
in
person.
It's
not
going
to
be
held
virtually
this
year.
However,
the
conference
itself
is
a
hybrid
in
person
and
virtual
event
for
for
coupon
and
Cloud
native
cons.
So
that's
that's
worth
while
pointing
out
too
I
do
believe.
Like
like
Abby
said
we
we
do
have
some
plans
to
try
and
do
a
lot
more
things.
Virtual.
A
The
sigdocs
community
is
really
truly
a
globe
Global
and
async
in
terms
of
where
we
are
located
in
our
time
zones.
Just
even
the
the
assorted
leads
that
we
have
throughout
the
Sega
represent
many
different
countries
and
time
zones
so
doing
something.
Virtually
is
also
absolutely
a
high
priority
for
us
to
include
everyone
great
thanks,
so
much
Abby
for
that
update
for
anyone.
Who's
got
ideas
around
this
feel
free
to
put
us
in
the
Sig
docs
Community
Channel,
you
can,
you
can
add
myself
or
Abby.
A
If
you
like,
we
really
want
to
hear
some
great
ideas
so
that
we
can
get
a
a
good
few
hours
in
in
terms
of
hopefully
future
planning
for
for
docs
and
what
we
want
to
be
working
on
already.
Moving
on
to
the
next
agenda
topic,
we've
got
a
Mark
here,
looking
at
the
windows,
docs
update,
so
next
steps
so
Mark
take
it
away.
E
Yeah
I
I
was
I
kind
of
covered
this
issue
in
one
of
the
previous
sigdax
meetings,
but
I
can
reintroduce
myself
I'm
the
chair
of
Sig
windows
and
one
of
the
goals
that
we
had
recently
was.
We
really
wanted
to
move
all
of
the
information
out
of
that
page.
That
I
had
listed
to
kind
of
more
relevant
pages,
and
that's
because
one
like
I,
don't
think
any
of
the
information
in
that
page
was
actually
about
how
to
set
up
and
run
things
into
production
environment.
E
They
were
it's
all
reference
material,
so
it
made
sense
to
move
it
out
in
the
issue.
I
had
captured,
there's
a
number
of
different
PRS
that
we
wanted
to
do.
The
last
time
I
spoke
I
think
the
plan
was
to
have
all
of
the
PRS
that
touched
that
page
kind
of
stay
open
after
the
initial
124
to
into
main
merge
and
then
review
those
separately
with
a
little
bit
of
rebasing.
E
E
My
hesitation
with
that,
though,
is
that
I've
noticed
that
whenever
we
try
and
like
make
a
p
like
a
single
most
of
the
smaller
PR's,
have
reviews
from
different
audiences
and
I
just
want
to
know
what
the
best
way
to
Signal,
how
to
say
like
most
of
the
content
for
these
other.
For
this
one,
big
PR
has
already
been
reviewed.
This
is
really
just
aggregating.
It
all
together.
D
They
are
all
approved,
they
are
all
lttm
and
they're
all
held.
Could
someone
magically
make
them
all
merge?
Then
you
know
that
is
technically
possible
and
we
can
make
that
happen.
That
is
the
easy
bit
the
hard
bit
I
think
is.
Well,
you
know
the
the
hard
bit
is
getting
to
the
point
where
you
have
n
approved,
LGT
and
good
to
go.
Prs.
E
Yeah,
okay
and
I,
so
I'll,
probably
how
how
should
I
signal
the
like
that
we
have
a
whole
bunch
of
little
PR's
that
are
all
approved,
should
I
put
oh,
should
I
convert
all
those
to
draft
or
I
I
should
say
they're
reviewed
they're
not
approved?
Would
you
like
me
to
convert
them
all
to
draft
PR's
message.
E
A
E
E
A
Perfect
awesome
thanks
so
much
Mark
thanks
for
thanks
for
bringing
that
up
again
yeah.
It
can
definitely
happen
been
in
terms
of
communication
mishaps,
where
just
generally
in
docs
we're
trying
to
keep
a
certain
number
of
PRS,
open
and
kind
of
going
at
all
times
and
just
trying
to
make
sure
that
we're
enabling
contributors
as
much
as
possible.
So
I'm
sure
it
was
just
a
a
misstep
in
terms
of
of
of
the
mergingness.
E
A
A
F
A
A
It
in
great,
we
will
be
I,
believe
broadcasting
that
to
the
mailing
list,
as
well
as
as
Ray
mentioned,
and
we
can
a
single
boost
that
in
in
the
channel
too,
along
alongside
the
couple
of
other
things
that
we've
got
to
signal
boost
as
well
great
thanks,
Ray,
thanks
so
much
and
now
we
have
come
to
the
end
of
our
agenda.
So
this
is
where
I
ask
the
folks
on
the
call
any
other
topics
that
we
want
to
chat
about,
that
we
want
to
add
for
today's
meeting.
C
C
E
D
A
Great
thanks
for
that.
Thanks
for
that
cool
out
things
that
collab
they
made
vital,
definitely
not
a
silly
question
in
the
chat
there.
You've
got
there.
How
do
you
reach
out
to
members
to
ask
them
sponsor
for
a
GitHub,
org
membership?
All
you
need
to
do
is
jump
into.
Stick,
docks
and
paste.
Put
in
your
information
there
put
in
the
call
out,
say:
hey
I'd
like
to
get
a
sponsorship
to
become
to
become
an
org
member.
A
D
Oh
sorry,
for
the
typing
those
people
but
yeah
to
to
vital's
Point
I
I,
if
you're,
if
you're
doing
that
thing,
if
anyone
is
trying
to
look
for
membership,
what
I've
said
is
my
tip
is
start
a
thread
reply
to
yourself.
Yeah
I,
know
talking
to
yourself,
but
in
that
thread
that
you
started
reply
with
some
more
details,
so
that
keeps
the
main
sigdox
Channel,
nice
and
clean
for
people.
D
But
anyone
who
wants
to
help
sponsor
you
you've,
given
them
the
evidence
right
they're
like
oh
wow,
look,
there's,
there's
four
PR's
and
an
issue
great,
and
then
they
can
ask
you
questions
in
that
thread.
So
starting
a
thread.
There
is
just
helps
other
people
in
the
channel,
but
also
makes
things
there
for
anyone
who
wants
to
help
and
and
sponsor
you
which
they
probably
will
foreign.
A
E
A
Alrighty
I'm
gonna
take
silence
as
a
definite
we're
done
for
the
day,
thanks
so
much
to
everyone
for
taking
part
and
for
adding
adding
to
the
agenda
today
really
really
great
meeting
and
join
us
next
week.
On
slack
we'll
have
a
we'll
have
our
weekly
slack
thread
update
there
to
follow
up
on
any
other
agenda
items
that
we
need
to
follow
up
on.
So
thanks
everyone
and
have
a
great
rest
of
your
week,
signing
off.