►
From YouTube: K8s SIG Docs Meeting for 20230530
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
Hey
folks,
welcome
today
is
May.
30Th
2023
today
is
the
welcome
to
the
kubernetes
tig
docs
bi-weekly
Zoo
meeting
I'm
your
host
today,
my
name
is
Ray
lahan
I'm,
one
of
the
co-chairs
for
kubernetes
sick
docs
I'm,
going
to
share
my
screen
here
and
as
I
do
that.
Do
you
want
to
remind
folks
we
do
abide
by
the
cncf
code
of
conduct
which
boils
down
to
be
kind
to
everyone,
and
this
meeting
is
also
being
recorded
and
will
be
uploaded
to
YouTube.
A
Once
we
get
our
once,
we
go
through
our
queue
to
upload
to
Youtube,
so
just
be
mindful
of
that
as
well.
So
as
we
as
we
tend
to
start
off
and
want
to
welcome
any
new
contributors.
If
anyone
wants
to
come
off,
mute
and
want
to
say
hello,
please
do.
A
All
right
see
a
lot
of
familiar
folks,
who've
been
here
and
haven't
been
here
in
a
while.
So
welcome
back
we're
for
those
of
you.
Let's
start
through
the
agenda,
some
updates
and
reminders
the
this
week's
PR
Wranglers
Tim
Bannister.
So
if
you
have
any
open
PR's
that
you
want
reviewed,
please
please
reach
out
to
your
PR
Wrangler.
Next
week's
PR
WR
Wrangler
is
Natalie
flatko,
so
please,
next
for
next
week
for
any
PR
open
PR
as
we
want
to
you
need
reviewed,
have
any
comments
or
questions.
A
Please
reach
out
to
Natalie
next
week
and
there's
a
link
to
PR
Wrangler
shifts
for
those
for
for
approvers.
For
if
you
want
to
know
your
shift
just
please
take
a
look
at
the
at
the
link
here.
A
Also,
if
you
notice
any
code
of
conduct,
violations
for
any
kind
of
meeting
or
slack
channels,
please
feel
free
to
reach
out
to
the
kubernetes
code
of
conduct
committee
all
right
going
to
the
agenda
starting
off
at
release.
128
we
release
128
just
nearly
started
not
too
long
ago,
so
I
think
it's
about
a
week
two
or
three
I
got
the
the
status
from
the
one
from
the
release.
Team
meeting
notes
and
status
is
green
and
the
Shadows
have
gone
through
onboarding
steps.
A
I
did
see
if
you
PR's
to
sync
the
dev128
branch
as
well,
so
I
did
I
saw
those
get
approved
and
merged
so
on
the
Deb
branches
being
synced
weekly,
all
right
any
comments
or
questions
on
the
release,
128s
and
I
believe
the
target.
The
scheduled
release
date
is
for
August
15th.
A
B
Hi
everybody,
hello,
I,
do
have
three
PR's
to
have
looked
good
to
me
label
and
one
has
a
proof
and
but
being
installed
like
one
for
more
what
I
got
a
couple
weeks
and
the
other
one
in
a
week.
I
don't
get
a
reply
from
the
reviewers,
although
I
I
done
what
they've
been
requested
and
one
has
a
kind
of
a
cryptic
note
that
I
don't
know
how
to
interpret
it.
What
what
it's
I
don't
understand,
the
the
apps.
C
A
Yeah
we
could
we
could
discuss
here.
If
we
just
needs
another
review,
we
could
we
could
reach
out
to
the
pr
Wrangler
for
this
week,
which
is
Tim
Bannister
or
you
could
add,
in
the
links
to
the
PRS
on
the
agenda.
If
you're
in
the
agenda
doc
I
am.
B
A
Open
it
yeah
I'll
I
will
paste
it
into
each
other.
B
A
A
So
Cube
system
is
a
namespace
in
kubernetes
and
a
lot
of
most
cnis
will
add
their
running
pods
in
this
keeps
us
and
Mainstays,
but
there
are
some
parts
some
cni
plug.
Is
that
don't
and
there
are
on
their
own
namespace
or
are
not
in
Cube
system
namespace.
A
E
It's
coming
in
from
looks
like
the
kubernetes
page
yeah
gotcha.
A
A
A
Yeah
I
mean
you
would
have
to
go
back
to
where
this
quote
is
from
and
it's
because
it's
you
know
you
didn't
edit
this
section
originally,
but
the
reviewer
might
be
asking
to
please
edit
the
section
as
well
having
more
make
it
or
edited.
So
that's.
It
is
correct,
more
correct
to
how
cnis
work
currently.
A
Yes,
yeah
I
mean
in
the
early
ons,
yes
from
what
I
remember
of
CNN's,
pretty
much
lived
in
keep
system,
but
potentially
not
any
more.
There
are
some
C9
plugins
that
could
be
in
their
own
namespace.
A
A
D
A
I'll,
just
let
I'll
prove
this
PR
and
I'll.
Let
it
and
I'll
make
a
follow-up,
PR
and
I'll
tag
you
and
link
this
PR
to
the
fall
PR
so
that
week,
so
that
we
could
continue
that
discussion
on
that.
On
that
change,.
B
A
A
B
D
A
You
all
right,
any
other
issues
are
PR's
I've.
E
The
other
thing
to
note,
just
in
terms
of
you
mentioned
a
week
or
two
weeks
going
by-
please
don't
take
that
personally.
It's
not
that.
B
They're
busy-
and
they
do
this
voluntarily
so
yeah.
E
So
we
do
appreciate
well
we
well,
we
understand
that
timeliness
is
important,
that
we
also
appreciate
patience.
B
D
A
A
no
GTM
that
would
count
as
a
as
a
tech
review,
so
this
person
would
need
to
give
an
LG
TM,
ideally
or
someone
from
cigats.
A
Give
an
LG
TM
yet
so
chiming
did
from
Sig
Docs,
but
stick
so
typically
for
this
kind
of
change.
So
he
says:
I
don't
know
if
it.
This
covers
the
request
in
the
issue.
A
So
I'll
just
I'll
just
tag
him.
This
person,
who
is
you
know,
see
if
if
he,
if
this
person
is
satisfied
with
the
change
to
please
give
an
LG
TM.
A
A
With
jobs
I'm
sure
it
is
tip
okay,
I'll
ask
the
person
to
provide
an
lgcm
as.
B
B
A
Yeah,
so
did
it
ask
you
to
squash
your
commits
as
well
yeah.
D
A
B
C
Hey
Ray
or
just
a
comment
to
the
folks
on
the
phone
right
here,
so
we've
been
working
a
while
on
the
on
the
kubernetes
Network
model,
diagrams
PR
so
and
with
respect
to
atoms.
I
see
that
there's
an
installing
add-ons
page
that
does
provide
a
list
of
of
network
plugins
I
also
have
in
that
PR
a
set
of
cni.
C
You
know
references
because
I
didn't
want
to
go
into
a
whole
lot
of
detail
in
that,
so
that
might
be
helpful
here
and
then.
Finally,
at
the
bottom
of
the
pr
I
took
sort
of
a
facsimile
of
the
kubernetes
components,
discussion
and
attempted
to
superimpose
the
the
network.
Specifics
of
that
or
at
least
the
next,
some
of
the
network
components.
So
things
like
a
network
plug-on,
the
Pod
IP
addresses
so
on
and
so
forth.
So
I
don't
know
where
that
stands.
C
We've
been
going
on
with
this
for
for
a
long
time,
but
as
just
an
additional
reference
or
if
you
want
to
think
about.
Okay,
we've
got
kubernetes
components,
but
you
know
what
what
are
the
network
components
and
the
idea
was
to
maybe
try
and
explain
that
in
the
kubernetes
Network
model
discussion,
so
yeah
keep
going.
I
mean
there's
a
gads
of
diagrams
here
that
we
were
looking
I.
Think
at
the
very
bottom
oops.
A
C
Images
I
think
I
plugged
it
into
the
into
the
I
think
the
pr
text
itself,
the
pr
discussion.
Oh
there,
we
go
yeah.
C
I
think
I
just
I
I
slung
it
into
a
body
of
a
note,
gotcha
yeah.
C
It
hasn't
been
documented
to
the
extent
that
I
think
it
should
be
so
anybody,
anybody
and
everybody
that's
interested
in
in
trying
to
sort
out
an
initial
Cut,
Above
and
Beyond
the
two
or
three
paragraphs
that
are
in
the
kubernetes
Network
model,
please
by
all
means
included
with
so
this
would
be
Loosely
Loosely
the
components
of
the
architecture
and
then
we're
hoping
to
include
some
implementation
examples,
not
actually
how
you
do
it,
or
this
is
the
only
way
of
doing
it.
C
The
idea
would
be
for
the
reader
to
be
able
to
okay
I
see
this
architect.
What
are
we
doing
here?
How
might
I
do
you
know
interpod
networking
on
the
same
node
sort
of
what?
What
does
it
look
like
and
again
all
these
things
would
be
labeled
with
just
examples
just
to
give
sort
of
the
reader,
the
new
reader,
the
new
to
networking
reader,
actually,
the
networking
folks
itself
like
okay.
C
So
what
are
we
doing
here
because
the
only
documentation
I
think
when
the
in
the
kubernetes
documentation
sphere-
that
includes
you
know
all
the
blogs
that
are
out
there?
C
You
know
the
blogs
go
into
this,
some
of
the
detail,
but
I
think
it's
important
to
have
here
within
the
doc
in
a
kubernetes
documentation,
some
of
which
is
out
there
in
in
all
of
the
blogs
but
they're
specific
to
I
think
implementation.
So
ours
would
be
just
examples
because
the
whole
kubernetes
Cloud
native
Network
spaces,
you
know,
there's
almost
sort
of
endless
combinations.
A
Yeah
I
I,
so
networking
model
and
kubernetes
and
the
documentation
is
very
lightweight.
In
my
opinion,
it
pretty
much
states
that
the
networking
model
is
how
pods
can
get
to
other
pods
cubers
can
connect
to
to
other
pods
as
well
without
netting,
and
we
don't
it's
always.
You
know
kubernetes
abstracts,
the
networking
and
it's
good
to
actually
have
a
deep
diagram
into
how
the
networking
model
is
implemented.
A
So
I
love,
this
hundred
percent
I'll
bring
I'll
I'll
join
a
Sig
Network
meeting
as
well
just
to
bring
it
up
so
that
they
could
do
their
review
on
this.
C
We
have
had
a
review,
so
foreign
architecture
or
components
and
then
again
make
clear
that
these
are
are
just
examples
to
sort
of
get
the
uninitiated
and
the
initiated.
You
know
an
idea
if
you
know
how
do
we
put
these
things
together?
What
do
they
look
like
and
that
sort
of
thing
yeah
yeah,
of
course,
there's
a
bazillion
other
details
that
I
think
we
could
Deep
dive
into
after
at
least
something
is
out
there.
A
C
Yeah,
so
I
was
advised
by
Tim
to
not
speak
specific
to
cni
per
se,
but
you
know
network
plugins,
yeah.
A
100
love
this
I'm,
going
to
bring
it
up
to
this
network
meeting
just
to
get
another
more
eyes
on
it.
A
See
yeah
just
paid
signal,
work
and
Sig
docs
as
well
ask
for
reviews
on
it
from
the
sign,
Network,
slack,
Channel
and
then
yeah,
and
then
we'll
drive
it
from
there.
Okay.
C
Okay
and
Tim
has
been
providing
outstanding.
You
know,
Sensational
guidance
on
this,
so
definitely
want
to
incorporate
any
and
all
subsequent
Tim
Bannister
comments.
At
least
we
got
a
review
from
one
of
the
Sig
Network
folks,
yeah
and
then
Nate
has,
you
know,
suggested
some
other
things
as
well.
So
that's
all
for
now.
This
is
sort
of
you
know.
C
An
active
PR
networking's
involved
a
lot
but
again
putting
on
my
my
networking,
nubile
hat
or
just
again,
somebody
experiencing
kubernetes,
but
not
so
much
the
the
networking
aspect.
This
would
be
somewhere.
This
would
be
something
I
think
I
think
would
helpful
yeah.
A
I
totally
agree
100.
This
will
help
out
new
folks,
too
kubernetes
networking,
even
if
even
veteran
Humanities
users
are
always
abstracted
from
the
network,
so
I
think
the
swap
out
to
give
some
insight.
Definitely.
E
Feeling
a
need.
It's,
it's
appreciated.
A
All
right,
thank
you,
Chris
any
other
issues
or
PRS.
A
All
right
I
want
to
talk
about
two
topics.
What
one
is
a
nomination
for
the
localization
subproject
for
a
colleague
for
syokosan
syoko
is
the
been
one
of
the
leads
for
the
Korean
localization,
and
a
lot
of
the
processes
have
been
really
wonderful.
That
they've
other
localizations
have
actually
adopted
their
their
process
and
localization
for
the
Korean
localization.
So
there
was
a
email
to
the
to
the
Sig
in
terms
of
the
nomination
and
the
there's.
A
lazy,
lazy
consensus
ends
on
June
13th.
A
So
please,
if
you
have
any
questions,
please
reply
to
that
email
chain
or
you
can
bring
it
up
here.
A
A
So
there's
another
one
as
well
for
the
new
name,
roll
issue,
Wrangler
feedback
suggestions
until
June
9..
It's
not
really
in
lazy
consensus
dates,
but
it's
more
of
like
once.
If
we,
if
we
have
enough
positive
feedback
or
on
by
G9,
we'll
go
into
the
next
steps
which
is
defining
and
documenting
the
role
or
issue
Wrangler
and
for
call
for
nominations.
A
The
GitHub
discussion
has
a
good
number
of
descriptions
on
what
that
role
would
be,
and
what
what
that
role
description
be
it's
because
we
have
a
whole
number
of
issues
that
takes
a
long
time
to
triage.
So
we,
it
says
better
maintenance
of
the
issue
of
issue
tracking,
since
the
pr
Wrangler
tends
to
be
over
since
there's
a
lot
of
PR's
right
now.
So
the
pr
Wrangler
tends
to
be
tends
to
work
on
mostly
PR's,
instead
of
going
through
the
issue.
A
So
there's
been
a
call
for
a
new
name
role
for
issue
Wrangler
and
that
has
a
June
9,
not
necessarily
a
lazy
consensus,
or
it
could
be
a
lazy
consensus
but
not
exactly
finalized
until
it's
just
more
of
the
next
steps,
so
feedback
suggestions
until
June
9th
there's
a
link
link
to
the
email
notification
of
that
and
to
the
get
up
discussion.
So
all
any
feedback,
please
add
it
to
the
GitHub
discussion.
D
A
D
To
yeah
sorry,
yeah
I
wanted
to
ask
how
we
can
get
in
touch
with
the
pr
Wranglers
to
become
their
peer,
Wrangler
shadow.
A
Yeah
actually
contact
Abby
or
Brad
or
myself
on
there's
a
date.
You
want
to
be
our
PR
Wrangler
for
you.
Could
you
could
ask
we
could
edit
this
and
we
could
introduce
you
to
the
pr
Wrangler
for
for
that
like
if
we
could
have
it.
So
you
know
you
have
interest
in
PR
WR
wrangling
is
there?
Is
there
specific
dates?
A
You
want
to
be
a
PR
Wrangler
for
kind
of
take
care
of
it.
Now.
A
D
Reached
out
to
Ray
like
a
couple
of
months
back
I
believe
yeah.
A
Over
a
month
yeah,
so
there
are
some
dates
coming
up.
I
know:
Natalie
is
available
in
Nate
and
myself
on
July,
2nd.
D
A
All
right,
any
other
topics
or
questions
or
discussion
points
that
folks
want
to
bring
up
or
any
questions
on
the
localization
sub
project
or
at
the
nomination
for
the
for
a
colleague
for
the
localization
sub
project
and
the
new
issue.
Wrangler
role.
A
It
also
allows
folks
a
way
to
to
claim
what
we
call
the
contributor
ladder.