►
From YouTube: K8S SIG Docs Meeting for 20221115
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
so
welcome
everyone
to
today's
Sig
docs
meeting
today
is
Tuesday
the
15th
of
November
in
the
central
European
time
zone
with
daylight
savings
now
making
sure
that
we
are
all
kind
of
again
aligned
I
know.
Last
two
weeks
ago,
the
meeting
was
likely
a
bit
confusing
for
some
of
some
folks
experiencing
some
daylight
savings
changes,
but
that's
all
taken
place
now,
so,
hopefully
everything's
back
on
track.
A
Given
this
is
a
Sig
docs
meeting
the
kubernetes
project
I
do
want
to
remind
everyone
that
we
abide
by
the
kubernetes
code
of
conduct
here
specifically,
and
so,
if
you
notice
any
kind
of
issues
or
violations
in
the
code
of
conduct
in
an
event
or
a
meeting
specifically
in
our
agenda,
which
I've
linked
in
the
chat
you
can
reach
out
to
the
code
of
conduct
Community
for
the
communities,
project
anonymously
or
otherwise
to
be
able
to
report
that
and
generally
the
tldr
is
that
we
want
to
make
sure
we're
respectful
to
each
other
in
meetings
in
slack
in
PRS
and
issues
and
so
on,
so
that
we're
able
to
work
together,
efficiently
and
respectfully.
A
And
so
with.
That
being
said,
I'd
like
to
kick
off
with
the
first
item
on
our
agenda,
which
is
always
if
you
are
a
new
contributor
to
sigdocs.
We
always
want
to
give
time
for
folks
to
be
able
to
say
hello
and
introduce
themselves,
and
so,
if
there's
anyone
new
on
the
call
to
the
community
to
this
meeting
to
generally
kubernetes
or
docs
in
general,
that
wanted
to
say
hello
feel
free
to
either
unmute
yourself
and
do
so
or
let
us
know
in
the
chat.
B
Hey
degant
from
San
Diego
I
visited
the
cubecon
recently
and
I'm
very
due
to
contribution,
so
I
just
want
to
see
how
the
speeding
works
and
how
documentation
works
in
the
open
source
community
in
the
communities
committee.
So
just
came
here
to
check
that
out.
A
Awesome
Dion
welcome.
Thank
you
so
much
great
to
hear
that
you're
at
kubecon,
as
well
big,
big
event,
big
conference.
A
You
may
know
that
the
next
one
is
coming
up
already
somewhat
soon
in
for
in
on
the
European
side,
in
Amsterdam,
in
April
and
I
mentioned
that
for
anyone
who
is
interested
in
submitting
a
call
for
the
presentations
for
kubecon
in
the
EU
in
in
Amsterdam
next
April
that
closes
actually
this
Friday,
the
18th
of
November,
so
I
kind
of
wanted
to
just
let
anyone
know
if
you're
interested
in
in
speaking
at
kubecon.
A
First
time,
speakers
welcome
as
well
feel
free
feel
free
to
submit
that,
but
welcome
we're
really
really
pleased
to
have
you.
We
definitely
recommend
that
you
join
our
Channel
sick
docs
on
the
kubernetes
slack.
It's
a
lot
of
really
great
resources
and
to
help
you
get
started
there
in
terms
of
your
contribution,
journey
and
learning
about
documentation
at
kubernetes.
So
welcome.
Thank
you.
A
All
right
for
anyone
else,
who's
new
who's
joined
the
call,
and
you
wanted
to
say,
hi
feel
free
to
do
so
in
the
chat
you
can
also,
if
you're
you've
got
access
to
the
agenda
which
you
should
have
if
you
have
joined
the
Google
group
for
Sig
docs,
that
that
means
that
you
should
be
able
to
edit
the
agenda
feel
free
to
add
your
name
under
the
new
contributors
that
say
hi
and
a
fun
Emoji.
If
you
wish
we're
happy
for
folks
to
add
their
information,
there.
A
All
right
so,
with
that
being
said,
we're
going
to
move
on
to
our
quick
reminders
and
updates
that
we
do
for
the
meeting
each
each
two
weeks,
and
the
first
thing
I
want
to
point
out
is
our
PR
wrangling,
PR,
Shadow,
ring
and
wrangling
program
for
folks
when
you
we
in
seek
docs
every
week,
assign
an
approver
to
do
something
called
pi
wrangling,
and
what
that
means
is
that,
as
you
can
imagine,
we
get
a
lot
of
PR's
in
the
kubernetes
project,
specifically
in
docs
as
well,
and
we
want
to
make
sure
that
we're
shepherding
through
these
contributions
as
efficiently
as
possible,
and
so
every
week
we've
got
someone
whose
task
is
to
be
the
person
that
jumps
into
PR's
to
figure
out
their
status,
get
them
moving.
A
Get
them
reviewed,
see
which
sigs
need
to
actually
do
a
technical
review
of
these
PRS
to
make
sure
that
we
can
actually
move
these
contributions
through.
Sometimes
it
means
even
closing
PRS
as
well
anything
to
kind
of
get
the
contributions
going
through,
but
also
making
sure
that
contributors
are
are
being
able
to
get
feedback
on
what
their,
what
they're,
what
they're
contributing
as
well
and
and
so
with
that
this
week's
PR
Wrangler
is
supposed
to
be
Tim
Bannister.
One
of
our
tech
leads
techniques
here
for
sick
docs.
A
However,
it
seems
that
we
may
need
someone
to
step
in
for
Tim,
and
so,
if
we've
got
any
approvers
on
the
call
who
are
interested
in
doing
so,
please
let
me
know
otherwise:
I
am
going
to
make
a
call
out
again
to
the
community
to
see
if
someone
else
can
step
in
I'm
going
to
try
my
best
as
well,
and
the
reason
I
mentioned
stepping
in
is
because
next
week's
PR
Wrangler
is
no
one,
given
that
in
the
US
there
is
a
holiday
called
Thanksgiving.
A
That
is
on
with
a
lot
of
folks
likely
to
be
out
for
the
holiday
break,
so
putting
out
a
call
there
to
anyone
watching
this
as
well
either
we
can
maybe
put
in
a
bit
of
a
team
effort
for
different
approvers
to
jump
in
this
week
to
help
with
PR
wrangling.
A
That
would
be
great,
otherwise
I'll
be
following
up
in
our
slack
Channel
later
on
today,
vital
I
know
you're
on
the
call
how
you're
supposed
to
be
shadowing
this
week,
I
and
I
know
Tim
was
probably
very
helpful
at
first
until
he
was
able
had
to
kind
of
step
out.
So
please
let
us
know
if
there's
a
future
shadowing
slot
that
you
want
to
take
up
to
possibly
replace
that
too.
That's
completely
okay
for
those
who
also
don't
know,
we
also
do
some
shadowing
of
the
pr
wrangling
job.
A
So
people
understand
what
kind
of
tooling
that
we're
using
what
kind
of
possible
processes
that
we
use
every
approver
does
different
things.
So
it's
always
worthwhile
signing
up
if
you're
interested
to
learn
about
the
process,
all
right,
we'll
go
on
to
the
next
sections
here
again,
I've
noticed
I've
mentioned
here.
I
could
have
contact
info
just
always
putting
that
in
our
agenda
now
as
a
way
to
be
able
to
reach
out
to
that
Community
if
you've
got
any
issues.
A
But
next
on
the
agenda
is
the
1.26
release
just
wanted
to
check
I,
don't
think,
we've
got
anyone
on
the
call
here
from
our
docs
team,
but
I
can
take
this
update.
Really
quick.
If,
for
folks
who
don't
know,
1426
is
coming
up
soon
as
a
release,
and
today
is
actually
the
deadline,
which
is
probably
why
we
have
no
one
joining
today.
A
Is
the
deadline
to
have
the
docs
ready,
docs
PR's,
ready
for
review,
and
so
today
is
going
to
be
a
very
interesting
day,
making
sure
that
things
are
going
great.
The
status
right
now
is
green,
which
is
awesome
and,
and-
and
that
means
generally
that
we're
things
that
we're
tracking
from
the
release
stocks
side
is
going
great
and
we've
also
have
link
there
in
the
agenda.
A
The
release
docs
P
Alpha,
merging
1.26
into
the
main
branch
that
will
take
place
during
the
end
of
the
actual
release
cycle
to
it's
got
a
big,
do
not
merge
and
hold
the
area
there,
as
you
can
likely
see
for
folks
clicking
into
the
pr
and
a
quick
recap
on
some
of
the
other
key
dates
from
the
release
schedule
as
well.
A
The
29th
is
the
next
deadline
to
be
aware
of
docs.
That's
when
we've
actually
completed
all
review
of
the
docs
and
that
docs
are
going
to
be
merged.
So
we've
got
another
two
weeks.
Your
PRS
in
terms
of
the
folks
who
are
putting
in
docs
for
the
126
release
the
pr
should
be
in
by
now
and
then
the
rest
of
the
reviewing
needs
to
get
done
over
the
next
two
weeks
so
that
those
mergers
can
take
place
if
you've
got
any
questions
around
the
release.
A
You'll
see
a
lot
of
information
going
on
in
there
about
our
1.26
release
as
well
all
right
that
was
a
really
quick
update
on
the
release
side,
and
now
we
are
going
to
the
general
bulk
of
our
agenda
today
and
we've
only
got
the
one
specific
topic
with
Mahia
bringing
up
a
specific
PR.
So
please,
my
head:
take
it
away.
C
Yeah
I
I
just
launched
a
gubernator
and
figured
out
that
this
thing
was
not
a
merged
at
all,
so
I
was
maybe
thinking.
I
could
bring
that
up
in
the
during
the
meeting.
It's
just
a
really
small
modification.
So
we
had
like
two
issues
about
the
fact
that
the
tutorial
with
the
mini
Cube,
which
is
apparently
quite
used,
will
not
support
RM.
So
someone
actually
made
a
PR,
but
it
was
abandoned.
Somehow
so
I
just
made
a
1pr
with
the
new
image
they
used
in
the
testing
for
a
cigar.
C
I,
don't
remember
exactly
but
yeah
if
you,
if
you
want
to
take
a
look
at
that,
it
will
be
nice
because
it
will
solve
like
two
issues
and
close
one
PR.
So.
A
Yeah,
that's
great.
The
first
thing
I
want
to
say
is:
firstly,
thank
you
for
putting
this
up.
This
is
awesome
that
we
could.
Potentially,
there
are
two
issues
with
one
PR,
so
to
speak,
so
which
is
great,
but
also
this
will
definitely
need
a
tech
lgtm
as
well.
So
we
definitely
want
to
get
some
of
the
folks
from
testing
jumping
in
there
to
have
a
check
I
believe
we
can.
A
We
should
be
able
to
see
if
there's
an
alias,
to
tag
them
in
on
the
pr
itself,
or
we
can
try
and
jump
in
to
see
tagging
some
certain
leads.
I
know
different
sigs
do
things
differently,
but
we
can
explore
that
as
well
to
find
out
I
see
that
Tim's
already
given
a
review,
which
is
great
and
you
let's
say
in
Spirit,
but
we
definitely
would
want
a
lgtm
before
we
had
a
look,
did
any
further
review.
C
Okay:
okay,
because
I
already
like
put
the
seat
testing
label,
so
maybe
I
feel
like
to
put
that
thing
into.
There
was
like
a
channel
and
we'll
try
to.
A
I
will
say,
as
a
person
involved
in
two
sigs,
with
the
many
labels
added
and
just
the
C.
Unfortunately,
the
addition
of
the
Sig
label
is
often
not
enough
to
get
folks's
attention.
A
We
obviously
want
to
label
them
with
the
right
stick
so
that
you
know
people
are
aware
of
where
things
belong,
but
needing
to.
For
example,
often
sigs
will
have
an
alias
for
things
like
PR.
Reviewing
as
an
example
is
something
that
an
alias
we
have
a.
We
also
have
aliases
and
Sig
dogs
for
like
owners
of
the
blog
and
those
kinds
of
things,
so
you
should
be
able
to
find
one
of
those
I'm
also
happy
to
have
a
look
later
on.
A
If
you
need
my
hair,
but
I
think
this
just
needs
a
tech,
lgtm
and
then
I'm
happy
to
go
ahead
and
also
help
approve
this
as
well.
Once
that's
happened,.
C
A
Yeah
right
thanks
thanks,
perfect
yeah,
no
worries
but
yeah,
a
good
tip
for
like
next
time,
if
you're
looking
for
someone's
attention,
tagging
the
specific
Sig
on
top
of
adding
the
Alias
or
specific,
let's
say
leads
that
you'd
like
to
get
reviews
from
always
recommended
as
well
perfect.
A
Nope
big
thanks
again,
my
hair.
This
is
just
want
to
also
say
this
is
a
great
example
of
working
in
the
you
know,
doing
a
process
that
is
actually
kind
of
iterative
and
working
on
things
as
you
as
you're.
Seeing
them
it's
a
great
description
and
great
editing
of
things
that
you've
kind
of
done
and
tried
I
just
want
to
say
that's
a
really
great
example
that
you're
setting
for
the
rest
of
the
community.
So
thank
you.
C
Yeah
no
problem:
it's
a
lot
of
texts
for
a
one
line:
change
but
yeah,
sometimes.
A
That
extra
context
is
super
needed
and,
as
you
can
see,
you
also
explained
how
you
kind
of
like
tested
that
approach.
So
I
think
that
was
very,
very
preferred
there.
A
All
right
that
was
actually
the
only
thing
on
our
agenda.
I
just
want
to
make
sure
that,
if
any
folks
on
the
call
want
to
bring
up
something
else
for
today's
chat
that
they
have
the
space
to
do
so,.
A
All
right
looks
like
no,
which
is
fine,
a
short
and
sweet
meeting
today
of
15
minutes,
always
fun
for
folks
who
join
the
call,
maybe
perhaps
late
and
who
are
new
to
seek
docs.
Firstly,
welcome
and
second
feel
free
to
add
your
name
to
the
gender
as
one
of
the
new
contributors.
We
always
want
to
make
sure
that
folks
are
jumping
into
the
sick,
docs
channel
to
try
and
find
all
of
the
really
helpful
resources
that
we
had
for
getting
started.
A
As
you
can
imagine,
it's
a
very
busy
time
towards
the
end
of
the
year
for
kubernetes
as
we're
coming
to
another
release
cycle
big
big
day
coming
up
in
terms
of
December,
the
6th,
which
is
the
the
next
release
and,
as
I
mentioned,
feature
blogs,
and
the
docs
deadlines
coming
up
on
the
29th
of
November
that'll.
Be
the
next
big
thing
that
we'll
be
discussing
in
terms
of
things
to
get
finished
all
right
thanks
so
much
everyone
for
this
quick
and
short
meeting.