►
From YouTube: Kubernetes Sig Docs 20190122
Description
Meeting notes: https://docs.google.com/document/d/1zg6By77SGg90EVUrhDIhopjZlSDg2jCebU-Ks9cYx0w/edit#
The Kubernetes special interest group for documentation (SIG Docs) meets weekly to discuss improving Kubernetes documentation. This video is the meeting for 22 January 2019.
https://github.com/kubernetes/website
A
And
we
are
recording
so
hello,
everyone.
This
is
the
weekly
meeting
for
kubernetes
sig
docs
I
am
Zack.
Carlson
today
is
Tuesday
January
22nd.
It
is
7:00
p.m.
because
this
is
a
fourth
Tuesday
and,
as
usual
on
4th
Tuesdays.
We
meet
at
7:00
p.m.
Pacific
time
in
order
to
make
it
easier
for
folks
from
the
asia-pacific
region
to
attend,
hey,
Brad,
Lola
Donald,
so.
A
A
B
A
C
C
Thank
you,
I'm
from
South
Korea
I'm
working
for
three.
It
is
one
of
national
chased
in
South.
Korea
I
also
participated.
The
last
cone
I
think
I
met
you
there
and
I
hope
to
contribute
to
correlative
qualities
and
majorly
to
the
developing
some
new
functionalities
for
as
a
starting
point,
I
choose
to
to
country
based
document.
First,
so
I'm,
currently
working
on.
C
A
So,
let's
see
that's
good,
let's
move
on
to
updates
and
reminders
in
housekeeping
I'm
back
I
will
create
a
new
PR
Wrangler
schedule
for
the
first
six
months
of
2019
this
week.
So
we
can
get
back
on
a
regular
rotation.
Brad
I
know
that
you
filled
in
last
week.
I
think
Tim
Fogarty
is
filling
in
this
week
and
does
anybody
know
who
did
we
have
anyone
filling
in
like
the
first?
The
the
week
before
you
Brad.
A
E
E
I
guess
gonna
be
part
of
our
shadow
and
crew
and
that's
Cody,
Jared
Barney,
Naomi
instantly
tuned
it
and
so
you'll
see
more
of
them
on
different
channels
in
various
areas
and
one
kind
of
cool
quick
side
note
was,
since
there
was
so
many
applicants
for
the
shadows,
role,
we're
able
then
to
send
I,
don't
want
to
convert
Jesse
letters
but
saying
that
or
other
release
other
release.
Shadow
positions
are
full,
but
that
doesn't
mean
you
can't
help
out
with
sick
ducks.
E
E
A
E
One
thing
I
forgot
to
mention
a
side
note
here
was
that
the
overarching
goal
for
this
release
team
is
to
really
finalize
our
playbook
I
shouldn't,
say
finalized,
but
get
is
at
a
point
where
every
iteration
from
there
can
use
as
a
playbook.
So
that
would
be
one
of
our
main
goals
that
I
work
on
with
the
shadows.
A
G
G
The
present
well
yes,
so
when
you're
well,
you're
looking
for
that,
I
can
give
a
little
background.
So
one
of
the
things
we
decided
it
at
the
beginning
of
qq1
and
that
one
of
the
things
we'd
focus
on
this
quarter
is
choosing
a
few
topics
that
we
would
like
to
update
and
possibly
some
new
topics.
We
would
like
to
write
and
just
making
a
very
small
list
of
writing
projects
we've
them.
This
has
been
the
one
thing
that
tends
to
get
get
forgotten.
We
we
have.
You
know
many
people
helping
with
implementers
of
infrastructure
translation.
G
All
these
are
good
efforts,
but
we
decided
this
quarter.
We
wanted
to
make
sure
we
got
some
writing
done,
and
so
these
here
in
this
project,
I've
listed
I
think
six,
six
things
that
I
thought
it
would
be
good
to
focus
on
for
q1.
Two
of
them
already
have
owners
this
first,
one
on
ingress
is
owned
by
Cody
Clark
and
the
next
one
on
Cube
admin
set
up
is
owned
by
Jennifer
Rondo,
but
the
other
four
don't
have
owners
yet
so
Zach,
if
you
could
click
on
the
one.
That's
about
a
replica
sense.
G
So
Andrew
Chan
and
Dominic
Tourneau
have
been
working
on
some
fundamental
modeling
concepts
for
kubernetes
and
they've
written
some
blog
posts,
and
one
of
the
things
they
came
across
is
that
there
there
are
some
misconceptions
about
how
replica
sets
work
and
the
replicas
that
is
really
what's
behind
the
deployment,
and
so
we
thought
to
you
know
to
go
along
with
that
effort,
and
we
just
thought
this
was
a
important
thing
to
clear
up
was
that
we
would
update
this
replica
set
Const
topic,
so
I've
talked
to
you
know,
listed
some
things
that
I
I
think
we
ought
to
do.
G
But
then
we
came
across
some
things
like
replica
set
basis.
It's
it's
actions
on
both
pod
labels
and
this
something
called
Tod
owner
reference.
An
owner
reference
is
not
very
well
explained
right
now,
and
so
we
think
that
this
is.
This
is
a
you
know:
it's
a
critical
concept
to
get
explained
in
this
topic,
so
this
is
just
one
example
of
how
he
you
know.
We've
chosen
one
thing
that
we
could
improve
in
that
you
know
an
actual
topic
to
be
updated
and
so
we're
looking
for
owners
for
these
things.
G
So
if
this
is
something
you're
interested
in
doing,
you
know
doing
actual
writing
work.
This
is
the
this
is
the
place
to
look
for
ideas,
and
if
you
can
put
your
come
onto
one
of
these
assign
it
to
yourself
and
then
you
can.
You
can
own
that
project
for
q1.
A
D
D
F
A
D
I
A
I
think
it's
a
great
entry
level,
yeah
I
think
it's
a
good
place
to
start
I
mean
Steve,
did
a
pretty
good
job
of
scooping
out
the
requirements
and
what
particularly
needs
to
happen
there
and
you
know
if
you
run
into
difficulty.
If
you
have
any
questions,
I
mean
you
certainly
don't
have
to
do
it.
Although
we
exist,
we
exist
as
a
community,
they
help,
and
you
can
also
talk
to
feature
developers
as
well.
We
can
get
you
pointed
to
the
right
SIG's.
If
you
have
any
questions
about
the
technical
material.
B
G
F
G
G
Okay,
but
yeah,
we
can
get
you
in
touch
with
Dominic
if
it
turns
out
that,
that's
that's
what
you
need.
Thank
you.
A
J
B
B
A
A
Want
to
become
an
organ
of
the
kubernetes
github
organization
and
the
path
to
that
is
when
you
put
together
like
five
PRS,
so
I
would
say
just
follow
the
instructions
for
like
forking
and
cloning,
the
repo
and
they
follow
the
follow
the
contribution
guide
and
get
started.
And
if
you
have
any
questions
about
that
or
if
you
want
to.
If
you
want
someone
to
walk
through
with
you,
like,
while
you're
doing
the
initial
setup
and
I'm
happy
to
do
that.
Thank.
A
A
A
E
E
That's
when
I
got
involved
with
the
different
branching
strategies
and
the
different
cycles
that
everyone
was
in
and
say,
I
wish
I
got
involved
with
that
sooner
so
I
was
trying
to
see
if
there's
a
known
method,
to
get
a
hold
of
everybody
or
if
it's
just
individually,
being
a
male.
It's
okay,
it's
okay!
That's
the
answer
to
stress.
If
there
is
a
community
direction
there.
A
A
A
See
the
Chinese
list
is
a
little
long
because
it
still
is
probably
still
representative
in
at
least
some
capacity
of
like
having
gone
to
Shanghai
and
they
reviewed
a
whole
bunch
of
Chinese
Pierre's
in
progress,
but
like
so
here
in
the
Korean
owners
list
that
Claudia
and
Junyi
and
Ian.
So
there's
like
some
guidance
you
can
get
here,
but
if
you
open
in
like,
if
you
open
an
issue,
you
can
probably
get
ahold
of
folks
like
I'm.
Using
this
contact
info
slack
is
another
good
way
to
do
that.
A
A
E
A
That
was
one
area
that
definitely
could
have
gone
more
smoothly
during
the
last
cycle
was
it
was
the
first
time
in
fairness.
It
was
the
first
time
that
we
had
ever
done
a
release
with
an
active
localization
so
yeah,
that's
that's
a
really
good
idea
to
get
in
touch
really
and
figure
out.
Branching
branching
strategy
in
advance
at
the
need.
L
I
posted
a
question
on
slag,
so
I
understand
now
that
we
also
have
a
separate
github
page
for
kubernetes.
Esi
I
was
wondering
how
you
would
handle
the
localization,
because
there
are
links
to
kubernetes
documentation
website
and
if
we
were
to
link
out
to
kubernetes
ESA
github.
How
would
we
manage
the
uniformity
in
translation
and
localization
so.
H
I
L
A
D
A
L
F
G
L
G
G
M
A
A
We
don't
have
any
coercive
power,
the
what
what
power
we
have
is
persuasive
and
if
we
are
seeing
you
know
if
we're
starting
to
see
sort
of
one-off
sites
or
sites
with
kubernetes
specific
content
that
that
aren't
in
NK
web
site,
then
I
think
maybe
let's
take
a
look
at
why
that
is,
and
if
there's
something
about
like,
maybe
we
should
maybe
we
need
to
look
at
our
workflow.
Maybe
we
just
need
to
like
have
greater
visibility.
Maybe
we
need
greater
accessibility
to
getting
content.
A
You
know
under
the
roof
of
K
website,
so
I
would
say.
I
would
encourage
us
to
like,
let's,
let's
find,
who
owns
these
and
have
a
conversation
with
them
about.
A
L
A
Sorry
Raji
thank
you
for
bringing
this
to
our
attention
in
the
future
I.
Can
you
put
it
on
the
agenda.
A
E
Taking
notes,
there's
like
I
was
gonna
say
that
Roger
brought
up
was
kind
of
the
next
agenda
item
as
well.
I
think
the
slight
variance
there
when
I
started
to
talk
about
this
is
the
Cooper
knife.
Csi
documentation
does
seem
to
be
directly
within
the
domain
of
kubernetes
and
potentially
makes
sense
that
should
be
within
our
documentation
and
obviously
we
can
turn
over
that
a
little
bit
more.
But
are
we
ready
to
move
on
to
the
next
agenda
item
similar
to
this
topic
or
young
one?
So
I'm
gonna
give
me
one.
Second,
sir:.
E
Yeah
no
worries
so
I
was
talking
to
Ben
on
slack
and
he's
part
of
the
project
kind
kubernetes
in
dr.
and
he
joined
the
call
today
just
to
briefly
discuss.
Essentially
he
wants
to
host
his
own
documentation.
Everyone
speaks
a
little
more
of
that
because
it
is
a
sub-project,
but
since
it's
a
community
project
under
the
same
umbrella,
you
know
where
does
sigdoc
step
in?
Where
do
we
step
out?
Do
we
say
IRA
totally
hands-off?
You
know
where's
that
compromise
there
and
trying
to
open
up
the
discussion.
You
know.
N
N
A
A
A
What
specifically,
are
you
asking
for?
Are
you
asking
to
like
host
a
subdomain
off
of
like
kubernetes?
Do?
Are
you
asking
to
like
take
advantage
of
the
take
advantage?
Is
a
terrible
language.
Are
you
asking
to
like
just
like
piggyback
off
of
the
the
hugo
themes
like?
Can
you
can
you
say
a
little
bit
more
about
what
it
is
specifically
that
you're
that
you're,
hoping
for.
N
Some
thoughts
I
had
was
potentially
we
could
eventually
have
a
son
like
suggested,
see
me
more
tooling
how
you
might
go
about
I
mean
if
we
want
to
tell
things:
okay,
we're
not
gonna,
maintain
anything.
You
need
to
use
github
pages
I
can
at
least
tell
pull
together
spin
docs
on
how
you
go
about
doing
that,
because
I
can
think
of
at
least
two
projects
that
I'd
like
to
do
this
for
and
I'm
sure
there
are
others.
A
Yeah,
that's
well,
first,
thank
you
for
collaborating
and
they
collaborating
proactively.
That's
like
maximally
awesome,
so
I
think
I
I
want
to
be
careful
because
I
don't
want
to
increase
the
maintenance
burden
of
the
SIG's,
we're
already
stretched
kind
of
thin
there.
But,
on
the
other
hand,
I
think
this
is
like
in
some
ways
like
D
big
question
for
communities.
A
Future
development
and
documentation
is
how
to
how
to
empower
good
documentation
to
as
many
as
like
the
tools
for
that
to
as
many
people
as
possible
and
I
think
you
know
like
if
the
if,
if,
if
sigdoc
says
in
providing
that
kind
of
guidance,
people
are
just
going
to
do
their
own
thing.
Like
you
know,
we,
we
cannot
serve
a
gatekeeping
function
and
we
won't
like
we're
not
able
to.
If
we
tried
we
would
fail.
A
To
reciprocate
that
collaboration
and
try
and
figure
things
out,
at
least
in
terms
of
like
guidance
of
these
are
some:
these
are
some
mistakes
to
avoid
these
are.
These
are
like
this
is
how
to
make
this
easier
think,
just
in
terms
of
being
able
to
provide
some
guidance,
and
you
know
maximize
our
own
collaboration
with
future
developers.
A
G
Yeah
you
mentioned
prowl.
What
what's
the
other
one?
That's
on
top
of
your
mind
that
you
might
want
to
do
this
with
Oh
kind,
I
sort
of
like
many
cute,
but
not
uh-huh,
and
these
are
things
where
you
feel
like
a
github.
Readme
is
not
not
adequate,
like
there's
enough
material
that
could
have
a
readme,
it's
become
inadequate,
yeah.
N
A
A
How
much
of
like
the
the
stand-up
work
for
a
static
site
we
can
that
we
can
like
just
make
in
common,
so
that
you
know
if
you're,
if
you're,
building
a
kubernetes
project
like
devote
here,
let's
make
it
as
easy
as
possible
to
actually
like
develop
the
feature,
and
you
know
like
spends,
make
sure
the
time
spent
documenting.
It
is
expense
on
the
actual
documentation
and
unlike
site.
Standout
would.
N
N
F
N
Just
gonna
add
that
I
I
talked
to
a
few
people
offline
about
this,
and
the
first
thought
we
had
is
that
the
DNS
is
actually
something
that's
checked
in
and
configurable
by
PR
now,
and
we
were
thinking
that
and
we
could
do
something
like
maybe
like
project
named
States,
that
IO
for
things
that
are
encrypted
in
e-cigs
and
for
things
that
aren't.
Maybe
they
go
under
a
different
Kate,
said:
IO
sort
of
mean
something
along
those
lines
and
use
it
using
the
net.
Will
fight
would
be
super
helpful,
yeah.
A
So
at
this
point,
I'm
gonna
say:
let's
bring
this
discussion
to
sing-sing
docs
tools
because
we're
getting
into
like
specifics
of
configuration,
I
think
if
we
can
share
an
LFA
site
in
common
that
has
some
advantages,
administered
well,
security
and
administration
is
one
of
the
pieces
that
I
don't
know
enough
about
and
and
respect.
You
know
far
more,
but
let's
at
this
point,
Ben
are
you?
Okay,
if
we
like
defer
this
conversation
into
into
the
slide
channel,
so
that
people
can
collaborate
a
sickness?
Absolutely
thank
you
for
having
me
absolutely
thank
you
for
joining
us.
A
E
The
very
least
of
just
creating
some
first
standards.
You
know
if
we
end
up
not
being
able
to
collaborate
or
just
saying
hey,
here's
our
standards
that
we
have
here's
our
Hugo.
Maybe
we
even
turn
down
as
one
of
our
q2
or
q3
products,
trim
down
the
theme
that
we're
currently
using
or
it
sounds
like
there
might
be
one
in
the
works
and
say
here's
a
base
of
what
we
think
is
acceptable
and
then
let
them
go
from
there.
If
we
didn't
want
the
overhead
but
to
be
discussed
right.
A
A
Let's
see,
let's
see
actually
Andrew
Co
Co
I'm
gonna
bump
you
to
Mehta
after
Andrew
Andrew.
F
Cuz,
this
came
up
in
the
slack
channel
a
while
ago.
I
did
get
a
chance
to
follow
up
on
it,
but
really
since
you're
on.
Could
you
describe
the
problem
because
I
wasn't
sure
whether
this
was
some
issue
of
like
things
being
auto,
translate
it
or
what
the
width
of
broken
links
were
exactly
you
sent
me
some
links
of
the
pages,
but
I
still
wasn't
clear
on
what
what
the
mismatch
was
right.
I.
M
M
M
F
F
M
M
A
M
A
C
Right
in
the
previous
meeting
of
Korean
localization
team
meeting,
we
shared
the
idea
that
if
then
life
is
supported
to
Korean
working
branch
will
help
help
to
review
the
PR.
So
we
hope
to
know
that
then
like
Linda,
if
I
can
be
supported
for
Korean
working
French
edge,
where
it
is
first
question
and
the
congestion
is
for
ingestion
is
how
how
how
we
can
support
my
life
and
my
life
I
to
Korean
working.
C
F
F
C
A
Like
for
Ben's
question
about
setting
up
subdomains
whether
or
not
we
can
set
up
an
administrator
access,
that's
specific
to
that
site
like
how
granular
we
can
get
with
metla
fie
permissions,
because
if
the
Korean
development
branch
is
always
going
to
be
changing,
I
assume
that
you're
going
to
be
iterating
that
development
branch.
That
means
that,
every
time
you
change
a
development
branch,
we
have
to
repoint
that
site
right.
F
So
there's
there's
two
issues
in
that
in
that
Lefou
we
can
set
up
a
separate
group
of
people
and
just
let
them
just
control
specific
thing,
but
then
there's
also
the
permissions
issues
within
the
kubernetes
github
org,
because
I
used
to
be
able
to
set
these
things
up
and
then
point
it
out
whatever
a
repo
and
branch,
but
something
change
and
I
can't
do
that
anymore
and
I.
Think
you
need
a
higher
privilege
to
be
able
to
do
that.
Okay,
what
you.
F
I
think
with
like
I
couldn't
for
the
new
ones
we
had
to
spin
up.
Like
a
you,
know,
a
version
branch
or
a
version
like
the
Phi
sub
site
right,
but
I
wasn't
able
to
do
it
and
you
and
you
were
so
that's
why
I
think
something's
change
and
you
have
a
higher
permission
somehow
than
me
in
the
kubernetes
org.
F
A
F
A
Like
isolate
that
specific
to
that
that
particular
site
yeah,
that's
so
we'll
take
into
that
I
wish
that
I
could
promise
that
this
week,
she'll
go,
but
it
might,
it
might
take
till
the
end
of
next
week,
if
I'm
being
I
will
try
to
do
it
sooner
than
that,
but
I
don't
want
to
I.
Don't
want
to
disappoint
you
I
would
rather
I
would
rather
estimate
taking
too
much
time
then
promise
at
any
sooner.
It's
not
urgent.
A
Thank
you,
yeah
I
think
you
then
to
answer
your
chat
question.
It
may
very
well
read
permissions
from
from
github,
but
whether
it's
still
reading
permissions
from
github
or
whether
that
was
like
a
one-time
initiation
thing
I,
don't
know
because
that
I
know
that
list
is
not
necessarily
contiguous
with
what
I
expected
you
to
be
the
last
time
that
I
looked
at
it
so
shrug
emoji.