►
From YouTube: K8s SIG Docs meeting for 20221101
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
A
Folks,
welcome
to
the
Sig
docs
November
1st
2022.
bi-weekly
Zoom
meeting
I'm
your
host.
My
name
is
Ray
lohano
I'm,
one
of
the
co-chairs
for
Sig
docs,
a
few
things
before
we
start,
so
we
do
abide
by
the
cncf
code
of
conduct
which,
which
pretty
much
boils
down
to
just
to
be
kind
to
each
other,
and
this
meeting
is
recorded
and
uploaded
to
YouTube,
so
be
mindful
what
you
say
in
the
chats
as
well.
I
have
placed
the
agenda
or
the
link
to
the
agenda.
A
I
added
one
more
time.
If
you
want
to
add
yourself
I'm,
going
to
start
sharing
my
screen.
A
A
But
first
thing
I
like
to
start
off
as
well
is
I
want
to
welcome
there's
any
new
contributors.
If
you'd
like
to
introduce
yourself,
please
feel
free
to
go
ahead
and
unmute
yourself
and
give
a
little
brief
introduction.
C
Hey
so
I'll
go
ahead
and
take
that
First
Step
at
it
hi
everybody,
my
name
is
Michael
benavidez
I've
actually
contributed
to
Google
flow
docs
in
the
past.
A
few
years
ago,
before
it
went,
1.0
I
participated
in
some
docs
Sprints
and
I've
had
some
PRS
out
there,
but
it's
been
a
while.
So
I
wanted
to
get
engaged
with
the
product
again
and
I
thought.
A
great
way
to
start
would
be
to
attend
one
of
these
meetings
and
get
a
sense
for
what's
going
on
what
needs
work.
D
Hi
everybody,
my
name,
is
bad
moscola
I
am
from
Nigeria
I'm
a
software
engineer
I'm.
Also
a
technical
writer
and
I've
been
log
into
contribute
to.
D
Documentations
for
why
but
I
don't
know
how
to
go
about
it.
So
I
guess
I
should
be
able
to
find
some
answers
to
my
questions.
There.
E
F
Hi
I'm
Aline
I
was
more
involved
last
year.
I
got
another
job
and
now
I'm
re-engaging.
F
A
All
right,
so
we
could
move
on
to
the
next
topics
of
updates
and
reminders.
This
week's
PR
Wrangler
is
Nate,
who
is
on
the
call?
Thank
you
Nate
for
reviewing
PR
as
I'm,
also
going
to
try,
try
to
review
PRS
as
well
and
yeah,
and
continue
to
help
with
that
efforts
and
also
review
some
issues
as
well.
A
Next
week's
PR
Wrangler
is
Jim
angel
I'm
also
made
I'm
also
created
a
message
on
the
Sig
docs
stock
Channel
as
well
to
remind
Nate
and
Jim
as
well
and
for
those
and
for
folks
who
who
are
reviewers
or
who
are
approvers.
Please
take
a
look
at
the
pure
Wrangler
schedule
to
take
a
look
at
when
your
shift.
Your
next
shift
is
all
right.
Next
topic
on
the
agenda
is
released
1.26.
Anyone
here
from
the
release
team
that
would
like
to
give
an
update
on
docs
or
comms.
A
All
right,
I
did
copy.
The
last
update
with
from
the
release
team
meeting
agenda
on
the
docs
update
that
the
current
status
is
green.
A
Last
topic
was
that
there
was
a
new
project
being
used
to
track
docs
changes
that
aren't
covered
by
kepts,
but
that
are
charting
the
dev
126
branch
and
for
key
dates
for
the
upcoming
release
schedule
for
126..
It
is
scheduled
to
be
released
on
December
6th.
Some
key
some
key
Milestones
is
today
there's
a
feature
blog
freeze,
November
10
is
key
dates
for
Sig
docs.
A
It's
docs,
placeholder
PR,
for
when
we
know
kind
of
see
the
number
of
docs
that
were
needed
to
be
reviewed
before
the
126
deadline.
November
10
is
also
when
we
do
plan
to
publish
a
deprecations
and
removals
blog
last
I
saw
that
we
are
planning
to
to
publish
a
Blog
for
that
and
also
November
15th
and
docs.
Prs
are
ready
for
review
and
and
at
towards
the
end
of
my
doc.
A
November
29,
the
all
126
stocks
are
completes
and
merge
and
also
feature
blocks,
are
ready
for
view
for
review
as
well
and
feature
box.
10
are
scheduled
to
be
published
after
the
released.
A
All
right
just
want
to
open
up
for
any
comments
or
questions
about
these
dates.
G
Yeah
just
one:
it's
not
specifically
a
docs
item,
but
next
Tuesday.
The
8th
is
also
a
code
freeze
day,
so
that
probably
won't
affect
Dr
very
much
but
maybe
worth
mentioning.
A
One
issue
is
37522,
it's
add
a
new
page
documenting
Prometheus
metrics
in
core
kubernetes
I
did
take
a
look
at
the
preview
of
this
last
week
during
kubecon
and
it
looked
fine
in
terms
of
the
preview.
But
there
is
a
comment
here
about
have
been
released.
Team.
Add
this
add
to
their
tasks.
A
I
did
bring
this
up
to
the
Sig
release
meeting
and
we
will
discuss
it
in
the
126
retro,
but
I
believe
we
should
start
having
there
are
there
and
I
believe
there
is
documentation
on
how
to
produce
this
reference
docs
that
as
long
as
we
have
good
documentation
here,
we'll
we'll
present
this
on
the
126,
retro
and
and
the
release
team
will
decide
on
if
they
will
carry
this
forward
as
one
as
as
one
of
their
tasks
for
the
release
docs
team.
B
A
I
would
like
to
see
this
merge
I
think
this
benefits
every
all
consumers
of
kubernetes
and
the
this
is.
This
is
why
I
actually
brought
this
up
for
this
big
release
meeting
today,
I
kind
of
wish
that
we
had
I
guess
a
more
of
a
discussion
on
it,
but
they
would.
They
would
like
to
have
this
discussed
on
at
the
Retros.
A
Instead,
personally,
I
would
like
to
see
this
emerge,
and
but
I
believe
that,
if
documentation
I'm
willing
to
help
write
the
documentation
so
that
reference
docs
are
generated
for
so
that
the
release
team
can
add
this
to
their
task.
A
A
part
of
this
also
I
know
that
reference
docs
to
generation
has
been
pretty
tricky
in
this
last
several
years
of
the
release
as
well
so
I
I
know,
I've
been
looking
to
have
to
how
to
get
folks
or
something
on
my
on
my
plates
is
to
get
the
tech
leads,
who
who
are
familiar
with
generating
those
reference
stocks
to
also
help
to
revamp
the
the
documentation
on
on
all
reference
stocks.
For
that
we
have
so
far,
foreign.
B
A
Yes,
I
I
did
see
that
the
other
way
and
I
saw
that
that
second
instrumentation
now
so
that
they're
willing
to
to
Shepherd
this
be
maintainable
by
the
really
stocks
team
as
well.
So
yeah
I
did
see.
That
I
also
do
agree
that
this
this
that
the
pages
generated
by
by
the
support
requests.
What
benefits
the
the
website.
A
All
right
any
additional
questions
on
this
or
comments.
G
Whenever
we
see
a
a
generated
thing
like
this,
where,
where
will
the
documentation
for
the
generator
live,
would
that
would
all
be?
Would
would
all
that
be
in
KK?
G
And
would
this
be
like,
like
with
this,
with
the
process
for
generating
this
be
in
line
with
the
rest
of
the
generated
content
that
we
that
we
run,
or
is
it
going
to
have
to
be
a
separate
third
thing
that
we
need
to
Auto
generate
auto-generate
trigger.
D
G
Like
we
want
this
in,
but
I
don't
I'm
also
hesitant
to
push
back
too
hard
on
locations
and
whatnot,
but
is
this?
Is
this
the
way
we
want
that
to
be
set
up,
or
do
we
have
an
opinion
on
that.
A
G
We
could
open
up
a
follow-up
if
we
wanted
to
change
that.
Tim
I
think
you
had
your
hand
up.
B
Thank
you
so
I'm
trying
there's
a
there's,
a
Blog
which
I'll
stick
in
the
the
zoom
chat.
The
title
of
the
article
is
k8ci
bot,
helper
job,
automating,
mate
update
and
it's
an
article
on
the
contributor
site
and
the
inimitable,
dims
and
I
might
say
this
wrong.
B
Some
subasmita,
Swain
or
Swain
made
a
thing
for
the
KK,
so
not
for
K
website,
but
for
kubernetes
itself
there
is
a
command
that
you
can
send
to
to
prowl
and
prowl
will
build
you
a
zip
file
of
all
the
generated
files
that
you
haven't
had
updated.
B
So
this
is
useful
for
another
bit
of
the
reference
docs.
So
when
someone
comes
and
says,
hey,
there's
a
typo
in
the
reference
page
for
a
service,
and
we
say
well
that
needs
fixing
Upstream
when
they
go
fixing
it
Upstream.
They
realize
that
they
haven't,
got
a
build
environment
for
the
for
kubernetes
and
now
they're
one
line
fix,
becomes
you
know
a
four-hour
Endeavor
to
work
out
how
to
build
go.
B
G
Yeah
I
think
that's
an
interesting
point.
I
I,
like
I,
like
the
idea
of
making
that
I
like
the
idea
of
of
documenting
the
whole
thing
and
making
it
a
lot
easier
to
do
right
now.
It's
it's
a
pain.
So
let
me
let
me
take
some
time
to
read
that
over
and
see
how
we
might
be
able
to.
Are
you
suggesting
that,
as
a
separate
issue
that
we
Implement
what
they're
suggesting
there
on
our
side
or
what?
What
what
would
the
action
be
on
our
on
our
side
here.
B
I
would
think
we
would
reach
out
to
sick
testing
and
buy
sick
testing
some
beverages.
D
B
Don't
have
the
skills
in
Sig
docs
to
build.
You
know
most
people
in
sick
docs.
Don't
have
the
skills
to
build
this,
but
there
are
lots
of
people
in
suggesting
who
are
only
some
very
nice
cocktails
away
from
being
willing
to
help.
B
And
the
end
result
is
that
the
the
we
sold
this
specific
issue
with
another
knit
around
instrumentation
and
that
we
make
the
release
team's
job
on
release
day
more
pleasant.
C
H
I
just
wanted
to
either
suggest
or
ask:
if
we
have
do,
we
currently
have
an
issue
talking
about
this
topic
or
capturing
our
long-term
hopes
and
dreams
for
the
reference
talks,
so
that
we
can
continue
to
have
this
conversation
somewhere.
It
might
exist.
I,
don't
know
the
issues
that
well
so
I'm,
just
I
just
want
to
make
sure
that
we're
tracking
what
we're
talking
about
this,
like
in
a
step
farther
if
it's
something
we
really
want
to
take
on
and
and
reference
people
to.
H
H
A
Yeah
I
could
fill
in
some
details
about
the
issue
with
generating
reference
stocks.
I
could
take
that
on
as
an
action
item.
Okay,.
G
G
G
We
want
to
link
the
the
issue
that
we're
creating
here
back
to
this,
once
it's
approved,
or
do
we
want
to
hold
off
or
I
heard
there
was
some
talk
about
having
it
land
for
a
specific
release,
or
do
we
just
want
to
get
it
in,
because
it
looks
like
like
I
said
it
looks
like
it's
ready
to
go
as
is,
but
we
may
want
to
make
some
changes
afterwards.
A
I
believe,
if
there's
any
change
that
needs
to
be
done
afterwards,
we
should
definitely
make
a
comment
on
it
and
I.
Don't
know
if
follow
PRS
will
help,
because
it
would
have
to
be
changed
on
the
generator
side.
Otherwise,
it
will
just
be
replaced
right,
like.
A
Issues
or
or
like
yeah,
so
I
suggest,
and
there
are
there,
have
been
suggestions
on
on
the
pull
requests
for
changes
and
on
that
looks
like
it's
been
updated
as
well.
So.
A
All
right,
I'll
do
quit.
I'll
do
a
review
on
this.
So
did
take
a
look
at
the
last
week.
Nates
would
be
great
if
he
could
do
a
third
reveal
one
as
well
yeah
to
get
a
third
set
of
eyes
on
it
and
see
the
benefits
and
I'll
link
the
previous
of
these
pages.
So.
A
All
right
next
topic
of
discussion,
Abby
I,
do
see
you
on
here
the
we
had
a
doc
Sprints
last
week
at
kubecon
I
thought
I
won
grades.
Abby.
Did
you
want
to
give
the
summary
of
the
the
doc
Sprints
I?
Have
the
I
linked
the
issue
on
the
agenda
here.
H
I
can
certainly
try,
so
we
had
an
in-person
event
last
week
at
the
kubecon
North
America
conference
in
Detroit,
where
a
group
of
us
got
together
and
it
was
open
to
everyone
who
was
at
the
contributor
Summit
to
come
in
and
help
us
work
on
our
particular
docs
issues
that
we
have
kind
of
designated
as
what
we
wanted
to
work
on.
So
that's
a
little
bit
about
a
doc
Sprint
and
we
had
some
really
great
participation
from
people
at
the
event.
H
I
think
we
we
created
about
20
PRS,
which
was
really
awesome
to
see,
and
one
of
the
two,
the
issue
that
I
think
Ray
has
in
the
agenda.
I
can
open.
It
up
was
about
addressing
some
pageway
issues
that
were
on
the
English
language
docs,
so
some
of
our
Pages
either
didn't
have
a
page
weight
or
had
an
overlapping
page
weight,
which
is
what
determines
where
the
page
lies
within
the
side.
Nav.
H
If
you
look
at
the
kubernetes
website
on
the
side
nav
in
the
documentation,
the
pageway
is
what
determines
where
that
the
rests,
and
if
there
is
no
page
weight
or
if
there
is
a
page
with
an
overlapping
weight
in
the
English
language
documentation,
the
the
site
will
default
everything
to
be
alphabetical
order
which,
in
the
English
language
docs
is
you
know
pretty
much
as
we
want
it
to
be.
But
when
we
translate
those
documentation
ducts
into
different
languages,
it
gets
a
little
a
different
alphabet.
H
Different
way
of
you
know
different
words
of
whatever,
so
it
will
be
sort
of
differently.
So
that
was
something
we
wanted
to
address.
That
was
what
the
majority
of
the
issues
or
the
PRS
we
addressed
within
the
doc
Sprint.
But
then
we
also
talked
some
of
the
other
issues
about
another
issue
that
I
can
link
in
a
second
which
was
title
case
within
the
docs,
so
I
think
there's
still
some
work.
H
Cleanup
work
that
I
know
I
need
to
clean
up
myself
to
make
sure
that
we
have
all
these
completed
for
the
page
weights
and
I'll.
Add
a
the
issue
in
I.
Think
Chris
created
Chris
nagas
created
an
issue.
Sorry
I.
H
If
you
could
share
that
that
one
also
still
needs
some
work,
and
that
is
about
fixing
title
cases
within
the
page.
Titles
I
believe.
H
But
the
summary
of
all
this
long
and
short
of
it
is.
We
have
some
really
really
great
participation
and
it
was
a
really
great
event.
We
had
a
couple.
People
come
in
with
our
first
create
their
first
PR
as
their
first
contribution
to
the
site,
so
we
got
them
all
set
up
and
it
was
really
awesome
to
see
and
I
look
forward
to
running
future
events
with
for
the
community.
Yes,
thank
you
Chris,
if
you're
interested
in
in
picking
up
any
continuing
to
work
from
the
the
doc
Sprint.
H
These
are
some
two
issues
you
can
check
out.
Yeah
I,
don't
know
if
anybody
else
I
know
some
of
the
people
who
are
able
to
attend.
So
if
anybody
else
had
any
comments
on
Doc
Sprint,
if
not.
G
Yeah
it
was,
it
was
a
great
event.
I
mean
one
of
the
things
as
a
part
of
my
wranglership
this
week,
I'll
make
an
effort
to
either
follow
up
with
or
merge
any
sort
of
related
PRS
that
are
still
open
from
last
week.
I
was
really
pleased
with
with
how
many,
how
many
PRS
we
got,
how
many
merges
we
got
in
and
I
want
to
make
sure
that
they
don't
sort
of
languish
past
the
the
about
this
week.
G
I
A
Yeah,
that
was
a
great
event
as
well.
Just
do
we
always
had
a
few
new
contributors
as
well,
so
there
was
a
few
new
contributors.
There
were
existing
contributors
to
kubernetes
but
new
to
Kate
websites,
so
they
were
ramped
up
pretty
quickly
in
the
document
room.
So
that
was
great
to
see
and
great
to
see.
The
first
support
request
created
as
well.
H
Yeah
I
just
wanted
to
address
one
comment
in
the
the
chat
just
to
clarify,
so
this
was
an
event
that
we
just
did
specifically
at
kubecon,
so
it's
technically
over,
but
we
do
try
to
run
them
at
each
Q,
in-person
kubecon.
H
We
have
hopes
and
dreams
of
doing
one
virtually.
So
it's
just
a
specific
time
set
aside
for
a
group
of
folks
from
the
community
to
join
in
and
work
on
issues
within
the
the
docs
ethos,
but
it
was
just
for
a
specific
set
of
time,
but
there
are
those
two
issues:
there's
still
some
work
to
be
done
on
those
that
we
have
listed
there.
So
if
you
are
looking
for
a
first
contribution
that
might
be
something
to
check
out
if
you're
interested.
G
And
feel
free
to
reach
out
in
the
CNN
in
the
kubernetes
slack,
if
you
have
any
questions
about
either
the
processor
or
getting
set
up
or
anything
like
that,
we're
happy
to
help
out.
A
Any
other
comments
or
questions
or
any
additional
topics
or
issues
or
pull
requests
that
folks
want
to
bring
up.
I
I
have
a
quick
question
just
wondering
when
they're
going
to
start
choosing,
shadows
and
release
leads
for
the
next
release.
A
So
that's
usually
around
the
mid-December,
so
application
should
go
out
actually
should
probably
go
early
December
this
this
time
around
early
to
mid-December
and
selections
will
probably
go
into
the
first
week
of
January
or
probably
for
second
week
of
January,
but
most
likely
going
to
be
first
week
of
January.
So
just
keep
an
eye
out
for
folks
who
are
looking
to
contribute
and
to
join
the
release
team
or
the
release
or
the
release.
Docs
team
as
part
of
the
release
team,
they
have
to
shout
out.
A
Shadow
applications
will
go
out
early,
probably
early
to
mid
December
and
up
to
and
selections
will
be
done
around
first
week
of
January.
A
F
I
have
a
question
about
the
new
contributor
meet
and
greet
monthly
meeting.
Now.
Is
that
a
meeting
where
you
would
ask
questions
like
if,
when
I
have
followed
the
documentation
like
there's
a
reviewing
pull
requests
page
I'm,
finding
that
some
of
the
stuff
that
it
says
to
do
results
in
kind
of
not
being
good,
so
I
mean
that's?
Actually
something
I
could
do
a
pull
request.
F
Like
you
know,
I
could
create
simple
requests
for,
but
I'm
I'm
just
wondering
how
often
do
people
review
these
steps
and
I
don't
know
whether
I'm
just
doing
something
incorrectly
but
I
noticed
that
I
kind
of
get
in
a
you
know
situation
where
I'm
sort
of
at
a
standstill
like
yeah
I
installed
Hugo
great,
but
where
does
it
have
information
from
that
page?
F
To
tell
us,
you
know,
you
know
the
next
steps
like
okay,
you
can
so
I
I
just
feel
like
the
the
contribution
documentation
is,
is
really
I,
don't
think
it's
easy
to
follow.
I'm
sure
people
have
found
it
easy
because
they
they're
contributing
right,
but
personally,
I
I've
had
difficulty
with
it.
So
anyway,
that's
my
comment.
Sorry.
J
I
will
say
that
I
don't
disagree
with
you.
It
does
kind
of
rely
on
expecting
that.
You
know
how
to
use
Hugo,
which
I
think
is
perhaps
a
little
bit
of
an
unrealistic
expectation
and
that
we
that
that
should
be
documented,
better
yeah.
F
I
would
love
to
be
able
to
go
through
this,
and
just
if
I
could
add-
or
you
know
make
you
so
that
I
can
I
can
make
it
better
because
I
think,
just
in
my
experience
it's
been
it's
been
kind
of
rough,
so
but
I
I
can
do
that
at
any
time.
Right
I
could
just
do
the
pull
request.
I
just
feel
like
it's
a
continuity
thing
like
going
from
one
thing
to
another,
not
sure
how
to
okay.
Well,
it
is
documentation,
so
I,
I,
guess
I'm
in
the
right
place.
F
A
I
think
that's
a
great
point
to
bring
up.
I
I
have
heard
folks
as
well
folks
trying
to
get
their
own
local
development
system
set
up
like
on
on
like
on
Windows
itself.
It's
you
know
it's
not
as
well
documented
as
as
well
something
that
we
could
take
a
look
at
into
revamping
or
refactoring
to
to
me
are
taking
your
notes.
There's
no
tracking
issue
yet
and
I
will
create
a
tracking
issue.
A
I'll
create
a
few
tracking
issues
this
evening
or
to
to
to
help
with
the
website's
contribution,
documentation
and
and
I'll
create
that
later
today,.
B
G
This
is
an
opportunity
to
to
look
into
some
of
the
other
tooling
that's
coming
online
things
like
GitHub
code,
spaces
or
or
git
pod
to
try
and
make
the
environment
setup
automatic.
So
all
somebody
would
need
to
change,
is
the
the
documentation
or
is
that
a
little
bit
outside
of
the
scope
of
what
we're
discussing
here.
B
I
think
Nate.
Does
it
like
there's
a
few
options
like
we
have
a
container
setup
that
you
can
do
so
we
explain
to
people
how
to
get
a
preview
working
and
I
wonder
if
there
are
snags
around
okay.
Well,
you've
got
a
preview
working,
but
you
don't
know
how
what
to
do
next
like
right,
and
there
is
also
two
related
issues
like
can
I,
do
the
preview
in
the
cloud
instead
and
can
I
do
the
preview
if
I'm
running
Windows
so
there's
a
whole
I
expect.
B
G
H
I
think
thank
you
for
bringing
this
up.
I
think
this
is
awesome
that
we
are
addressing
this
I.
It's
sometimes
once
you
get
so
far
within
the
tooling
and
the
projects,
it's
hard
to
see
the
gaps
for
new
new
folks
joining,
because
you
get
more
use
of
the
tools.
H
So
you
would
know
what
comes
next,
so
I
think
it's
really
awesome
to
be
addressing
these
issues.
I
did
want
to
say
about
the
new
contributor
meet
and
greet
which
I
know
you
mentioned
yes,
so
that
is
a
monthly
meeting
that
we
have
centered
around
helping
new
folks
if
they
have
questions
and
they
want
to
learn
more
about
the
community
and
they
want
to
take
a
little
more
time
to
ask
very
specific
questions.
H
It's
currently
monthly
I
believe,
but
if
that's
something
you're
interested
I
would
look
forward
to
attending
I
think
it
actually
just
happened
earlier
this
week,
so
something
to
think
about
attending
next
week
or
next
month.
If
you
do
have
more
questions,
I
want
to
hear
more
about
the
new
contributor
experience.
A
All
right,
if
there
are,
are
there
any
other
topics
or
issues
or
PRS
or
questions
that
folks
have
please
bring
them
up.