►
From YouTube: K8s SIG Docs Meeting for 20210608
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
Hi
folks,
it
is
tuesday
the
8th
of
june-
and
this
is
the
q
and
et
documentation
special
interest
group
weekly
meeting.
A
We
are
going
to
abide
by
the
cloud
native
communication
cloud
native
computing
foundation,
code
of
conduct
and
be
generally
excellent
to
one
another,
hello,
everyone,
I'm
tim,
a
technical
lead
for
the
special
interest
group.
A
First
of
all,
actually,
let's
see
if
there's
anyone
new
on
the
call.
I
think
I
recognize
everyone,
so
I
doubt
it
but
yeah.
I'm
gonna
put
the
agenda
link
in
the
chat
just
so
that
that's
useful
to
anyone.
Who's
wants
to
see
it
jesse,
hello
and
brad.
A
B
Hi,
if
that
was
to
me
my
audio,
was
still
joining,
I'm
jesse
butler.
So
I'm
on
the
the
122
release
team,
the
comms
team-
so
I
just
I'm
showing
up
to
to
plug
in
and
see
what
I
should
be
paying
attention
to.
A
C
I
cannot
edit,
I
can
see
the
dog
now,
but
I
cannot
edit
just
the
headset.
Let.
A
Me
give
you,
I
presume
you,
you've
got
some
sort
of.
D
A
New
access
restrictions-
I
guess.
C
C
I
can
give
the
the
status
meanwhile,
so
integration
branch
is
healthy,
I'm
still
waiting
on
the
pr
to
merge.
It
needs
a
steering
committee
because
I
believe
there's
it
touches
on
something
that
was
merged
on
either
the
blog
or
some
public
announcement,
or
something
like
that,
but
I
think
it
should
be
solved
very
soon.
Currently,
we
have
40
45
enhancements
that
need
the
documentation
that
need
pull
requests.
C
We
have
nine
draft
prs,
seven
that
are
ready
for
review
and
three
that
were
already
merged,
plus
one
that's
not
in
the
tracking
sheet,
which
is
also
open,
and
I
will
merge
probably
soon.
I
requested
some
some
changes
to
that
and
that's
it.
I
know
no
outstanding
problems,
no
issues
or
anything
else
from
our
side.
A
Okay,
now
I'm
looking
at
the
agenda
here
and
we
have
an
empty
list
of
issues
and
pr's
to
discuss
and
an
empty
list
of
topics
to
discuss
as
well.
It
could
be
a
short
weekly
meeting
but
feel
free.
Now,
if
you
haven't,
got
access
to
right
to
that
agenda,
put
it
in
the
chat
and
we
can
add
it
but
feel
free
now
to
propose
something
to
talk
about.
E
I,
oh
you
can
go,
go
jesse,
okay,
so
I
just
wanted
to
raise
something
for
a
project
that
I
had,
which
is
tracking
spell
content.
That's
a
bigger
project,
this
part
of
our
quarterly
review
process
and
I've
been
sort
of
not
able
to
work
on
that
as
much.
E
But
I
did
want
to
raise
it
here
because
I'm
going
out
on
leave
starting
at
the
end
of
the
month-
and
I
won't
be
back
you
know
until
november,
so
I
was
wondering
if
there'd
be
somebody
who'd
be
interested
in
taking
over
that
project,
and
I
can
give
more
context
if
people
don't
remember
what
that
is,
basically
we're
trying
to
find
a
way
to
track
still
content
on
the
kubernetes
dot,
io
website,
building
automated
processes
to
go
through
the
content
and
see
if
things
have
been
updated,
given
a
certain
window
of
time
and
and
go
through
that,
so
just
wanted
to
throw
that
out
there.
E
If
somebody
on
this
call
was
interested,
I
can
also
follow
up
in
the
channel
and
see
if
get
a
good,
broader
net
of
people
might
be
interested
in
that.
A
A
Well,
that's
not
the
sort
of
response
I
was
hoping
for,
but
it's
you
know
it's
the
honest
answer.
I
don't
think
anyone
does
abigail.
You
are
breaking
somewhat
level
ground.
F
At
least
for
cigarettes,
I
think,
in
terms
of
automation,
the
only
thing
I've
done
in
the
past
is
you
know,
just
have
something
go
through
and
check
that
there
aren't
broken
urls
things
like
that.
What
what
kind
of
things
are
you
thinking
of
abigail
to
check.
E
More
like
content-wise
to
say
whether
or
not
certain
pages
are
out
of
date
if
they
haven't
been
updated
in
like
a
year
or
haven't
been
updated
in
a
while
there's
also
an
idea
of
having
like
a
reviewed
like
a
last
reviewed
date
as
kept
as
metadata
within
a
page.
So
we
can
say
whether
a
sig
has
reviewed
something
for
technical
accuracy
within
a
given
time
period.
So
that's
sort
of
the
goal
more
detect.
The
detective
actually
actual
content
on
the
page
has
been
updated
or
is
out
of
date.
F
Yeah,
that
makes
sense
I
actually
ran
into
something
manually,
tried
to
pull
a
container
to
use
in
one
of
the
procedures
and
basically
hadn't
been
updated
for
five
years,
and
that's
the
kind
of
thing
you
can
find.
You
know
container
names
and
versions
and
try
to
pull
them
and
see
if
they're
still
available,
see
if
they're
outdated,
see
if
they
need
to
be
updated.
That's
kind
of
thing
that
could
go
in
that
could
be
maybe
automated.
E
I
just
posted
a
link
to
a
doc
that
I
had
about
when
I
originally
started
this
project
in
the
chat.
If
people
want
to
learn
more
or
refresh
their
memory
about
where
things
are,
there
hasn't
been
a
lot
of,
maybe
I'm
not
sure
if
people
have
access
to
that.
I
haven't
checked
the
permissions
in
a
while.
E
Maybe
it
was
the
same
issue:
okay,
just
for
more
context
and
some
thoughts
that
I
have
had
and
working
with
other
people
in
the
community
haven't
made
a
lot
of
progress
beyond
putting
this
stock
together.
Unfortunately,
but
I
would
be
really
interested
in
working
with
people
for
the
next
little
bit
if
somebody
is
interested
in
working
on
this
more.
A
Okay,
anyone
wanna
dip
their
appendages
in
the
in
the
in
the
pool
and
stand
out
from
the
herd.
Anything
like
that.
D
Yeah,
I
I'd
definitely
be
interested
in
taking
a
look
at
this,
I'm
just
starting
to
free
up
here
for
the
summer.
I
know
probably
just
jinxed
myself
by
saying
that,
but
you
know
we'll
we'll
see
what
happens.
I
would
definitely
love
to
help
it
on
this
front.
This
looks
this
looks
fantastic.
A
Thank
you,
taylor
right.
I
have
now
lost
my
agenda.
Sorry
about
that.
There
wasn't
anything
on
it.
Are
there
any
other
topics?
There
is
one
thing
I
might
cover,
but
any
other
topics.
People
want
to
talk
about.
B
I
wanted
to
just
ask
so
I
this
is
my
first
time
on
a
release
team.
This
is
really
my
friend
I've
shown
up
to
six.
I've
looked
at
pr's
before
that's
about
it,
so
really
psyched
to
just
be
in
the
loop
learning
a
lot
from
anybody
who's
been
around
in
this
sig
like
is
there
anything
that
the
comms
lead
typically?
Does
that
we
haven't
done
yet?
Is
there
anybody
with
a
raised
eyebrow
going?
B
Well,
we
should
be
doing
x
y
z
that
the
role
handbook
and
the
release
for
folks
who
might
not
know
the
release
team
has
various
functions
and
each
function
has
a
role
handbook
and
there's
a
set
of
shadows
that
can
intern
against
that
and
sort
of,
I
think
shadows,
do
it
with
people
that
have
done
it
before
as
leads,
and
then
you
know
what
to
do,
and
so
the
royal
handbook
isn't
super
detailed.
So
I'm
just
sort
of
asking:
are
we
missing
anything
yet?
C
We
should
have
a
sink
before
the
the
release
and
before
the
release
I
mean
during
the
the
last
week
during
the
last
week
before
the
release,
I
think
the
the
docs
handbook
states
something
technically
I
I
should
come
into
your
chat
and
ask
if
you
have
anything
that
you
want
to
communicate
to
us,
but
definitely
we
we
can
talk
about
it
and
we
can
sync
up
at
this
point.
I
can't
I
have
to
be
honest.
I
can't
think
of
anything.
C
The
only
thing
that
I
think
comes
is
some
some
somewhat
involved
and
from
what
I
take
from
the
release
team
meeting.
The
last
time
is
the
the
blog,
but
other
from
that.
Honestly,
I
don't
know
and
someone
that
is
more
familiar
with
the
blog.
Please
like
I,
I
remember
there
was
a
meeting
for
for
the
blog,
but
I'm
not
sure
I
think
there
was
a
work
group
or
something
but
honestly,
like
I'm
totally
out
of
that.
So
I
think.
B
On
the
release
blog,
I
think
we
have
a
pretty
good
handle
on
that
and
we'll
we'll
shepherd
feature
blogs
as
well.
I
was
under
the
impression
that
we
wrote
them
all,
I'm
so
happy
that
that's
not
the
case
but
yeah
if,
if
anything
comes
up
from
from
anyone
or
anybody,
who's
who's
been
around
in
the
project
for
a
while
and
you're
thinking.
Oh
this.
They
should
have
done
this
by
now,
just
just
holler
at
me.
Otherwise,
just.
A
There
are
a
couple
of
things
that
I
think
sig
docs
doesn't
want
to
happen,
and
you
know
the
release.
The
the
sort
of
the
juncture
of
release
and
sig
docs
is
is,
can
help
avoid
those.
So
one
of
those
things
is
the
sort
of
the
two-line
change
that
deprecates
a
feature.
People
are
going
to
care
about.
Oh,
let's
not
have
docker
shim
anymore.
A
Some
of
these
deprecations
are
really
easy
to
do
in
code,
and
people
might
miss
that
actually,
the
comms
part
of
that
can
be
massive,
so
this
is
as
much
about
listening
to
people
as
it
is
about
talking
to
people,
and
it's
as
much
about
you
know
that
kind
of
detail
as
it
is
about
looking
at
code
and
so
on.
C
Yeah,
I
noticed
that
there's
a
lot
of
pr's
that
that
do
exactly
this.
I
caught
some
of
them
that
weren't
even
tracked
that
were
trying
to
modify
documentation
without
even
being
without
an
exception
filed,
and
I
usually
try
to
to
see
all
the
prs
that
are
opened
against
dev122
and
and
go
over
all
right
now,
there's
also
someone
trying
to
remove
some.
I
noticed
that
you
commented
you,
you
removed
the
lgtm
from
there
someone's,
also
trying
to
remove
a
feature
gate
completely.
A
Think,
that's
just
a
mistake.
You
know
like
yeah
if
we
have
a
separate
piece
of
work
that
I'm
moving
forward
to
make
that
be
a
generated
page,
so
it'd
be
much
easier
to.
That
would
be
an
obvious
ad.
Add
a
deprecated
version
to
a
field
rather
than
anything
like
I
don't
mind
people
getting
it
wrong
there.
That's
that's,
not
a
problem.
Actually.
A
The
second
thing
to
watch
out
for
is
big.
Big
ticket
features
landing,
so
we
have
had
a
couple
of
times
when
we've
we've
released
a
big
feature
to
ga
and
it's
it's
been
sort
of
picked
up
by
the
documentation
side
of
things
really
quite
late
in
the
cycle
that
that's
happening
so
again.
If
anything
big
is
landing.
Maybe
it
went.
Insta
beat
her
in
one
two
one
or
that
kind
of
thing,
and
actually
it's
it's
ready
to
graduate,
but
we
never
documented
it.
A
That's
a
really
good
thing
to
find
out
and
jesse
and
everyone.
This
can
again
be
there's
lots
of
different
ways
to
find
it.
You
can
find
it
by
looking
at
pr's,
but
you
can
also
find
it
by
liaising
with
six
or
with
talking
to
well-connected
people
on
the
internet.
There's.
No.
I
don't
think
there
is
one
good,
good
right
or
wrong
way
to
find
this
out,
but
if
you
can
and
you
spot
anything
you've
done
as
a
great
service.
A
Okay,
we
mentioned
the
blog
a
couple
of
times.
Does
anyone
hear
I
want
to
talk
about
the
kubernetes
blog?
D
Oh,
I
don't.
I
always
want
to
talk
about
it.
I'd
say
that
I
think
that
I
I
have
seen
definitely
an
uptick
in
just
overall
blogs
that
have
come
in
different
requests
and
just
kind
of
using
it
as
a
way
to
announce
to
the
community
and
kind
of
talk
through
some
things
like
was
brought
up
around
the
the
nginx
ingress
project
and
kind
of
getting
getting
the
word
out
there.
D
Definitely,
you
know
always
the
if
you
know
someone
that
wants
to
jump
in
and
help
out
with
reviewing
blogs
and
might
need
some
help
kind
of
establishing
what
that
might
be.
You
know
please,
please
bring
those
people
in
it'd
be
great
to
have
more
help
on
that
front.
We
definitely
go
through
seasons
when
it
comes
to
that
front
too,
we
definitely
see
all
you
know
the
influx
jump
on
that
front
and
then
kind
of
scale
back
during
some
of
the
holidays
and
and
summer
holidays.
D
You
know
other
holidays
around
the
year,
but
yeah
it's
been
it's.
It
seems
like
it's.
We've
been
a
little
bit
overloaded
on
that
in
some
capacity
as
of
late,
but
you
know
definitely
looking
for
more
help
on
that
front
and
and
and
again,
I'm
I'm
starting
to
free
up
apologies
for
for
kind
of
ducking
out
and
hiding
in
the
woods
there
for
a
little
bit,
as
other
things
have
been
going
on.
A
Well,
I
agree
with
all
of
that.
I'm
gonna
call
out
a
couple
of
ways
that
I
think
people
can
help
with
the
the
blog.
That
might
not
be
obvious,
so
one
thing
I
think,
would
be
useful
and
like
never
harmful,
really
is
anyone
who's
got
like
an
administrative
or
you
know,
sort
of
naturally
good
at
organizing
things,
project,
managing
and
so
on,
because
the
blog
project
wants
to
have.
A
I
think
it's
a
weekly
or
fortnightly
meeting
and
if
you
know
someone
who's
looking
to
contribute
like
that,
like
let
them
you
know,
let
them
know
the
opportunities
there,
because
there
isn't
someone
who's
got
the
bandwidth.
I
think
I
think
at
the
moment
to
organize
that
weekly
meeting
and
facilitate
you
might
not.
You
don't
have
to
write
a
word
of
blogger
articles
to
do
that,
although
you're
very
welcome
so
anyone
who's.
Looking
for
that
kind
of
role
or
know
someone
who's,
you
know
interested
in
that
way.
Please
please
mention
us
to
them.
A
There's
been
a
few
people,
who've
sent
me
sort
of
direct
messages
on
slack
and
otherwise
said.
How
do
I
get
involved
in
the
blog,
so
I'm
going
to
try
and
do
some
stuff
to
help
those
folks
get
more
involved.
This
week,
I've
been
on
vacation
a
couple
weeks
and
generally
sort
of.
A
Put
kindling
on
the
embers
of
of
the
sigdoc's
blog
channel
in
slack
and
so
try
and
keep
things
going.
It's
been
a
little
quiet,
but
I
think
it's
it's
not
dead
and
we
can.
We
can
definitely
move
things
forward.
There
do
not
have
any
questions
on
blogging
on
the
kubernetes
blog.
A
Okay,
last
call
for
any
issues,
pull
requests
or
discussion
points
we
want
to
bring
up
in
this
week's
meeting.
F
Actually,
I
do
have
a
question
about
the
the
blogging,
so
in
general
the
types
of
things
that
people
can
submit
for
blogs
is,
it
tend
to
be
maybe
less
formal,
less
stringent
than
maybe
the
doc
site
itself.
So
if
somebody
wants
to
talk
about
something,
that's
sort
of
maybe
a
little
peripheral
or
more
tuned
to
you
know
a
particular
you
know
even
something
associated
with
with
a
particular
company's
way
of
doing
things
I
mean,
because
I
know
they
moved
a
lot
of
that
stuff
out
of
the
docs.
F
A
I
mean
the
one
thing
that
the
blogs
are
not
for
is
outright
advertising,
so
you
know
if
I
went
to
say
I
work
for
the
scale
factory.
You
know
we're
a
consultancy
business
and
you
know
we're
great
at
kubernetes,
because
that's
not
a
blog
post.
That's
that's!
That's
marketing.
A
If
you
want
to
say
I've
got
a
cloud
platform
and
it's
compliant
and
not
mention
any
other
cloud
platforms.
That's
that's
advertising.
A
If
it's
not
advertising
and
it's
kind
of
relevant
to
the
audience,
people
who
who
read
the
blog
are
likely
to
be
interested,
then
then
it's
good.
It
can
totally
be.
I
work
at
this
company
and
we
have
this
really
interesting
way
of
using
kubernetes
it
can
be.
I
wrote
this
thing
that
works
with
kubernetes
and
it's
not
part
of
kubernetes,
and
this
is
how
I
wrote
it.
A
D
A
Well,
there's
plenty
more
ideas
there
and
you
know
feel
free
to
go
back
through
the
blog
archives.
The
the
the
positioning
has
changed
slightly
in
the
last
seven
years
that
we've
been
around
as
a
as
a
project,
but
not
that
much
earlier
blogs
included
weekly
meetings
of
the
whole
project,
which
you
know
we
don't
do
that
anymore,
but
the
kind
of
I
think
it's
kind
of
obvious
how
that's
changed.
A
I
think
it's
pretty
easy
to
look
at
the
last
few
years
of
blog
articles
in
the
index
and
infer
how
it's
done
and,
let's
I'm
very
happy
to
see
people
er
on
the
side
of
of
submission.
I
have
seen
articles
come
in
that
are
like
far
too
advertisingy
and
I've
said.
Look
I'll
review
this
for
you.
That's
that's
too
advertising,
but
there
is
a
great
point
to
be
made
here.
A
Take
out
this
advertising
take
out
these
things
or
link
to
some
other
projects
and
sure
you
can
link
to
your
company's
product,
provided
you
link
to
these
other
three
as
well,
and
you
know
like
we're
not
here
to
facilitate
advertising,
but
we
are
here
to
facilitate
getting
people's
articles
out
there.
Even
if
they
you
know,
do
get
paid
for
writing
them.
A
A
It's
probably
the
right
way
to
go,
even
if,
ultimately,
they
decide
to
close
their
pr,
because
they
did
want
to
to
take
things
a
different
way
like.
Let's,
let's
be
nice,
let's
assume
good
intent.
A
Okay
back
to
the
countdown,
because
does
anyone
have
anything
they
want
to
talk
about
in
terms
of
issues,
pull
requests
or
discussion
points
for
this
week's
sig
docs
meeting?
Otherwise,
I'll
give
you
your
time
back,
counting
down
five,
four,
three,
two
one
that
is
a
sig
meeting
people.
Thank
you
very
much
thanks
everybody
later.
Thank
you.