►
From YouTube: K8s SIG Docs Meeting for 20210803
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
are
now
recorded
if
you're,
watching
this
recording.
This
is
sig
docs,
a
a
group,
a
community
group
within
the
kubernetes
project.
We
have
six
awesome
people
here
today
to
give
us
some
updates
as
to
what
they're
doing
and
just
talk
to
us
about.
What's
going
on
in
the
land
of
documentation,
one
of
the
most
important
lands
that
we
have
and
also
if
there
are
any
new
contributors
on
the
line
not
right
now,
but
in
a
second
you
can
feel
free
to
introduce
yourselves
if
you
want
to
introduce
yourself
anyway.
A
Even
if
this
is
your
like
60th
time,
that's
fine,
too,
but
let's
go
through
some
of
the
reminders
this
week.
Who
knows?
Who
is
this
week's
pr
wrangler
pop
quiz,
I'm
going
on
to
the
the
wiki?
Now?
Let's
see
it
is
august
3rd,
I
can't
believe
it
is
august
already
looks
like
zach
arnold,
which
is
a
problem,
probably
anybody
that
can
fill
in
for
pr
wrangler
this
week.
If
not,
I
will
work
that
out
with
jim
and
we'll
get
somebody
on
there.
Anybody
want
to
volunteer.
B
A
A
D
Those
are
really
cool.
Oh,
what
is
it
it's.
A
And
what
else
can
I
do
hold
up?
I've
got
this.
Oh
I
do,
but
I
have
everything
you
have
probably
like.
I
have
some
of
the
I
have
some
of
the
like,
like
the
peppy,
the
pippy
goes
to
like
the
adventure
books
and
oh
yeah
anyway,.
E
A
A
C
Yeah,
it's
it's
good.
I
already
froze
the
communities
website
repo
and
currently,
I'm
doing
all
the
release
process
steps
to
prepare
for
tomorrow.
There
are
a
couple
of
things
that
I
cannot
do
on
my
own.
One
of
them
is:
I
need
either
someone
to
provide
me
access
with
to
netlify
to
be
able
to
create
this
sort
of
subdomain
for
the
snapshot
for
121,
or
I
need
someone
that
has
access
to
netflix
to
do
that.
For
me,.
F
So
in
the
past,
jim
did
that's
for
me
for
121.,
so
ping
jim
angel,
who
has
access
to
now
internet,
live
and
oh
yeah,.
C
And
yeah
so
tomorrow,
I
kind
of
I
need
some
approvals
for
merging
some
some
pr's,
but
I
guess
that
that
doesn't
necessarily
need
someone
like
a
chair
or
a
coacher.
I
just
need
a
docs
lead,
basically
to
to
approve
some
prs
that
I
need
to
merge
in
order
to
sync
the
branches.
C
There
I
will
need
to,
I
will
need
approval,
review
and
a
well
review
yeah,
you
could
say
review,
I
mean
check
out
the
website
if
it's
the
deployed
property
and
approval
on
some
pull
requests
that
basically
will
merge,
will
keep
in
sync
the
the
main
branch
that
we
will
do
and
the
release
121
branch,
which
is
basically
the
snapshot
for
the
121
docs.
E
Sure
do
you
want
to
just
you
know,
slack
me
the
actual
pr's,
either
the
priority
and
I'd
be
happy
to
to
take
care
of
it.
I
assume
we're
not
breaking
anything
in
these
pr's
right.
C
C
C
Yeah,
so
there
is
a
there
is
a
problem.
I
don't
know
if
anyone
on
this
call
really
can
help
me
with
this.
Maybe
I
should
thank
someone
else
about
it,
but
basically
there
are
two
processes
for
or
based
or
better
said,
yeah
two
processes
that
are
defined
in
the
handbook
for
generating
the
api
references
and
so
on
for
cubecto
for
the
kubernetes
api
reference
for
a
bunch
of
other
stuff
too
one
of
them.
C
I
already
did
what
it
said
there
somehow
and
opened
the
pull
request,
but
at
the
same
time
it
seems
like
the
there
is
also
a
second
way
of
doing
it,
which
is
the
new
way
and
I'm
kind
of
conflicted,
because
I
don't
really
know
which
one
needs
to
get
merged.
C
C
I
think
I
have
a
couple
of
people
that
I
can
think
about:
yeah,
probably
jim
right,
jim
and
feljoy.
I
don't
know
what
his
name
is
the
but
his
github
is
her
name
is
feldja.
He,
basically
is
the
person
that
I
think
took
care
of
this
during
the
121
release
as
well.
So
I'll
select
him
and
ask.
F
G
F
Has
answered
for
that
and
for
121
we
did
merge
in
his
pull
request
and
I
had
the
same
issues
you
had
as
well
to
generate
the
reference
stocks
but
chi
ming
and
karen
rachael,
who
is
linked
or
assigned
on
that
pull
request,
and
they
helped
me
out
in
quite
a
bit
so.
C
And
I
think
that's
it
for
me.
I
don't
have
anything
else.
A
G
A
There
wasn't
anything
else
on
the
agenda
today:
does
anybody
have
any
other
business
or
any
other
outstanding
prs
or
anything
that
they'd
like
to
get
reviewed?
I
see
a
hand
from
ray.
F
Yeah,
so
this
is
coming
from
sig
security
there
and
it's
what's
a
work
in
progress.
It's
a
threat
model
for
mission
for
admission
controllers
and
they
wanted
to
bring
up.
If
there
is
a
proper
place
to
have
this
in
the
k
websites
on
the
kubernetes
website,
or
should
it
be
a
blog
or
should
it
actually
be
a
place
in
in
the
documentation,
I'll
post,
the.
F
Draft,
currently
that's
the
right
draft.
Okay,
it's
just
a
google
doc,
but
yeah
it
is
coming
from
originally
from
the
cncf
tag.
Security
then
also
kubernetes
security
as
well
yeah.
So
that's
just
a
topic
to
bring
up
nothing,
it's
nothing
that
needs
to
be
addressed
right
away.
We
can
have
a
conversation
about
it.
A
C
I
think,
by
the
looks
of
this,
it
should
probably
be
somewhere
in
the
docs
and
not
just
a
blog
post,
but
because
I
I
mean
I
look
at
doc
at
blogs.
More
like
it's
sort
of
like
you
know,
ephemeral.
I
don't
know
if
anyone
really
goes
back
in
time
or
in
after
five
releases
to
look
at
this,
and
if
this
is
still
relevant,
then
it
probably
should
be
part
of
the
docs,
but.
G
I
would
I
would
tend
to
agree
with
that
as
well.
Historically,
we
don't
go
back
and
update
blogs
either,
so
this
would
get
if
somebody
were
searching
for
this
a
year
from
now
and
it
were
out
of
date,
it
wouldn't
get
updated.
A
I
would
love
the
why,
like
that's
sort
of
at
the
top
to
be
the
blog
post,
like
so
more
of
the
story
of
the,
why
and
why
it
was
necessary
and
then
a
link
to
the
new
documentation
with
the
document
with
a
home
for
the
documentation-
and
I
know
tabitha
and
others-
are
some
storytellers
they're
really
good.
So
that's
that
was.
That
would
be
my
my
take.
F
A
E
Yeah
I
have
one
and
just
to
give
you
all
an
update
from
the
the
sig
docs
localization
work
group
that
I
chair.
There
was
a
request
that
we
look
at
the
ability
to
have
a
pr
that
that
made
updates
across
multiple
of
the
language
repositories.
E
E
It's
just
I'm
touching
a
link
that
needs
to
be
updated
and
say
20,
20,
different
repositories
and
right
now
I
got
to
do
20
different
prs,
and
so
you
know,
could
we
have
an
exception
to
our
current
guidelines
that
says:
hey
if
you're
doing
an
update
that
doesn't
require
any
translation
review,
because
it's
a
minor
typo
thingy
that
occurs
in
all
the
different
language
repos.
E
Could
you
do
it
in
one
pr,
and
I
remember
vaguely
there
was
some
reason
why
we
do
not
allow
those,
so
I'm
just
giving
an
update
here,
but
I
think
I'm
gonna
have
to
follow
up
with
our
our
sigdoc
leadership
and
try
and
refresh
our
memory
if,
if
it's
okay,
to
have
an
exception
for
that
case
or
not.
A
A
And,
yes,
I
am
a
part
of
the
google
group
so
anyway
yeah
I
know
jim
and
I
are
looking
into
that
after
the
meeting.
But
now
I've
got
I've
got
notes
down.
I
will
check
with
jim
and
talk
with
jim
about
what
the.
Why
is
on
that
and
see
if
we
can
get
an
exception,
because
that
does
seem
appropriate.
E
Yep,
let
me
let
me,
try
and
grab
you
the
I'll
put
it
in
the
it's
been
written
up
as
an
issue.
So
let
me
yep
get
to.
H
Oh
yeah
chris
messier,
so
I
just
wanted
to
mention
that
our
submission
for
the
sig
docs
deep
dive
was
accepted.
I
think
we
have
one
deadline
which
is
tomorrow
to
to
send,
in
the
speaker,
accept
acceptance
but
I'll
defer
to
brad
or
chris
to
comment
on
the
next
steps.
I
I
think
we
do
need
to
start
efforting
some
of
the
collateral
or
content
that
we
want
to
put
together
for
this,
and
you
know,
come
up
with
a
looser,
loose
agenda.
I
know.
H
Docs
but
maybe
we
should
have
some,
you
know
separate
meetings
or
you
know,
assign
some.
E
H
To
start
moving
forward.
E
Absolutely
you
know
now
that
it's
been
accepted
it's
time
to
get
serious
and
we
definitely
want
to
just
you
know,
figure
out
how
much
time
did
they
give
us?
What
do
we
want
to
cover
in
the
agenda
and
the
deep
dive
and
and
then
we'll
see
what
we
can
then
reuse
from
previous
presentations
and
what
new
content
we
want
to
add,
but
definitely,
I
think
we
have
a
little
private
slack
channel
for
the
the
group
of
us
right
that
we
do.
G
H
Well,
I'm
thinking
we
want
to
encourage
contributors.
Maybe
it's
one
of
the
first
things
we
want
to
do.
We
want
to
give
folks
sort
of
an
outline
of
the
process
of
contributing
to
the
to
sig
docs.
Maybe
some
separate
little
items
discussing
you
know
how
to
do
these
things
for
the
for
the
uninitiated
again,
brad.
H
I'll
I'll
look
to
you
guys
for
maybe
how
we
want
to
proceed
here
in
some
of
the
you
know,
firmware.
E
Yeah,
so
so
you
know
historically
what
we've
used.
This
is
a
great
opportunity
to
start
filling
the
funnel
for
new
contributors
and
not
just
new
contributors
to
docs,
but
there's
a
lot
of
people
who
don't
know
who
eventually
want
to
move
on
and
be
a
contributor
to
the
say,
the
development
to
the
code
base,
but
they
don't
know
how
to
get
started.
And
you
know
my
experience
and
other
people's
experience
has
shown.
The
best
way
to
get
started
becoming
an
open
source
contributor
is
go
start
with
the
docs.
E
So
whether
you
want
to
always
be
you
know
just
docs
only
or
if
you
want
to
start
with
contributing
to
the
docs
and
then
become
a
you
know,
a
contributor
to
the
to
the
code
base.
It's
it's
a
wonderful
way
to
start,
and
so
usually
what
we
do
in
these
things
is
we're
going
to
provide
enough
scaffolding
so
that
people
can
really
understand
how
the
cube
docs
is
structured,
how
it
works,
and
typically
we
even
give
opportunities
to
to
help
them
get
their
first
pr.
E
You
know
now
for
the
deep
dive
and
we
usually
do
that
in
the
doc
sprint.
Rather,
but
for
the
deep
dive
we'll
pretty
much
cover
everything
they
need
to
understand
about
our
structure,
how
things
work
jim
angel
will
also
talk
about
how
we
use
netlify,
so
usually
what
the
takeaway
is.
A
A
A
I
can
run
some
data
too.
That
says
like
what
some
repos
are,
that
haven't
been
touched
too
much
in
docs
to
see
like
I
mean.
Obviously,
some
of
them
might
not
be
touched
for
the
good
reason.
So,
but
if
any
of
those
are
like
priority,
we
can
look
at
those
and
like
talk
about
those.
D
H
I
E
B
A
A
I
A
It's
good
that
we
have
this
much
this
much
stuff
and
I
think
they
did
change
the
time
for
the
deep
dive
so
brad.
It's
important
that
you
check
that
because
I
know
they've
changed
it
a
few
times
with
the
combinations
of
the
intros
and
the
deep
dives,
and
vice
versa,
to
like
30
minutes,
90
minutes,
etc.
So.
J
That
makes
a
huge
difference
whether
you
got
30
minutes
or
90
minutes.
So
yes,.
I
A
And
I
don't
think
that's
on
the.
I
don't
think
that's
on
your
acceptance,
email
either
yet
so
we
probably
won't
know
that
for
a
few
days.
I
Yeah,
I
just
have
one
thing:
we
are
going
to
be
having
our
bi-weekly
blog
meeting,
so
I'm
looking
the
time
just
to
make
sure
11
30
a.m.
Pacific
time
so
figure
it
out
from
there
12
31
through
2
30..
So.
F
I
Like
in
a
half
hour
right
so
yeah,
and
if
anybody
here's
the
agenda,
how's.
A
That
going
chris
tell
us
a
like
give
us
a
little
tldr
as
to
like
how
that's
going.
I
G
Links
are
in
the
in
the
agenda
as
well.
I
Oh
okay,
all
right
yeah,
so
and
right
now
I
think
they
have
about
nine
nine
blogs
and
they're
they're
rolling
them
out
every
few
days,
starting
eight
six
so
in
three
days
and
then
so
so,
we've
been
trying
to
like
review
them
in
order.
I've
read
through
about
five
of
them.
So
if
anybody
wants
to
jump
in
and
review,
go
go
ahead
and
do
that,
but
that's
kind
of
I
guess
the
main
thing
we
need
to
talk
about
and
then
whatever
else
comes
up
as
well.
A
A
I
don't
know
just
that
literally,
it
was
just
something
that
was
in
my
head.
I
Yeah,
that
might
not
be
a
deal.
A
That
it
may
be
like
a
do,
you
all
have
like
a
project
board
or
anything
like
that,
or
any
any
way
that
you're
tracking
that
stuff.
I
G
Drop
the
project
word
link
in
the
in
the
conversation.
I
Oh
yeah,
and
it
said
we
put
that
at
the
top
of
the
slack
channel,
I
think
nate
you
did
that
last
a
week
or
two
ago.
So
so
you
can
see
what
the
status
of
things
yeah
thanks.
I
forgot
about
that.
A
A
I
Yeah
jesse
butler
has
been
running
that
and
I
know
him
from
amazon,
so
we
kind
of
you
know
we
work
together
at
amazon,
so
I've
had
no
trouble
getting
information
from
him,
but
I
think
yeah.
I
think
it's
gone
pretty
smoothly.
A
A
I
think
I'm
gonna
call
the
meeting,
then
okay,
but
the
other
thing
before
I
call
the
meeting
I've
seen
some
things
that
sig
said
of
other
things
that
are
doing
that.
I
think,
is
very
interesting
that
I'm
asking
jim
and
some
other
folks
what
they
think
too
is
some.
Other
groups
are
doing
slack
stand-ups
in
lieu
of
meetings
every
week.
A
So,
for
instance,
like
a
group
that
you
can
look
at
that's
very
public
is
sig
contrib
x.
They
have
a
slack
channel
that
says
sig
contribex
meetings
and
then
every
week
bob
that
one
of
the
chairs
goes
in
and
writes
like
the
sub
project
headings
for
each
one
and
then,
if
you're
working
on
either
one
of
those
sub
projects
or
if
you're
working
on
a
general
area
or
if
you
have
something
that
needs
to
be
approved
or
something
like
that
it
flows
in
and
then
what
he
does.
D
I
like
that
idea.
I
I
like
that,
just
for
the
ability
to
to
search
and
look
things
up,
I
know
we
can
do
that
now
with
google
docs,
but
just
that
ability
to
like
my
week's
crazy
and
you
know,
being
able
to
kind
of
put
things
in
like
that
would
be
helpful
and
and-
and
I
I
think
that
me
personally,
I
think
that
that
would
make
me
feel
more
included
when
work
is,
you
know,
can
be
a
tire
fire
or
just
life
is
wild
at
that
point
in
time,.
I
Yeah,
I
I
agree,
I
think
we
talked
about
doing
this
with
with
the
blog
subgroup
just
because
there
isn't
really
enough
business
for
us
to
do
every
week,
so
we're
now
every
two
weeks,
so
maybe
the
ones
in
between.
I
think
it
was
actually
suggested
to
do
that.
You
know
maybe
just
have
a
little
slack
meet.
A
Awesome
and
then,
on
that
same
note
too,
we
are
still
looking
for
chairs.
I
am,
I
am
the
substitute
for
at
least
three
months,
and
one
of
my
responsibilities
of
substitute
is
to
grow
and
train
and
mentor
new
chairs
for
this
group.
A
Let
us
know,
like
I
said,
free
mentoring
and
training
and
all
kinds
of
fun
stuff,
so
we
do
have
some
people
now
that
have
said
they
were
interested,
though
so
it's
good
news,
so
we
do
have
some
folks
who
are
like.
Yes,
let
me
try
this
out,
but
always
looking
for
more,
and
there
are
also
other
things
too
that
are
looking
for
chairs,
so
not
only
docs,
but
if
you
know
folks
who,
just
in
general,
are
in
the
kubernetes
land
and
you
think
they
could
use
a
boost
up.
A
This
is
a
great
opportunity
on
that
note.
We'll
end
things
here
and
I'll
talk
to
jim
about
some
of
those
ais
that
I
have
I'll
also
make
sure
that
I
get
the
right
access
for
this
dang
agenda
and
we'll
keep
it
moving,
see
you
next
week.
It
may
be
slack,
but
whatever
way
it
is
it's
going
to
go
in
the
mailing
list.
First,
so
that
we
can
get
some
consensus.