►
From YouTube: K8s SIG Docs Meeting for 20230502
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
Alrighty,
everyone,
hello
and
welcome
today
is
Tuesday
the
2nd
of
May
2023,
and
my
name
is
Natalie
vodka
I'm
one
of
the
co-chairs
of
Sig
docs
I'm,
also
joined
by
one
of
our
other
co-chairs,
Ray
lahano
who's
on
the
call,
as
well
who's
going
to
be
graciously
taking
notes
today
for
today's
sync
docs
community
meeting
for
folks
who
are
new
or
for
the
folks
who've
been
around
for
a
while.
A
You
might
know
that
this
meeting
takes
place
every
two
weeks
on
a
Tuesday
if
you're
subscribed
to
the
sigdox
mailing
list.
You'll
have
the
invitations
coming
to
you
in
your
calendar
and
as
it's
a
Stig
of
the
communities
project,
meaning
special
interest
group
as
a
kubernetes
project
and
a
group
and
part
of
the
cncf.
A
So
if
you've
got
any
issues
when
it
comes
to
anything
around
code
of
conduct
related
things-
and
you
wanted
to
kind
of
reach
out
to
any
of
us
to
ask
questions
or
you
wanted
to
report
a
violation-
that's
totally
okay
on
the
here
in
the
agenda,
we've
got
a
way
for
you
to
do
so,
where
you
can
reach
out
to
conduct
kubernetes,
dot,
IO
and
you're,
a
no
no
no
limit
will
be
protected
as
well.
A
All
right,
I
wanted
to
get
started.
I
mentioned
that
there
might
be
a
couple
of
new
folks
here.
I
wanted
to
get
started
with,
inviting
those
who
are
new.
If
you
wanted
to
say
hello,
either
in
our
chat
or
to
unmute
yourself,
please
do
so
now
we'd
love
to
welcome
you.
B
Can
you
hear
me?
Well,
yes,
Marcelo
hi
welcome
hi.
Thank
you.
I've
joining
the
last
week,
I
started
to
make
some
commits
in
the
repo
I.
Have
four
PR
opens
awesome.
A
B
A
Great
that's
great
to
hear
welcome
to
the
meeting.
We're
definitely
happy
to
have
you
and
welcome
to
the
community
if
you've
got
any
questions
about
anything
that
you've
been
working
on
so
far.
This
is
definitely
the
place
to
ask,
but
yeah
welcome.
It's
really
really
great
to
have
you.
Thank
you.
A
A
Great
and
ayush
is
that
how
you
we
pronounce
your
name
ayush.
C
A
Excellent
ayush
welcome
to
the
community.
It's
great
to
have
you
thanks
so
much
for
joining,
and,
yes,
it
would
be
great
to
it's
always
great,
to
have
new
contributors
who
are
wanting
to
take
part
in
in
kubernetes
in
the
docs.
A
If
you
haven't
yet,
we
would
definitely
recommend
joining
the
kubernetes
Sig
docs
slack
channel
that
we
have
great
excellent
and
there
we've
got
a
lot
of
pinned
messages.
That'll
help
you
get
started
with
some
of
the
contributions
that
you'd
like
to
make,
so
you
can
definitely
read
up
a
little
bit
more
on
how
to
contribute
there.
C
A
Awesome
thanks
so
much
and
welcome
and
anybody
else
that
wanted
to
say
hello.
A
All
right
going
once,
if
that's
okay,
if
folks,
want
to
say
hi
specifically
in
the
chat,
that's
also
fine,
no
worries.
If
you
don't
want
to
unmute
and
say
hello,
we're
we're
welcoming
of
all
types
of
communication
that
you
wish
to
employ
here
in
zigdocs.
So
great
thanks,
so
much
for
saying,
hi
everyone.
A
What
I
want
to
do
now
is
just
go
on
with
a
couple
of
things
that
we
do
here
as
a
as
somewhat
admin
that
we
do
in
our
in
our
meetings
and
here
in
Sig,
docs
we're
we're
special
interest
groups
that
gets
a
lot
of
contributions,
a
lot
of
PRS
that
come
through
and
to
make
sure
that
we're
driving
these
contributions
through
in
a
really
good
well-paced
way.
A
We
have
a
role
that
we
call
the
pr
Wrangler
and
that's
the
role
of
someone
who's
an
approver
who
can
approve
the
different
PRS
coming
in
that
every
week
we
have
someone
different
on
that
shift
to
try
and
make
sure
that
they
can
push
those
PR's
and
those
contributions
through
our
pipelines
that
we're
keeping
our
numbers
at
a
manageable
level
and
so
that
we're
sharing
also
the
burden
of
the
work
amongst
our
different
approvers
of
the
sick.
A
And
so
with
that
being
said,
this
week's
PR
Wrangler
is
a
tuming
and
one
of
our
tech
leads
and
the
next
piaz
Wrangler
is
Karen.
Another
one
of
our
tech
leads
here
for
sick
Docs,
so
I
mentioned
pringler's
here,
because
if
you're
often
looking
for
approval
or
feedback
on
a
PR
in
a
certain
week,
we
definitely
recommend
that,
if
you're
looking
to
tag
someone,
the
pr
Wrangler
is
always
a
good
person
to
to
get
involved
as
they'll
be
looking
at
PR's
for
the
week.
A
Otherwise,
you
can
always
jump
into
the
stigdocs
channel
and
post
your
pro
issue
there,
and
we
can
also
get
eyes
on
it
in
there
as
well,
but
for
approvals
who
are
on
the
call,
please
make
sure
you
know
your
schedule
and
for
those
who
are
interested
in
a
little
bit
more
of
this
work
and
you'd
like
to
maybe
Shadow
a
PR
Wrangler
for
the
week.
A
You
can
definitely
reach
out
to
anyone
who's
on
the
list
of
the
pr
Wranglers,
that's
linked
here
in
the
in
the
agenda,
and
you
can
ask
them
to
Shadow
for
the
week
where
they
will
set
up
some
time
with.
You
show
you
the
different
tooling,
that
we
use
to
keep
on
top
of
our
different
workloads
and
generally
give
you
generally
give
you
a
rundown
of
how
we
how
our
different
philosophies
as
approve
is
in
terms
of
what
we
push
through
and
how
we
work
with
the
community
goes
on
the
pr
Wrangler
side.
A
So
anyone
interested
in
the
shadowing
front
reach
out
to
the
folks
so
you're
interested
to
Shadow,
and
they
can
help
you
out
all
right.
Moving
on
to
the
next
part
of
our
agenda.
I
wanted
to
note
that
this
part
here
for
new
folks,
we
often
jump
into
speaking
about
the
latest
release
for
communities
kubernetes
releases
three
times
a
year,
and,
and
so
that's
usually
a
four-month
Cadence
in
terms
of
what
we
work
on
for
releases
and
for
those
who
may
know
may
or
may
not
know.
A
We
recently
just
put
out
1.27
for
kubernetes.
It
was
a
really
great
smooth
release
and
the
application
process
for
being
on
the
release
team,
as
a
shadow
actually
closes
today
at
23,
59,
UTC
time
Universal
standard
and
to
be
on
the
release
team
as
a
shadow
means
that
you
would
be
helping
out
with
a
lot
of
the
different
kinds
of
Duties
that
the
release
team
has,
including
specifically
the
docs
lead,
which
is
something
that
we
are
very
very,
very
involved
in
here
with
sigdocs.
A
If
you've
got
any
questions
about
any
of
the
process
that
you'd
like
to
ask
about
or
any
of
the
rules,
Ray
actually
is
a
great
person
to
ask
a
few
questions
of,
as
is
Nate
he's
also
on
the
call
both
who've
been
greater
participants
in
leads
in
the
release
process
previously.
A
But
if
you're
interested
definitely
put
your
application
in
the
worst,
that
can
be
said
is
no
we're
always
willing
to
have
folks
put
in
their
applications
and
and
show
some
interest
and
support,
as
as
we've
got
in
here
and
thanks
Ray
for
adding
in
these
these
great
extra
bits
of
information.
A
The
release
cycle
starts
on
the
15th
of
May,
so
we
are
in
currently
a
period
of
just
like
an
in-between
releases
right
now,
as
we
get
the
release,
the
team
configured
and
put
together
and
Richard
Dudley
will
be
the
doxley
for
this
cycle,
so
that
means
that
our
seek
will
be
corresponding
and
working
really
closely
with
Richard
and
the
Shadows.
That
Richard
will
have
to
make
sure
that
the
docs
for
1.28
are
done
in
an
efficient
and
frictionless
way.
A
A
couple
other
important
roles,
Brad
McCoy,
is
the
1.28
comms
lead.
Comms
lead
is
also
an
important
role
for
us,
given
that
the
Sig
docs
group
also
owns
the
blog
and
the
comms
lead
will
be
doing
a
lot
of
work
on
the
blog
as
well.
So
that's
also
something
that's
of
importance
there
and
thanks
again,
a
big
thank
you
to
Ray
for
linking
on
the
docs
and
comms
roles
handbooks
just
in
the
agenda
there,
for
anybody
who
wants
to
read
Ray
I
just
want
to
double
check
anything
else.
D
No,
that's
pretty
much.
It
I
think
it's
well
covered.
A
Awesome:
okay,
great
now,
let's
move
on
to
the
rest
of
our
agenda.
A
We
have
a
very
short
one
so
for
folks
who
are
on
the
call
that
have
questions
feel
free
to
jump
into
the
agenda
and
add
them
directly
if
you
wish
now
I'll,
also
at
the
end
of
the
meeting,
give
an
open
space
for
folks
who
have
anything
that
they
wish
to
add,
but
vital
I
can
see
you've
jumped
in
and
added
and
created
this
following
issue
linked
here,
based
on
a
previous
meeting
and
I
believe
that
was
specifically
around
what
we
would
possibly
let
slide
in
terms
of
maybe
small
errors
and
things
when
it
came
to
reviewing
and
you
know,
release
deadlines.
E
Yes,
we
hear
you
yes
yeah,
so
yeah,
it's
just
basically
what
Natalie
said
about
but
like
in
the
previous
meeting
as
well.
We
were
not
able
to
like
decide
what
like
what
parameters
could
be?
Actually
let
it
slide
or
not.
E
So
so
anybody
who
is
who's
on
this
call
can
add
their
own
perspective
like
how
much
lags
could
we
allow
a
PR
to
slide,
given
that
it's
accurate
and
and
it's
important
to
get
that
release
out
and
also
I'm,
not
sure
if
I've
written
the
issue
in
a
correct
manner.
E
So
if
you
feel
something
is
like
missing
or
not
clear,
so
feel
free
to
reach
out
to
me
and
I'll
update
it
as
well,
because
it
was
a
long
time
ago
and
I
felt
sick
and
then
I
like
lost
track
because
of
coupons.
So
that's
all.
A
Thank
you
so
much
retail
and,
firstly,
totally
understand
about
losing
track
for
kubecon
I.
Think
there
was
a
few
of
us
cubecon
Europe
that
have
experienced
the
same,
but
big.
Thank
you
for
putting
this
issue
together.
I
know
we
had
a
really
involved
conversation
around
what
parameters
we'd
be
interested
in
in
terms
of
what
things
can
slide
and
what
shouldn't
I
do
remember
really
distinctly.
We
spoke
a
lot
about
also
spelling,
spelling,
specifically
and
I've
I,
think
I
think
Chris
Metz,
you
might
be
on
the
call.
A
I've.
Definitely
I've
definitely
come
around
a
bit
to
thinking
that
you
know.
A
lot
of
misspelling
is
probably
not
the
greatest
greatest
thing
to
be
able
to
letting
slide
through,
but
at
the
same
time,
I'm
super
open
to
the
rest
of
the
community's
thoughts
on
that
anybody
wanted
to
jump
in
and
add
any
further
comments
around
this.
A
For
the
release,
shutter,
yes,
I
believe
there
is,
there
is
a
little
bit
of
criteria,
but
the
main
one
is
that
you've
read
the
actual
role
handbook.
That
is
a
big
definite
criteria
and
we've
linked
them
specifically
here
in
the
how
to
say
in
the
agenda
here
on
the
docs
roll
that
I'm
just
highlighting
in
the
agenda,
if
you
can
see
there
and
in
the
comms
role
as
well.
So
a
big
criteria
is
that
you've
read
these
the
roles
that
you
are
applying
to
be
a
shadow
for.
A
Not
you
don't
have
to
be
a
kubernetes
member
to
be
on
the
release
team,
the
kubernetes
member
you
don't
need
to
be,
but
you
do
have
to
have
read
the
handbook
and
that
information
is
in
the
handbook
there
for
you
as
well.
A
Of
course,
I
wanted
to
just
go
back
to
the
issue
that
we're
at
hand
with
vittel's
info
around
the
guidelines
for
what
we're
willing
to
let
slide
when
it
comes
to
review
anybody
if
I
just
put
this
back
on
the
screen
on
the
on
the
issue
here,
anyone
have
any
further
comments
or
things
I'd
like
to
add
to
this
discussion.
D
D
For
a
few
reasons,
a
a
if
the
author
of
the
pr
has
not
come
back
to
your
to
address
comments.
Those
mistakes
can
be
fixed
in
a
follow-up
PR.
They
could
also
be
good
first
issue
as
well.
D
There's
also
some
some
some
basic
things
that
we
we
could
also
be
more
strict
on.
You
know
like
like
spelling,
but
maybe
like
perfect
grammar,
isn't
isn't
required.
So
those
are
just
some
examples:
I'm,
okay,
with
with
letting
some
PR's
merge.
If
the
sound
guy
is
not
perfectly
followed.
D
A
Cool
I've
tried
to
I've
tried
to
capture
that
in
that,
in
that
note,
there
ready
feel
free
to
hit
it
if
needed,
but
I
I
actually
I
also
agree
with
you
around.
This
idea
of
you
know
if
it's
an
improvement
to
the
docs,
but
I
do
think
that
this
idea
actually
may
be
a
little
bit
vague
for
folks
who
are
you
know,
first
time
or
like
not
many
time,
PR
authors
and
maybe
the
newer,
reviewers
and
so
on,
and
so
this
idea
of
does
it
improve
the
docs?
B
I
have
a
question
sure
Mozilla.
So
so
far
my
PRS
have
are
deal
with
existing
content
so
where
I
go
and
fix
them,
something
I
have
they're
they're
all
based
on
open
issues,
so
somebody
detected
an
error
and
go
and
fix
it.
But
what
about
contributing
when
it's
a
feature
request
when
you
want
to
continue
a
new
document,
a
new
page
in
the
site?
Are
there
existing
templates
where
you
can
start
off
a
template?
Let's
say
that's
at
your
template
and
you
you
start
with
that.
B
A
D
At
the
hierarchy
of
the
layout
as
well,
there's
Concepts
there's
task.
There's
reference
documentation
as
well.
I,
don't
know
if
he
act,
we
we
don't
keep
I,
don't
think
we
have
templates
in
for
a
brand
new
page,
but
the
style
guide
has
the
information
on
like.
D
D
B
A
B
A
But
you
you're
talking
about
templates
for
the
website.
Yes
for
the
website,
gotcha,
yeah,
yeah!
Sorry,
because
I
heard
you
say
when
you're
looking
through
the
issues
and
then
I
was
confused
there,
which
is.
C
B
C
B
I
got
that
question
from
one
of
my
PRS.
The
pr
Wrangler
asked
me.
B
You
added
these
tags
and
I've
seen
it
written
differently
and
I
went
to
the
Hugo
that
has
a
guide
for
short
shortcuts
and
I
I
noticed
that
they
were
correct,
so
I
linked
the
page
of
the
Hugo
temp,
the
code
shortcuts
and
I
posted
that
to
the
prank
to
see
look
I'm
I'm
using
the
what's
in
the
guy
in
the
style
guide
from
Hugo,
so
I
believe
it's
correct,
but
he
wasn't
sure
because
he
said
I've
seen
this
written
differently.
A
Yeah
yeah
I
think
also
we
have
a
style
guide
to
make
sure
that
there
is
some
I.
We
want
to
I
want
to
say
consistency,
but
because
we
are
many
people
from
a
lot
of
places
in
the
world,
contributing
it's,
it's
more
about
understanding
the
ease
of
being
able
to
use
and
interpret
the
docs,
and
so
there
may
be
little
small
inconsistencies.
That
way,
because
of
some
of
some
of
this,
so
a
star
guide
is
definitely
meant
to
try
and
create
that
consistency.
A
But
in
the
issue
that
we're
just
speaking
about
and
on
the
topic,
we're
just
speaking
about
we're
there
talking
about
what
are
we
willing
to
accept,
as
maybe
Divergence,
especially
if
we
need
to
push
through
certain
changes
for
release
as
an
example?
And
what
things
are
we
willing
to
deviate
on
and
be
a
little
less
strict
on
and
and
why
but
yeah
I
think
you've
brought
up
a
great
Point.
A
We
I
want
to
just
I
want
to
take
the
meeting
now,
I
think
I,
don't
think
anyone
else
has
any
questions
specifically
on
the
topic
we're
just
speaking
about,
which
is,
if
you
tell
your
issue
around
the
guidelines
there,
so,
firstly,
a
big
thanks
to
vital
for
writing
up
that
issue
and
for
any
further
comments.
Please
go
to
the
issue
itself
around
the
guidelines
of
what
we
would
be
willing
to
pass
or
not
on.
If
something
is,
is
pending
a
release
but
yeah
Marcelo
I.
Think
that's
a
great
point.
A
Also
echoing
Ray,
possibly
having
a
template
is
a
good
idea.
My
one
concern
is
getting
too
granular
in
the
template.
You
mentioned
things
like
how
do
we
highlight
code
or
so
on?
A
I
do
want
the
style
guide
to
still
actually
be
a
reference
point
for
folks,
too,
and
so
I
think
a
lot
of
those
aspects
should
belong
in
a
style
guide
versus
an
overall
template
that
you
start
with,
since
templates
with
a
lot
of
info
can
also
be
overwhelming
too
so
I
feel
like
there's
a
there's,
a
there's,
a
room
there
to
figure
out
what
goes
in
the
template
versus
how
you
should
interpret
the
style
guide
as
well.
She.
A
Exactly
yeah
but
yeah
great
idea
in
terms
of
something
that
we
could
possibly
add
in.
That's
something
that,
if,
if
you
would
like
to
write
up
an
issue
for
this
of,
we
should
create
a
template
for
for
four
pages
on
the
site.
That's
something
that
we
can
triage
and
folks
can
also
contribute
to.
A
Great
now
that
we've
moved
on
from
our
one
agenda
item
I
wanted
to
check
if
anyone
else
has
any
questions
or
issues
or
PR's
that
they'd
like
to
bring
up
or
chat
about
here.
In
today's
meeting.
G
Since
we've
got
a
fresh
match
on
the
line,
I've
seen
I've
taken
a
look
at
your
I
believe
it's
the
the
networking
node
PR
with
updated
diagrams
and
I
just
want
to
say
that's
a
it's,
a
a
big
PR.
G
Is
there
a
way
and
I'm
sorry
I,
don't
have
the
link
to
it?
Maybe
Chris
you
you've
got
it
but
I
wonder
if
there's
a
way
of
breaking
it
up
to
make
it
smaller
and
easier
to
review,
or
is
that
maybe
not
what
your
plan
is
for
that
particular
set
of
updates.
F
F
You
know
you
need
to
put
a
little
explanation
into
it,
but
I
understand
that
it
can
get
a
little
bit
too
wordy
number
two
I
have
I
continue
to
trim
that
down
almost
daily
I
did
it
yesterday,
I
did
it
today,
I.
F
Right
right
so
I
understand
that
it
we
don't
want
it
to
be
too
wordy,
and
you
know
present.
You
know
like
a
wall
of
text,
so
to
speak,
so
I'm
really
efforting
to
try
and
you
know,
bring
that
down
to
something.
That's
consumable
and
and
I'll
take
that
into
account
as
well
Nate
and
when
you're
ready
to
review
and
I
hope
to
have
it
done
by
tomorrow.
F
Please
everybody,
you
know
if
you
think
it
is
too
wordy,
then
let's
figure
out
a
way.
We
can.
You
know
better
present
and
again,
there's
there's
four
aspects
of
this
network
model
and
each
of
them
have
their
own
little
sort
of
intricacies
and
we're
just
going
with
the
example
approach.
So
we
don't
have
to
go
through
any
possible
iteration.
But
yes,
word
received
and
I'll
I'll
strive
to
make
this
as
a
simple
readable
and
as
possible
and.
G
I,
wonder
too,
if,
like
I
I
want
all
the
information
there,
because
it's
all
good
right
but
I'm
wondering
if
and
again
I
haven't
I
haven't
looked
at
the
the
updates
from
yesterday
or
today,
but
in
lieu
of
of
dropping
stuff
out
and
wondering
once
we
like,
don't
don't
don't
lose
it,
it
might
be.
It
might
be
good
content
for
a
sub
page
later
later
time.
G
But
if
you
made
updates
I'll
take
another
look
at
it
and
I
think
I
think
Sig
network
has
already
been
paid.
So
hopefully
we
can
get
a
technical
review
in
there
fairly
quickly
as
well.
F
Absolutely
absolutely
and
yet
I
I
I'm
looking
to
have
this
thing
done
by
tomorrow
morning,
so
I
just
finished,
the
penultimate
section
and
I'll
hope
to
have
the
final
section
done
tomorrow.
Awesome
appreciate.
F
It
looks
great
so
far,
absolutely
and
hey
thanks
for
the
input
Nate
really
appreciate
it.
A
Thanks
Nate
and
thanks
Chris
I
wanted
to
now
actually
Michelle
you
would.
You
and
I
were
just
chatting
in
the
chat,
but
I
wanted
to
see
if
your
audio,
if
you
wanted
to
give
it
a
try
now,
if
your
audio
might
be
working.
A
And
I'm
not
hearing
you
I'm,
not
sure
if
anybody
else
is
on
the
call,
but
Michelle
has
a
question
in
the
chat
that
I
wanted
to
yeah
I'm,
sorry
Michelle.
Hopefully
we
can
get
it
fixed
for
the
next
time,
but
I
wanted
to
ask
you
a
question
in
the
chat
that
you've
got
here
about
the
1.25
blog
post
on
deprecations,
where
you
say
that
the
volume
of
decorifications
is
not
necessarily
accurate
and
you
wanted
to
correct.
A
We
allow
updates
on
order
blog
posts
I'm
going
to
let
a
Blog
person
Nate
here
answer
this.
Yes,.
G
So,
yes,
absolutely
if
there's
something
that
is
technically
incorrect,
please
we
would
very
much
appreciate
a
a
PR
correcting
it
in
the
case
of
blog
posts,
generally,
anything
that's
less
than
a
year
old,
we're
willing
to
to
correct
and
update,
and
in
this
case
the
process
would
probably
be
something
like
you
would
open
up
a
correct
NPR
and
we
would
probably
invite
the
original
authors
to
review
just
to
make
sure
that
things
are
are
still
starting
with
they
intended
to
say.
A
Great
thanks
thanks
Nate
and
thanks
for
asking
a
question
Michelle
I
would
I
do
want
to
state
that
we
do
have
this
General
policy
of
if
a
blog
is
a
year
or
older,
we
generally
don't
update
them
unless
there's
technical
inaccuracies
that
need
to
be
fixed
as
Nate
mentioned.
So
that's
the
general
tldr
for
sure
thanks
so
much
okay,
do
we
have
any
further
questions
that
anyone
might
have
that
they'd
like
to
bring
up
as
we've
reached
the
end
of
our
agenda
for
today.
A
Oh
Marcelo
I
can
see
you've
got
a
question
in
the
chat
too.
What
are
the
meaning
of
the
labels
at
the
top
of
sub
documents?
Future
State,
you
know
kubernetes
version
1.15
stable.
My
quick
answer
for
you
and
I'll.
Let
someone
else
jump
in
is
that
that
is
the
version.
That
is
the
release
that,
in
this
example,
that
you've
given.
A
That
is
the
version
that
this
specific
feature
has
become
stable
in
in
kubernetes,
and
that
means
that
we
have
features
that
go
Alpha
and
beta
and
they
graduate
as
well,
and
the
stability
is
basically
what
we're
aiming
for
for
features
to
become
as
an
example
but
Ray.
If
you
wanted
to
expand,
please
go
for
it.
D
Yeah,
that's
exactly
it
that
we
Mark
the
the
graduation
status
for
the
feature,
so
you
might
see
Alpha,
Beta
or
stable
in
a
feature
on
the
documentation
and
if
it's
stable,
we
keep
it
there
with
the
version
that
where,
when
that
enhancement
or
feature
became
stable
or
graduated.
D
D
The
graduation
criteria
from
like
Alpha
to
Beta
beta
to
to
graduate
to
stable
that
the
enhancement
has
stated,
and
that's
all
listed
in
the
what
we
call
the
kubernetes
enhancement
proposal
and
once
that's
all,
it's
been
satisfied
once
it's
code
completes,
then
then
the
the
corresponding
Sig
and
the
contributors
will
typically
make
the
update
to
the
documentation
website.
A
Yeah
I
think
it's
important
to
note
that
it's
not
us
as
a
Sig
here
in
docs
making
that
decision,
it's
the
it's
the
group
who
is
creating
that
feature
itself
and
working
on
it
too.
We
as
docs
maintainers
here
for
the
kubernetes,
are
trying
to
keep
on
top
of
when
features
do
graduate
if
our
docs
are
updated
for
this
information,
but
it
is
not
up
to
us
in
Sig
docs
to
decide
on
when
features
graduate
is
feature
authors
and
that
comes
from
other
sigs
other
contributors
in
the
in
the
community.
A
B
A
You're
welcome
Ray
was
mentioning
what
we
call
the
kubernetes
enhancement
process,
enhancements
process
or
enhancement
proposals
or
cap
you'll
hear
for
short
kep.
A
That's
definitely
something
that
is
I
would
say
in
the
kubernetes
lifecycle,
generally
still
modern,
as
a
as
a
concept
and
tool
that
we
use
for
our
releases,
but
there's
a
lot
more
information
in
the
enhancements.
The
Proposal
work
Marcelo.
That
might
be
very
useful
for
you
to
read
to
understand
why
we
apply
labels
like
this
and
why
there
are
certain
things
in
the
docs
that
are
labeled
the
way
they
are
for
sure.
A
A
Welcome
all
right,
this
will
be
the
last
call
out
for
any
further
questions
or
issues
or
PR
that
folks
want
to
bring
up
before
we
bring
today's
meeting
to
a
close.
B
Thank
you.
The
last
one
I've
encountered
several
times
issues
with
Hugo
and
timing
out,
I
posted
in
team
bannister's
as
a
issue
open
to
it.
I
posted
that
this
happened
last
night.
It
was
supposed
to
be
fixed
with
the
latest
update,
but
still
happening
as
of
last
night,
with.
A
The
latest
version,
unfortunately,
the
timeouts
are
something
that
have
plagued
docs
for
quite
some
time.
You
are
not
the
first
contributor,
nor
will
you
be
the
last
to
experience
this.
Unfortunately,
this
is
something
that
needs
to
be
fixed
on
Hugo's
end.
It's
not
it's
not
an
issue
that
we
ourselves
can
only
address,
and
it's
it's
it's
something
that
has
been
plaguing
us
for
some
time.
A
There
is
an
issue
that
was
opened
up
a
while
back
about
being
able
to
try
and
try
and
fix
some
of
this
work,
and
we
have
done
some
attempts,
but
unfortunately
this
is
something
that
does
plague
us
a
little
Marcelo
so
I'm.
Sorry,
we
all
feel
your
pain.
B
And
I
pointed
it
out
because
in
the
issue
was
some
people
were
saying
it's
it's
fixed
in
the
latest
version
because
we
bumped
it
to
the
newest.
But
it's
still
happening.
A
That
that's
good
feedback.
You
know
and
that's
something
that
we'll
try
and
have
a
look
at
and
keep
an
eye
on.
If
there's
a
let's
say
claims
of
it
being
fixed,
but
not
so
and
figure
out
what
we
can
try
and
do
there.
But
thank
you
for
bringing
that
up.
Unfortunately,
not
a
new
issue,
something
that
we're
struggling
with
for
a
little
while.
A
Okay,
so
it
caps
information.
If
you
just
go
into
the
chat
Marcelo
and
whoever
else
is
interested
in
reading
up
on
our
enhancements
proposal
process,
you
can
do
so
there.
A
lot
of
great
information
as
a
tldr
caps
are
what
we
use
to
actually
introduce
new
features
into
kubernetes
and
thus
be
able
to
work
on
them,
and
docs
are
always
going
to
be
most
for
the
most
part,
either
if
they're,
auto-generated
or
not
I'm,
going
to
be
for
the
most
part
involved
in
in
creating
new
features
and
kubernetes
as
well.
A
So
we
are
often
very
much
involved
in
a
lot
of
those
processes
too,
but
generally
I
wanted
to.
Firstly
apologize
to
my
cat
playing
for
a
tour
in
the
background.
If
you
can
hear
that
but
say
a
big
thank
you
to
folks
who
have
participated
in
today's
meeting
and
for
all
your
great
questions.
A
Thanks
to
our
newcomers,
who
have
asked
some
questions
as
well
and
for
welcoming
I'm,
saying
hi
and-
and
hopefully
we
can
welcome
you
to
Future
meetings
as
well.
And
finally,
if
you've
got
any
further
questions
that
were
answered
here
today,
you
can
always
come
to
the
Sig
doc,
slack
and
post
your
question
there.
A
We
do
try
and
have
also
slack
meeting
updates
on
the
off
weeks
that
we
don't
have
Community
meetings
on
so
we'll
try
and
make
sure
that
we
do
a
slack
thread
meeting
for
next
week
as
well
other
than
that
I
hope.
Everyone
enjoys
the
rest
of
their
day
wherever
they
may
be
in
the
world
or
a
great
next
day,
if
you're,
some
of
our
folks
joining
from
the
Apec
region,
I
know
it's
quite
late
for
you,
but
thanks
again
for
joining
and
we'll
see
you
at
the
next
one.
Thank
you.