►
From YouTube: SIG Docs meeting for 20210720
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,
everyone
welcome
to
july
20th
edition
of
kubernetes
sig
docs.
I
am
paris.
You
have
probably
maybe
never
seen
me
before.
Some
people
maybe
see
me
before,
depending
on
what
kubernetes
channels
you're
tuned
into,
I
sit
on
the
kubernetes
steering
committee.
I
also
used
to
co-chair
an
awesome
group
called
contributor
experience
for
two
years,
so
I've
done
this
chair
thing
a
few
times,
I'm
filling
in
for
jim
angel,
who
is
the
most
wonderful
chair
ever.
Fortunately,
I
will
never
live
up
to
jim's
awesomeness
so
hold
that
to
hold
tight.
A
But
the
reason
why
I
am
here,
though,
is
sig.
Docs
is
going
through
a
growing
period
where
we
need
more
chairs
and
I'm
gonna
be
filling
in
for
at
least
the
next
two
to
three
months
with
some
meetings
and
things
like
that,
some
very
light
stuff,
but
I
wanted
to
give
that
as
a
high
level
as
we
start
this
meeting,
because
if
you
are
looking
to
grow
in
the
sig,
I'm
willing
to
mentor
train
and
do
sort
of
group
mentoring
if
you're
interested
in
growing
the
contributor
ladder.
A
Here,
we
can
talk
a
little
bit
about
that
later
on.
In
the
meeting,
but
I
know
we
have
a
ton
of
sig
docs
related
work.
I
know
tim's
on
the
call
and
we'll
get
going
now.
So
first
things.
First,
we
do
have
a
code
of
conduct.
Please
be
excellent
to
each
other,
of
course,
and
as
I
mentioned
before
nine
times
out
of
ten,
I'm
most
likely
not
going
to
know
what's
going
on
in
your
world,
so
feel
free
to
give
context
or
say
hello
to
me.
A
I
would
love
to
get
to
know
all
of
you,
especially
if
I'm
going
to
be
here
for,
like
I
said
at
least
two
to
three
months
with
y'all
hanging
out
so
yeah
feel
free
to
tell
me
if
you're,
a
sub
project
owner
or
an
approver
or
someone
that
writes
blog
posts.
Anything
like
that.
I
would
love
to
get
to
know
y'all.
So
first
things.
First,
do
we
have
any
new
contributors
and
that
would
like
to
introduce
themselves.
A
I
see
pernicious
chat,
feel
free
to
come
off
of
mute
and
or
video
say
hello
to
us
and
same
with
anybody
else.
Here,
that's
new
for
the
first
time.
A
That
means
we
have
a
ton
of
you
that
have
been
here
before,
okay,
so
now
that
means
that's
all
right
now.
I've
got
a
lot
of
people
to
know
to
find
out
and
learn
about.
So
I'm
really
excited
to
get
to
know
all
of
you.
There
are
a
couple
of
updates
and
reminders
that
jim
put
in
for
me
in
the
in
the
agenda.
A
Also,
let
me
go
ahead
and
lazy
web
the
agenda
to
y'all
in
chat
so
who's,
this
week's
pr
wrangler
and
if
you
could
say
hey
to
me
that
would
be
awesome
if
you're
on
no.
A
Okay,
cool
all
right
and
then
who
is
who's,
got
an
upcoming
pr,
wrangler
shift
just
so
again,
so
I
get
to
know
you,
I'm
looking
at
the
pr
wrangler
list
right
now.
Let's
see
what
week
is
this?
It's
july
20th,
I
think
july.
There
we
go
zach
and
I
think
it
sounds
like
celeste
might
be
filling
in
next
week
for
zach
after
that
is
another
zack
is
that
arnold
still
around,
I
haven't
seen
zach
arnold's
name
in
a
minute.
D
We
should
check
in
with
with
zach
too
zack
arnold
to
to
make
sure
that
they're
happy
too
we'll.
A
Check
in
with
zach
to
make
sure
zach's
still
good
with
that
one
and
then
the
following
week
is
savita
I'll
check
in
with
her
too
I'll
just
check
in
about
three
weeks
three
weeks
ahead
of
time
and
if
folks
on
the
line
are
curious
as
to
what
a
pr
wrangler
is.
This
is
someone
who
this
is
an
approver
someone
who
can
approve
prs
and
is
helping
us
clear,
the
prq
and
making
sure
all
of
your
stuff
isn't
sitting
in
a
black
hole
and
helping
you
get
through
the
process.
A
So
all
right
and
then
agenda,
we've
got
release
122
stuff.
Who
is
the
release
liaison
and
say
hi
to
me?
Please.
A
E
Yes,
so
our
status
is
yellow,
mostly
because
the
integration
branch
is
currently
broken.
There
are
some
conflicts
I
intend
to
fix
them
today.
Other
from
that
today
is
also
the
deadline
for
ready
for
review
for
pull
requests
on
k
website
for
122..
E
We
have
six
drafts
that
are
working
progress,
prs
that
need
to
be
basically
ready.
I
assume
that
they
will
miss
the
deadline.
E
At
least
some
of
them
depends
on
at
if,
at
the
end
of
this,
at
the
end
of
today,
anyone
will
reply,
but
if
I
don't
get
any
kind
of
replies,
I
will
reach
out
to
the
enhancement
owners
via
slack
tomorrow.
E
24,
pull
requests
that
are
ready
for
review
and
22
that
are
merged
once
the
deadline
will
be
over.
We
will
start
to
review
as
many
as
possible
out
of
those
24
pr,
so
we
can
get
we
can
get
as
many
as
the
merged
and,
yes,
I
think
that's
pretty
much
it
from
us.
E
No
we're
good
everything
is,
is
fine,
yep,
okay,.
A
And
then
does
anyone
else
have
any
business
that
they'd
like
to
bring
up
to
the
meeting
whether
things
that
you're
working
on
something
that
you're
blocked
with
anything
else
related
to
something
that
you're
working
on
that
you'd
like
to
talk
about?
We
don't
have
anything
else
on
the
agenda.
I
know
we
have
a
discussion
from
tim.
F
F
G
So
a
lot
of
times
you're
just
you
know
I
haven't
done
a
whole
lot
of
pr's,
but
I've
done
a
few
and
a
lot
of
times.
What
happens
is
like
you
get
the
buy-in.
The
docs
people
are
really
quick,
they
get
in
there
and
they
give
you
all
their
comments.
And
then
they
say,
oh
now,
we'd
like
to
get
an
expert
from
sig
whatever,
and
then
it
just
sits
like
forever,
and
I
or
you
know,
maybe
a
short
period
of
time,
maybe
a
long
period
of
time,
but
it's
different
is
there?
G
Have
we
thought
about
different,
like
tactics
or
something
to
to
get?
Maybe
maybe
show
up
at
a
meeting
and
say
hey.
G
We
have
12
prs
for
docs
that
we
would
love
this
this
organization
to
this
sig
to
help
us
with,
so
that
that's
kind
of
what
I
was
thinking
have
we,
you
know
tried
a
concerted
effort
to
say,
hey
we're
waiting
on
you,
guys
and
and,
and
you
know,
finding
ways
to
get
them
to
respond
more
quickly,
because
they're
all
very
important
people
and
they're
busy
people
and
docs
is
probably
not
the
first
thing
they're
thinking
of
so
any
any
thoughts
on
that.
C
So
I
have
a
few
strategies
in
the
past.
I've
used,
one
is
the.
When
you
add
secret
on
the
github
comment,
you
can
add
the
sig
dash
pr
reviews
for
tech
review.
Sometimes
that
works
also.
C
My
next
approach
usually
works
the
best
which
is
going
to
that's
that
sig
slack
channel
and-
and
I
go
to
the
the
six
in
the
k
community
repo,
the
sig-
will
have
a
file
file
of
all
the
reviewers
of
that
sig,
and
so
I
would
ask
all
those
folks-
and
I
would
also
end
if
it's
tied
to
a
cap-
I
would
go
to
the
kef
dot
yaml
and
the
ket
yell
might
have
tech,
reviewers
or
and
reviewers.
I
would
add
all
those
folks
as
well
so
it
is
it
does
take.
C
G
C
And
my
last
my
last
tactic-
or
I
guess
one
I
would
call
a
tactic,
but
my
last
step
would
be
finding
out
what
company
that
person
is
with
and
I
would
go
to
a
friend
of
mine.
You
know
usually
there's
people
you,
you
would
know
that
worked
in
the
same
company
and
they
would
helping
ping
them
in
there
in
their
internal
messaging
system.
So
that's
my
last
resort.
E
I
have
a
question
ray:
did
you
folks
use
this
liaison
program
in
the
enhancements
team,
where
you
basically
reach
out
it's
supposed
to
be
sort
of
like
an
experiment
for
at
least
for
this
release,
where
each
sig
should
have
a
liaison
that
interacts
with
sick
release
or
kind
of
like
tries
to
shield
people
or
tries
to
forward
important
topics
to
the
sig?
I
only
got
three
three
people,
I
think
contacts
from
three
people
and
from
three
six.
E
I
think
it
was
sig
network,
sig
and
sorry,
sick,
node
and
something
else
I'm
not
not
sure.
C
Yeah
we
we
have
the
same
liaisons
as
well.
We
not
all
the
six
participated
in
and
yeah.
We
have
the
same
three
liaisons
so
and
just
bear
in
mind
that
those
the
the
leah,
the
liaisons
themselves
might
be
new
to
the
to
the
community,
so
they
may
not
know
who
the
proper
enhancement,
owners,
reviewers
and
tech
reviewers
are
too
so
so
it
might
be.
You
know
just
a
little
bit
of
a
hand
holding
for
the
next
few
releases.
D
Well,
I
mean
ray
and
victor
have
more
information
about
the
the
release
process.
I
kind
of
agree
with
what
ray
said
about
you
know
how
you
would
engage
with
another
sig.
I
mean
one
thing
you
can
do
is
you
could
escalate
it
to
a
technical
lead
like
like
me
or
karen
branch?
One
of
the
technical
leads
to
the
sig
and
say
hang
on.
We
need
some
help.
You
can
take
it
to
this
weekly
meeting
and
say
whatever,
and
there
is
of
course
a
pr
wrangler
you
can.
D
You
can
contact
the
pr
angler
and
say
I'd
like
to
get
this
moving.
What's
the
best
step,
all
of
those
are
valid.
Yeah
I
mean
if
things
are
really
not
going
well,
there's
some
mechanisms.
We
can
use
some
escalation
mechanisms,
but
I
don't
think
we'll
ever
need
them
like
if
we
were
to
sort
of
take
things
more
formally,
but
I
don't
see
the
point
in
engaging
that
way.
I
think
what
ray
said
was
going
to
work
better
and
has
always
worked
eventually
for
me.
G
Yeah
yeah,
I
don't
get
the
feeling,
it's
anything
malicious
at
all.
It's
just
that
they
either
don't
notice
or
it
never
rises
to
the
top
of
their
queue.
You
know
it's
really
just
a
way
to
say
how
do
we
wake
them
up
so
they'll,
you
know
come
look
at
this
thing.
You
know
because
a
lot
of
times
it'll
be
something
simple
too,
that
they
just
and
and
it
won't
ever
get
approved
because
it's
sitting
there
right
with
saying
hey,
we
need
an
approval
from
this
sig
or
something
like
that.
D
I
guess
what
also
the
other
thing
I
would
say
on
this
is
that
it's
not
just
a
pr
angler
that
does
approvals
in
a
week
that
doesn't
scale
very
well,
so
the
pr
wrangler
is
there
to
catch
that
that
tail
and
sweep
up.
But
if
they're
doing
all
the
sweeping
that's
a
problem,
we
need
to
address
and
really,
I
think
if
we,
if
we
got
more
a
bigger
pool
of
reviewers
or
we
got
more
reviewing
done,
we,
you
wouldn't
see
that
backlog
because
we'd
be
more
effective
at
liaising.
D
A
G
I
I
haven't
really
tried.
I
I
really
you
know,
since
I've
really
only
been
participating
actively
for
the
last
few
months,
so
I'm
I'm
really
try.
I
want
to
get
the
protocol
too.
I
don't
want
to
just
be
someone
who's.
Oh
there's
that
annoying
guy
again,
you
know,
so
I
want
to
make
sure
I'm
doing
the
protocols
right.
So
so
I'm
not
just
you
know
randomly
going
after
everybody,
so
you
know
you're
doing.
A
C
G
A
All
right,
I
don't
have
any
business,
but
it
is
only
eight
of
you
and
I
would
really
like
to
just
get
a
small
intro.
If
that's
okay
from
all
of
you,
I
know
like
just
just
just
appease
me
right
like
just
a
really
quick
small
intro
and
then
just
punt
it
to
someone
else
I'll
call
I'll
call.
Your
name
feel
free
to
punt
it
to
anybody.
It
can
be
as
small
as
your
first
name
and
pass
it
on,
but
I
would
love
to
know
what
you've
contributed
to
and
like
what
I
could.
A
What
I
could
call
on
you
for
and
things
like
that,
especially
if
you're
an
expert
in
any
area.
So
I'm
gonna
kick
it
to
nate
w
nate.
Are
you
listening.
H
I'm
nice
to
meet
you,
paris.
I
think
this
is
the
first
time
I've
been
in
a
meeting
with
you,
I'm
nate
waddington.
I
am
a
a
developer
advocate,
focusing
on
documentation
with
the
cncf,
so
I
work
with
the
tech,
docs
crew,
celeste
horgan,
all
those
folks
yeah.
A
Nice,
nice:
let's
kick
it
to
christopher
metz.
B
Yeah,
hey
paris,
how
you
doing,
I
guess
the
couple
of
things
I'm
working
on
is.
I
originally
worked
on
a
very
good
first
issue
with
mermaid
and
then,
since
I'm
sort
of
a
diagram
guy
with
some
of
the
documentation,
I've
done
for
both
some
internal
projects,
as
well
as
some
external
open
source
projects.
I
thought
I'd
work
on
that
a
bit
and
particularly
in
the
open
pr
documentation.
I
think
it
can
be
intimidating
for
folks
that
are
trying
to
get
a
handle
on
that.
B
So
I
thought
some
simple
diagrams
might
help.
I
crafted
a
document
on
how
to
use
mermaid.
I
had
forwarded
that
or
socialized
that,
with
a
couple
of
folks
and
anna
suggested,
I
open
a
pr
as
well
so
netnet.
I
have
an
open
tr
to
add
some
mermaid
diagrams
to
the
to
the
open
pr
documentation,
and
then
I
thought
somewhere
we
could
stick.
B
You
know
this
how
to
do
mermaid
diagrams,
and
I
think,
if
we
encourage
folks
to
use
that
or
even
existing
tools
or
even
how
to
get
an
idea
on
the
correct
procedures,
for
you
know
creating
and
implementing
diagrams
into
much
of
the
documentation.
I
think
will
make
it
a
lot
more
readable.
A
I
love
knowing
that
we
have
more
folks
here
than
just
word
folks,
so
visual
visual
folks
for
the
win
hello,
christopher
all
right.
So
chris
chris
you
just
spoke
to
chris
migus.
G
Sure
I
used
to
be
mostly
just
a
linux
writer.
I
wrote
books
on
linux
for
decades
and
then
I
started
doing
containers
container.
You
know
docker
containerization
and
then
kubernetes
and
openshift
for
a
few
years,
and
now
I'm
at
amazon
web
services
and
I'm
told
I
can
do
pretty
much
anything
open
source
that
I
want
and
I
want
to
do
kubernetes.
So
that's
why
I
showed
up
here
and
my
first
thing.
B
G
B
G
Yeah,
it
was
yeah,
it
was
stupid,
but
but
it
got
through
and
you
know
thanks
to
you
guys,
really
and
and
since
then
I've
been
trying
to
do
smaller
things
and
and
and
look
for
opportunities.
That's
about
it.
A
Awesome
and
then
I'm
gonna
put
tim
on
the
spot.
I
already
know
tim
but
tim.
How
long
have
you
been
with
us
now
by
the
way
yeah.
D
Tell
you
what
I
have
an
api
for
that.
Well,
I'm
gonna.
Look
at
github,
I
have
the
page
open
takes
a
while
my
first
pr
was
in
2018
november
2018.
I
was
learning
kubernetes
because
I
wanted
to
pass
my
cka
yeah,
I'm
gonna,
I'm
gonna
share
that
view.
Actually
there
you
are
back
in
2018
and
if
we
switch
to
the
I
have
too
much
work
in
progress.
I
think
it's
my
my
big
challenge
with
sigdoc's
contributions
is
like
my
code.
D
Contributions
are
all
work
in
progress
and
they
need
not
to
be
so.
I
am
a
technical
lead
of
sig
docs.
So
all
special
interest
groups
for
communities
have
chairs
and
they
can
also
have
like
administrative
helpers
and
technical
leads.
In
fact,
I
think
you
have
to
have
at
least
one
technical
lead.
We
have
several.
I
am
one
of
them,
so
the
technical
leads
for
sig
docs.
Do
things
like
admin
at
the
system
we
use
for
publishing
the
content.
Netlify
technically
review
changes
like
major
changes
to
the
site
to
the
mechanism.
D
If
we
were
to
switch
from
hugo
static
site
generator
or
from
the
doxie
theme
that
would
go
for
that.
Would
want
to
review
from
a
technical,
lead
or
a
chair,
and
another
thing
I
think
is
important
is
that
tech
leads
try
to
help
new
contributors
or
indeed,
contributors
on
any
stage
of
their
journey,
get
involved
in
sick
docs
and
to
level
up
their
skills
and
their
ability
to
contribute.
D
I
was
going
to
say
what
I
do
for
a
living,
I'm
an
I.t
consultant.
I
work
for
a
uk
company
called
the
scale
factory
which
works
for
amazon
web
services
or
not
works
for
our
customers,
use
amazon
web
services
and
we
give
them
advice
on
how
to
do
it.
That
kind
of
thing.
So
this
isn't
like
this
isn't
my
main
role.
My
main
role
is
the
consultancy,
but
I
do
this
on
the
side
and
I
enjoy
it.
D
So
it's
it's
helped
me
learn
an
awful
lot
about
kubernetes,
I'm
going
to
throw
to
ray
right
over
to
you.
C
Hello,
so
I
was
the
1.21
release.
Dox
lead
currently
the
enhancements
team
and
I'm
going
to
be
the
123
release
lead
coming
up
in
august.
I
actually
met
you
pear
in
paris
in
san
diego
coupon
2019.
You
had
a
diversity
luncheon,
that's
actually
how
I
got
started.
I
I
was
at
taylor's
table
and
talked
to
him
and
he
said
yes
yeah
and
he
said
he
was
yeah.
He
did
stuff
with
sick
docs
and
got
started
started
with
that
yeah.
So
I
also
participate
in
other
sig
sig
release.
C
C
I
work
with
susa
by
the
way
ranch
labs
and
we
have
I'm
I'm
I'm
an
engineer
there.
So
we
have
a
few
open
source
projects,
rancher
keyboard
and
harvester
for
hci,
so
lots
of
different
fun,
stuff.
A
E
Yes,
hello,
so
I'm
a
software
engineer.
I
worked
for,
coincidentally,
for
at
t
and
red
hat,
that
kind
of
at
the
same
time
with
chris.
E
Currently
I
don't
really
use
kubernetes
anymore
at
l,
at
least
in
in
my
day-to-day.
It's
not
really.
That
doesn't
doesn't
happen.
That
often
I
used
to
be
part
in
red
hat
on
of
the
developer
experience
team
in
openshift,
so
that's
kind
of
where
I
got
started
and
yeah
it's
I
mean
I
kind
of
wanted
to
contribute
to
kubernetes
because
it
really
offered
me
some
really
good
opportunities
in
my
career
since
2015
I
was
able
to
land
really
good
jobs
just
because
of
this
project.
E
Basically,
so
that's
one
of
the
reasons
why
I'm
here
that's
one
of
the
reasons
why
I
will
still
be
here,
I'm
currently
the
docs
fleet
for
122,
and
I
was
a
shadow
under
under
ray
in
121.
E
A
Awesome
I
love
that
you're
still
hanging
out
with
us,
even
though
you're
not
necessarily
using
kubernetes
during
the
day.
That's
a
a
lot.
We
see
a
lot
of
contributors
that
come
and
go
and
a
lot
of
them
say
like.
Oh
I'm
not
doing
it.
You
know
as
part
of
my
day,
job
anymore
and
unfortunately,
don't
contribute.
So
thanks
for
sticking
around
that's
so
important.
A
I
think
that's
everyone
watching
spar
if
you'd
like
to
say
anything.
If
not,
I
know
folks,
then,
if
I
ever
put
y'all
anybody
on
the
spot,
tell
me
to
take
a
hike
you
feel
free
to
to
not
say
anything
but
we'd
love
to
say
hello
to
you.
I
think
that's
it
did.
I
miss
anybody
else.
A
I
I
Hello,
I'm
punisher
and
I'm
from
india-
and
this
is
my
first
meeting
in
a
kubernetes
site,
and
I
found
this
sick
dogs
like
something
relatable
like
since
I'm
a
complete
beginner
in
this
field,
and
I
just
wanted
to
come
here
and
enjoy
the
community
once
so
yeah.
I
just
I'm
here
and
till
now.
It
felt
awesome
and
I'd
like
to
have
my
first
pr
or
my
first
issue
or
just
learn
from
the
community
and
yeah
excited.
A
We
would
love
to
have
you
stick
around
there's
tons
of
stuff
that
you
can
get
involved
with
help
wanted
wise
and
good
first
issue.
Wise
tim
even
gave
you
some
good
stuff
in
the
chat,
so
this
is
a
great
place
to
get
started
and
figure
out
where
what
other
cigs,
especially
some
of
the
like
intensive
cigs,
like
victor
just
said,
sig
node,
that's
one
of
our.
In
my
opinion,
a
super
super
intensive
sig,
but
anything
you
need
just
ping
us
on
the
slack
channel
cool.
D
So
what
I've
done
before
when
we've
had
a
new
person
who's
joined
the
meeting
and
said
that
they
they
are
new
and
would
like
questions
as
I've
said
right,
we'll
use
the
the
end
of
the
meeting
as
a
sort
of
new
contributor.
Ask
me
anything,
and
this
isn't
a
regular
scheduled
thing.
It's
completely
unscheduled!
It's
like
oh,
a
new
person.
D
So
yeah
I'm
punishable,
I'm
probably
saying
your
name
wrong,
but
please
feel
free
to
ask
questions
and
we
will
try
and
help
nah.
It's
okay.
B
I
I'm
trying
to
learn
communities
and
all
the
whole
things
we
had
cloud
native
on
our
technology,
so
I'm
basically
in
my
final
year
of
my
engineering,
so
it's
kind
of
hectic
to
manage
everything
all
by
the
side,
so
yeah
I'm
going
slow
but
yeah.
I
really
want
to
do
something
for
this
community
looking
forward
to
it
still
cool.
A
A
We
are
trying
to
have
it
as
a
hybrid
event.
It
will
most
likely
be
on
conference.
There
is
capacity
restraints
it
will
sell
out.
So
this
is
at
kubecon
in
los
angeles.
In
a
few
months
I
was
going
to
say
at
the
end
of
this
year,
but
technically
in
a
few
months,
and
that's
really
it
for
me.
D
I
will
just
add,
and
thank
you
paris
for
that
announcement.
I'm
gonna
try
and
go
one
thing.
I
wanted
to
say
in
the
chat
here
and
in
the
the
the
sig
channel.
I've
put
a
link
to
a
video
that
some
of
us
did
about
getting
started
with
sick
docs.
A
We
should
put
that
at
the
top
of
the
agenda
too
tim.
That's
so
like
a
wealth,
that's
like
a
gold
mine
right.
There.
A
I'm
so
happy
to
be
here
y'all,
it's
been
such
a
minute
since
I've
hosted
anything
outside
of
governance,
so
I'm
so
happy
to
see
all
your
faces.
If
you
need
any
advice
at
all,
please,
like
I
said
dm
me
all
right.