►
From YouTube: K8s SIG Docs Meeting for 20221129
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,
hello,
everyone
today
is
Tuesday
the
29th
of
November
2022.
We
are
exceptionally
close
to
the
latest
release
for
this
year
for
kubernetes.
This
is
the
Sig
docs
meeting.
It
is
1830
UTC
I'm,
going
to
try
and
use
the
universal
time
here
for
our
recordings,
and
my
name
is
Natalie
I'm,
one
of
the
co-chairs
of
sigdocs
and
hopefully
for
those
on
the
call
hello
and
everyone
watching
me
recording
hope
this
finds
you
well
in
the
future.
A
A
Once
again,
you
will
see
that
under
the
updates
and
reminders,
we
have
got
information
about
the
code
of
conduct
there
that,
if
you
notice
any
kind
of
violation
in
an
event
or
meeting
or
in
slack
you
can
reach
out
to
the
kubernetes
code
of
conduct
committee
that
is
linked
there
or
via
email,
where
you
will
be
anonymous
general
gist
of
the
code
of
conductors
that
we
want
to
make
sure
that
we're
excellent,
respectful
and
kind
to
each
other,
and
that
is
I,
mean
meetings
in
text
on
slack
and
mprs
and
issues
as
well.
A
Thanks
again
for
everyone
joining
us,
we've
got
a
few
folks
on
the
call
which
is
awesome
and
I've.
Also,
as
I
mentioned,
I
posted
the
agenda,
because
we
did
only
have
up
until
me
looking
at
it
just
recently.
Just
the
one
topic
so
feel
free
to
add
any
issues,
PRS
or
questions
discussion
topics
as
we
go
through.
A
We
can
also
just
discuss
them
ad
hoc
as
I
go
through
everything,
but
the
first
thing
that
I
wanted
to
do
on
this
week
before
a
lot
of
a
couple
weeks
before
the
release
it
takes
place.
A
Is
that
any
new
contributors
on
the
line
that
wanted
to
say
hello,
anyone
new
to
either
sigdocs
new
to
kubernetes
new,
to
open
source?
That
wants
to
say
hi
now's
your
time
to
unmute
and
say
hello.
B
Hello,
this
is
Rajesh
I'm
joining
for
the
first
time
for
the
Commodore
six
talks,
meeting
yeah.
A
Hi
Rajesh
welcome.
Thank
you
so
much
for
joining
great
to
have
you
and
if
you've
got
any
questions
about
anything
regarding
sync
docs,
a
lot
of
helpful
folks
here
in
the
virtual
room
today,
but
we've
also
got
a
lot
of
really
great
resources
in
our
Sig
docs
channel.
On
slack
where
you
can
join
us
as
well.
B
Yeah
I
already
joined
in
the
commodity
slack
channel
on
the
sick
dogs.
I
am
also
closely
following
up
in
the
slack
Channel
yeah.
A
No
worries
any
other
new
folks
want
to
say
hello.
If
you
don't
want
to
unmute,
you
can
also
say
hi
in
the
chat
as
well.
C
Hi
I'm
not
new
to
Zig
talks,
but
it's
my
first
time
in
this
meeting.
My
name
is
Maureen
and
I
have
been
contributing
localization
for
the
Brazilian
Portuguese.
A
Also
Maureen
hi
thanks
so
much
for
joining
I
do
believe
we
met.
Did
we
meet
at
the
at
the
kubecon
I
believe?
Yes,
we
did.
Yes,
we
did.
There's
your
face,
hi
great
great,
to
see
you
thanks
so
much
for
joining
great
to
have
some
folks
in
our
localization
groups
also
joining
us
as
well.
So
that's
awesome.
Welcome
to
the
meeting.
Thank
you
very
much.
A
D
A
Awesome
hi
it's
and
welcome
thanks.
So
much
for
joining.
This
is
great
to
have
a
bunch
of
our
localization
folks.
So
thanks
so
much
for
saying
hi,
yes,
welcome!
We
are,
as
you
know,
questions
in
sync.
Docs
are
also
the
docs
localizations
channels
as
well
also
great
places
to
ask
questions
as
well.
A
A
Going
twice:
okay,
oh
hi,
Karthik!
Yes,
see
you
in
the
chat
hi
there.
How
are
you
welcome
to
the
meeting
we?
Hopefully
we
can
answer
any
questions
that
you
might
have,
or
hopefully
help
with
any
kinds
of
issues
or
Piers
that
you
wanted
to
bring
up
or
just
help.
You
learn
some
new
stuff
about
docs
and
communities,
we're
all
we're
all
here
and
we're
all
friendly
so
happy
to
happy
to
answer
questions
for
you.
A
Great
I
think
we
then
set
on
the
hellos.
If
anyone
else
wants
to
say,
hi
feel
free
to
do
so
in
the
chat
or
great
to
hear
Karthik
that
you're
making
some
contributions.
That's
awesome,
the
more
the
better
we're
always
for
that,
but
yeah,
more
Hollows
in
the
chat
or,
if
you
want
to
just
add
yourself
also
under
the
new
contributors
in
in
our
in
our
agenda,
feel
free
to
do
so
as
well.
A
What
I
want
to
do
now
is
quickly
move
on
to
just
some
updates
and
reminders.
So
this
week's
PR
Wrangler
is
kimming.
Who
is
one
of
our
tech
leads
here
for
sigdocs
important
week,
because
we've
got
a
few
docs
deadlines
coming
up
as
well,
so
kimming
is
also
doing
his
fair
share
of
reviews
and
I
know
Tim
who's
on
the
call
to
is
doing
a
bunch
of
reviews
alongside
a
couple
of
us
in
myself,
Divya
and
Ray
as
well.
A
So
as
a
note
folks,
the
pr
Wrangler
is
what
we
call
someone
who's
weak.
It
is
to
Shepherd
contributions
through
that
we're
getting
in
Sig
docs
to
try
and
move
contributions
forward
so
that
we
can
keep
our
PR
count
at
a
decent
level
at
the
moment,
given
that
we
are
so
close
to
a
release
and
we're
at
a
docs
deadline.
Pr,
the
number
is
up
right
now,
but
that
will
change
very
soon
as
we
merge
a
lot
of
docs
changes
and
feature
blocks
through.
A
But
as
a
note,
we
do
have
a
weekly
roster
of
PR
Wranglers.
These
are
approvers
in
Sig
Docs,
who
can
make
sure
that
changes
get
shepherded
through
to
to
the
website,
so
big,
a
shout
out
to
kimming
and
also
to
Tim
I,
know
you're
doing
a
lot
of
work
this
week.
So
thanks
so
much
and
I
do
want
to
mention
that
next
week's
Wrangler
is
Anna
young
as
well,
so
for
any
other
approvers
on
the
call
make
sure
you
know
your
scheduled
shifts.
A
As
a
note,
we
are
coming
up
to
a
holiday
season
where
we
will
have
two
weeks
at
the
end
of
the
year
where
we
won't
have
Wranglers
on.
It
is
a
quieter
time
on
the
on
the
general
kubernetes
contribution
from,
but
for
anyone
who
wants
to
kind
of
jump
on
and
still
do
some
reviewing
at
that
time.
It's
always
welcome
great
another,
just
call
out
again
in
the
updates
or
reminders.
A
Of
course,
if
you
know
notice
anything
on
the
code
of
conduct
side
that
you
want
to
report,
please
feel
free
to
use
the
Avenues
at
your
disposal
to
do
so.
We
want
to
make
sure
our
community
is
inviting
in
kind.
Okay.
Let's
move
on
to
the
rest
of
our
agenda.
Now,
with
the
1.26
release,
do
we
have
anyone
from
the
release
docs
team
on
the
call
I,
don't
think
so,
but
I.
A
E
My
update
I
think
we're
at
yellow
for
docs
at
this
point,
I'm
actually
at
the
bottom
here.
If
we
have,
if
anyone's
got
time
to
help
with
reviews
today
is
the
deadline,
we've
got
about
six
or
eight
outstanding
reviews.
Pr's
that
are
are
need
stocks
that
are
ready
for
review.
So,
if
you
have
time,
that's
lovely
I,
think
I
think
some
of
them
are
are
requiring
tech
reviews.
E
A
Definitely
thanks
so
much
Nate
yeah,
just
a
reminder
for
folks
who
may
not
know
we
have
a
lot
of
different
deadlines
throughout
a
release,
and
today
the
29th
is
the
deadline
to
have
all
docs
changes,
not
only
reviewed
but
merged
as
well.
So
a
lot
of
us
are
doing
a
bit
of
extra
work
to
make
sure
that
those
changes
are
coming
through.
A
There
will
be
folks
throughout
the
day
slash
evening
in
their
respective
time
zones
doing
some
work
as
a
end
of
day.
I
believe
on
in
the
PST
time
zone
is
when
we
expect
all
of
those
changes
to
be
merged
and
done
great
PST
being
Pacific
time.
I
should
I
should
not
use
too
many
acronyms.
A
Okay
with
that
being
said.
Also,
today
is
the
deadline
for
feature
blog
review
as
well.
I
know
we
do
Tim
I,
don't
know
if
you
wanted
to
kind
of
chat
about
any
blogs
that
do
need
kind
of
some
support
or
help
on
your
end,.
F
We've
got
a
new
process
this
this
release,
so
there's
a
deadline
and
it's
it's
a
deadline
as
in
something
changes.
If
you
don't
meet
it,
it's
not
that
your
blog
doesn't
go
out,
but
your
blog
doesn't
form
part
of
the
Post
Release
stream,
so
release
comms
are
leading
on
that.
Anyone
from
release
comes
on.
This
call.
F
So
they're,
leading
on
that
side
of
things
and
we'll
see
how
that
goes
on
the
Block
team
side
and
that
blog
team
is
anyone
who
wants
to
say
I'm
part
of
the
Blogger
team.
Really
thanks
for
the
thumbs
up
Nate
once
we
know
what
what
has
has
you
know
got
ready
for
the
deadline
like
there's,
obviously
a
Blog
in
place,
a
Blog
article,
it's
like
reviewable,
it's
not
missing
half
the
article.
It's
there.
F
F
Something
I
am
going
to
try
and
do
I
am
going
to
try
and
find
tasks
like
small
to
medium
tasks
with
like
there
is
a
thing
rather
than
me.
You
know
doing
things
and
Nate
doing
things
so
I
encourage
everyone,
who's
who's,
who
who's
on
board
of
this
to
do
it,
publish
some
tasks
in
the
in
the
blog
channel
and
say:
hey,
there's
a
task
that
he's
doing
who
wants
to
pick
it
up?
I
did
one
earlier
and
more
of
that
will
be
good
because
it
ain't
it.
F
It's
like
a
good
first
issue
for
it
for
other
forms
of
contribution,
so
I'll
be
doing
more
of
that,
as
I
can
and
I
think
that'll
be
a
good
way
to
to
broaden
access
and
and
help
people
who
don't
know
how
to
do
the
task
at
all.
Like
that's
fine,
you
don't
have
to
do
it
yet
we
will
help
you.
That's
that's
my
aim.
A
That's
awesome
thanks.
So
much
Tim
I've
just
noted
that
in
the
in
the
agenda
too,
so
as
a
note
for
anyone
either
watching
currently
or
on
the
call
right
now
for
anyone
interested
in
helping
out
with
sigdocs.
But
maybe
you
don't
know
how
to
get
started.
Maybe
you'd
like
to
help
with
things
that
you're
still
learning
about
in
terms
of
kubernetes
and
how
a
lot
of
it
works.
Reviewing
blogs
is
actually
a
great
way
to
jump
in
and
help
out,
and
it
sounds
like
Tim.
A
A
We
just
noted
that
November
29
is
all
the
1.26
docs
are
completed
and
emerged
and
feature
blogs
are
ready
for
review,
but
the
final
deadline
is
on.
The
6th
of
December
is
the
release
which
is
which
is
on
Monday
I,
believe
not
Tuesday
the
following
week.
Sorry-
and
so
with
that.
A
Interestingly,
we
do
do
a
bit
of
work
in
Sig
dogs,
but
we
do
need
to
freeze
the
website
and
we
do
need
to
do
a
bit
of
work
on
our
end
on
the
release
side
to
make
sure
that
changes
can
go
in
and
everything
goes
smoothly
with
the
release
as
possible
and
fortunately,
slash
unfortunately,
looks
like
I'm
the
person
doing
the
freezing
this
this
cycle,
and-
and
so
this
would
be
a
this-
would
be
even
even
chair.
A
Even
co-chairs
of
Sig
docs
get
to
learn
new
things,
and
this
will
be
something
that
I'm
teaming
up
with
another
co-chair
of
ours:
Jim
Angel
and
hopefully
the
two
of
us
are
going
to
get
through
things.
Just
fine
another
creature
of
ours.
Ray
who
isn't
here
he's
unwell
but
he'll,
be
a
fit
as
a
fiddle.
Very
soon
has
written
up
some
great
information.
A
Interestingly,
for
me
to
follow
as
well
so
that'll
be
that'll,
be
a
fun
experience
for
everyone,
so
even
I'm
learning
something
new
for
folks
on
the
call
jump
in
and
help
us
with
some
blog
reviews.
That's
it's
a
great
way
to
get
started.
A
Okay,
with
that
being
the
case
thanks
so
much
for
adding
those
those
links
in
there
Tim.
Finally,
we're
now
going
to
go
over
to
the
next
part
of
our
agenda
with
issues
and
PRS
and
I
want
to
thank
Maureen.
Thank
you
so
much
for
adding
this
specific
PR
did
you
want
to
take
the
mic
and
have
a
chat
about
it?.
C
Sure
so
I
created
this
PR
to
pick
it's
kind
of
a
fix,
so
we
originally
had
before
I
started,
contributing
to
the
docs.
We
had
one
folder
for
the
Portuguese
content
that
was
called
just
PT
and
at
some
point
last
year
I
was
not
involved
yet
so
I'm
not
I,
am
not
clear
on
the
circumstances
it
seems
like
there
was
an
update
with
the
doxy
theme,
which
started
to
break
some
links
and
that
folder
was
updated
to
pt-br,
which
is
the
language
code
and
location
code
for
Portuguese
from
Brazil.
C
What's
happening
right
now
is
that
we
have
this
folder,
that's
still
called
PT
and
I
intended
to
rename
it.
So
it
becomes
consistent
with
the
rest
of
the
website
and
I
just
wanted
to
check
if
there
are
any
concerns
or
any
objections
to
this
change.
So
we
can
push
this
back.
F
Portuguese
is
an
interesting
language.
There's
there's
two
languages
in
the
world
where
the
sort
of
the
the
country
with
the
big
number
of
speakers
is
not
where
they
invented
the
language.
So
English
obviously
has
a
sort
of
anglo-saxon
origin,
but
you
know
there's
the
most
English
speakers
are
in
America
and
it's
Canada,
and
what
have
you?
Portuguese
has
a
similar
thing
due
to
the
the
history
of
Portugal
traveling
to
South,
America
and
all
of
that
stuff,
going
on.
F
There's
lots
of
Portuguese
speakers
in
one
country
in
Brazil
and
that
is
kind
of
the
dominant
Portuguese
localization.
That's
where
the
people
contributing
come
from,
so
people
who
are
localizing
kubernetes
to
Portuguese
are
localizing
it
to
Brazilian
Portuguese.
We
don't
have
a
localization
to
British
English,
although
that
would
be
fun.
F
Maybe
that'll
come
later,
so
Portuguese
is
kind
of
breaking
ground
here
like
there
might
be
other
examples,
but
I,
don't
think.
There's
many
languages
in
the
world
which
have
that
history,
where
spoken
in
a
different
country
and
then
the
the
not
that
the
home
country
is
not
what
the
one
way
which
speaks
it
most.
A
I
do
want
to
point
out
as
well
Seko,
so
helpfully
pointed
out
that
there
it
was
the
Chinese
case
of
the
renaming
from
zh
to
zhcn,
specifically
for
for
that
case,
so
there
is
some
precedent
which
is
which
is
good,
but
I
with
that.
Being
that,
with
that,
existing
I
personally,
don't
feel
like
there's
a
there's,
a
there's,
a
blocker
here,
but
happy
to
hear
from
other
folks.
F
The
motivation
for
doing
the
change
to
Chinese
was
that
doxy
uses
zhcn,
and
it
was
just
a
pain
to
have
things
in
doxy
that
then
every
time
we
updated
doxy
it
made
Chinese
the
Chinese
stuff
look
stale.
So
that
was
the
motivation
of
for
the
Chinese
rename.
E
Is
there
a
I'm
just
looking
through
the
doxy
site,
I'm,
not
seeing
it?
Is
there
a
localization
preference
for
Brazilian
Portuguese
that
Doxie
uses
should
we
should
we
be
matching
their
stuff
or
is
it
something
that
we're
doing
that
is
novel.
A
Look
yeah,
yeah,
I'm,
not
sure,
but
I
think,
firstly
again,
Maureen
thanks
for
bringing
this
up.
I
think
this
is
one
of
those
things
where
it's
good
for
visibility
to
chat
about
it
and,
as
you
can
see,
we
haven't
chatted
about
a
change
like
this
before
much
so
it
was
there's
not
a
lot
of
not
too
much
for
or
against
strongly
in
either
way,
just
figuring
out.
A
What's
going
to
be
the
least
pain
and
makes
the
most
sense
specifically
for
the
workflows
that
you'll
be
following
and
and
with
with
doxy
I.
Think,
that's
the
that's
the
way
to
go
here.
What
I
might
suggest
then
Nate?
You
said
that
you're
looking
into
what
does
doxy
use,
perhaps
if
you
do
end
up
finding
it.
If
we
keep
moving
through
our
agenda,
we
can
kind
of
come
back
to
this
point
and
see
great.
A
If
not
maybe
we
can
we've
you've
linked
the
pr
there
more
in
the
in
the
agenda
and
I've
also
linked
it
here
in
the
chat.
We
can
also
continue
that
chat
in
the
in
the
pr
itself,
so
we
can
make
the
changes
ASAP
if
changes
are
to
be
made.
Yeah,
that
sounds
great.
Thank
you
awesome.
Thank
you
so
much
thanks
for
bringing
that
to
our
attention.
A
Alrighty
then
jumping
over
to
actually
before
I
jump
over
to
anything
else,
given
that
we're
in
the
issues
and
PR's
section
of
the
of
the
meeting
I
do
want
to
see
if
anyone
has
any
other
issues
or
PRS
that
they
wanted
to
bring
to
our
attention
here
at
today's
meeting
feel
free
to
just
throw
it
in
the
chat
and
unmute
yourself.
If
you
wish
totally
fine.
A
Alrighty
I'm,
taking
that
silence
as
a
no
that's
great.
So
we
will
move
on
to
the
next.
The
next
topic
then-
and
the
next
topic
is
actually
from
me
in
terms
of
discussion
points
I
mentioned
that
here
in
the
agenda
that
we
do
have
one
last
meeting
of
the
Year
scheduled
for
sick
dogs,
which
is
on
the
13th
of
December.
A
But
that
will
come
after
after
a
release
very
soon
after
a
release
and
it'll
also
come
in
a
kind
of
a
time
period
where
people
are
getting
ready
to
spin
down
for
the
year
before
we
kind
of
get
started
with
the
next
next
release
cycle,
and
so
I
wanted
to
propose
that
we
canceled
that
meeting
and
move
it
to
a
slack
meeting
so
that
folks
can
kind
of
get
started
in
having
less
Zoom
time
happy
to
hear
exceptions
or
or
rejection.
A
Right,
so
that's
what
we're
going
to
do
then,
unless
anyone
else
and
anyone
else
says
otherwise,
happy
to
make
as
much
async
as
possible,
so
that
we
can
get
a
bit
more
time,
spinning
down
and
and
bringing
in
the
New
Year
alrighty.
A
That
was
the
only
agenda
topic
that
I
specifically
had
I
mentioned.
That
Divya
was
all
for
it
too,
but
she
and
I
didn't
want
to
just
make
a
decision
in
a
vacuum.
So
hence
me
bringing
it
to
the
meeting.
Any
other
discussion
points
that
folks
wanted
to
bring
up
in
this.
Our
last
Zoom
call
of
2022.
E
It's
always
good,
it's
always
good
to
see
so
many
folks
and
it's
been
for
me
I'm
from
my
part.
It's
been
great
working
with
all
of
you
this
year.
So
I
wanted
to
say
that,
verbally
before
we
get
into
our
HD
sync
format
but
happy
Holidays,
happy
New,
Year,
and
all
that,
if
I
don't
see
you
all
before,
then.
A
Well,
thanks
Nate
yeah,
happy
happy
holidays
and
happy
New,
Year
too
I
know
all
of
us
will
be
in
our
different
parts
of
the
world.
You
know
celebrating
in
our
different
ways.
That's
really
nice
of
you
to
say
it's.
A
A
If
you
do
join
the
Sig
docs
slack
Channel,
that's
where
we
will
do
our
asynchronous
bi-weekly
slack
meetings
there,
either
myself
or
Ray
or
Divya
the
coach
other
co-chairs
that
we
have
we'll
start
threads
where
you
can
chat
about
or
put
in
different
issues
and
topic.
Sender
PR's
that
you'd
like
to
chat
about
so
that'll
be
the
way
that
we
do
any
further
communication
for
the
rest
of
2022
alrighty.
A
Folks
with
that
being
said,
Tim
thanks
for
adding
that
that
PR
in
there
I'll
happily
do
a
review
in
there
once
we
jump
off
the
call.
A
Sorry
did
someone
just
unmute
hi,
no
bye.
Okay,
sorry
Tim
was
that
you
I.
A
No
worries
at
all
no
worries
I'm,
just
just
speaking
to
the
speaking
to
the
camera
right
now
for
everyone
else
wishing
you
all
the
really
great
rest
of
the
year
great
rest
of
this
morning,
reviewing
time
that
we've
got
left
for
docs
for
the
1.26
release,
keep
your
eyes
peeled
for
a
lot
of
cool,
interesting
work.
Coming
up
for
the
next
release
that
will
take
place.
A
A
That's
going
to
be
something
that'll
be
interesting
for
you
to
keep
an
eye
on
if
you're
interested
in
getting
a
little
bit
more
involved
in
the
kubernetes
project
that
will
be
under
the
the
channel
sting
release,
Australia
program.
Karthik
is
where
you
basically
team
up
with
someone
who
is
doing
a
specific
role
in
the
release
schedule
for
kubernetes.
The
specific
role
that
us
as
seek
docs
as
a
group
is
involved
in
often
is
the
documentation
that
is
coming
and
we
have
a
release.
A
Docs
lead
and
we
have
a
Communications
lead
that
takes
the
role
of
making
sure
that
all
of
the
work
around
those
points
are
streamlined
and
and
and
moving
accordingly
for
the
specific
release.
So
you
would
then
get
it
get
to
team
up
with
those
folks
and
see
what
kind
of
work
that
is
and
if
you
want
to
possibly
do
that
work
as
a
lead
yourself
in
future.
A
A
Alrighty,
that's
enough
for
me.
It's
dinner
time
where
I'm
at
so
I'm
gonna
eat
some
food.
But
wishing
you
all
a
great
rest
of
the
end
of
the
year,
hope
you
stay
healthy
and
safe
and
we
will
connect
back
on
zoom
in
2023.