►
From YouTube: K8s SIG Docs Meeting for 20210615
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
All
right,
you
heard
the
zoom
robot.
This
meeting
is
being
recorded,
hey
everybody,
welcome,
I'm
jim
angel
zig,
doc's
co-chair
and
we're
kicking
off.
The
weekly
meeting
today
is
june
15th
and
it
is
10
30,
pacific
time
so
before
we
get
started
any
new
contributors
that
care
to
introduce
themselves.
A
Looks
like
all
familiar
faces,
shannon.
I
know
we've
chat,
but
I
don't
think
we've
officially
introduced
each
other,
so
I'm
sure
you've
introduced
on
another
call.
So
I'll
just
say:
hey
publicly
here.
A
So,
moving
on
to
this
updates,
this
week's
updates
and
reminders
this
week's
pr
wrangler
is
only
dole
taylor,
dolezal
and
next
week's
pr
wrangler
is
avita,
as
always
pr
wranglers
make
sure
you
know
your
shifts.
They
are
linked
in
the
pr
wrangler
shifts
link
in
the
agenda.
A
C
Yes,
absolutely
hi,
so
for
the
release,
not
not
great
news.
So
far.
Currently
the
integration
branch
is
broken.
C
It
seems
that
when
we
did
the
the
sync
on
friday
a
pr
was
merged
before
hours,
I
think
in
in
prowess
q
and
basically
it
broke
the
it
broke
the
branch
I
will
submit
the
pr
it's
it's
not
anything
specifically
difficult,
but
I
will
submit
the
pr
to
fix
that.
Currently
we
are
tracking
67,
I
would
say
68,
I'm
not
sure
if,
if
the
exception
for
job
controllers
was
added
yet,
but
basically
we
are
tracking
67
out
of
which
43
enhancements
need
need
dogs.
C
A
C
A
Got
you
perfect
and
one
other
heads
up
victor
when
I
was
going
through
some
of
the
pr's?
If
I
noticed
they're
targeting
the
dev
branch,
I
cc'd
you
on
there
or
assigned
you
on
there
feel
free
to
reassign
those
to
shadows
or
do
what
you
want
to
do
with
them.
I
figured
I'd
sync
with
you
today
and
let
you
know
that
if
I
see
anything
going
to
the
dev
branch,
usually
I'm
going
to
tag
you
into
it.
Just
for
general
awareness.
A
No
worries
at
all
I
totally
get
it
and
for
anybody
who
should
apologize
for
targeting
this
is
myself.
So
as
I'm
getting
to
prs,
I
notice
I
haven't
been
commented
in
30
days.
There's
there's
definitely
an
issue
there.
So
no
no
issues
on
that
end.
I
get
it.
I
think
that
the
world
is
kind
of
crazy
in
general,
but
it's
extra
crazy.
Now
so
take
the
time
you
need-
and
you
know
we'll
definitely
be
around
to
help
out.
A
D
Bit
of
a
segue
for
from
releases,
because
this
is
going
to
be
a
great
boon
to
future
docs
release
leads,
I
hope,
and
also
a
pain
for
the
one
who's
the
person
who's
docs
released
lead
when
it
goes
in
victor
you've.
Seen
some
of
this
already.
This
is
a
pull
request.
Let
me
stick
it
in
the
chat.
D
Oh,
so
that's
the
issue,
but
there's
an
issue
and
a
related
pull
request
that
I've
put
in
with
a
preview
ready
to
go
about
producing
the
feature
gate
page
by
rendering
some
data,
so
I've
taken
the
existing
feature
gates
table
like
from
whatever
the
merge
base
of
that
pull
request
is,
and
I
have
turn
into
yaml
and
hugo
can
take
that
yaml.
I
could
render
it
it's
pretty
similar
rendering.
But
what
do
people
think
about
the
overall
approach,
like
I
think
it's
a
mixture
of
awareness?
C
I
have
a
few
questions
because
I
was
thinking
about
this
and
basically
I
so.
The
way
that
I
was
thinking
about
this
was
to
generate
the
feature
gates
list
from
from
the
actual
code.
C
But
there
is
a
problem
with
that,
because
once
you
once
you
build
a
tool,
you
would
need
to
update
basically
the
dependency
for
kubernetes
for
this
tool
continuously
when
you
generate
new,
if
it's
written
in
go
for
example,
and
that
that's
that's
kind
of
tricky,
because
what
I
I
don't
understand,
the
user
experience
so,
for
example,
if,
if
I'm
an
enhancement
owner
and
I'm
opening
a
pull
request
to
update
the
features
list,
feature
gates
list,
how
do
I?
How
do
I
do
that?
Do
I
download
the
tool
that
does
that?
C
For
me,
this
tool
also
needs
to
pull
in
because
it
basically
the
go
mode,
has
the
the
sha
of
of
the
commit,
and
I
would
need
to
update
the
shelf
to
commit
and
so
on.
So
it's
it's
a
very
involved
process
and
the
other
one
was:
should
the
ci
do
this
automatically
and
if
so,
how?
How
would
that
work?
Because
it's
still
really
up
to
the
user
right
to
to
update
the
yaml
file
effectively.
A
Yeah
I
do
want
to
make
a
comment
and
kind
of
allude
to
what
victor
mentioned
as
well,
and
definitely
would
like
to
hear
from
other
folks
as
well
is
that
this
is
a
very
manual
process
today,
and
it
is
definitely
something
that
comes
up
regularly
with
merge
conflicts,
mainly
around
the
way
it's
handled.
I
I
would
like
to
hear
from
you
tim
whether
or
not
you
think
this
would
solve
some
of
those.
You
know,
merge
conflicts
and
the
kind
of
toil
around
this
feature
gate
site.
D
Then
I'll,
then
I'll
start
answering
okay.
So
what
I
first
will
say
is
that
this
is
kind
of
a
staged
change.
So
you
know
the
ultimate
goal.
Is
that
at
release
point
when
someone
cuts
a
release,
like
you
know,
kubernetes
1.23.2,
actually,
a
patch
release
that
build
process,
one
of
its
artifacts
could
be
a
json
document
of
what
the
feature
gates
are
there,
and
actually
I
would
shift
that
responsibility
onto
like
the
kubernetes
repo.
D
So
if
you've
got
you
know
if
you're
building
a
kubernetes
release
and
you're
doing
all
of
that,
it's
another
artifact,
we
don't.
We
and
sig
docs,
don't
build
that.
We
we
we
liaise
and
so
on,
but
it's
actually
a
release
artifact
or
it's
built
by
the
release
process.
D
Obviously
sig
release
would
have
a
huge
you
know,
involvement
there.
You
could
also
generate
that
from
like
the
primary
branch
as
well
to
have
like,
what's
the
feature,
gate
status
for
the
primary
branch.
But
the
interesting
thing
is
for
releases,
because
that's
what
matters
to
end
users
you'd
want
to
do
a
few
changes.
D
D
This
enabling
change,
lets
us
separate
out
and
the
different
bits
of
that.
So
all
the
localizations
can
pick
up
this
change
ahead
of
when
any
sort
of
improved
automation
on
the
k,
kubernetes
side
comes
in
so
the
hugo.
So
the
golang
changes
that
you're
talking
about
victor
and
calculating
future
gate
status
directly
by
by
running
or
compiling
go
code.
That
can
happen,
but
we
don't
have
to
like
line
all
of
the
changes
up
to
happen
at
once.
That's
like
13,
localizations
plus,
you
know
the
whole
kubernetes
project
plus
releases.
We
shouldn't.
D
We
shouldn't
bundle
all
that
together
and
so
I've
done
the.
If
you
like
the
easy
bit,
I've
done
the
short
code
for
the
english
localization.
I've
made
it
localizable,
at
least
that's
my
theory.
It
needs
reviewing.
So
we
can
do
this.
All
of
the
localizations
can
pick
it
up
and
if
we
do
this,
the
process
for
someone
who
is
working
in
a
sig,
that's
producing
code
is
that
they
have
a
yaml
document
to
produce.
D
You
know
a
commit
that
patches,
it
and
typically
you'll
add
a
line,
because
if
you
want
to
go
and
look
at
that,
let
me
screen
share.
Actually
I
will
I
realize
I'm
burning
some
time
on
this,
but
I
reckon
it's
it's
an
important
concept
to
talk
to
people
through.
So
I
will,
if
that's,
okay
with
you
jim,
I
will
talk
through
it.
A
D
Yeah
yeah
I'll
be
less
than
that.
I
hope,
but
let
me
fire
up
the
screen
share.
I
could
definitely
agree
on
the
time
box.
D
Okay,
so
if
I've
done
the
right
stuff,
you
are
seeing
a
screen
share,
yeah
yep,
let
me
find
the
actually
I'll
do
the
raw
view
of
the
yaml
file?
Okay,
so
here's
what
the
ammo
actually
looks
like
and
here's
what
it
looks
like
into
the
rendered
view.
So,
let's
pick
a
feature:
that's
not
stable,
a
cpu
manager.
D
You
make
that
stable.
You
add
one
line
to
say
stable
from
version.
That's
it
that
should
change
so
much
easier.
A
common
slip
is
for
people
to
delete
the
alpha
version
when
they
promote
something
to
beta.
That
happens
loads.
It's
an
easy
mistake
to
make,
but
with
this
yaml
it's
kind
of,
if
you
can
yaml
you
can
do
this,
I
believe
that's
and
that's
my
aim
and
so
the
the
cleverness
and
the
not
the
cleverness,
but
the
thinking
happens
in
a
short
code.
D
So
you
don't
have
to
know
the
rules
for
how
you
update
the
table.
You
have
to
know
how
to
add
a
line
to
some
yaml
and
then
this
there's
some
go
templating
that
does
the
necessary.
D
A
Awesome
yeah.
I
think
this
is
great
work
and
I
completely
agree
the
question
I
had
about
toil
you.
You
kind
of
indirectly
answered
it
that
if
you're
adding
a
line
there
shouldn't
be
merge
conflicts
as
regularly
as
there
are
with
a
feature
gate,
so
it's
actually
bumping
down
and
moving
things
around
so
that
that's
a
great
win
there.
A
I
see
no
reason
why
not
to
implement
this
at
this
kind
of
early
stage
level,
I'm
happy
to
take
a
look
at
reviewing
it,
but
I'd
love
to
have
some
other
folks
get
involved
on
this
call
as
well.
The
one
area
that
really
jumps
out
to
me
that
I
think
we
need
to
focus
on
is,
let's
make
sure
that
sig
release
gives
it
a
thumbs
up.
It
could
even
be
informal
via
slack,
maybe
an
email
or
attending
one
of
the
meetings
I
feel
like
this
is
going
to
impact
almost
every
single
sig.
A
A
So
the
way
I
see
this
would
be
getting
sig
releases
thumbs
up
implementing
it,
as
is
today,
whereas
if
it
were
to
stay
at
this
current
stage,
implementation
is
still
a
reduce
of
technical
debt,
reduce
of
toil.
I
find
it
to
be
a
big
win
for
this
to
be
in
a
staging
area,
and
then
I
would
look
at
handing
it
off
to
a
sig
release
from
that
point.
Once
it's
implemented
and
maybe
the
whole
artifact
discussion
comes
later
and
have
been
a
bigger
scope.
A
I
know
that
there's
an
initiative
started
by
sig
release
for
artifacts
there's
a
big
umbrella
issue,
it's
all
about
where
we're
moving
artifacts
we're
building
them.
Where
things
go.
This
could
very
well
fall
into
there
as
probably
a
lower
priority
on
the
overall
artifact
umbrella
issue,
but
I
could
see
this
as
being
part
of
a
wider
strategy
for
sig
release,
but
I
think
at
the
the
fundamental
level
we
could
implement
this
early
stage
and
reap
the
rewards
of
it.
A
Assuming
that
the
entire
sig
release
team
is
thumbs
up
thumbs
it
up
giving
it
a
thumbs
up.
D
Victor,
I
wonder,
could
you
discuss
with
your
shadows
and
would
one
of
the
release
team
be
willing
to
sort
of
lead
on
the
liaison
with
the
release?
Stick.
C
Yes,
absolutely
absolutely:
I
can
bring
it
up
tomorrow.
I
think
in
the
thank.
A
A
Cool
and
I'd
be
very
clear
victor
when
you
bring
it
up
that
we're
looking
for
thumbs
up
or
comments
or
reasons
not
to
do
it,
and
assuming
that
we
don't
hear
any
negative
feedback
we're
going
to
move
forward
with
implementing
this.
So
I
I
would
make
it
very
clear
that
it's
waiting
on
action
from
sig
release
prior
to
making
any
moves,
yep,
definitely
cool
awesome,
yeah.
Thanks
for
that
tim
thanks
victor.
A
All
right
moving
on
to
the
official
docs
image,
so
this
came
up.
It's
kind
of
a
stale
issue
talking
about
getting
back
around
to
some
some
older
older,
open,
pull
requests,
and
this
is
to
create
an
official
kind
of
a
sig
sig
docs
image
that
could
build
our
website.
It's
kind
of
the
way
we
do
things
in
nk
website.
A
We
started
a
process
where
you
can
build
your
own
container
to
host
your
images,
make
your
changes
but
you're
still
building
it
locally.
So
this
pr
here
is
a
way
that
we
can
start
to
integrate
with
prow
and
the
ci
the
test
infra,
basically
to
build
containers
on
our
artifact
registry,
our
gcr
registry,
google
container
registry,
and
what
the
idea
here
is
that
we
have
an
officially
published
hugo
image
to
use
with
our
website.
A
So
it
would
be
built
out
of
our
make
file,
and
what
you
could
do
is
run
that
and
pull
a
container
from
a
artifact
repository
as
opposed
to
building
it
locally
than
doing
development
work.
So
what
the
pr
is
is
some
minor
changes
that
are
needed
in
the
make
file
to
build
the
docker
image.
The
next
step
would
be
to
start
to
integrate
into
the
tooling
systems,
actually
build
and
publish
the
container,
and
then
once
we
had
everything
in
place,
then
we
could
update
the
readme
with
how
you
could
use
it.
A
So
very
little
impact
I
would
say
initially,
but
in
the
future
it's
a
very
large
impact
to
overall
kind
of
workflows
here.
So
I
posted
it
here
for
awareness.
The
one
comment
that
I
wanted
to
ask,
and
I
don't
have
enough
context
around
it
and
it's
okay.
If
we
can't
answer
it
here,
is
part
of
the
change
to
do
the
build
is
to
use
a
specific
tag
that
will
actually
use.
A
I
believe
it's
a
hash
file
and
I
forget
against
what
what
area
and
it's,
basically,
how
do
we
trigger
a?
I
forget
I
forget
the
actual
requirement,
but
it's
basically
how
our
word
we're
triggering
certain
mechanisms
in
ci
based,
I
want
to
say
the
image
tag.
So
how
do
you
keep
publishing
and
tagging
the
latest
or
new
images?
A
A
I
gotta
get
re-engaged
with
this
issue,
but
the
the
big
thing
I
wanted
to
bring
up
is
that
tag
that
gets
created.
I
wanted
to
call
out
to
see.
Is
there
any
issues
changing
the
make
file
to
update
a
tag
based
on
a
hash
as
opposed
to
what
it
is
today,
so
I'll
stop
there?
If
there's
any
comments,
I
can
do
or
any
any
clarification
I
can
provide.
Let
me
know
and
then
any
comments,
I'd
be
open
for.
A
You're
in
a
whole
lot
of
nothing,
I
I'll
take
that
as
general,
you
know
alignment
there.
I
I
really
feel
like
to
be
honest
with
the
folks
in
this
call
here
is
that
I
feel
like
this
change
could
be
quickly
reverted
the
folks
that
are
using
make
files
to
build
containers
into
to
publish
docs
they're,
going
to
be
they're
going
to
be
technical
enough
to
realize
what
has
changed
and
what
was
broken,
and
if
there
is
anything,
has
changed
and
or
broken.
We
can
then
go
and
revert
fix,
make
changes
from
there.
A
All
right
easy
enough:
let's
roll
on,
I
did
want
to
bring
up
there's
a
proposed
hugo
archetype
for
a
blog,
and
I
have
a
link
in
the
agenda.
There's
pull
nine
request.
One
and
rolf
brought
this
up
about
creating
a
hugo
archetype
for
a
blog
post
and
essentially
be
a
way
to
run
hugo
new
blog
post
and
create
a
template.
You
could
then
fill
in
the
template.
It
really
prevents
folks
from
having
to
rebuild
and
recreate
the
structure
for
a
blog
post
every
time
they
want
to
go
about
doing
so.
A
A
A
A
There
is
one
exception
where,
if
there's
a
usability,
you
know
that's
going
to
impact
the
user
experience
it's
going
to
impact
security.
There
are.
There
has
been
times
where
we've
made
changes
on
old
kind
of
quote,
unquote,
stale
branches.
A
So
this
pr
that
I
saw
came
in
and
there
is
a
extra
it
looks
like
a
bracket
in
the
117
documentation
that
breaks
a
link
for
api
reference
when
you
click
on
it
very
minor,
fix
very
minor
tweak.
I
noticed
this
is
a
first
time
contributor
and
really
what
I
wanted
to
bring
up
is.
Do
we
think
it's
worth
merging
this
usability
fix,
or
should
we
just
hold
tight
to
this?
It's
not
really
security
impacting
and
let's,
let's
let
it
let's
let
sleeping
dogs
live.
C
Don't
we
need
to
do
another
snapshot
if
we
do
this?
Sorry
for
my
ignorance,
but
the
way
that
I
understand
is
that
each
release
we
do
a
snapshot
of
the
hold
and
then
we
create
we.
I
noticed
that
we
have
a
special
custom
domain
for
that,
so
my
question
is:
should
shouldn't
we
do
that
this.
D
Will
just
work
that
branch
that's
created
during
the
release
process
is
the
thing
that
this
pr
plans
to
update
with
you
know
a
one
character,
change.
A
Yeah
and
and
victor
it's
not
not
really,
it's
a
great
comment,
and
what
I
wanted
to
call
out
is
the
snapshots
that
are
done
per
the
release
cycle
is
really
referential
they're,
not
really
leveraged
heavily.
No
one
really
uses
them
and,
to
be
honest,
I
think
if
they
went
away
in
the
release
process,
there'd
be
almost
no
impact
to
the
overall
end-to-end
operations.
A
Saying
that,
though
it
is
a
good
kind
of
sanity
check
to
say
hey,
this
is
what
the
docs
looked
like
back
in
version
1.2
or
1.3,
and
it's
really
more
historical
and
capturing
that
kind
of
tarball
at
the
point
of
time
of
transitioning
from
release
a
to
release
b,
but
as
far
as
functionality.
That's
really
all
it
is
it's
a
time
stamp.
It's
a
reference.
It's
a
release,
it's
an
artifact,
but
the
actual
release.
A
117
website
is
just
the
live
branch
itself,
so
you're
absolutely
spot
on,
though,
if
we
merge
this,
that
tower
ball
of
117
is
no
longer
an
accurate
reflection
of
like
what
true
117
is.
However,
I
don't
think
the
purpose
is
necessarily
conflict
with
each
other
to
prevent
you
know
one
or
the
other
from
being
being
impacted.
A
A
Well,
let's,
let's
let
it
rip
done.
Awesome
beat
me
to
it
appreciate
it.
Thank
you
so
yeah
and
the
reason
I
bring
that
up
is
really
it's
one
of
those
things.
There's
not
a
right
or
wrong
solution
there.
It's
really
a
community
decision,
you
know,
and
especially
for
this,
it
sometimes
is
a
clear
judgment.
Call
okay!
This
is
security
impacting
okay.
This
is
you
know.
This
falls
in
our
framework
of
what
we
actually
back
for,
but
at
the
end
of
the
day
there
are.
A
A
All
right,
and
then
I
have
another
pr
for
discussion
here
and
it
looks
like
I
put
the
wrong
link
in
here.
Maybe
api
translations
in
flight
yeah.
I
put
the
wrong
link
in
here.
This
is
supposed
to
be
philippe's
work
to
localize
the
reference
docs
generation.
A
So
right
now,
felipe
did
a
google
summer
of
docs
initiative
to
generate
all
of
our
reference
documentation
and
publish
them
based
on
the
current
release.
What
felipe
has
done,
furthermore,
has
has
enabled
the
ability
to
translate
based
on
different
locales
and
started
the
pr
for
the
french
language
and
really
certain
initiatives.
So
we
can
start
running
these
api
reference
generation,
scripts
for
multiple
languages
and
sam.
I
saw
you
sent
the
actual
pr
there.
I
appreciate
that.
Thank
you.
D
A
And
really,
the
reason
why
I
bring
this
up
is
more
just
general
awareness.
I
bring
this
up
for
localization
teams
that
might
be
listening
in
I
plan
on
bringing
it
back
up
for
the
apac
meeting
that
we
host
and
really
just
drive
in
general
awareness
that
today
our
reference
docs
are
generated.
They
are
not
localized
and
there's
a
process
in
place
currently
being
discussed,
and
if
you
want
to
check
it
out
the
links
in
the
agenda
all
right,
any
other
issues
prs
that
folks
want
to
discuss.
B
Yeah,
so
I've
been
trying
to
help
out
with
consolidating
the
garbage
collection
docs
that
we
have,
because
I
think
tim
asked
for
help
on
that.
So
I
analyzed
the
current
the
existing
content
we
have
on
garbage
collection,
found
a
bunch
of
different
pages
that
mention
it
and
I
drafted
up
like
a
doc
plan
with
this,
both
scope
of
changes
and
I'm
hoping
that
we
can
get
people
or
hopefully
smith's,
to
review
the
scope.
B
D
D
D
That
makes
sense
to
a
reader
who
wants
to
know
about
garbage
collection
overall,
but
we
are
going
to
have
to
talk
with,
or
you
know
like
involve
this
would
be
tech
reviewed
by
api
machinery,
because
some
of
this
is
about
the
machinery
of
the
kubernetes
api
by
sig
apps
and
several
more
six,
and
I
I
what
I
think
is
someone
I
I
will
volunteer
to
put
some
of
this
in
like
it
would
be
good
to
pay
with
someone
who
can
help.
You
identify
the
right
six
to
liaise
with
six
plural.
B
Okay,
yeah,
I
guess
like
we
should
probably
add
members
of
those
sigs
on
the
dock
plan
as
well,
so
that
they
can
lgtm
it
before
we
do
anything
then.
D
Yeah,
you
will
probably
uncover
it
like.
I
think
it's
okay
to
start
this
and
say:
okay,
it's
up
to
you
like
it's
your
piece
of
work,
but
if
you
didn't
uncover
all
of
the
things
right
at
the
start,
you
could
still
make
get
a
long
way
and
then
you
might
find
that
later
on,
you'd
realize
there
was
an
extra
bit
of
detail
that
you'd
missed
and
it
might
take
a
week
before
you
find
out,
I'm
afraid.
A
Go
ahead,
and
I
would
second
what
tim
said
and
agree
that
it
would
be
important
to
get
multiple,
cigs,
buying
or
liaisons
to
help
out
with
this.
I
don't
think
it's
necessarily
blocking.
I
think
you
can,
like
tim
said,
get
a
lot
of
progress
done.
As
is
you
can
build
a
lot
of
the
framework
and
some
of
the
generalities.
D
A
Anything
else
we
can
help
with.
D
Well,
is
there
anyone
in
this
cool
who'd
be
happy
to
pair
with
shannon
to
help
move
this
thing
on
and
help
with
things
like
introductions
to
six
because
yeah,
it's
a
it's
a
chunky
piece
of
work,
and
you
know
I
think
we
want
to
help
you.
D
Well,
not
hearing
a
a
whole
bunch
of
volunteering
going
on
I'll.
Do
that
I
will.
I
will
take
that
shannon
I'll.
A
And
I'm
happy
to
help
out
as
well
too,
I'm
just
currently
quite
over
subscribed
at
the
moment,
so
I
don't
want
to
put
my
name
in
the
ring
just
yet,
but
I'm
happy
to
offer
guidance
where
I
can.
A
Thank
you
no
problem
all
right.
Moving
on,
I
did
want
to
draw
attention
to
pull
request
27991.
It
is
actually
already
merged
and
I've
put
the
links
in
the
agenda
as
well.
This
is
great
work
by
abigail
and
abby,
put
together
a
google
data
studio
dashboard
to
look
at
some
of
the
analytics
for
the
localizations.
A
So
this
is
a
huge
effort
that
has
taken.
I
don't
know
a
handful
of
months,
maybe
even
years
now,
just
to
kind
of
consolidate.
How
do
we
most
effectively
convey
information
to
to
everybody
about
useful
docs,
especially
when
it
comes
to
localization
and
before
we
were
sending
out
pdf
reports
and
people
said
it
was
too
kind
of
spammy
too
noisy.
A
Then
we
started
to
look
at
generating
a
analytics
dashboard,
but
we
were
limited
on
how
many
widgets
you
could
have
and
abigail
came
up
with
a
solution
where
data
studio
is
a
free
offering
it
plugs
into
google
analytics.
You
can
make
it
available
to
everyone
to
view
and
that's
exactly
what
abigail
did
and
the
reason
I'm
sharing
it
here
is
that
it's
wide
open
everybody.
A
It
is
a
little
slow,
that's
just
the
nature
of
data
studio,
analytics
and
the
size
of
our
site,
but
you
can
go
and
click
on
the
drop
down
and
filter
by
language,
look
at
popular
sites
and
then
really
gets
a
sense
of
the
current
state
of
the
general
analytics.
Now
you
can
also
go
as
a
member
of
docs
and
go
and
read
and
review
the
google
analytics.
A
You
can
ask
for
an
invite
and
get
invited
to
the
google
analytics
actual
portal.
If
you
will.
But
personally
I
found
the
dashboard
to
be
a
lot
more
convenient
to
get
a
quick
state
of
the
world
rather
than
going
into
analytics
and
for
those
that
have
it's
kind
of
hairy,
depending
on
what
kind
of
information
you're
trying
to
get
out
of
it
so
kudos
to
abigail
great
work.
I
really
wanted
to
boost
that
and
and
raise
awareness
so
do.
A
All
right
so
moving
on
the
maintainer
track
at
cubecon
cloudnativecon,
north
america
2021.
So
I
saw
this
in
my
inbox.
We
have
a
opportunity
to
do
a
35-minute
session,
an
intro
and
a
deep
dive
into
sig
docs.
We
did
this,
I
shouldn't
say
we
did
tim
and
celeste
and
irva
did
this,
for
is
it
keep
kind
of
you.
D
A
Yeah
and
brad
you're
involved
in
that
too
sorry
to
me
to
leave
you
out
there,
and
so
we
did
that
for
cube
kind
of
you,
and
this
is
the
question:
do
we
want
to
do
this
for
kubecon,
north
america?
I
feel
like
we
should,
but
I'm
open
for
for
folks
comments.
D
A
E
Yeah
I
was
saying
we
want
to
freshen
things
up
right,
so
I'm
sure
things
have
changed
and
whatever
so
I
mean
we
can
reuse
what
makes
sense
to
reuse,
we
don't
need
to
reinvent
wheels,
but
it's
always
a
good
opportunity
for
us
to
take
a
fresh,
look
and
see
what
we
want
to
change
and
add.
Obviously,
things
have
changed
in
our
projects
since
then
right.
D
A
recent,
if
you're,
if
you've,
recently
started
joining
contributing
to
sick
docs.
What
would
you
have
liked
to
have
seen
in
that
video?
You
know
answers
on
no
answers
in
slack,
please
or
or
now.
E
Yep-
and
I
was
I
would
envision
in
addition
to
that
input,
we
would
go
look
at
the
deck
that
was
presented
and
then
you
know
by
looking
at
the
deck.
I
think
we
can
look
at
what
would
we
want
to
change
or
add
so
yeah.
A
No,
I
think
the
couple
areas
that
stick
out
to
me
are,
I
know
at
cubecon.
I
think
it
was
seattle,
2018,
maybe
20,
either
way
doesn't
matter,
I
want
to
say
we
did
a
session
where
I
started
to
walk
through
the
overall
repo
structure
and
how
it
integrated
with
hugo.
So
here's
where
the
content
is,
here's
where
localization
happens,
here's
where
static
files
are
and
really
painting
the
broader
picture
of
the
repo
and
how
it
integrates
with
you
and
how
to
how
to
actually
like
kind
of
read,
k,
slash
website
if
you
will
wasn't.
E
A
A
Don't
think
it's
worth
maybe
an
entire
20
minutes
or
making
that
the
entirety
of
the
deep
dive,
but
I
think
that
there
are
folks
that
are
just
generally
interested
in
how
does
kubernetes
do
docs
and
I
think
we
can
boil
down
some
of
the
fundamental
principles
of
how
we
do
it
and
get
into
the
technical
details
of
the
repo
structure,
but
just
food
for
thought.
I
think
what
we
should
do
is
get
a
smaller
team
together,
I'm
happy
to
help
out
brady
volunteered
as
well.
If
anyone
else
is
interested,
I
think
we
huddle
around.
A
B
Yeah
because
the
other
day,
I
was
trying
to
update
an
api
dark
set,
but
I
couldn't
figure
out
where
to
where,
in
the
kubernetes
list
of
repositories,
I
had
to
go
to
update
the
source.
B
A
A
E
A
E
A
Yeah
yeah
definitely-
and
you
know
I
I
don't
know
specifically
about
cubecam,
but
I
know
other
conferences
like
def
con.
For
example,
it's
a
hybrid
event,
so
there
are
people
attending
in
person
and
people
attending
remotely
in
different
price
tickets.
Based
on
that
and
then
the
actual
conference
speakers
are
submitting
videos
to
defcon.
So
I
don't
know
if
they're
hosting
a
video
in
the
room
and
then
maybe
the
attendee
is
there
for
questions
or
how
they're
actually
handling
that
I'll
get
more
details
on
kubecon.
A
A
All
right,
it
looks
like
semi-related
kicking
off
to
you,
brad
about
a
kubecon,
doc
sprint
and
real,
quick.
Just
some
context
there
between
the
two
of
them
is
the
maintainer
track
session.
That
we
just
talked
about
is
something
that
happens
during
the
kubecon
traditional
hours.
I
guess
things
like
tuesday,
through
friday
or
tuesday
through
thursday.
It's
part
of
the
overall
kubecon
event.
There
is
a
contributor
summit
the
day
before
and
here's
where
we
normally
run
like
sprints
and
and
do
the
the
various
I
guess
more
contributor,
hands-on
keys.
A
E
Right
and
then
so,
these
two
topics
are
wonderfully
related.
So
I
think
what
happened
this
year
is
there,
isn't
a
quote-unquote
contributor
day
per
se
or
something,
but
they
are
willing
to
give
us
space
on
the
schedule
on
that
on
that
monday,
which
is
a
pre-event
day
and
used
for
co-located
events.
E
So
the
really
nice
thing
is-
and
this
is
really
valuable
when
you
think
about
it:
they're
right
now,
they're
giving
us
for
kube
doc
sprint
a
room
for
a
full
day.
Now,
if
we
don't
need
the
full
day,
we
can
let
them
know
and
they'll
they'll
they'll,
happily
take
half
the
day
and
give
it
to
somebody
else.
But
right
now
I
kind
of
grab
the
whole
day
just
in
case,
because
it
is
an
in-person
thing
and
we
could
you
know.
E
So
we
got
to
figure
out
what
makes
sense
to
do
in
the
35-minute
session
and
deep
dive
and
what
you
want
to
cover
on
a
video.
But
then
we
really
do
have
a
full
day
of
you
know.
We
can
have
a
lot
of
fun
on
a
full
day
on
a
pre
on
a
pre-event
day
and
and
cover
a
lot
of
stuff.
Typically,
what
we've
done
in
the
past
is
we
spend
some
time
teaching
people
how
to
get
their
their.
You
know
how
to
do
git
and
how
to
get
up
and
running.
E
We've
used
it
as
a
way
to
get
people
sort
of
their
their
first
pr,
their
first
commit
into
docs
and
and
used
it
as
a
mechanism
to
sort
of
spread.
You
know,
increase
our
number
of
contributors,
which
is
really
a
lot
of
fun,
and
we
have
some
built-in
advantages,
so
you
know
trying
to
jump
in
and
become
a
cube
kk.
You
know
development
contributor
right
away.
Well,
that
takes
a
little
bit
of
work.
It's
a
little
bit
intimidating.
E
I
know
we
try
and
make
it
easier,
but
some
people
like
that
they
can
come
over
to
coob
docs
and
get
a
little
bit
of
hands-on
mentoring,
we're
real
friendly.
We
we
have
some
nice
advantages
to
to
bring
people
in,
and
you
know
if
they
want
to
go
from
working
on
docks.
I
mean
that's
one
of
the
best
ways
to
to
get
people
rolling
in
in
kubernetes
anyway,
start
in
the
docks
and
then
move
over
anyway,
so
the
the
tldr
we
got
a
full
day
that
we
have
the
opportunity
to
fill
with
an
agenda.
E
So
if
there
are
things
that
you're
like
oh,
I
wish
we
could
have
done
it
in
the
littles
and
the
video
session,
but
we
just
can't
pack
it
all
in
you
know
we
could
maybe
spend
say
an
hour
or
two
on
on.
Oh,
let's,
let's
really
understand
how
the
api
reference
works
or
or
the
stuff
that
that
jim
did
before
walking
through
how
the
release
builds
work
right.
We
got
a
full
day
and
a
room,
and
we
just
need
to
come
up
with
a
wonderful
agenda.
E
You
know
who's
going
to
be
there
and
what
would
they
love
to
cover
so
sort
of
the
first
couple
questions
are
we
ought
to
put
names
next
to
who
wants
to
volunteer
and
is
actually
going
to
be
there
in
person,
and
then
you
know,
probably
jointly
with
the
other
initiative.
I
think
we
had
to
do
them
together.
Just
to
keep
things
simple,
jim
is:
let's
figure
out
what
we
want
to
cover.
E
I
I
think
it's,
it's
usually
a
lot
of
fun
and
I
don't
think
historically,
we've
necessarily
filled
the
full
day,
I
think,
usually
by
3
30.
We're
kind
of
exhausted
we're
ready
to
go
to
whatever
event
with
refreshments
is,
is
coming
up
on
that
day,
if
I
recall,
but,
but
we
usually
get
some
pretty
good
pretty
you
know
we
get
a
decent
crowd
and
we
help
a
lot
of
people.
It's
it's
a
lot
of
fun.
A
Awesome
man,
I
was
just
about
to
say
my
I'm,
a
hundred
percent
in
align
with
exactly
what
you
said.
I
think
it's
a
great
idea.
I
I'm
on
board
100.
The
one
caveat
is
exactly
what
you
just
mentioned.
I
do
think
things
kind
gonna
peter
out
after
lunch
and
I
feel
like
we
all
kind
of
get
exhausted
of
going.
You
know
all
and
I
feel
like
especially
kubecon,
for
me
at
least
I
feel
like
a
dog
or
like
a
kid
in
a
candy
store.
I
run.
A
A
Think
that
maybe
we
cut
it
off,
maybe
a
little
bit
after
lunch
or
maybe
break
at
lunch
and
just
take
that
morning,
reservation
there
and
give
somebody
else
the
time
or
the
room.
Yes,.
E
I
agree
historically,
that's
exactly
how
it's
been.
We
we
have
all
this
energy,
we
do
all
this
cool
stuff
and
then
we
go
to
lunch
and
then
maybe
we
get
another
hour
and
then
we're
all
just
like
baked,
and
and
so
you
know,
if
we
want
to
maybe
just
say,
hey,
you
know
reserve
the
room
like
you
said
like
I
guess
it's
like
nine
to
two
or
something
I'm
totally
cool
with
that.
E
We
just
have
to
I'll
just
let
deb
know,
but
but
I
do
recommend
that
I,
I
think
the
full
day
is
just
a
little
too
much.
You
know
go
ahead,
sir.
D
What
we
could
do
is
for
anyone
who's
feeling
super
keen
to
carry
on.
We
could
have
a
little
team
like.
I
think
I
could
do
this
of
remote
folk
who
are
on
board
with
getting
pr's,
getting
same-day
reviews
for
pr's
and
so
on
and
just
say:
well,
you
know
you
have
a
laptop,
you
have
the
internet
go
forth
and
document.
E
D
E
E
All
right,
somebody
doesn't
sleep
like
me,
I
love
it
so
yeah.
I
think
that
that
that's
a
wonderful
addition
that
you
know
we'd
have
sort
of
that
virtual
office
hours
and
we
would
let
people
know
that
that
you
were
available
on
slack
and-
and
you
know
that
way
they
could
get
a
little
extra
time
if,
if
they
wanted
and
then
you
know,
I
think
by
say
2
30ish,
jim
and
I
and
whoever
else
is
there-
is
going
to
be
pretty
much
baked
right
and
I'm
just
telling
you
how
it's
always
been.
E
F
E
I
think,
as
part
of
the
other
meeting,
we
ought
to
look
at
the
agenda.
Let's
start
with
who's
going
to
be
there
in
person
and
what
topics
they
feel
comfortable,
covering
and
and
then
we'll
put
an
agenda
together
and
then
obviously
we'll
start,
you
know
advertising
it.
You
know
the
more
people
we
get
there.
It's
it
makes
it
a
lot
more
fun.
So,
okay,
cool.
A
Awesome
and
so
I'm
gonna
take
the
action
brad.
I
completely
agree,
let's
tie
in
the
two
initiatives
together,
just
to
make
sure
that
we're
delivering
unified
content
on
both
fronts,
and
so
I'm
happy
to
work
on
both
them
with
you
you're
happy
to
work
on
both
of
them
chris,
I
don't
wanna
speak
for
you.
Are
you
interested
in
tagging,
along
for
the
additional
scope
of
here.
A
A
And
chris
negus
can
I
add
you
to
the
the
maintainer
track
as
well,
so
you
can
get
plugged
in
there
sure
yeah.
I
hate
to
scope
creep
on
folks,
but
I
feel
like
that's
going
to
be
a
necessary
evil
for
this
to
be
a
success,
yep
and
so
chris
metz
you
volunteered
to
help
out
with
the
deep
dive
session.
Are
you
also
interested
in
helping
out
the
docs
print?
A
Yes
put
me
down
for
that
awesome
and
I
think
we
have
enough
overlap
now,
if
folks
needed
to
plug
in
more
to
certain
areas
versus
others.
I
think
we
can
divvy
this
up
internally
or
you
know
as
a
smaller
group,
but
I
don't
think
it's
going
to
be
everybody
doing
everything
all
the
time.
Fortunately,
it's
cool.
A
B
A
With
humans,
since
I've
gotten
vaccinated,
is
introducing
myself
to
a
new
person,
so
I
ran
into
somebody
and
you
initially
go
for
like
a
handshake,
but
now,
like
you,
can't
really
do
that.
We're
both
facts,
but
I'm
not
ready
to
handshake
yet
and
there's
elbow
bumps
fist
bumps
you
could
do
the
star
trek.
I
just
feel
like
I've,
never
had
such
a
weird
moment
of
self-reflection
when
I
ran
this
way,
hey
nice
to
meet
you
and
like
instinctually,
just
reached
out
to
grab
a
hand
and
so
yeah.
A
It
will
be
interesting,
I'm
here,
for
it
awesome
cool.
Moving
on.
I
threw
this
on
the
agenda.
This
is
a
little
bit
of
a
curveball.
I
don't
mean
to
catch
anyone
off
guard
eddie
zane
brought
up
the
cube,
cuddle
docks
and
starting
to
bring
that
under
the
umbrella
of
kubernetes
website
and
that's
curious.
If
there's
any
updates
on
that.
D
F
I
I
have
also
done.
I
think
that
chris
is
me
yes,
because
I
yes,
okay,
because
I
did
volunteer
for
that-
I'm
going
to
be
talking
to
eddie
this
afternoon
on
something
else,
a
related
issue
associated
with
kind
lists.
F
F
Yes-
and
I
think
I
understand
I'm
going
to
talk
to
him
about
it-
yeah
it's
it's
weird,
because
you
you
use
it
and
then
it
doesn't
show
up
anywhere.
It's
like
weird.
You
can't
find
it
again,
but
anyway,
oh.
E
Contraire,
just
a
nice
data
point
that
feature
showed
up
in
the
operator.
Sdk
helm
plug-in
big
time
big
time
because
it
then
those
came
in
and
nobody
knew
what
it
was
and
didn't
know
how
to
process
it
and
it
caused
the
operator
sdk
helm,
plug-in
to
blow
chunks.
So
if
I
do
know
somebody
on
my
team,
who
is
an
expert
on
this
help
to
help
do
the
fix
for
for
that
plug-in.
So
if
you
want
more
details
about
what
the
mysterious
thing
is
slack
me
I'll
get
you
contacted
with
martin
hickey.
D
Okay,
okay,
yeah
docs,
I'm
gonna
yeah,
it's
it's!
It's
sort
of
my
my
next
chunky
bit
of
work
to
pick
up.
F
A
Yeah
and
one
other
thing
that
I'll
throw
out
there
too,
is
with
migrating
over
the
cube
cuddle
docks.
It
doesn't
have
to
be
an
all
or
nothing
thing
can
be
iterative.
I
mean
the
how
flexible
websites
are
with
netify
and
the
way
we
build
stuff
I
mean
we
could
start
even
duplicating
content
as
a
pr
or
a
work
in
progress.
F
A
Cool
and
did
I
give
context
on
that
issue.
I
know
I
transitioned
into
it.
I
kicked
over
tim
and
chris
on
that.
Did
I
tell
everybody
just
basically
bringing
cube
cuddle
external
docs
into
the
kubernetes
website,
so
instead
of
having
many
different
sites,
a
big
mono
site
that
covers
everything,
it's
unified,
looks
the
same
information
architecture,
fun.
E
A
Yeah
it's
a
collaborative
effort.
If
I
can
kind
of
paint
a
broader
picture,
there
was
initiative,
I
want
to
say:
is
google
summer
of
docs
or
a
similar
initiative
to
really
improve
the
cube
cuddle
documentation
and
as
a
effort
to
kind
of
scope
that
or
bound
it
to
a
smaller
scope?
They
created
our
own
standalone,
cube,
cuddle
website
and
now
that
it's
up
and
running
and
the
work
has
been
done.
A
A
All
right
and
we're
right
up
on
time
here,
just
in
time
for
some
housekeeping.
I
just
want
to
let
folks
know
that
our
youtube
playlist,
I
believe,
is
incredibly
out
of
date,
I'm
still
working
on
a
better
way
to
automate
just
for
a
context.
There's
a
plugin
for
zoom
that
when
I
click
end
this
meeting,
it
should
see
that
there's
a
new
recording
and
upload
it
to
youtube.
A
A
As
a
technical
operator
engineer,
I
have
a
big
problem
with
the
bandage
fix:
that's
going
to
keep
causing
the
same
pain
over
and
over
again,
so
I've
been
leaving
it
in
this
non-sinking
state,
because
I
think
there's
going
to
be
a
better
solution
out
there,
either
leveraging
zapier
or
some
other
plug-ins
or
integrations
in
correlation
with
contrib
x.
To
streamline
this
in
the
meantime,
it's
out
of
date,
I'm
going
to
manually
upload
those
I've
shared
with
some
of
the
tech
leads
and
co-chairs
how
to
do
that.
A
Just
given
some
general
information
there,
I
also
plan
on
cleaning
up
the
agenda,
so
there
are
some
permissions
issues
as
well.
So
really
what
this
involves
is
copy
and
pasting,
creating
a
new
agenda,
updating
some
of
the
links
so
there's
gonna
be
some
some
shake
into
branches
if
you
will
around
sig
docs
and
some
of
the
the
things
that
we
have
going
on.
A
In
addition
to
that,
we
usually
will
take
a
previous
year's
meeting
notes
I'll
take
them,
convert
them
to
markdown
and
upload
them
to
our
contributor
or
our
community
repository
and
just
keeps
our
document
a
little
smaller,
a
little
lighter
a
little
easier
to
load
and
maintain.
I
think,
we're
at
like
87
pages
right
now
or
something
like
that.
Not
crazy!
There's
bigger
google
docs
out
there,
but
let's
keep
things
clean
and-
and
you
know,
isolate
it
by
year.