►
From YouTube: Kubernetes SIG Docs Meeting for 20210216
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
Hello,
everyone
today
is
tuesday,
the
16th
of
february
2021,
and
this
is
the
weekly
meeting
of
kubernetes
sig
docs,
I'm
tim
banister.
I'm
gonna
run
this
meeting.
I'm
a
tech
lead
if
anyone's
new
here
now's
a
great
time
to
introduce
yourself,
I'm
going
to
put
a
link
to
the
agenda
in
the
chat,
and
everyone
should
be
able
to
see
that.
But
if
you
yeah,
if
you've,
if
you've
not
spoken
before-
and
I
don't
recognize
everyone
here-
please
pipe
up
and
feel
free
to
say,
hi.
A
A
Carmel,
if
you
can
hear
me,
feel
free
to
put
something
in
the
chat,
we're
not
hearing
you.
I
don't
think.
B
A
Thank
you
ray.
I'm
gonna,
move
on
to
updates
and
reminders.
This
week's
pr
wrangler
is
jim
angel,
who
is
in
texas
with
no
electricity
but
we'll
be
wrangling
at
appropriate
junctures
and
next
week's
is
kellen
barnard
and
if
you're
approver,
you
have
to
know
your
angular
shifts.
That
is
a
good
idea.
A
Let's
move
on
to
hello
celeste,
let's
move
on
to
the
release
docs
update,
please.
B
All
right
so
last
week
was
a
big
day.
We
had
an
enhancement
spree,
so
I
have
a
lot
to
go
over.
I'm
currently
saying
that
the
status
is
yellow,
because
we
have
many
enhancements
that
that
have
not
indicated
if
they
do
need
docs.
Yet
the
docs
team
will
not
start
to
communicate
until
march
10
with
enhancements
owners.
We
talked
about
this
with
the
enhancements
team
and
they
will.
They
will
communicate
with
the
enhancements
owners
until
code
freeze,
which
is
march
9..
B
They
will
include
the
question
if
they,
if
the
announcements
needs
docs
for
1.21,
and
they
will
include
the
docs
placeholder
pr
deadline,
also
with
the
instructions
as
well,
so
I'm
so
I
am
stating
that
the
status
is
yellow.
This
is
this
is
common
for
a
release
cycle
and
that
we
go
into
a
cycle
of
yellow,
maybe
red,
once
closer
to
the
placeholder
pr
deadline.
So
this
is
kind
of
normal.
So
continuing
with
the
status
last
week's
dev,
121
branch
sync
was
merged.
I
placed
a
link
in
the
in
the
agenda.
B
The
integration
branch
is
healthy
for
1.21.
We
are
tracking
67
enhancements
total,
which
is
quite
a
lot.
That
does
include
three
exceptions
out
of
those
67
we're
only
tracking
17
for
docs
currently,
but
this
is
the
very
beginning
of
our
I
guess
of
our
work,
so
there's
gonna
be.
This
will
be
increasing
until
we
get
closer
to
doc's
placeholder
pr
deadline
out
of
those
17
tracked
docs
three
have
merged.
One
is
in
draft
to
require
no
docks
and
11
enhancements
need
docs,
but
there's
no
pr
yet
so,
and
50
are
unknown.
B
So
we'll
continue
with
this
and
numbers
will
be
changing
every
you
know.
Every
week
there
will
be
an
email
to
kdev,
and
I
have
requested
in
that
email
to
have
a
little
section
on
if
your
enhancement
for
1.21
needs
docs
to
please,
please
place
a
placeholder
pr,
and
that's
it
for
me.
A
A
Ray
you
said
it's
yellow,
so
I'm
going
to
ask
you
a
set
of
a
question
explicitly.
Do
you
need
any
help
from
sig
docs
at
the
moment
from
other
people.
B
Not
right
now-
and
I
I
do
want
to
make
a
statement
that
this
cycle
is
kind
of-
we
are
changing-
how
we
communicate
with
the
with
the
enhancements
owners
this
cycle
and
next
cycle.
Also,
so
it's
there's
going
to
be
so.
We
won't
go
through
like
the
standard,
we're
going
to
ping
an
annas
owners
every
week.
So
just
want
to
make
a
note
of
that.
No
help
needed
right
now,
probably
closer
to
march
15th,
definitely
will
ping
some
people.
A
Okay
and
divvy
is
not
on
the
call
but
has
put
in
some
notes
into
the
the
chat
anyone
want
to
talk
about
either
raise
update
or
divya's
update.
A
Okay,
thanks
very
much
that
ray
moving
on
to
the
blog
and
does
anyone
on
the
call
wish
to
speak
about
the
the
blog
subproject.
A
I
think
I'm
going
to
take
that
as
a
as
I
know,
I
know
there's
some
blogs
in
progress.
Moving
on
to
issues
and
pull
requests,
this
one's
from
me
just
one.
I
think
at
the
moment
the
updated
api
reference
generator.
A
A
Okay,
so
it's
at
one
utc
on
friday
or
for
a
people,
sort
of
west
of
greenwich
it'll
be
on
thursday
in
like
the
afternoon,
sometime,
probably
absolutely
in
the
morning,
okay
yeah.
So
I
want
to
get
the
api
reference
generator
on
the
agenda
and
I
I
want
to
see.
Are
people
happy
to
not
discuss
this
now
and
park
that.
C
Sorry,
I
would
love
if
you
could
give
a
summary
of
why
this
is
on
the
agenda
and
why
you
want
to
bring
this
up
at
quarterly
review,
because
my
impression
is
that
we've
already
integrated
the
work
into
the
website.
A
Okay
yeah,
so
I
had
a
task
on
me
to
talk
to
sig
architecture,
about
the
switchover
and
like
the
new
api
reference
generator
is
live
so
yeah
thanks
ray
the
new
reference.
Generator
is
live.
If
you
go
and
have
a
look
at
that
issue,
you
will
see
links
to
it
and
there
is
an
old
api
reference
generator.
A
Apparently,
the
old
api
reference
and
its
generator
are
canonical.
We
want
to
move
at
some
point
so
that
it's
a
two-phase
transition
as
well.
A
First
of
all,
the
new
api
reference
becomes
canonical,
the
old
one
is
there
but
deprecated
and
then
later
the
old
api
reference
goes
because
it
does
have
shortcomings.
It's
not
very
accessible.
A
It's
a
single
page,
it's
hard
to
hyperlink
too,
but
before
that,
I
think
there
are
some
snacks
and
you're,
probably
if
you're
looking
at
that
issue,
seeing
them,
but
if
not
I'm
gonna
set
up
screen
sharing,
which
I
have
not
prepared
for,
but
I
should
have
done
because
I
knew
I
was
joining
this
meeting
one
second
folks.
A
I
don't
want
to
talk
while
I
just
do
a
bit
of
degree,
poetry,.
C
Yeah
I
mean
I
as
soon
as
you
said
that
it
was
not
canonical.
I
understood
the
problem
like
on
a
very
fundamental
level,
to
which
yeah,
I
think,
you're
you're
right.
We
absolutely
need
to
address
it
or
else
all
of
philippe's.
Hard
work
has
gone
to
waste
and
I
would
not
want
for
that.
B
Do
have
a
question
so
at
the
end
of
the
towards
the
end
of
the
release,
we
do
do
some
tasks
with
api
generation.
I
believe
so.
We
might
have
to
circle
back
with
you,
tim
and
jim,
towards
the
end
of
the
release
on.
If
there's
any
changes
to
those
steps.
A
Yeah,
so
let
me
zoom
in
a
bit
on
this
yeah
one
of
the
the
the
migration
steps
is
about
that
switchover.
A
So
absolutely
we
we
need
to
like
we've
done
generation
once,
but
I
don't
think
we've
really
got
the
process
of
generating
the
new
api
reference
nailed
down.
A
There's
a
related
task,
probably
later
than
that
around
the
the
incoming
links.
We
might
need
some
short
codes,
there's
the
actual
switch
over
but
yeah.
I
think
this
this
point
about
updating
the
reference
documentation
and
making
sure
that
the
release
handbook
for
documentation
is
really
clear
and
I'm
going
to
scroll
down
a
bit
to
some
more
discussion
yeah.
This
comment
here
from
neolit123,
quoting,
I
think
it.
A
The
the
draft
that
we
have
now
the
the
new
api
reference
generator
it
looks
great,
but
the
mappings
between
what
you
have
in
the
kubernetes
api
when
you
use
it,
when
you
talk
http,
two
kubernetes
and
then
the
urls
in
the
documentation.
A
So
let
me
oh
yeah,
so
if
we
look
at
the
url
here
is
like
ends
in
authentication,
hyphen
resources,
and
here
it
ends
in
services,
hyphen
resources,
and
here
it
ends
in
common
definitions.
Here,
cluster
resources,
these
make
sense
to
people,
but
it's
not
easy.
In
fact,
I
would
say
it's
really
hard
if
you
are
automating
api
generation-
and
you
want
to
say
okay,
you
can
go
here
for
more
information
and
I
have
programmatically
generated
a
hyperlink
to
the
documentation,
that's
currently
possible,
but
the
new
generator
and
the
new
things
it
generates.
A
Doesn't
let
that
happen.
So
that's
that's
an
issue.
A
Yep,
there's
I
mean
there's
a
bunch
of
things
so
yeah.
I
think
this
is
a
big
enough
task.
To
put
on,
I
mean
what
I
propose
to
do
is.
Is
I'm
gonna
suggest
that
later
in
the
week
when
we
have
the
quarterly
meeting
my
proposal-
and
I
don't
intend
to
discuss
like
what
the
answer
is,
then
my
proposal
is
going
to
be
that
we
put
a
lot
of
effort
behind
that,
and
so
I
wanted.
B
A
Any
questions,
because
if
people
want
to
read
up
on
this
and
are
going
to
come
to
the
quarterly
review
like
now
is
a
good
time
to
ask
questions
I
think
about.
I
want
to
read
up
on
this
I'm
intending
to
clarify
my
thinking
around
this,
but
I
have
questions.
Does
anyone
have
that
kind
of
question
in.
A
A
Okay
and
if
anyone's
watching
this
like
there
is
a
sig
docs
channel
on
the
kubernetes
slack,
people
can
come
and
ask
questions
there
as
well,
if
you're
watching
this
asynchronously,
okay
and
the
next
item
on
the
agenda
is
indeed
that
we
are
having
a
quarterly
review,
and
essentially
this
is
review
of
q4
of
2020
and
a
half.
A
I
don't
know
what
you
call
a
halfway
planning
meeting,
it's
two
quarterly
planning
meetings
back
to
back
for
the
start
of
2021
and
that's
on
yeah
thursday,
5pm
pacific
friday,
1am
utc,
those
at
the
same
time.
In
different
time
zones.
Details
are
in
the
agenda.
A
So
if
anyone
would
like
to
propose
an
agenda
item,
you
can
do
that
in
the
google
doc.
You
can
use
suggestion
mode
if
you've
got
access.
You
can
put
comments
if
you're
having
trouble
accessing
that,
then
you
can
use
the
kubernetes
slack
and
you
can
get
an
invite
from
I'll
put
it
in
the
chat.