►
From YouTube: K8s SIG Docs Meeting for 20210330
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
To
discuss
I'll
leave
it
to
you
tim.
A
Actually,
jim,
I'm
not
really
prepared
for
this
I'll.
Let
you
if
drive,
if
you
may
yeah
no
worries.
Oh,
I
just
saw
the
recording
has
started
awesome,
cool
cool
yeah,
not
a
problem
at
all,
so
hey
everybody,
thanks
for
bearing
with
us
for
the
rocky
start
here
for
the
sig
docs
weekly
meeting.
I
am
jim
angel,
one
of
your
co-chairs.
A
A
All
right
well
welcome
back
good
to
see
everybody
moving
on
to
the
updates
and
reminders.
This
week's
pr
wrangler
is
jimmy,
and
next
week's
pr
wrangler
is
zachary
sarah
on
github,
or
is
that
core
lesson
approvers
make
sure
you
know
your
scheduled
pr?
Wrangler
shifts
the
link.
There
is
also
in
the
agenda.
A
C
All
right
so
tomorrow
is
a
big
deadline
for
docs.
It's
the
docs
complete
deadline.
I
put
our
current
status
as
yellow
because
we
still
have
seven
open
dock
pr's
that
are
under
review.
We
did
ping
appropriate
sigs
and
appropriate
people
who
are
marked
as
reviewers
under
under
the
kept
under
the
cap
for
tech
reviews.
Most
of
them
are
we're
waiting
on
additional
tech
reviews,
except
for
one,
though
I'll
talk
about
a
little
bit
later,
so
the
integration
branch
is
healthy.
C
Next
week
I
put
in
the
agenda
just
the
high
level
steps
of
what's
going
to
occur
next
week
in
regards
to
the
121
in
regards
with
the
121
release
like
creating
the
release
branch,
getting
help
from
sig
doc's
chair
to
updating
up
netlify
freezing
the
repo
on
on
the
day
before
and
so
forth.
So
put
those
high
level
steps
in
the
agenda.
I
know
gemini
you
gotta
go
someone
go
into
great
detail,
those,
but
anyway
so
yeah.
So
that's
pretty
much
it.
C
I
just
want
to
thank
all
the
sig
docs
reviewers
for
all
their
reviews
and
especially
on
on
how
quick
and
thorough
they've
been,
and
so
I
think
that's
it
for
me,
and
I
do
want
to
continue
a
little
bit
more
with
the
issues
and
prs
and
the
next
in
the
agenda
in
a
little
bit.
A
Cool
yeah
thanks
great
and
one
thing
I've
done
in
the
past.
I
don't
think
I
did
it
for
the
120
release.
Is
we
usually
will
create
a
zoom
kind
of
war
room
if
you
will
for
docs
it
helps
out
just
having
that
link
handy
and
ready
to
go
in
case
any
fires
do
occur.
I
will
say
over
the
past
three
or
so
releases
things
have
been
a
little
less
on
fire
e,
so
knocking
on
wood
is
not
needed,
but
feel
free
to
dm
me.
If
I
don't
create
that
it
just
comes
in
handy.
A
You
and
thank
you
for
all
your
work
on
this
release.
It
it's
been
a
fun
one
and
then
also
I
saw
that
divya
mention
some
of
the
blog
posts
coming
out
in
the
timing
around
that.
Is
there
any
updates
or
any
concern
for
folks
in
sig
docs
around
the
blog
post.
B
I
guess
I
can
speak
for
the
blog
team
a
bit
because
recently
I
became
a
vlogs
reviewer,
but
I
haven't
really
done
much
for
vlogs.
But
what
I
will
say
is
that
it's
a
bit
unclear
from
from
my
point
of
view
and
I'm
intending
later
today
to
to
sort
of
kick
off
some
conversations
and
find
out
the
best
way
that
I
can
help
and
what
needs
to
happen.
A
C
All
right
so,
first
pr27088,
so
this
is
a
121
dock
pr,
and
this
is
the
one
that
needs
more
than
a
tech
review.
So
a
new
page
was
added.
C
Yes,
page
was
added
so
to
want
to
highlight
this.
Appropriate
people
were
pinged
on
to
give
a
tech
review
tim.
I
saw
your
your.
I
see
your
comment
there
as
well
anyway,
so
this
is
for
service
internal
traffic
policy,
since
we
have
the
addition
of
that
new
page
that
wanted
to
get
eyes
on
this.
D
C
Now
see
it,
thank
you.
That's
great.
A
C
All
right
should
we
go
on
to
the
next
one.
C
All
right
next
one,
I
just
updates
the
config.tomwell
for
121..
It
already
has
some
lgtms
on
it
made
some
changes
on
it,
but
I
think
we
just
need
needs
and
approval,
and
this
is
for
the
dev
121
branch.
This
is
pr2723.
C
And
this
is
part
of
the
release
process
of
updating
the
config.tomol.
B
I'm
gonna
drive
by
approve
that,
because
the
intent
of
the
pull
request
is
entirely
in
line
with
what
we
should
do
for
the
release
yeah.
Thank
you.
C
All
right,
I'm
going
to
continue
on
with
the
next
one.
The
next
two
are
actually
kind
of
related.
It's
it's
for
the
reference
stocks
for
121.
C
And
there's
some
changes
so
the
first
one
27248
generate
reference
stock
with
the
1.21
release
candidate,
zero
tag.
We've
had
some
build
issues
with
this
with
karen
and
I
tested
it.
C
And
one
of
the
later
comments
is
that,
since
the
attack,
the
v
0.21.0
tag
isn't
available.
Yet
until
the
121
release
next
week
about
possibly
preparing
this
document,
I
guess
on
the
release
day
or
short
or
within
hours
of
the
release,
but
both
karen
and
I
had
did
have
some
bullet
issues
that
we
couldn't
debug
at
and
timed
in
here.
A
And
I'm
wondering
if
we
should
move
this
process
to
after
the
release
is
cut
the
updating
the
reference
docs
in
the
handbook.
Unless
someone
has
an
alternative
way,
maybe
karen
or
scheming
could
suggest
an
alternative
solution
with
this
non-existent
tag.
A
It's
not
necessarily
a
mission,
critical
set
of
documents
that
come
out
with
the
release,
so
it's
very
favorable
to
get
an
asap,
but
I
know
a
few
releases
back
when
I
was
leading
one
of
the
docs
release
actual
release
process
when
we
went
to
go
live
there
were
some
issues
with
the
reference
generation
and
I
think
we
didn't
get
it
resolved,
for
I
want
to
say
around
three
or
four
weeks
until
it
was
actually
fully
up
and
working
again,
and
so
I
tell
that
antidote
by
basically
sharing
that
it's
not
going
to
be
the
end
of
the
world.
A
If
these
aren't
in
place
to
go
live,
I
wouldn't
consider
it
a
blocker.
However,
I
do
think
we
should
consider
the
the
process,
or
at
least
document
awareness
around
this
kind
of
chicken
and
egg
problem
that
we
have
and
maybe
there's
a
better
time
or
a
better
place
to
do
generate
those.
I
don't
know
if
any
anyone
else
has
any
questions
or
comments
on
that.
C
I
do
like
the
idea
and
I'll
bring
it
up
with
with
karen
and
chi
ming
as
well,
and
that's
something
that
we
could
change
in
the
royal
handbook
in
the
timeline
and
have
a
change
for
one
1.22
cool.
That.
C
All
right,
the
last
pr
is
two
six
four
one,
three
sort
of
related:
it's
about
preparing
the
api
reference
documentation.
C
I
just
wanna
get
eyes
on
this,
so
it
kind
of
ties
in
with
the
release
as
well,
and
if
this
is
some,
if
the
reason
why
I
want
to
bring
this
up
is
if
this
is,
if
we
need
to
add
in
additional
tasks
on
the
docs
role
handbook
for
any
feature,
release
to
to
do
something
similar
that
philippe
has
done
with
this
pull
request
on
preparing
the
api
reference
documentation
for
future
releases.
C
So
that's
what
I
wanted
to
bring
up
with
this
pull
request
is
mostly
just
like.
Is
there
something
that
we
can
add
on
to
the
to
the
doc's
role
handbook
that
relates
to
this
pull
request?.
A
Yes,
I
know
zach's
been
really
working
with
philippe
on
on
generating
that
and
I
haven't
been
as
close
closely
involved
with
it.
But
do
we
have
the
instruction
set
of
what
philippe
did
here
for
the
pr
that
was
opened
or
no,
because
it
seems
like
adding
those
instructions
to
the
release
handbook,
so
it
could
be
managed
by
other
folks
would
be
helpful.
A
B
A
few
things
that
I
spoke
to
sig
architecture
about
this
a
while
ago
and
there's
a
few
things
that
I
think
we
want
to
do
before.
We
can
properly
deprecate
the
old
page
and
I
haven't
done
them
yet.
I
wanted
to
get
them
done
for
before
the
release,
but
that
hasn't
happened,
and
so
I
think
we
need
to
unfortunately
put
more.
You
know,
because
we've
got
two
in
parallel:
we
need
to
one
prioritize
the
switch,
but
also
make
sure
that
the
old
single
page
is
done
as
well.
A
It
sounds
to
me
like
we
should
prioritize
this
on
some
of
our
quarterly
planning
as
well
track.
It
keep
up
with
it,
but
it
sounds
like
maybe
for
the
121
cut
being
so
close,
we
might
be
leaving
it,
as
is
unfortunately,
or
fortunately,
I
guess,
depending
on
the
who's
involved.
Okay,
so
let
me
clarify
one
thing:.
B
Sig
architecture,
the
request
from
sig
architecture
was
when
we
deprecate
it
dual
run
for
one
more
release.
After
that.
B
So
if
well,
I
I
don't
think
we'll
get
that
done.
It's
too
soon.
I
think
we're
more
likely
to
deprecate
in
122
and
123
will
be
the
final
release
that
has
the
single
page
api
reference
and
I
think
that's
as
good
as
we
can
make
it
like.
I
don't
have
time
to
get
that
done.
I
don't
think
what
I
need
ray.
Does
that
make
sense.
You're.
B
Do
you
know
what
you
need
for
for
the
old
you
know
currently
canonical
but
kind
of
soon
to
be
deprecated
single
page
api
reference.
C
I'll
have
to
look
into
it,
but
I
I
could
paint
the
sig
docs
channel
if
I
need
any
inputs
on
that.
B
B
Bye,
jim
and
also
thanks
jim,
for
covering,
when
I
was
kind
of
hitting
the
ground
running
at
the
start
of
the
meeting.
Okay,
are
there
any
more
issues
or
pull
requests
that
people
are
keen
to
discuss
before
we
move
on.
B
Okay,
abby
google
data
studio
tell
us
about
that.
E
Yes,
hello,
hopefully
my
internet
stays
stable
and
I
don't
have
video
I've
been
having
some
internet
problems
all
day,
but
jim
and
I
and
irvy
have
been
working
on
how
we
can
get
google
analytics
out
to
the
masses,
in
particular
the
localization
group
who's,
requesting
access
to
that
in
a
in
a
better
sort
of
more
manageable
way
than
just
emailing
it
out,
weekly
or
whatever,
monthly
or
whatever.
E
B
Yes,
if
you
don't
have
access
to
do
that,
let
me
make
sure
that
you
do
have
access
abby.
Do
you
have
screen
sharing
enabled
now
I
don't
know
what
the
settings
are.
E
Okay,
so
this
is
just
sort
of
a
basic
template
that
was
honestly
something
that
was
defaulted
from
google
data
studio
and
it's
set
up
sort
of
like
the
same.
It's
the
access
level
is
the
same
way
for
like
google
drives.
You
can
share
it
and
have
the
link
accessible
to
anybody
who
can
find
it
and
it
pulls
directly
from
the
google
analytics
site
for
the
kubernetes
website,
and
you
can
see
what
was
there
for
the
you
can
change
the
time
limits
on
it.
E
You
can
see
what
the
most
popular
pages
have
been
in
some
shiny
graphs,
just
a
lot
of
breakdowns
of
things.
People
were
looking
to
get
access
to.
This
is
what's
what
things
have
been
the
top
search
items
for
that
time
period.
You
can
also
adjust
for
specific
continent
and
regions,
so
you
can
update.
So
you
could
just
see
you
know
whatever.
If
you
only
want
to
see
what
people
are
seeing
in
england
there's
a
lot
of
data
to
process
things
are
a
little
bit
slow.
E
This
is
probably
a
bad
example
because
it
might
take
forever
to
load,
but
anyway,
so
you
can
just
sort
of
see
just
an
example
of
what
we
were
thinking
about
doing.
So
we
can
give
people
more
regular
access
without
having
it
be
something
we'd
have
to
email
out,
so
the
idea
is
we'd
be
able
to
set
up
in
some
email
address
wow.
This
is
really
taking
forever
loads.
E
This
is
a
really
bad
example,
but
set
up
this
in
some
accessible
way
for
some
account
that
is
owned
by
whoever
the
sig
group
is
and
have
it
accessible
just
to
anyone,
and
then
we'd
have
to
figure
out,
you
know
the
best
place
to
ptosis
and
who
would
have
access
to
it
for
any
other
requests
for
additional
information
or
whatever.
I
don't
know
how
to
cancel
trying
to
do
this.
B
If
it's
really
slow,
you
might
find
it's
turning
off
screen
sharing
kind
of
lets.
Your
internet
recover
a
bit
abby.
E
That's
a
good
idea:
okay,
so
so
yeah.
So
that's
sort
of
our
overview
of
what
we
were
thinking,
so
we
wouldn't
have
to
set
up
regular
emails
that
exporting
emails
through
google.
Google
analytics
is
nice,
but
it
has
a
lot
of
overhead
you
have
to
you.
Can
only
do
it
for
a
certain
period
of
time,
so,
every
six
months
somebody
would
have
to
re-update
setting
up
the
schedule
and
whatever.
E
So
we
were
thinking
of
doing
it
like
this,
but
we
wanted
to
obviously
present
it
to
the
community
and
see
if
there
were
any
feedback
or
any
ideas
people
had
or
if
anyone
had
more
experience.
I
haven't
used
google
data
studio
that
much
so
if
somebody
had
experiences
or
had
more
information
about
why
this
wouldn't
necessarily
work
happy
to
hear
any
feedback
there.
F
B
E
Yeah,
so
it
was
the
sharing
requirements.
Are
you
can
set
them
access
so
that
anyone
on
anyone
on
the
internet
can
find
and
view?
E
So
I
I
haven't
tested
it
much
because
we
haven't,
I
haven't,
opened
it
up,
but
it's
it's
being
able
to
set
that
up,
so
people
will
be
able
to
just
find
it
over
the
internet,
so
you
wouldn't
necessarily
need
a
google
account
and
maybe
we
can
find
out
some
way
to
have
a
a
specific
url.
So
it's
not
just
like
the
long
ugly
google
data
studio
url,
but
actually
have
it
accessible
to
some
on
the
website
or
something
so
it
looks
like
it's
on
the
website.
B
Okay,
cool-
I
don't
know
if
you
want
to
do
this
abigail,
but
we
could
log
a
couple
of
issues,
one
for
the
short
short
link
and
the
other
one
to
sort
out
resource
ownership
for
the
data
studio.
There's
like
an
infrastructure
group
that
I
think
might
be
a
good
fit.
E
Yeah
sure
I
can
set
up
setting
up
those
issues:
yeah
cool.
B
Any
more
comments
on
the
data
studio
and
the
public
analytics
access.
B
F
F
Go
ahead,
oh,
do
you
think
it's
it'll
be
possible
to
for
to
maintain
access
like,
depending
on
the
language
or
like,
depending
on
on
a
team
in
different
directive,
for
example,
I
don't
know
how
it
works,
because
you
know
each
language
or
each
I
don't
know.
B
I
believe
we
will
be
able
to,
and
abigail
is
proposing,
that
we
will
be
able
to
make
data
available
that
do
not
reveal
any
personal
information
about
people,
and
so
we
will
be
able
to
make
this
public
for
everyone.
That
is,
I
think,
what
you're
aiming
for
abigail
is
that
right.
B
B
Okay,
that
looks
really
interesting
and
I
think
that's
going
to
be
a
really
valuable
feature
for
a
different,
a
bunch
of
different
contributors,
localizations,
whatever
I'm
just
really
impressed
already.
Okay,
well,
that
moves
on
to
the
agenda.
Are
there
any
other
topics?
People
would
like
to
raise
before
we
close
the
meeting.