►
From YouTube: K8s SIG Docs Meeting for 20230516
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
this
is
the
kubernetes
Sig
docs
meeting
today
is
May
16th
2023
I'm
your
host.
Today,
my
name
is
Ryan
Juan
I'm,
one
of
the
co-chairs
of
kubernetes
sick
docs,
along
with
Nelly
who's,
also
on
the
call
here,
who's
also
coach
here
and
Divya
is
a
third
co-chair
who
is
in
the
different
time.
Zones
of
this
call
is
not
at
a
great
time
for
Divya,
so
I'm
gonna
kick
off
the
meeting
here.
I
just
want
to
make
a
note.
A
This
meeting
is
recorded
and
uploaded
to
YouTube.
So
please
be
mindful
what
you
say.
This
meeting
is
also
buys,
but
by
the
CN
tip
code
of
conduct,
so
that
just
boils
down
to
just
to
be
kind
to
everyone
as
well.
I'm
gonna
share
my
screen
here.
I'm
going
to
share
the
the
agenda,
put
the
link
to
the
agenda
on
the
Zoom
chat
here.
A
All
right,
so
you
should
be
seeing
my
desktop
here
or
the
Google
docs
for
the
agenda,
so
I
want
to
make
some
time
first,
first
off
as
usual.
If
there's
any,
we
do
meet
bi-weekly.
We
do
have
the
zoom
links
on
the
top
of
the
agenda
as
well.
We
also
have
a
monthly
APAC
meeting
that
is
every
11,
A.M
IST
as
well,
and
every
fourth
Wednesday
of
the
month.
A
A
Also
folks,
if
you
we're
gonna,
go
over
some
of
them
of
the
meeting
templates
here
so
do
want
to
welcome
any
new
contributors.
If
you
want
to
introduce
yourself
if
you're
new
to
sick
docs
or
if
you've
been
on
a
few
calls
already
and
just
want
to
say
hello,
so
I'll
give
some
time
for
folks
who
want
to
say
hello.
B
And
when
I
was
in
my
last
meeting,
I
had
my
first
PR
open
and
that
was
their
last
meeting
and
now
I
have
six
merch.
A
Nice,
congratulations
now,
I've,
definitely
seen
you
be
active
as
well
someone
and
welcome
Marcelo
Giles
to
the
to
Sig
docs,
and
thank
you
for
your
contributions.
Thank.
B
A
All
right
any
other
new
contributors
or
who
this
may
not
be
your
first
Sig
docs,
call
or
might
be
returning
after
a
long
absence
or
or
if
you
or
you've
or
you've,
been
on
a
few
Sig
docs
calls.
C
A
A
A
All
right
welcome
welcome
to
pesh
anyone
else,
who's,
a
new
contributor
who
would
like
to
introduce
introduce
themselves.
A
All
right,
I'm
gonna,
go
on
with
the
agenda
in
this
week's
PR.
Wrangler
is
Brad
topple,
so
Brad
is
a
veteran
coming
sick
docs
and
he
also
has
led
the
localization
efforts
in
the
past
as
well.
So
if
you
have
any
questions,
if
you
have
any
open
PRS
and
you
want
them
reviewed-
please
reach
out
to
Brad
next
week's
PR.
A
Wrangler
is
Taylor
dolezal
so
next
week,
if
you
have
any
prison
for
next
week
or
next
week,
reach
out
to
Taylor
and
also
there's
a
link
to
the
pr
wranglerships
on
the
agenda,
also
an
updates
or
just
a
reminder
if
you've
noticed
any
code
of
conduct,
violation
as
well
at
meetings
or
events
or
even
slack
messages
or
even
get
up
comments
as
well.
Please
reach
out
to
the
kubernetes
code
of
conduct
committee,
all
right
so
going
on
with
the
agenda
for
release.1.28
part
of
Sig
docs.
A
We
also
review
PR's
that
are
part
of
the
documentation
updates
for
each
new
release.
So
each
new
feature
enhancement
that
goes
into
release
or
any
updates
your
feature
enhancements
or
as
a
feature
enhancement,
goes
to
graduation
from
Alpha
Beta
to
GA.
We
do
review
those
those
documentation,
Changers
and
so
release.
1.28
just
started
say
this
is
the
first
week
of
the
release,
I
added
the
link
to
the
release
timeline
on
the
agenda.
A
The
only
update
which
I've
added
was
that
the
docs
lead
for
the
release,
1.28
team
is
has
created
us
Branch,
sync
that
was
merged
today.
So
that
is
this
pull
request.
I
didn't
did
merge
as
well,
so
he
so
person
did
create
the
merge.
So
we
occasionally
We
sync
the
dev
one,
that
one
dev-1.28
branch
two
with
main
so
before
this
sync,
this
PR
was
merge.
The
dev
1.8
Branch
was
about
700
and
something
commits
behind
Maine.
So
now
it's
only
13
commits
behind
me.
A
So
we
like
to
do
weekly
syncs
to
make
sure
the
128
branch
is
is
caught
up
with
Maine.
That
also
helps
with
any
merge
conflicts
on
the
release
day.
A
It's
business
as
usual:
it's
part
of
the
standard
workflowing,
you
know,
kubernetes
has
three
releases
a
year
and
that's
part
of
every
this
part
of
almost
every
single
workflow.
A
We
we
do
so
it's
part
of
the
or
that
we
help
out
with
okay,
moving
on
to
issues,
nprs
I've
added
several
issues
and
PR,
as
they
were
mentioned
in
slack,
the
first
one
is
netley:
five
build
timeouts,
I'm
sure
a
lot
of
people
have
seen
this
and
where
your
netlify
build
for
your
open,
PR
has,
has
failed
and
to
a
timeout,
and
the
fix
is
that
we've
had
to
ask
people
to
amend
their
their
PR
or
to
or
to
do
an
empty
or
do
an
empty
commit
to
the
pr,
because,
even
if
the
your
put
your
PR
has
it,
it
has
been
reviewed,
has
an
LG
TM
and
has
an
approved
label.
A
It
still
won't
merge
until
those
until
the
tests
actually
passed.
So
so
there
was
an
issue
created.
Ncoko
has
has,
has
detailed
the
issue
with
the
bug
report
here.
So
I
have
that
link
still
there's
no
I,
don't
think
we
have
a
fix
in
mind
yet
and
follow
the
the
comments
on
the
issue
as
well.
So
we're
still
working
on
that,
so
hopefully
we
will
get
that
resolved.
So
this
is
an
issue
that's
been
since
going
on
since
last
year.
A
So
but
we
see
it
more
frequently,
especially
in
the
last
last
few
months.
Definitely
any
comments
or
questions
on
that.
A
B
Do
those
empty
commits
to
overcome
it?
One
thing
I
notice
is
when
you
go
to
the
tests
tabs
in
the
in
the
see,
if
you
go
from
the
main
tab
to
the
test,
one
when
you
click
on
the
details
that
goes
to
network
file
immediately,
when
you
don't
see
the
Hugo
output
like
shows
like
columns
from
different
languages.
If,
if
a
thing
is
going
to
succeed,
it
will
show
up
immediately
and
then
we'll
take
some
time.
B
But
when
I
know
now,
when
it's
gonna
hang
because
it
takes
very
long
to
show
that
out
just
just
initial
output,
then
I
know
it's
going
to
fail
and
it
takes
like
a
Min
an
hour.
I
think
almost
I
think
a
timeout
mode
an
hour,
but
I
know
when
it's
not
at
least
I
know
when
it's
gonna
fail,
and
this
morning
I
submitted
one
I
was
successful
and
it
took
one
minute.
A
B
A
Looks
like
chiming
has,
as
a
has
added
a
fix
to
it
in
this
primary
poll,
from
this
pull
request
that
Natalie
posted
here
so
looks
like
it
has
been
helping
out.
I
have
seen
more
tests
passing
on
the
first
try
as
well,
and
it's
been
linked
and
I've
seen
whenever
we,
whenever
I
redeployabilities
well
I've
seen
it
pass.
Usually
after
just
one.
You
know
on
the
on
the
next
attempt,
so
it
looks
like
looks
like
the
fixes
is
coming
along.
So
hopefully
we
don't.
A
All
right
next
for
PRS
or
just
requests
for
reviews,
so
I
want
to
go
into
great
detail,
because
these
are
requests
from
movies
from
various
people
on
slack,
one
is
actually
from
an
issue
that
I
created
so
we'll
take
a
look
at
this
on
in
on
on
an
endpoint
slice
controller
label.
So
we'll
take
a
look
at
this,
so
I
did
create
this.
This
was
related
back
into
like
I,
think
in
the
what
Dev
or
in
the
127
release
cycle.
A
What's
up
I
will
I
will
take
a
look
at
this
two
different
as
well
about
adding
updating
some
of
the
pixels
to
you.
I
think
one
with
services
to
the
downward
API.
A
So
I
want
to
take
a
look
at
this
a
little
bit
more
and
then
the
last
one
from
mahe,
and
this
is
about
a
the
SCD
scd9
plug-in.
That's
for
deprecation,
so
I
think
we
just
need
to
to
verify
it's
been
deprecated
I.
Think
I
did
do
a
review
on
this.
I
did
have
a
question
if,
on
this
PR,
so
we'll
take
a
look
at
mahese's
response
and
see.
If
and
if
that
is,
if
it's
good
to
go.
A
Oh
yeah
and
please
do
I-
want
to
spend
some
time
in
the
next
topic,
which
is
pretty
big
so
in.
If
you
look
at
our
human,
a
slash
website
repo,
we
have
a
lot
of
issues
and
we
and
Debbie
has
faced
this.
A
This
topic
here,
there's
a
GitHub
discussion
on
us.
It's
about
how
introducing
a
role
called
the
issue
Wrangler.
So
you
see
we
have
almost
600
issues
in
this
new
role
will
be
solely
just
just
to
issue
or
just
to
Wrangle.
Those
issues
to
see
if
issues
are
are
not
in
scope
for
the
project,
like
a
lot
of
like
support.
A
Related
issues
should
not
be
in
scope
for
the
project
if
issues
should
be
triage
accepted
as
well
or
or
if
it's
or
some
issues
that
are
not
appropriate
as
well
for
for
the
K
website,
issue,
I'm,
sorry,
repo
in
case
it
might
be
a
might
be
a
bug
issue
with
the
Cuban
lace
project,
as
might
be
a
code
bug
issue
which,
which
is
more
appropriate
for
the
cube
and
a
slash
kubernetes
repository
than
the
kubernetes
website
repository.
So
please
take
a
look
at
this
GitHub
discussion.
A
A
But
we
have
a
lot
of
open
PR,
so
so
the
role,
the
pr
regular
role
is
tends
to
be
very,
very
PR
intensive
versus
more
a
more
issue,
so
it
so
it's
so
we
want
to
spread
those
Cycles
or
the
I
guess
or
the
yeah.
We
want
to
spread
I
guess
the
duties
of
issue
Wrangler
to
a
separate
role.
So
take
a
look
at
the
proposed
requirements
like
a
kubernetes,
org
member
as
well.
A
How
where
this
is
with
the
contributor
ladder
as
well,
how
we
can
implement
it.
We
could
create
a
roster
of
folks
who
triage
issues.
We
could
pilot
a
shadow
program
to
see
if
there's
an
interest
as
well,
then
we
could
repeat
as
well.
We
do
need
documentation
as
well
for
this
role,
so
we
can
separate
that
that
out
from
the
pr
Wrangler
gives
me
documentation.
So,
please
add
your
inputs
to
the
GitHub
discussion
as
mentioned
as
well.
We
next
steps
are
more
formalizing.
A
The
role
so
we'll
send
our
Communications
to
the
EM,
to
the
email
channels
and
slack
slack
channels
as
well.
Any
folk
will
have
folks
raise
your
hand
or
we'll
ask
for
volunteers
to
be
on
the
issue,
Wrangler
rotation.
Then
we
also
need
to
document
the
role
as
well
and
we
will
start
off
with
that
program.
So
please
take
a
look
at
this
role
at
this
GitHub
issue
and
all
right,
sorry,
GitHub
discussion
and
have
your
your
comments
and
feedback
or
questions
on
this
GitHub
discussion.
B
A
That's
part
of
the
question
yeah.
Well,
there's
long
running
issues,
so
there's
long,
you
know
where
some
some
some
pages
some
section
needs
to
be
updated.
But
you
know
time
time
is
very
limited,
so
yeah.
So
there's
still.
We
have
long
running
issues.
Definitely
like
we
like
some
like
some
diagrams
are
mermaid
diagrams.
Some
diagrams
are
svgs
and
we
would
like
to
go
to
mermaid,
but
also
we
had
some
bug
issues
with
using
mermaid
diagrams.
So
there's
there's
lots
of
fish.
There's
there's
a
lot
of
backlog
issues
that
folks
can.
C
A
Is
also
one
of
the
roles
that
the
issue
Winger
can
can
prioritize
as
well
as
prioritizing
which
which
issues
should
be
looked
at
first
and
some
issues.
You
know
we
are
not.
We
could
put
on
the
back
burner.
A
Some
of
these
issues
needs
might
need,
like
some
detailed
technical
understanding
of
of
what
of
you
know
of
that.
Topic
is
as
well.
You
know
like,
so
there
might
just
be
some
or
more
inputs
from
us
from
another
state,
so
there's
several
different
options
and
why
you
might
be.
A
All
right,
I
do
apologize
to
be
here
in
some
construction.
There
is
something
construction
going
on
right
outside
my
door
next
topic
that
Tim
had
a
call
in
the
slack
channel
for
those
who
want
to
edit
and
organize
blog
articles.
So
for
that
please
join
the
Sig
docs
blog
slack
Channel
as
well.
We'll
put
the
link
on
that
on
the
agenda.
A
That
looks
like
organizing
could
be
like
how
how
helping
determine
when
to
schedule
new
blogs.
Editing
is
reviewing.
It
could
also
be
helping
to
obtain
or
or
help
folks
or
sort
of
review
blogs.
A
Like
we
get
a
lot
of
blogs
at
the
end
of
the
release
cycle,
so
you
talk
about
where
we
want
to
feature
a
certain
enhancement
for
a
release,
so
we'll
get
a
lot
of
blogs
at
the
end
of
a
really
cycle
and
weeks
after
a
release
cycle
as
well.
So
we
need
help
with
organizing
Windows
block
should
be
published,
which
ones
to
prioritize
and
to
review
those
blocks.
B
A
No,
so
the
policy
is
that
every
so
after
one
year,
there's
going
to
be
a
a
banner
or
a
highlight
on
the
blog
that
says
like
this:
blog
is
over
a
year
old,
so
it
may
not
be
updated
so,
but
then
we
also
do
not
updates.
We
do
update
blogs,
but
we
don't
update
blogs
if
they're,
if
they're
a
year
old
as
well.
So
we
could
take
a
look
at
the
blog
posts
here
and
we'll
just
excuse.
My
cleanup
here.
A
Well,
typically,
let
me
try
to
mine,
we'll
see
you
see
this
Banner
here.
This
article
is
more
than
one
year
old,
older
articles,
maybe
outdated
content.
A
A
Well,
the
blog
will
live
there,
but
but
they
won't
be
updated
forever
because.
C
B
A
Because
the
the
blog,
if
you
want
to
edit
a
blog
or
update
a
Blog,
you
should
also
ask
a
review
from
the
author
as
well,
because
the
author,
you
know
we'll,
have
we'll
have
that
domain
knowledge
to
to
the
blog
post.
A
Yeah,
okay,
all
right
and
just
want
to
open
up
to
any
more
comments
or
questions
as
well
about
blogs
about
about
the
issue
Wrangler.
This
GitHub
discussion.
A
Or
for
any
other
comments
or
any
other
topics
that
people
want
to
bring
up
as
well,
I
just
want
to
open
the
floor
here.
B
If
you
want
to
let's
say
so
far,
my
all
my
commits
have
been
Small
Things
I
wanted
to
tackle
a
bigger
issue,
but
I
feel
like
I
need
some
extra
help.
What's
the
best
way
to
go
about
it
like
if
I
need
like
a
mentor
to
tackle
a
bigger
issue,.
A
Yeah
so
there's
a
few
ways
to
go
about
it.
Usually
an
issue
or
a
topic
in
the
website
is
related
to
another
Sig.
A
You
know,
if
there's
any
like
documentation
changes
for
a
cubelet,
you
would
contact
Sig
note.
So
if
you
need
like
more
technical
assistance,
contact
the
the
Sig
that
might
be
responsible
for
that
topic,
also,
you
could
reach
out
on
the
slack
channels
on
our
Sig
doc,
slack
channel
on
the
related
six
slack
Channel
as
well.
A
B
Right
yeah,
yeah
I
got
a
taste
of
that.
My
last
issue,
I,
still
open
I
interacted
with
the
Sig
API
machinery
and
those
guys
helped
were
nice
for
helping
me
with
that
that
one.
A
Yeah
yeah,
and
that
Sega
would
also
be
you
know,
will
be
part
of
the
review
process
as
well.
So
it's
good
to
like
to
reach
a
handout
to
them,
and
so
that
they're,
aware
of
the
update.
A
All
right
any
other
comments
or
questions.
C
A
It's
not
I,
don't
think
we
actually
have
a.
We
have.
We
have
a
contributing
page
and
there's
the
Netflix
auto
repo
on
their
on
their
parents
on
the
roots
directory.
So
we
do
have
the
Tamil
configuration.
B
A
Netley
Phi,
so
you
could
kind
of
see
how
now,
if
I
set
up
from
there.
C
A
But
we
don't
have
like
a
certain
page
on
our
few
minutes:
documentation
for.
A
Fly,
maybe
we
didn't,
let
me
go,
take
a
look
see.
A
Yeah
we
yeah,
we
have
a
small
mentions
on
it's
just
on
the.
A
A
All
right
there's
also
a
question
on
from
vital
about
about
to
pair
up
with
the
reviewers.
Well,
so
you
could
always
look
at
the
pr
regular
schedule
and
request
to
be
a
shadow
for
one
of
the
experienced
reviewers,
so
vital
I
do
suggests
you
to
reach
out
to
see
on
the
pr
Wrangler
see
if
there's
any
openings,
for
you
know
an
experienced
reviewer
that
you
would
like
to
review
with.
A
A
Like
to
do
usually
I
like
to
do
a
zoom
session
towards
the
beginning
of
the
week
on
on
how
I
review
and
then
we
just
kind
of
go
async
or
we
do
communicate
async
throughout
the
week.
If
you
have
any
questions.
A
A
Okay,
I
guess
that
wraps
up
our
meeting
I'm
going
to
stop
the
recording
here.
A
All
right,
thank
you
very
much
for
those
who
have
joined
our
sick
docs
meeting
or
who
have
watched
this
recording.