►
From YouTube: K8s SIG Docs meeting for 20221018
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
Hey
folks
welcome
to
the
October
18
2022
kubernetes
meeting
I'm
your
host.
My
name
is
Ray
lahana
I'm,
one
of
the
Sig
Ducks
co-chairs,
there's
a
few
ground
rules.
First,
we
this
meeting
abides
by
the
cncf
code
of
conduct,
which
boils
down
to
you,
be
nice
and
to
excellent
and
excellent
to
each
other.
A
Also,
this
meeting,
and
also
be
mindful
that
this
meeting
is
being
recorded
and
will
be
uploaded
to
you
to
YouTube
later
first
off,
I
want
to
welcome
any
new
contributors.
So
if
there's
any
new
contributors,
please
feel
free
to
say
hello
or
say
hi
in
the
chats
and
give
a
few
moments
here.
A
All
right
well
welcome
all,
let's
start
with
updates
and
reminders,
so
this
week's
PR
Wrangler
is
me
so
feel
free
to
reach
out
and
ping
me
if
you
have
any
PRS
that
want
to
be
reviewed,
Nate
Waddington
is
also
shadowing,
and
so
we
had
a
little
session
just
before
this
call
as
well.
Next,
there
would
not
be
a
PR
Wrangler
for
next
week
because
it
is
kubecon,
North,
America
or
and
Cloud
native
con.
A
A
A
B
B
Yeah
I
I,
actually
I
have
a
question
that
I
think
I
asked
you
in
the
slacks
teams,
because
we
have
in
the
Doc's
teams
of
this
release.
We
have
to
track
the
caps,
but
also
we
have
another
pull
request
that
it's
the
it's
important
to
to
release
it
in
this
26
and
I
would
like
to
know
if
we
could
write
song
spreadsheets
to
track
it
to
track
this.
This
extra
pull
requests
to
to
try
to
help
with
all
the
docs
teams
right
to
to
be
releases
to
to
track
this.
A
Yeah
some
here's
the
enhancements
tracking
sheets
for
the
docs
View
and
for
each
release.
We
we
get
docs
for
the
upcoming
release,
they're
not
related
to
any
enhancements,
but
they
might
be
but
they're
targeting
the
the
next
branch.
In
this
case
the
dev
126,
Branch
and
yeah.
We
it's
it's
really
up
to
the
docs
release
team
or
our
sub
team.
A
If,
if
you
would
like
to
use
a
Google
spreadsheet
to
track
those
docs
that
are
targeting
the
dev
126
Branch
or
if
you
want
to
use
a
getups
project,
it's
another
method
as
well.
I,
believe
you,
if
you
have
the
I,
think
you
have
the
ability
to
create
a
new
project
because
I
believe
when
we
created
a
new
view
here,
it's
only
for
The
Inheritance
issues
here,
so
you
can't
add
any
new
issues
yeah.
Unfortunately,
so.
B
That's
the
reason:
I
was
thinking
in
the
project
of
website
in
their
own
project
that
we
could
track
thing
like
an
extra
new
project
in
the
GitHub
organizations
website
and
we
could
track
there
yeah.
Please.
C
Can
I
in
in
past
when
I
was
when
I
was
the
the
lead?
We
added
that
to
I
believe
just
the
the
projects
board,
because
we
had
an
ad
hoc
projects
board,
but
in
in
this
case,
while
I
recommend
doing
whatever
sort
of
works
for
you
and
your
team
I
would
push
back
on
enhancements
and
say
hey.
C
These
are
these
are
things
that
we
need
to
track
for
the
documentation
that
is
separate
from
the
traditional
caps
and
so
on
the
docs
board,
even
though
it's
not
necessarily
specifically
an
enhancement,
I
think
that
we
can
make
an
argument
that
this,
while
even
even
though
it's
not
an
enhancement,
it
is
important
to
be
able
to
track
this
stuff
4126
for
documentation
and
I.
C
Think
that's
a
if,
if,
if
we're
not
able
to
make
that
change
for
this,
this
new
system
that
we're
rolling
out
I
think
that
we're
potentially
failing
ourselves
so
I
would
I
would
I
would
I
would
reach
out
to
the
enhancements
team
and
see
if
we
can't
track
it
using
the
system
that
that
we're
using
to
track
everything
else.
Even
even
though
it
is
a
little
bit
different
from
what
is
traditionally
a
a
an
enhancement.
A
For
that,
and
it
can
be
done
I,
you
know,
I
would
suggest
to
go
with
Nate's
suggestion
about
seeing
if
scene
of
those
related
issues
can
be
added
to
the
enhancements,
not
necessarily
they
might
need
to
be
an
added
notes
here.
That
says
it's
not
opted,
not
technically
opted
in,
but
there
is
a
change
with
related
to
this
enhancements.
That's
going
into
126
whether
it's
docs-wise,
whether
it's
code
wise.
If
it's
co-wise,
then
they'll
definitely
need
to
be
an
option
so
non-code
enhancement.
That
will
be.
A
And
some
of
these
might
be
older,
older
issues
or
closed
issues
like
let's
say
if,
like
an
issue
is,
has
has
closed,
the
features
been
graduated,
but
they
might
remove
some
apis,
so
so
some
of
those
removals
might
have
to
be
in
the
126
documentation.
So
it's
not
necessarily
an
enhancement.
That's
opted
into
126,
but
it
does
affect
the
126
release.
B
B
Yeah
I
know
if
I
I
think
I
can
I,
don't
have
enabled
it
at
project,
but
maybe
we
could
play
with
that
to
try
to
create,
and
when
we
see
in
the
stack
talks
conversation
that
someone
is
pointing
us
that
we
need
to
these
pull
requests
to
track
for
this
release.
We
could
have
some
boards
similar
like
this,
to
help
us
to
track
to
to
have.
C
That's
what
I'm
suggesting
do
you?
My
recommendation
is
to
do
the
thing
that
you
think
is
going
to
work
for
you
and
your
team,
but
I
would
also
use
that
as
evidence
or
as
an
example
that
there
are
things
outside
of
the
traditional
enhancements
tracking
that
do
need
to
be
tracked
so
that
we
can
update
that
for
next
time,
so
that
we
capture
these
types
of
issues,
because
this
was
this
has
been
an
ongoing.
C
This
has
been
an
ongoing
issue
for
several
releases
now,
where,
where
docs
changes
aren't
getting
cracked
in
the
the
traditional
systems
and
I
think
that
we
need
to
especially
currently
because
we're
building
out
a
new
system,
we
need
this
system
to
work
for
all
of
the
stakeholders.
So,
yes
do
do
what
you
do.
What
worked
for
you
now,
because
you
need
to
get
the
thing
done,
but
I
I
do
I.
Do
ask
that
you
you
you
take
this
opportunity
to
and
if.
C
Help
with
it,
we
can
we're
definitely
here
to
help
craft
that
pushback
if
you'd
like,
but
we
we
should
push
this
up
to
to
the
enhancements
team
to
ensure
that
we
can.
We
can
capture
these
things
moving
forward.
B
A
Can
also
create
your
project
in
K
website,
like
you
pointed
out
just
so
that
you
could
also
see
what's
best
for
your
team
and
you
might
you
know
we
may
not
be
able
to
get
those
enhancements
in
this
github's
project,
but
in
order
to
track
you
could
use
a
Google
spreadsheet
or
you
could
also
use
a
good
apps
project.
So
I'll
create
one
for
you
as
well,
and
I'll.
Send
you
and
I'll
set
the
right
permission
so
that
you
are
able
to
edit
and
control
that
project.
A
Okay,
I'll
label,
its
126,
docs,
tracking
or
and
but
let
me
know
if
you
want
to
change
a
name
for
that.
A
All
right
just
going
over
the
rest
of
the
updates.
This
is
just
from
the
last
update
from
the
release
team
notes
so
that
if
there's
79
enhancements
going
on
being
tracked,
which
is
a
quite
a
bit
number
of
enhancements
and
so
far
and
there's
a
link
to
the
126
stocks
track
and
view
on
GitHub
as
well,
and
the
only
other
updates
is
from
let's
from
the
console
perspective
there
is
there
will
they
are.
A
There
is
a
draft
for
the
mid-cycle
removals
deprecations
and
not
major
things
for
for
this
for
this
cycle.
So
there
is
a
draft
being
worked
on,
there's
something
to
select
thread
as
well.
For
that
and
that
any
other
questions
for
the
126
team.
A
There's
other
key
days
fall
coming
up.
November
1st
the
feature
blog
freeze,
feature
blogs,
come
come
shortly
after
the
release,
so
there's
some
enhancements,
I'll
be
featured
on
kubernetes.io
with
blogs.
Also
the
docs
placeholder
PR
is
coming
up
in
several
weeks
more
or
less,
and
also
the
duplication,
removals
blogs.
A
The
mid-devember
is
when
the
docs
PR
should
be
ready
for
review.
Then
at
the
end
of
November,
the
docs
PRS
for
126
should
be
complete
and
merge
all
right
and
the
targeted
release
dates
is
December
6
for
kubernetes
1.26.
A
All
right,
there's
no
other
comment,
your
questions.
Let's
move
on
to
issues
and
PRS
three
Ram:
are
you
on
the
call
here?
I,
don't
see
sorry
I'm
on
a
call
but
looks
like
that.
Sorry.
D
Ray
I
just
realized
SRI
Ram
just
updated
the
thread
right
now
to
say
that
they've
just
gotten
a
review
so.
A
We
don't
need
to
all
right
forecast
for
review.
I'll,
take
a
look
at
it
anyway.
After
the
call,
any
other
issues
are
PR's.
A
All
right
moving
on
to
discussion
points,
I
have
a
few
topics
here.
One
is
the
docs
Sprints.
If
you're
going
to
be
at
coupon
in
Detroit
in
person,
there
is
a
contributor
Summit
on
the
Monday
of
the
week
of
kubecon
and
they're,
and
please
register
by
this
Thursday
by
5
PM
Pacific.
The
link
is
in
the
agenda.
Also,
there
will
be
a
doc
Sprint
as
well
from
11
A.M
local
time,
which
is
Eastern,
Daylight
Savings
Time
to
3
20
p.m.
So
there
will
be.
A
There
is
a
room
that
is
allocated
for
a
doc
Sprint,
so
we're
going
to
focus
on
a
few
things
during
the
doc
Sprints,
of
course,
we'll
we'll
Natalie
myself,
W
will
be
theirs
as
well,
and
Abby
will
be
there
as
well.
So
we're
going
to
focus
on
a
few
things
like
the
localization
teams,
asked
us
to
for
page
weights
on
English
sites
in
the
English
site
as
Alpha
sorted,
but
it
does
not
work
the
same
for
the
localization
team.
A
So
we
could
do
a
global
effort
on
to
adding
the
page
weights
on
the
English
side
that
will
help
all
the
localization
teams.
A
Also
just
cleaning
up
some
of
the
of
the
I
guess
of
the
policies
that
we
have
for
front
matter
and
front
matter
is
that
we
don't
see
on
the
website,
but
it
well.
You
do
see
the
title,
and
so
we
also
need
to
add
this
as
well
to
to
the
style
guide
as
as
well
as
to
is
to
having
title
case
for
the
front
matter
since,
since
most
folks
are
I.
A
So
we'll
add
that
and
we'll
also
do
a
cleanup
for
that
as
well,
and
we're
also
there
as
well
to
discuss
any
any
Sig
docs
long-term
issues
or
issues
or
things
that
efforts
that
we
want
to
work
on
with
the
kubernetes
websites
or
any
other
sub-projects
like
localization,
the
blogs
as
well
or
any
other
I
guess
efforts
that
goes
into
K
website
like
diagrams,
maintaining
long
long
standing
issues
so
we're
there
for
for
those
discussions.
F
Yeah
I
last
week
last
meeting
we
had
I
brought
up
the
idea
of
maybe
working
as
a
as
a
team
to
do
like
one
of
the
I
think
you
called
them
major
tasks.
F
Epic
task
click
list
issues
I
seem
to
have
lost
the
link
to
that
I.
Think
I
see
a
couple
of
links
from
last
week
from
two
weeks
ago,
but
I
I
would
be
interested
in
doing
that.
F
If
there
are
other
people
you
know,
I
was
thinking,
storage
or
networking
or
something
you
know
take
on
one
of
the
big
ones
and
just
have
a
bunch
of
people
to
brainstorm
them
together
about
what
to
do,
and
then
we
could
either
try
to
write,
live
or
you
know,
try
to
write
offline
and
just
share
our
work
with
others.
A
A
That
has
those
examples
and
and
there's
been
long-term
important
issues
just
just
like
what
Chris
mentioned
before
that
need.
Some
updates
need
some
refactoring,
so
some
of
these
that
we
could
tackle
or
we
could
plan
around
as
well.
So
those
are
things
that
we
could
discuss.
F
A
Yeah,
well,
ideally,
we
since
we
have
11
to
12,
then
we
have
lunch
from
12
to
1.
Then
we
have
two
hours
after
that's
before
the
talk,
so
it
could
be
free
form.
So
we
have
different
levels
of
folks.
A
Some
might
be
newer
contributors
that
might
that
might
work
on
things
like
changing
the
title
case
or
changing
into
or
doing
the
page
weights
and
some
other
and
other
contributors
could
could
store,
could
could
discuss
on
this
long-term
important
issues
like
like
you
mentioned
before,
and
there's
listed
here
on
this
project
here
or
in
this
on
this
on
this
project
board
I've
also
wanted
to
automate
this
project
board
as
well.
A
A
A
All
right
other
than
that
on
Friday
of
kubecon
week
it
is,
there
will
be
a
sign,
meet
and
greets
and
that's
from
12
30
local
time
to
2
30
p.m.
Local
time,
Divya
and
Natalie
will
be
in
will
be
at
the
psych
meeting
grades.
So
please
feel
please
say
hi
if
you're
around
on
that
day,.
G
Hey
so
I
just
wanted
to
first
of
all
acknowledge
thanks,
Amor
mote,
nitish
and
vital
for
being
here.
Nita
Vitale
I
see
you're,
adding
something
here
in
any
case,
I
wanted
to
just
say
so.
I
had
raised
the
possibility
in
the
last
meeting
of
bringing
on
additional
reviewers
to
see
if
we
could
get
get
things
moving
forward.
G
The
results
of
the
conversation
were
inconclusive
of
the
participants
were
concerned,
about
trade-offs
between
stress
and
and
the
health
of
the
contributors
managers,
and
also
around
the
quality
of
reviews
and
merges.
In
any
case,
the
the
outcome
was
inconclusive.
It
didn't
seem
like
there
was
really
a
a
near-term
path
forward
since
then
took
a
number
of
pull.
Requests
has
grown
from
38
to
51,
and
the
last
PR
of
emerge
was
a
month
ago
on
September
18th.
G
I
know
that
some
of
you,
including
ubital,
have
been
providing
unofficial
reviews
for
the
PRS,
which
is
great
that'll,
really
help
when,
when
the
managers
are
become
active
and
start
merging
so
and
with
that,
I
I
need
to
feel
like
I
need
to
step
back
from
the
issue
and
and
maybe
step
back
from
localization
I
know
that
I've
been
trying
to
help
out
as
a
shadow
but
I
feel
like.
Maybe
it's
better
for
me
to
step
back
for
a
while.
So
you
know,
please
continue
your
efforts.
G
A
One
and
thank
you
very
much
for
all
your
contributions
with
with
that
effort,
as
well
I
know,
there's
there's
since
Cape
con
is
next
week.
There's
there's
a
lot
of
things
and
flux
here:
yeah
I'll,
bring
it
up
with
with
Abby
and
and
the
other
sigdox
leads
as
well
about
the
how
to
ramp
up
reviewers
I
know.
That's
been
awesome,
discussion
on
the
English
side
as
well,
which
we
usually
have
a.
We
would
have
a
cohort
to
ramp
up
folks
to
be
reviewers.
A
What
do
you
just
just
an
open
question
here?
If
folks
have
any
ideas
on
on
how
to
ramp
up
reviewers
for
a
localization
team?
It's
usually
it's
taken
on
from
what
I've
seen
it's
taken
on
from
the
localization
leads
to
ramp
up
reviewers,
but
I.
Don't
know
if
there's
any
like
sub
project
wide,
since
it
is
a
newer
sub-project.
If
there's
a
news,
if
there
would
be
a
project
wide
efforts
or
or
a
cohort
for
to
ramp
up
reviewers.
D
Yeah
thanks
I,
I,
yeah
I.
Think
it's
it's
a
it's
a
point
well
taken
rolls
and
I
think.
Unfortunately,
we've
got
a
lot
of
a
few
other
localizations
that
are
suffering
from
the
same
problem,
not
enough
reviewers
and
PR
as
not
being
able
to
be
merged
and
I.
D
Think
one
thing
that
we
can
do
is
that
at
least
for
the
smaller,
as
in
normal
non-language,
specific
PRS
in
the
specific
localizations,
for
example,
a
lot
of
Link
cleanup,
that's
something
that
other
reviewers
can
lean
into
helping
out
so
that
we
don't
have
to
kind
of
put
all
of
that
effort
on
on
the
very
few
reviewers
that
we
that
we
do
have
in
a
lot
of
the
localizations
I
know.
D
For
example,
Portuguese
is
another
localization
that
is
struggling
on
the
reviewer
side
right
now
and
even
and
and
the
Japanese
localization
has
been
trying
to
kind
of
get
a
few
more
reviewers
into
so
definitely
just
trying
to
empathize
with
the
with
the
reviewer
issue
on
the
Hindi
side,
like
even
unfortunately,
it's
a
little
bit
rampant
across
a
few
localization
groups.
G
Yeah
indeed,
and
if
I
could
just
add
to
what
I
was
saying
earlier,
I
I
believe
that
there
are
people
who
are
really
invested
and
have
contributed
significantly
to
the
pull
requests
and
to
reviewing
each
other's
work.
G
They
just
don't
have
they
don't
meet
all
of
the
criteria
for
traditional
reviewers,
and
so
my
proposal
was
to
Maybe,
on
a
case-by-case
basis,
select
a
few
people
from
that
have
demonstrated
a
commitment
to
the
project
and
it's
unfortunately,
it's
up
to
the
one
or
two
reviewers
remaining
and
they're
very
busy
and
and
have
other
challenges.
G
D
Totally
totally
understand
that
too
and
I
think
I
think
the
good
thing
going
for
the
Hindi
localization
is
that
this
is
a
problem
that
is
being
caught
now,
as
opposed
to
many
many
months
later.
D
I
I
do
want
to
celebrate
the
fact
that
only
having
the
month-long
weight
of
a
last
PR
merged
is
a
win
on
the
localization
and
in
comparison
to
our
other
groups
Abby,
you
may
have
a
bit
more
details
like
data
wise
on
that,
but
I
yeah
I
think
what
we
could
do
is
possibly
a
possibly
an
action
item
is
that
when
our
Hindu
reviewers
are
available
to
try
and
get
the
priority
of
getting
more
reviewers
on
board,
but
I
also
want
to
be
mindful
of
you
know
everyone's
lives
also
taking
up
time
in
terms
of
health
and
work
and
and
so
on
too
so
I
mean
I'm
off
camera,
because
I
am
unwell,
so
yeah,
so
I
I
totally
get
that
that
kind
of
stuff
can
can.
G
D
And-
and
we
just
have
have
to
unfortunately
be
patient
as.
E
I,
thank
you.
Natalie
for
for
chiming
in
I.
Just
do
want
to
make
it
clear
for
everyone
here
on
the
call
and
watching
on
the
the
videos
that
we
have.
This
has
been
something
that
we've
talked
about
with
the
maintainers
and
we
have
brought
this
up
to
them
and
they
they
they
recognize
that
they
have
been
a
little
bit
slowed
down
due
to
illness
and
holidays
and
vacations
that
have
been
happening
throughout
where
they
are
located,
so
it.
E
So
it
is
something
that
is
on
their
mind
and
they
are
working
to
get
back
Up
full
speed
on
the
localization.
They
just
had
a
some
some
breakups
and
availability
for
the
regular
responsibilities,
but
I
do
think
that
this
is
something
we
see
a
lot
as
everyone
as
people
have
mentioned.
This
is
something
that
we
see
a
lot
across
localizations
because
they
there
are
a
lot
of
localization
teams
that
we
have
I
think
we
have
like
14
live
localization.
E
So
that's
a
lot
of
contributors
working
in
a
lot
of
different
languages
that
we
need
to
work
on
a
way
to
get
get
things
working
and
more
sustainable
within
the
team.
So
it
is
definitely
something
that
we're
looking
into
and
I'd
like
to
take
on
a
deeper
dive
in
the
sub-projects
as
part
of
the
localization
effort.
So
thank
you
for
for
bringing
this
up.
G
A
You
very
much
all
right,
so
it
looks
like
we.
We
need
to
take
a
little
deeper
dive
into
the
localizations
and
then
the
there
are.
There
are
a
few
action
items
here:
the
deeper
dive
and
when
the
in
the
leads
are
available,
that's
and
they
can
help
whip
either
ramp
up
new
reviewers
or
we'll
we'll
see
the
outcome
of
the
deeper
dive
all
right.
Any
other
questions
or
comments
about
this
topic.
E
It's
sorry
I,
actually
for
on
this
topic.
I
forgot
I,
do
have
an
issue
about
improving
our
localization
docs
that
we
have
in
the
community
repo.
Let
me
see
if
I
can
find
a
link
really
fast,
and
it
is
basically
centered
around
this
topic
of
how
do
we
Define
roles?
What
sort
of
roles
do
we
need?
What
sort
of
things
can
we
be
talking
about,
and
how
do
we
keep
track
of
who?
E
The
delays
of
the
localization
teams
are
one
so
that
they
can
get
recognition
for
the
work
that
they're
putting
in
and
two
so
that
we
kind
of
know
who
our
touch
points
are
within
the
teams
to
reach
out
to
them.
Specifically,
when
we
have
this,
these
type
of
things
occur
all
right.
So,
if
you
have
more
thoughts,
please
I
put
the
link
in
the
chat
for
what
I.
Basically
it's
a
summary
of
what
I
was
just
talking
about
open
to
feedback.
E
I
I
didn't
get
a
chance
to
share
it
out
so
and
I
forgot,
obviously
to
add
it
to
the
agenda
until
last
minute,
so
be
great.
If
you
could
put
in
any
thoughts
you
have
on
this
topic-
and
hopefully
this
will
help
set
us
up
for
for
more
better
answers
and
and
better
better
ways
to
catch
this
and
help
people
on
board
going
forward.
A
All
right,
thank
you,
Abby
I
know,
there's
one
long-standing
ish
I'm,
sorry,
not
an
issue,
but
long
one
long-standing
action
I've
had
was
to
try
to
find
a
way
to
evaluate
how
current
the
localizations
are
like
versus.
That
could
be
like
the
number
of
of
commits
or
PR's
merge
for
each
localization
in
the
last
12
months
or
so,
but
just
to
see
how
how
active
the
localizations
are
or
and
to
help
identify
like
which
localizations
need
help.
A
I
know
we
we
know
of
a
few,
but
but
we
could
see
with
with
the
rate
of
change
and
commits
in
PRS
to
really
see
how
how
how
updated
those
localizations
are.
So
that's
some
that's
that
is
an
actual
item.
I've
had
I've
just
been
kind
of
been
busy
with
a
few
like
things,
so
I'll
try.
E
To
same
I,
I,
I
I
also
just
put
a
link
in
the
chat
to
A's
spreadsheet
that
I've
been
working
on
this
is
we
started
trying
to
do
some
of
this
work
at
the
beginning
of
the
summer
and
within
the
sub
project,
and
it
is
what
I
linked
is
a
spreadsheet
of
what
I've
been
tracking
semi-updated
in
September.
E
That
shows
information
about
the
sub
projects
and
then
or
about
each
of
the
teams
and
then
sort
of
how
much
activity
has
happened
within
the
past
30
days,
if
there's
been
PR's
merged
in
and
then
notes
whatever
when
it
was
last
updated.
So
it's
a
very
rudimentary
way
of
getting
started
on
what
you're
talking
about
right.
It's
not
formalized
in
any
way.
E
This
is
just
a
spreadsheet
I
put
together,
so
obviously
it
still
needs
more
feedback
and
a
better,
better
shopping
around
to
see
what
what
the
best
way
to
work
keep
track
of
these
things
are
so
folks
know
that
we're
here
for
support
and
how
to
reach
out
to
us.
So,
yes,
all
these
things
are
things
we're
trying
to
work
on
so
we'll
get
there
someday.