►
From YouTube: K8s SIG Docs Meeting for 20220208
Description
For more info see https://git.k8s.io/community/sig-docs
A
Foreign
folks
welcome
to
the
February
8th,
kubernetes
docs
meeting.
Do
you
want
to
let
everyone
know
that
the
this
meeting
abides
by
the
cncf
code
of
conduct,
which
boils
down
to
just
to
be
nice
and
to
be
excellent
to
each
other?
This
meeting
is
also
recorded
and
uploaded
to
YouTube
as
well.
So
I
just
want
to
be
just
just
one.
Let
everyone
know
just
to
be
cautious
of
what
they
say
if
they
don't.
A
A
A
D
A
B
Yeah
so
Nate's
here,
but
I
was
sort
of
scheduled
to
give
the
report
today.
So
basically
we're
green
still
early
on
in
the
docs
process
for
the
release.
The
enhancement
freeze
was
this
past
Friday,
so
this
week,
basically
we're
going
to
be
well.
Nate
will
be
handing
out
assignments,
basically
put
the
from
the
all
the
list
of
the
enhancements
on
our
spreadsheet,
we'll
assign
names
to
them
and
then
we'll
start
tracking
down
the
owners
of
the
enhancements
to
begin
filling
in
placeholder
PR's,
where
they
can
put
the
documentation.
C
No
I
just
wanted
to
maybe
mention
the
docker
shame.
Removal
project
is
still
continuing.
We
had
our
meeting
this
morning
and
there
are
still
unassigned
and
untriaged
issues.
So
if
you
want
to
go
through
and
look
at
unassigned
issues,
particularly
there
is,
there
is
work
to
to
to
be
done
and
we'd
be
happy
to
have
you.
A
A
B
C
When
you
say
signal,
we've
got
this
meeting
and
we've
got
the
docker
shim
removal
meeting
and
we've
got
blog
posts
scheduled
I.
Don't
think
the
blog
post
will
necessarily
help
with
our
capacity,
but
at
this
point
for
the
dockershim
side,
I'm
not
sure
that
we
have
hit
our
capacity
ceiling.
I
think
we
can
do
I
feel
like
we
can
do
more
and
I
feel
like
the
people
are
interested
in
doing
more
on
the
the
docs
side.
D
D
So
we've,
essentially,
if
you,
if
there's
a
dial
and
we've
got
sort
of
generic
on
one
end
and
focus
on
dockershim
on
the
other,
we've
turned
it
quite
a
lot
towards
focus
on
dockershim.
That
was
a
sort
of
a
Sig
level
decision
for
Sig
dogs.
But
what
that
means
is
there's
less
capacity
than
usual
and
there's
more
enhancements.
A
I
agree
in
that,
in
that
regard
and
I,
don't
think
we've
communicated
at
all
on
our
cigars
capacity
and
in
terms
of
these
increase
of
enhancements
for
124..
We
pretty
much
had
a
big
increase
or
an
increase
of
enhancements
since
118,
except
for
123..
That
was
the
only
release
that
we
did
not
have
a
continuing
increase
of
enhancements.
C
C
Each
of
us
visit,
sort
of
four
or
five
other
cigs
and
say
hi
may
not
even
be
that
many
to
be
honest,
and
then
say
this
is
this:
is
the
situation
and
do
that?
Probably
sooner
than
later,
I
can
also
bring
that
up
in
the
release
meeting
we
have
on
oh
where's,
my
calendar.
Now
we
have
a
weekly
meeting
tomorrow:
Lanza
8
AM
Pacific
Time
on
Wednesdays,
where
we
have
all
the
leads
for
the
release
and
I
can
bring
it
up
there
as
well.
A
Yeah
I
think
that's
a
good
topic
to
bring
up
in
tomorrow's
release
team
meeting
and
also
a
good
topic
to
bring
up
to
other
Sig
meetings.
The
release
lead.
Actually
he
or
she
joins
the
release
team
meeting
of
other
six
meetings
to
introduce
themselves
and
to
introduce
milestones-
and
this
is
a
good
point-
to
bring
in
the
importance
of
having
doc
PR's
targeting
124
pretty
early
on
yeah,
because
we
always
struggle
and
that's
to
say
the
least,
to
me
to
meet
the
deadlines.
E
A
We
always
tend
to
do
quite
a
number
of
reviews
towards
the
end
of
release,
so
we
spread
it
out
more,
but
there's
there's
a
timeline
issue
with
code
freeze
and
folks
want
to
work
on
their
code
first
before
getting
making
the
changes
to
to
to
the
documentation
so
yeah,
so
yeah
and
and
summary
yeah.
Please
bring
it
up
to
the
releasing
meeting
tomorrow
and
also
do
suggest
attending
those
sign
meetings
as
well.
Just
to
let
people
know
that
we
have
a
good
number
of
increase
of
enhancements.
B
B
You
know
names
within
the
organization
that
can
review
things,
because
that's
where
the
bottleneck
tends
to
be
at
the
end
of
the
release
is
finding
the
the
experts
to
be
able
to
say
that
the
the
docs
are
okay,
so
that
that
I
think
if
we
get
real
names
and
start
communicating
with
them.
Now
that
hey
start
getting
getting
ready,
we're
going
to
be
calling
you
this
last
week
to
to
come.
Look
at
some
some
docs
PRS
I.
Think
that
would
be
a
good
thing
for
us
to
do.
A
C
A
D
It's
over
here
so
yeah.
This
is
a
bit
of
an
odd
we've
got
a
couple
of
places
where
we
we
list
we're
linked
to
a
whole
set
of
essentially
I
think
the
way
I
see.
The
aim
is
that
we
want
to
to
have
a
neutral
way.
To
say
here
are
all
of
the
things
we
know
about
that.
Let
you
do
this
thing
and
container
run
times
would
be
another
topical
example.
D
We
don't
want
to
say
this
is
the
one
to
use
you
can
use
whatever
thing
you
know
you
want,
and
what
we
aim
to
do
is
to
link
to
people's
docs.
We
don't
want
to
say
I
mean
there's
exceptions
for
things
like
Linux
and
windows,
where,
like
you're,
going
to
have
to
be
specific
at
some
point,
but
the
general
thing
is:
if
we
can
get
away
with
saying
there
are
these
47
things
go
and
look
at
these
47
links
to
find
out
how
to
use
them?
D
That's
much
better
than
us,
documenting
47
things
and
how
you
use
them
with
kubernetes,
because
we
haven't
the
capacity
for
that
see,
Nate
doing
a
thumbs
up
so
I
think
that's
the
spirit.
Intent
of
of
this
change,
we
don't
want
to
remove
the
list
of
bone
cnis
entirely
from
the
website.
Yeah
like
somewhere
the
reference
section,
but
somewhere.
We
need
to
have
this
information
and
I
guess:
yeah,
Network,
plugins
somewhere,
but
linking
to
docs
is
strongly
favored
and
then
this
one
Jim
mark.
A
A
F
I
I
have
a
different
opinion,
I
think.
If
you
start
doing
that
people
get
uncomfortable,
you
know
we
try
and
show
that
we're
Thunder
neutral,
and
this
seems
like
it's
the
the
proper
amount
of
yeah.
You
know,
Calico
is
calico
and
what
have
you
and
Azure
is
azure
but
I
kind
of
think
it's
it's
it's
doing
a
nice
job
of
of
of
not
feeling
vendory
by
not
putting
that
in.
G
I
I,
don't
know
I'm,
not
sure.
If
us
advertising,
the
vendor
would
not
make
us
neutral,
but
it
would
help
other
folks
who
do
have
opinions
about
what
vendors
they
want
to
use.
Make
the
right
choice
or
decision
for
themselves,
perhaps
and
I'm
wondering
if
what
the
line
would
be
between
us
being
as
informative
for
folks
as
possible
versus
us
being
neutral.
F
G
F
F
B
D
We
have
no,
we
have
cubenet.
So
let
me
link
to
another
page
I'll.
Stick
this
in
the
chat.
You
can.
You
need
Cube,
you
need.
You
need
an
a
network
plugin
to
make
a
cluster
and
you're
not
going
to
get
very
far
with
what's
built
into
kubernetes.
That's
why
these
are
listed
at
all.
Otherwise,
would
like
that
have
gone
we're
trying
to
get
rid
of
anything
where
you,
you
don't
need
it
at
all
and
say:
I'm!
Sorry,
we're
not
gonna
have.
D
There's
pages
on
the
page
on
deploying
with
Cube
item
used
to
say
as
an
example:
here's
how
to
do
weave
and
we've
taken
that
out.
It's
like
now,
I'm
afraid
it's
just
so
much
more
important
to
be
neutral
than
to
give
an
example
that
we
have
taken
out.
The
weave
example
you'll
now
have
to
go
and
figure
it
out.
So.
G
G
D
H
A
I've
used
the
example
to
install
with
weave
and
when
I
took
the
CK
exam,
because
the
exam
for
I
mean
the
documentations
for
the
documentation.
It
is
also
used
for
the
for
for
exams
as
well
yeah,
so
I,
don't
know
what
what
that's
where
we
should
have.
Links
to
that
versus
have
a
have
some
sort
of
example.
I,
don't
know
where,
where
we
should
draw
that
line.
B
Could
could
we
do
something
kind
of
in
between
I
mean
I
know
this
is
probably
breaking
all
kinds
of
rules,
but
I
I
always
I
try
to
err
on
the
side
of
getting
users
happy
and
but
that's
probably
not
right
in
this
case.
But
what
if
we
gave
like
examples
that
you
know
here's
an
example
of
weave
now
any
other
vendor
can
show
up
and
give
their
links
to
how
to
to
how
to
do
that.
A
B
D
B
A
C
D
A
For
me,
I
have
I
I
have
a
harder
time,
understanding
like
where,
like
I,
think
Brad
mentioning
like.
Where
should
we
draw
the
line
of
what
needs
to
be
updated
on
this
page,
since
this
issue,
blinks
specific
for
specifically
to
the
to
this
networking
page
here
of
what
changes
we
should
have
for
hcni,
as
as
we
mentioned
with
the
link,
or
is
this
short
one
or
two
cents,
you
know
with
the
vendor?
A
Maybe
how
it's
a
little
difference.
That's
how
we
kind
of
have
it
for
some
of
the
cnis
I.
Should
that
be
and
I,
don't
think
that
should
be
part
of
it.
So
we
could-
and
this
is
just
my
opinion-
I
think
I-
could
have
example
of
what
a
change
would
be
and
if
we
could
have
folks,
I
could
link
that
PR
in
the
Sig
docs
slack
Channel
Once,
that's
open
to
have
the
cni
the
vendor
my
opinion
with
the
third
party.
A
What
they're
kept
about
third-party
content
removal
is
to
not
include
differentiating
parts
of
cnis
and
want
to
get
other
people's
opinions
on
this
as
well
or
should
we
include
like
what
what
the
cni
or
how
the
cni
works?
As
we
see
some
of
this
here
as
well,
my
opinion
should
just
be
the
link
in
the
vendor
and
just
maybe
one
sense
about
the
cni,
but
not
really
showing
the
advantages
of
a
cni.
D
I,
guess
is,
is
someone
and
I
have
to
admit?
I
was
doing
the
issue,
so
there's
my
thing,
I
might
be
repeating.
Is
someone
willing
to
to
own
or
or
act
as
someone
to
to
liaise
with
those
new
contributors
and
and
at
least
have
an
answer?
Even
if
the
answer
is
we're
still
discussing
this?
Would
someone
be
willing
to
take
that
liaison
role
so
they're
not
hearing
nothing
I
could
do
that.
H
So
if
you
just
go
down
a
little
bit
farther
you'll
see
a
screenshot
of
the
language
drop
down
on
the
docs
site
and
some
of
the
languages
have
you
know
the
the
language
written
in
the
nib
alphabet
and
then
also
in
English,
but
that's
not
the
case
for
all
of
them.
So
we
decided
to
you,
know,
create
a
standard
as
the
localization
group
and
so
it'll
be
written
in
you
know
the
native
language
and
then
also
in
the
the
English
alphabet,
not
English
the
Latin
alphabet.
H
H
A
F
You
know
if
you
look
at
the
ones,
if
it's
great,
if
you
look
at
the
top
three
compared
to
the
bottom,
three,
the
top
three
all
of
us
can
figure
out
which
language
it
is,
and
the
bottom
three
needs
some
very,
very
talented
people
and
educated
people
to
figure
out
the
last
three
or
four
or
you
take
a
guess.
Right.
I
could
maybe
get
one
out
of
four
right.
A
C
A
C
E
A
B
F
I
I
handled
the
UCLA
for
my
company
and
so
I've
I've
been
pretty
familiar
with
having
to
open
issues
regarding
acla
and
not
working
for
people
and
having
to
do
special
things.
Is
it
just?
Is
it
I
thought
that
had
calmed
down,
but
is
it
not
calmed
down
that
certain
people,
just
the
UCLA,
says
no,
no
go
and
they
can't
they
can't
push
their
PR.
E
So
you
know
we
had
one
bot
before
right
so
Brad,
so
that
bot
was
not.
We
didn't
have
the
source
code
to
browse
things
and
it
wasn't
giving
enough
information
so
easy.
Cla
was
a
thorough
rewrite
from
scratch,
and
cncf
funded
certain
set
of
people
to
write
that
bot.
Now
they
are,
they
are
rolling
it
out
for
like
two
months
or
so.
E
We
were
running
both
parts
parallely
just
to
shake
out
all
these
issues,
while
they
were
trying
to
sync
information
from
the
old
system
to
the
new
system
and
when
things
settle
down
there
now
we
feel
that
it
is
time
to
you
know,
disable
the
old
bot
and
just
use
the
new
bot.
That's
basically
what
happened.
E
So,
yes,
there
might
be
some
people
who
might
get
caught
with
the
easycls
stuff,
but
the
easy
UCLA
you
know
going
through
the
prompts
that
the
bot
leaves
as
comments
it's
easier
to
get
in
and
like
sign
your
CLA.
If
you
run
into
trouble-
and
we
also
have
an
open
issue
still
for
tracking
any
of
the
stragglers
which
we
might
see
in
during
this
release.
Okay,.