►
From YouTube: K8s SIG Docs Meeting for 20200908
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
All
right,
we're
recording
hello.
Everyone
today
is
tuesday
september,
8th
2020,
and
this
is
the
weekly
meeting
of
kubernetes
sig
docs.
I
think
what
is
it
like
the
154th
of
march?
Something
like
that
all
right?
Let
us
start
as
we
always
do
by
saying
hello
to
new
folks
or
folks
who
are
new
to
us.
So
matt
you
look
familiar,
I'm
assuming
this
is
not
your
first
time
to
the
docs
radio.
B
A
You
any
particular
areas
of
interest.
B
A
Excellent,
there
are
always
lots
and
lots
of
opportunities
to
triage
open
issues
that
haven't
been
does
an
amazing
job,
but
the
flow
is
never
ending
so
yeah
and
if
you
look
for
issues
tagged
with
good
first
issue,
they
tend
to
get
snapped
up
quickly,
but
that's
another
place
if
like.
If
you
want
to
actually
get
started
or
if
you
just
want
to
lurk.
That's
fine
too.
B
C
A
A
So
probably
not
a
ton
of
updates
there
svita,
I'm
guessing
that
this
is
you
to
add
milestone.
Maintainers
access
for
release,
shadows.
D
Yes,
so
anna
couldn't
be
here
today,
so
I'm
just
speaking
on
our
behalf,
or
maybe
I
have
to
both,
so
it
will
be
great.
So
the
least
themed
shadows
generally
have
a
milestone,
access
to
the
reports
and
for
dogs.
We
don't
give
milestone
access
to
the
shadows,
which
puts
the
load
on
the
pr
angler
or
the
lead
or
someone
who
taxes.
D
D
It
came
out
during
our
retrospective,
so
we
just
start
we'll
bring
it
up
here
to
see
how
sick
dogs
feels
about
it.
Is
it
okay
or
is
there
a
reason
that
it's
not
there?
The
actress
is
not
given
any
reason.
A
Sure,
thoughts
on
this
from.
A
A
E
Need
to
remember
to
remove
that
access
at
the
end
of
every
release
cycle,
but
that
seems
like
a
release.
Handbook
thing.
D
D
D
D
The
life
cycle
was
really
good.
There
was
an
integration
between
the
sig
release
and
the
release
team
and
the
dog
stick
dogs.
It
was
good,
I
feel
like
it
was
one
of
the
reasons
that
it
was
very
smooth
process,
so
we
are
trying
to
incr
incorporate
more
things
like
that
and
I'm
going
to
add
those
things
to
a
handbook.
D
Next
week,
I'll
come
back
with
margin
of
stuff
once
on
us
here,
it's
all
and
I'll
add
that
whatever
celeste
stole
to
the
handbook,
so
it's
good
clean
it.
Thank
you.
A
Thanks
yeah,
I
don't
see,
I
think,
adding
duck
shadows
to
sorry.
Let
me
restart
that
thought.
Giving
milestone
command
access
to
doc
shadows
makes
perfect
sense
to
me.
There's
there's
no
reason
to
to
hoard
that
privilege
in
one
place.
D
There
are
the
previous
leads
you
are
in
website
maintenance
or
some
some
places.
Do
you
want
me
to
clean
it
up
too?
I
will
add
a
note
to
the
handbook
so
that
the
new
lead
plan
clean
up
the
old
leaf.
How
does
that
work
like
honestly,
like
I'd
like
to
be
helped
with
pr
anglerships,
because
this
is
where
I
started
out,
and
this
is
like
I
feel
like
home,
so
I
want
to
be
helping,
but
I'm
not.
D
I
just
want
to
make
sure
that
in
this
need
that
we
need
to
clear
it
out
in
the
handbook
that
once
you
services,
some
things,
are
expected
out
of
you,
and
this
is
one
such
thing
or
I
see
folks.
I
I
just
want
to
ask
it's
it's
not
it's
not
that
I
need
to
get
an
answer
immediately,
but
I
thought
I
just
asked.
We
need
to
clear
the
other
stuff.
Wherever
we
provide
access
to,
there
will
be
provide
delete
access
too.
F
And
I
can
add
a
little
bit
to
that
as
well.
I
know.
Historically,
the
approver
access
has
remained
in
the
leads
possession,
for
you
know
pretty
much
until
they've
either
became
inactive
or
continued
doing
work
there,
and
I
know
from
a
release
perspective
they
like
to
keep
the
permissions
of
the
previous
lead
for
at
least
the
duration
of
the
supported
cycle.
So,
while
119
is
out
now
you
should
remain
in
your
release.
A
Thank
you,
sabita
okay,
chair
transition,
so
the
time
is
upon
us
september.
15Th
is
the
day
that
I
said
months
ago
that
I
would
be
promoted
to
chair
emeritus,
whatever
whatever
language
we're
using
to
talk
about
that,
but
yeah
promoted
to
chair
emeritus
and,
of
course,
now
the
rubbish
truck
decides
that
it's
going
to
rear
its
head.
One
moment.
A
To
deal
with
the
formal
governance
piece
of
a
transition,
I
am
giving
notice
that
I
am
stepping
down
his
chair
and,
as
is
allowed
in
governance,
I
am
nominating
my
replacement
and
I
am
nominating
irvi
aimee
ervy
has
been
a
chair
shadow
for
almost
three
months
now
and
irv
has
been
a
localization
lead
for
a
lot
longer
before
that.
So
I
have
lots
and
lots
of
advice
to
give,
but
the
last
thing
I
want
to
do
with
a
weekly
meeting
is
give
it
all.
A
Be
kind
to
each
other,
I
think
that's
where
we've
succeeded
the
most
and
where
we
succeed
the
most
as
people
who
do
docs
is
ultimately
the
the
thing
that
lets
us
know
that
we
succeed
is
when
we
make
someone
else's
lives
a
little
easier
when
we
make
it
easier
to
learn
how
to
use
kubernetes
when
we
make
it
easier
to
find
particular
commands
when
we
make
our
search
better
when
we
make
our
ux
better.
A
All
of
these
things
aren't
in
service.
Docs
don't
exist
for
the
sake
of
docs.
They
exist
to
help
and
when,
when
we
help
and
when
we
approach
the
work
that
we
do,
knowing
that
it's
a
it's
helping
work,
it
makes
all
the
difference.
A
So
I
think
that
the
moments
that
I'm
proudest
of
as
a
chair
are
the
moments
when
I
helped
in
ways
great
or
small
and
the
moments
of
which,
I'm
least
proud
are
those
where
I
forgot
that
what
we
do
is
helping
work.
So
thank
you
to
everyone.
A
You've
been
amazing
and
the
reason
that
I'm
saying
all
this
now
is
because
I'm
not
going
to
be
here
next
week,
I'm
taking
vacation.
So
this
is
my
last
meeting
as
a
sigdoc's
chair,
so
I'll
be
around
as
an
approver
afterwards.
So
I'm
not
going
away,
I'm
stuck
with
me,
but
yeah.
It's
in
the
kubernetes
community
values.
A
One
of
the
values
is
that
evolution
is
better
than
stagnation
and
we
should
expect
folks
who
are
new
to
step
up
into
leadership,
and
we
should
expect
folks
who
are
current
in
leadership
to
step
out
and
make
room.
So
it's
me
doing
my
part
cool
the
other
piece
associated
with
an
actual
governance
transition.
The
last
sorry,
air
quality,
so
high,
we'll
open
an
issue
in
the
kubernetes
website,
similar
to
18117.
A
A
So
I'm
happy
to
open
that-
and
I
will
do
that
sometime
this
week-
okay
and
that's
it
for
governance.
Let's
talk
about
prs
and
issues
so
tim.
I
saw
that
you
reopened
issue
12303
and
that's
due
to
someone
coming
into
slack
and
saying
hey
what
happened
to
the
release
1-14
docs?
Why
can't
I
find
them?
I'm
getting
a
certificate
error.
A
Yeah
so
there's
a
more
graceful
way
to
do
that
and
I
think
returning
an
http
410
is.
A
The
the
correct
response
here
so
like
technically
it's
it's
trivial
to
set
up.
We
just
add
a
line.
I
think
we
can
do
it
in
a
single
line
for
the
entire,
the
entire
release
branch
to
the
subredirects
file.
A
But
I
wonder
if
there's
a
way
to
automate
that,
because
right
now
adding
that
it's
going
to
be
branch
dependent
and
if
we
add
it,
it
will
basically
turn
into
an
increase,
a
block
of
increasing
size
in
that
redirects
file
that,
as
we
accrue
deprecated
release
branches,
that
branch
will
also
grow
longer.
So
I
wonder
if
there's
a
way
to
automate
that
piece
of
toil
it's,
you
know
one
less
thing
for
a
release
lead
to
track
during
doc's
release
cycle.
E
C
A
A
No,
so
the
way
that
netlify
is
set
up
there
is
a
separate
site.
We
serve
each
release
branch
as
a
separate
site.
So
when
a
branch
is
deprecated,
we
go
to
netlify
and
remove
like
delete.
That
instance.
E
E
G
A
Okay,
so
this
is
what
our
base
group
looks
like
in
that
lafaye,
so
you
see
that
basically,
all
of
the
subdomains
that
serve
content
from
subdomains
on
kubernetes.io
have
their
instances
here
as
well,
but
here
here's
the
here's,
what
it
looks
like
in
that
lafayette.
This
is
the
1.17
docks
and
little
118
docks
things
like
that,
so
1.15
docs.
A
Basically,
what
we
do
is
we
come
in
right
now.
Is
it?
Let
me
go
back,
it
is
site
settings
come
in
here
and
delete
the
site,
so
that
is
how
the
actual
removal
happens.
A
E
Not
about
it
410.
I
don't
know
about
that.
However,
that
netlify
does
have
an
api
for
deleting
sites,
so
we
can
automate
that
portion
of
it
just
by
talking
to
the
api,
the
four
would
netlify
have.
E
It
has
like
redirect
abilities
and
stuff,
but
I
believe
those
are
set
via
netlify.tomml,
so
it
would
still
be
like
going
in
and
editing
a
file.
G
C
Outcome
that
we
want
is
that,
no
matter
what
old
version
of
the
docs
you
visit
it
works
include
if
you
visit
kubernetes.org,
you
always
get
the
current
docs
and
if
you
visit
an
archived
version,
even
after
we've
stopped
providing
the
actual
documentation,
you
get
some
sort
of
thing.
C
We
could
do
that
with
netlify
by
creating
a
new
site
called
docs
removed
or
something
and
then
giving
it
14
aliases
for
one
for
each
of
the
versions
of
docs
that
we
no
longer
serve
and
every
release.
We
add
an
alias
sorry,
go
ahead.
That
was
it.
F
I
I
do
think
we
might
introduce
just
kind
of
dak
rat
and
some
sort
of
problems
by
supporting
or
keeping
those
old
docs
published.
I
know
we
have
a
general
policy
of
you
know.
We
support
five
of
the
latest
releases.
F
It's
why
we
removed
the
one
I
could
see,
maybe
a
redirect
or
an
alias,
pointing
to
either
the
current
doctor,
something
that
doesn't
break
the
url
in
case
somebody
finds
that
url
somewhere
out
in
the
wild,
but
I
think
if
we
leave
them
up
and
running
we're
giving
ourselves
potentially
security
risk,
potentially
old
docks,
pr's
getting
opened
up
on
branches
that
are
beyond
support.
I
don't
know
if
that's
the
the
correct
place
you
want
to
get
into
sorry
go
ahead.
Brad.
C
F
F
Yeah
yeah,
I
would
be
up
for
that
now.
I
don't
know
if
there
would
be
a
trade-off
between
some
sort
of
either
redirect
to
the
main
page
versus
hosting
it
gone
page,
but
you
know,
I
think
that
that
makes
sense.
A
I
mean
we
could
so
there's
no
good
reason
why
we
couldn't
have
an
alias
that
redirects
to
like
a
custom,
410
page
saying
not
here.
Okay,
so
it
sounds
like
there's.
A
A
I
I
would
hate
for
the
lack
of
perfect
automation
to
get
in
the
way
of
a
good
solution.
A
So
I
wonder
if
we
can
start
by
adding
a
block
to
the
current
redirects
file
for
basically
all
of
the
previous
versions
that
will
serve
at
410.
C
The
site
from
netlify
netlife
doesn't
know
which
of
the
other
kubernetes
websites
it
might
go
and
look
from
the
cooper
configuration
from
fair.
C
A
It's
one
of
the
things
that
I
love
about
this
sick
we've
never
done
it
before.
Why
should
that?
Stop
us
excellent!
Well,
do
you
want
to
do
you
want
to
take
a
stab
at
that.
C
Yes,
so
what
I
propose
to
do
I'll
listen
to
see
if
there
are
some
different
opinions
on
on
an
approach,
but
if,
if
this
is
roughly
consensus,
I
will
pick
up
the
issue
that
we're
discussing
one
two:
three
three,
I'm
gonna
not
mark
it
rotten
and
I'll,
add
some
comments
and
I'll
aim
to
pick
that
up.
A
Awesome,
thank
you
tim
all.
Right
and
tim.
I
see
also
you
have
something
about
the
redesign
of
the
api
reference
stacks.
C
Yep,
so
philippe
martin
is
a
google
summer
of
docs
season
of
docs
person
and
tomorrow,
if
he
was
on
this
call,
he'd
have
had
a
chance
to
come
in
more
directly
but
no
worries
tomorrow,
I'm
going
to
catch
up
with
philippe
and
talk
through
what
that's
involved
and
have
a
sort
of
kickoff
conversation.
C
I
guess
if
anyone's
got
any
feedback
comments
they
want
to
put
in
that.
Can
I
don't
know
the
issue
number
sorry,
but
I
can
find
it
if
people
want
to
contribute
if
it's
particularly
important
or
you
can
search
or
you
can
talk
now,
the
work
that
philippe
is
is
looking
at
is
improving.
How
we
render
the
api
reference
documentation.
That's
currently
there
we
auto
generate
it
from
upstream.
C
Doxy
also
has
its
own
view
of
how
to
take
open
api
documentation,
and
I
think
you
know
the
outcome
is
to
take
the
best
of
both
worlds
and
and
improve
the
experience
as
much
as
we
can.
C
Well,
I
have
not
the
kickoff
yet,
but
I
think
I
think
what
we
know
is
that
doxy's
approach
on
its
own
looks
at
the
kubernetes
specification
and
goes.
You
know
there's
way
too
much
information
to
decode
the
matrix.
A
I
wish
I
would
have
to
go
digging
to
find
the
url,
but
philippe
has
already
built
a
site
that
basically
serves
the
kubernetes
api
reference
in
a
pretty
fashion,
with
a
different
hugo
theme
and
philippe's
first
question
was
whether
or
not
it
would
be
possible
and
or
desirable
to
import
that
experience
into
the
website.
Repo
and
my
response
to
that
was
no,
because
it
creates
a
site
within
a
site
the
the
experience
of
maintaining
that
particular
construction
and
delivery
of
reference
content.
A
It
doesn't
really
play
nicely
with
the
rest
of
our
existing
site
configuration,
and
so
I
want
to
make
sure
that
whatever
we
adopt
doesn't
automatically
incur
technical
debt
simply
by
nature
of
its
existence
and
like
starting
with
the
the
starting
from
a
premise
of
this
is,
unlike
anything
else
on,
the
website
has
not
historically
led
to
hugs
and
puppies.
C
C
Are
there
any
qualities
that
it's
important
that
the
api
documentation
has
or
that
we
that
are
nice
to
have
but
important
nice
to
have.
E
The
answer
to
that
is
probably
yes,
but
not
that
I
am
prepared
to
do
so
now.
C
Cool
so
possibly
static
site,
rendering
versus
javascript
could
be
a
consideration
because
not
every
search
engine
renders
javascript.
C
G
Well,
I
have
one
right
before
this
agenda
closes
and
if
this
is
your
last
meeting
as
chair,
I
just
want
to
say
thanks
zach
I've
known
you
for
several
years.
You
know
I
don't
know,
maybe
I
don't
know
compared
to
other
folks.
I
don't
know
who's
known
you
the
longest
in
your
chairl.
I
think
it's
me
you've
always
made
sig
docs
a
wonderful
working
environment,
a
place,
a
great
community.
It's
one
of
the
reasons
why
I
kept
showing
up
is
because
it
was
just
such
a
wonderful
place
to
participate
and
contribute.
G
A
E
G
Do
we
have
any
idea
what
the
next
adventure
is
or
is
that
still
under
wraps.
A
It's
mostly
on
to
other
cncf
projects,
sort
of
expanding
outward
and
across.
A
Cool
well,
let's
do
the!
Let's
close
it.