►
From YouTube: Kubernetes SIG Docs 20181002
Description
Meeting notes: https://docs.google.com/document/d/1Ds87eRiNZeXwRBEbFr6Z7ukjbTow5RQcNZLaSvWWQsE/
The Kubernetes special interest group for documentation (SIG Docs) meets weekly to discuss improving Kubernetes documentation. This video is the meeting for 02 October 2018.
https://github.com/kubernetes/website
B
Okay,
so
thanks
again
just
for
the
recording
sake,
hey
112
is
done.
It
was
super
bumpy,
but
that's
okay.
We
plan
on
automating,
most
of
it
and
Tim
Fogarty
is
taking
over
for
me
and
113
and
first
off
he's.
Awesome
has
an
awesome
accent
and
then
secondly,
I
will
be
working
on
automating
away
a
lot
of
the
problems
that
we
add
in
112.
So
Tim
anything
you
want
to
say:
I
want
their
team.
C
B
D
A
E
A
B
B
So
hi
internationalization,
guys,
we've
been
having
like
problems
with
internationalization,
mostly
because
we're
like
not
a
hundred
percent
certain
there's
about
80
different
ways
to
do
it
and
get,
and
of
course,
when
you
throw
in
the
constraint
of
Hugo
neckla
Phi
our
release
process,
our
current
branching
strategy
and
then
all
of
the
languages
that
want
to
start.
We
have
like
five
fairly
large
variables
that
were
like.
We
don't
have
a
really
good,
ish
way
of
being
able
to
do
things
and
stuff
with
words.
B
So
Zack
core
lesson:
myself:
Jim
angel
met
last
week,
oops
sorry
with
Andrew,
and
we
chatted
about
internationalization
and
we've
been
discussing.
So
we
went
through
a
few
different
strategies.
So
just
so,
you
guys
know
for
context,
I'm
going
to
say
really
quickly.
It's
for
the
recording,
some
things
that
we
have
considered.
One
because
everything
in
Hugo
needs
to
live
in
content,
/
language
to
character,
code
/,
and
then
you
know
everything
in
there.
B
We
are.
The
the
original
strategy
was
to
fork,
make
a
website
repo
into
e
individual
language
and
then
have
them
used.
Since
they
have
the
same
base
commit,
then
they
have
similar
issues
and
get
can
reserve
all
those
it
can
resolve
all
of
those
Delta's
as
we
try
to
push
mash
them
back
in
to
the
K
website
repo,
because
that's
the
only
one
that
net
worth
is
worth
up
to
and
the
problem
we
run
in
with
that
is
one
obviously
for
Tripos,
plus
long-running
branches
plus
as
fast
as
PRS
are
merged
into
master.
B
In
our
side
of
things.
Sorry,
the
English
side
of
things
in
K
website
it
is.
It
is
a
challenging
problem
for
them
to
be
able
to
manage
the
velocity
of
commits
they
have
to
keep
up
with
and
the
fact
that,
every
time
they
pull
from
upstream,
it
blows
away
their
owners
files
because
they
have
separate
owners
and
approvers,
because,
obviously,
if
myself
or
Brad
or
Tim
or
Jared
we're
having
to
look
at
pull
requests
in
Korean
well,
I
actually
have
no
idea.
B
If
you
guys
know
Korean,
but
I
would
personally,
I
would
really
have
a
tough
time
knowing
like.
Oh
sorry,
this
is
Amit
you're
missing
a
comma
I
feel
like
I.
Don't
understand
any
of
that,
so,
let's
just
it
looks
good
to
me
so
when
you
poke
from
upstream
it
blows
by
the
owners
file.
So
given
all
of
that
and
the
fact
that
prowl
now
has
this
thing
called
inheritance,
actually
it
may
have
always
had
that.
B
B
The
reason
we
originally
decided
not
to
do
that
was
because
now
we're
going
to
have
almost
triple
the
number
of
PRS
on
a
weekly
basis
to
manage
and
for
those
of
you
who
have
done
a
PR,
regular
role,
you
already
know
that
there's
a
lot
to
do
without
having
four
or
five
more
languages
to
deal
with,
so
we
have
a
semi
solution
for
that
enter
github
labels.
So
so
this
is
the
demo
section
I'm
going
to
share
my
screen
and
everyone
see
slack
right.
B
This
I
quickly
scaffolded
a
server
list
app
so
using
AWS
lambda,
and
you
can
check
that
out
where
we
have
no
idea
where
the
final,
whatever
is
going
to
land
for
that
or
the
final
home
for
this
is
going
to
be,
but
basically
I've
scaffolded.
This
PR
Doc's
language,
labeler
I,
do
not
have
a
cool
grief.
Nautical
title
for
this,
but
suggestions
are
welcome.
I
think
the
word
for
labeling
creepy
Greek
is
epigraph,
so
maybe
it
could
be
called
that
I
don't
know.
B
Basically,
the
call
flow
for
this
thing
is
that
a
web
hook
comes
from
github
comm,
that
a
pull
request
has
been
open.
It's
an
Amazon,
API
gateway.
It
goes
into
a
function
that
all
it
does
is
push
and
push
a
message
into
a
queue
and
then
respond
with
a
200
response,
because
we
want
github
to
not
interrupt.
B
So
now
what
we'll
be
able
to
do
is
filter
pull
requests
by
language
so,
as
somebody
who's
triaging
pull
requests
in
the
English
language,
you
can
filter
by
language
slash
again
and
for
somebody
who
is
in
you
know,
managing
Chinese
PRS
as
an
approver
you'll
be
able
to
do
language
slashes
eh.
So
let's
go
over
here
just
to
prove
that
all
right,
everyone
make
a
sacrifice
and
the
demo
gods.
Oh
right,
sorry
before
I
say
that
so
right
now
it's
based
on.
B
B
I
will
assign
the
language
slash
c
and
label
just
like
prowl
does,
but
this
we
don't
actually
have
to
insert
into
prowl
it's
already
there
and
now,
when
I
go
to
like
the
whole
list
of
pull
requests,
I
can
filter
by
label.
So
if
I
filter
by
the
language
/cn
label,
I
see
only
four
requests
related
to
this
language,
so
that
is,
that
is
the
demo
and
that
is
I,
think
going
to
be
our
strategy.
So
to
get
this
into
Kay
website,
it's
already
live
and
ready
for
production.
B
Today,
all
we
have
to
do
is
add
the
bot
as
a
as
a
contributor
to
the
kay
website,
repo
and
add
the
webhook
URL
of
the
API
gateway
instance
to
Kay
website,
and
we're
done
so
I
think
Zack,
C
and
I.
We're
going
to
do
that
or
whomever
has
the
ability
to
access
that
section
of
kaleb
site
after
this
meeting.
I
guess
he's
out
so
I'll
have
to
find
somebody
for
that.
Any
questions
on
that
is
that,
like
super
confusing.
B
We'll
lay
back
law
with
a
language,
e'en
change,
create
issues
or
any
other
backlog
item
for
the
other
languages.
I
may
need
you
to
help
me
understand
your
question.
Look
a
little
bit
better,
but
the
goal
is
no
so
by
keeping
everyone
inside
of
the
same
repo.
Yes,
our
velocity
of
PRS
will
go
up,
but
ideally
it
would
be
a
transparent
change
for
anybody
in
any
language
because
they
will
know
that
everybody's
in
the
same
repo,
so
all
of
the
long-running
branches,
all
of
the
same
problems
we've
already
had
nothing,
there's
no
added
complexity.
B
B
F
This
is
Celia
I
hope
you
can
hear
me.
I
can't
yeah,
so
I
I'm,
not
sure
that
that
I
answered
that
do
answer
appropriately
answered
my
question
so
I
mean
let's
say:
I
change,
one
page,
because
there
is
something
missing
or
the
definition
of
it
has
changed.
Maybe
I
change,
one
word
or
anything
so
and
I
would
expect
that
same
change
to
be
visible
for
any
other
language.
So
and
if
I
am
doing
the
change.
I
personally
cannot
do
the
change
in
Chinese.
B
Think
I
understand
your
question
now
that
particular
what
you're
talking
about
may
be
a
bit
out
of
scope
for
for
this
particular
effort,
because,
right
now
our
internationalization
teams
are
just
getting
to
translate
Docs
as
they
are
now
so
I,
don't
know
of
any
coordinated
for
somebody
else
who
has
more
time
on
this
project
or
has
spent
more
time
with
a
notation
feel
free
to
correct
me.
But
to
my
knowledge,
no
I
don't
think
that
there
is
a
coordinated
effort
of
this
particular
file.
Let's
say
it's
slash,
doc,
slash
coop
control,
flag.
B
D
Another
source
projects
that
have
worked
on
there
were
models
that
when
there
was
an
English
change,
it
triggered
a
notification
and
then
there
was
sort
of
a
a
model
where
the
folks,
the
other
languages,
could
then
see
that
a
change
occurred
in
the
one
and
then
they
could
cue
them
up
and
decide
to
define
my
doubts.
Who
then
make
sure
the
change
occurred
so
would
be
good
if
the
models
somehow
in
the
future
supports
that
because
otherwise,
what
happens?
D
Is
it's
real
hard
for
those
other
languages
to
keep
up
and
stay
in
sync
without
a
model,
because
in
some
cases
they
could
even
crowdsource
and-
and
you
know,
a
whole
bunch
of
the
changes
queue
up
and
they
crowdsource
and
they
get
them
done,
they
get
them
done
in
the
other
languages.
So
that's
something
to
think
about.
If
there's
a
way
to
support
that
or
Nara
I'm.
B
Kind
of
spitballing
here
and
Jared
you'll
have
to
keep
me
on
track
in
case
I
start
to
run
over
time,
but
I
think
an
idea
that
could
work
is
in
the
case
of
like
when
a
pull
request
is
open
and
it's
something
that's
changed
as
opposed
to
something
that's
just
purely
added,
so
not
in
the
case
of
a
doc
ad.
But
it's
a
dog
change
for
a
reason
if
there
were
a
label,
that's
like
you
know
that
had
something
that
indicated
like
this
is
a
change
that
needed
a
change
in
English.
B
F
D
We'll
have
to
see
what
the
other
folks
can
work
with
I'm
a
little
worried
that
you
know
I
mean
this
would
be
great
for
now
and
okay
wrong.
We
can
all
use
the
same
repo
and
have
the
labels,
though,
to
keep
some
sanity
I.
Think
eventually
we're
going
to
need
something
that
that
enables
the
other
languages
to
get
changes
and
be
notified
and
and
be
able
to
update
you
know
as
they
see
fit.
Stevia
me
thoughts.
G
Well,
I
thought
this
was
already
in
place.
I
thought
we
already
had
some
mechanism
for
the
translation
teams
to
pick
up
the
diffs
as
they
happen.
G
G
F
Well,
will
I
have
a
sort
of
related
question?
The
rule
is
you
first,
do
the
changes
or
the
ads
in
English
right?
Is
that
stated
somewhere
because,
let's
say
in
a
hopefully
and
not
so
long
future
we
could
have
a
very
engaged
Spanish
community
and
then
maybe
we
could
end
up
with
a
with
larger
changes
in
a
specific
language.
That's
not
very
visible
in
English.
A
B
So
I
think
something
something
to
consider,
but
I
don't
know
that
it's
necessarily
something
that
that
I
think
it's
one
of
those
like.
Oh
they.
What
are?
They
was
a
delayed
consensus
for
something
anyway.
I.
Don't
think
it's
something's
going
to
matter
to
us
right
now,
but
I
think
it
is.
Some
is
going
to
matter
to
us
soon.
So
it's
something
we
could
keep
on
consideration,
but
I
don't
know
that
it
would
necessarily
like
stymie
any
any
ongoing
internationalization
efforts
at
present.
A
H
A
F
C
A
B
I
mean
for
this
particular
specific
issue.
Yes,
I
would
say
that
that's
definitely
something
that's
ongoing.
This
particular
problem
we
were
attempting
to
solve
is
the
question
of
branching
strategy
like
okay.
Now
that
we
have
a
place
where
all
of
us
are
at
least
managing
the
same
or
similar
docks
in
a
sane
way,
then
we
can
deal
with
the
more
nuanced
pieces
of
how
do
people
get
updated
with
sub
changes?
No
I
think
that's
a
fair
assessment.
I
didn't.
B
It
looks
like
I
am
able
to
enable
this
thing
on
K
website.
I
did
not
know
that
I
had
that
ability.
So
are
there
any
issues
with
that
happening
and
the
only
things
gonna
happen
on
K
website
now.
Is
this
pretty
much
gonna
label?
Everything
is
English,
so
it's
gonna
be
basically
not
useful
until
all
the
other
people
move
in,
but
they're
apparently
undergoing
that
at
the
beginning
of
this
new
release
cycle.
So
in
the
next
two
weeks
have.
A
I
can
give
a
little
bit
of
context
on
since
he
and
I
did
chat
about
it.
Basically,
there's
Zach
wanted
to
come
up
with
like
regular
quarterly
goals:
okay,
ours
kpi's.
What
have
you
as
well
as
yearly
goals
for
the
group
and
have
it
be
like
a
group
discussion,
decide
on
like
what
sort
of
model
we
want
to
use
actually
go
forward
with
it?
We
did
do
a
similar
meeting
after
right.
The
docks
in
Portland
this
year,
but
every
six
months
just
isn't
enough
time,
because
we're
moving
so
quickly.
A
So
he
was
to
get
kicking
this
off.
The
kook
on
Seattle
may
be
having
a
breakout
discussion
for
maybe
a
couple
hours
to
discuss
this
when
our
goals
are
just
coming
up
with,
like
a
higher
level
strategy.
I
think
he
had
some
thoughts
about
the
actual
process,
so
I'm
going
to
leave
that
up
to
him
to
run
and
decide.
So
he
can
hit
on
that
in
the
next
meeting
that
we
have.
H
Certainly
so,
for
those
who
haven't
met
me
before
spoken
aligned,
so
I
look
after
cat
coda,
I'm,
the
founder
of
cat
coda
and
we
power
the
interactive
tutorials,
which
one
the
kubernetes
website,
and
so
these
are
the
ones
which
help
people
get
started
with
kubernetes
faster,
allowing
them
to
experience,
mini
cube
and
deploying
pods
and
max
applications
without
any
concerns
or
risk
or
setting
anything
up
on
their
local
machines.
So,
basically
removing
the
fear
of
what
capabilities
is
and
allowing
them
to
get
talking
about
it
really
quickly.
H
So
I
guess
those
questions
being
raised
about
catch
Khoda
in
the
chat,
so
I'm
kind
of
here
just
answer
those.
If
anyone
does
ever
have
questions
just
ping
me
attach
me
on
the
github
issues
or
ping
me
on
slack
and
I
will
always
jump
in
I,
hang
around
and
watch
from
afar
for
everything
which
is
happening
and
keep
up
today
with
thick
docs,
etc,
so
keen
to
get
involved.
H
D
Yes,
this
all
comes
together,
so
we
have
the
person
with
the
call
and
and
team
I'm
gonna.
Let
them
talk,
they
will
talk
about
adding
a
new
interactive
tutorial.
That
shows
how
you
can
deploy
job
applications
to
kubernetes
and
they
wanted
to
use
caddy
coda
and
make
it
look
like
all
the
other
cool
interactive
tutorials.
We
have
so
with
that
intro.
E
Or,
of
course,
you
know
more
than
open
whether
this
would
be
simply
a
choice
for
them
to
choose
what
container
they
want
to
manage
through
the
interactive
guys
and
have
another
choice
for
an
open
source
java,
runtime
or
the
existing
nodejs
one.
Even
all
the
instructions
could
remain
the
same
outside
of
you
know
they
get
to
choose
which
container
and
of
course
the
container
can
be
structured,
such
that
all
the
curl
commands
would
be
the
same.
It
could
even
be
a
completely
separate
set
of
interactive.
E
D
Well-
and
it
was
more
than
that
right
so
there's
there's
there's
you
know
hey,
we
want
to
show
how
to
do
this
and
and
and
I
mean
interactive
tutorial
for
for
Java
applications,
but
then
there
was
the
concern
that
that
then
Zach
C
isn't
here,
but
the
concern
he
had
was
okay.
Well
where's.
This
thing
hosted
right,
you
know
and
where
do
you
get
the
kind
of
code
from
etc,
etc?
And
so
I
don't
know
Ben
can
help
with
those
questions
or
not.
D
H
Yeah
I
kind
of
with
following
the
discussion
I
know
it's
kind
of
also.
My
initial
question
is:
where
do
they
sit
within
the
overall
kubernetes
documentation
architecture,
because
the
content
which
we
have
at
the
moment
is
kind
of
a
flow?
It
may
be
broken
down
into
six
different
scenarios,
but
it
was
all
kind
of
different
experiences
before
telling
one
story
about
how
do
you
go
from
there
from
deploying
mini
qubit
such
mini
scanning,
out
your
application
and
rolling
out
updates?
And
if
we
started
to
add
segways
into
that,
it
could
add
some
confusion.
H
So
now
we're
I'm
not
sure
if
it
would
fit
I've
a
different
type
like
more
like
a
tutorial
which
just
happens
to
be
interactive.
I
know,
there's
a
longer
form
tutorial
guides
on
there.
Anything
used
to
be
like
with
fatal
applications.
There's
really
do
keeper
deploying
Cassandra
egg
fetcher,
so
maybe
it
fits
I
have
one
of
those
yeah
I'm,
not
sure
I'm,
probably
not
the
best
person
to
answer
that
in
terms
of
actually
making
it
interactive
more
than
happy
to
help.
H
We
can
update
the
content
so
that
they
update
the
environment
so
that
the
java
application
image
is
readily
available,
so
it
would
have
mini
cube.
It
would
have
the
nodejs
samples
that
were
using.
It
could
also
have
Java
PHP,
whatever
we
wanted
to
include.
We
can
just
pre
cast
that
into
that
one
environment,
and
so
it
could
get
repurposed
and
we
used
across
the
website
and
across
different
scenarios
which
being
created.
So
we
can
definitely
do
that
from
our
side
and
the
water.
It's
it's
I,
get
through
the
border
discussion
for
the
someone
else.
D
And
it
doesn't
have
to
be
sort
of
part
of
the
existing
interactive
tutorial,
which
I
think
would
be
confusing.
You've
got
an
existing
tutorial.
Putting
in
a
segue
of
where
you
go
here
here.
I
think
would
be
bad
right,
so
you
offered
the
suggestion.
I
think
this
is
a
separate
tutorial,
but
perhaps
we
can
reuse
some
of
that
infrastructure
to
make
it
happen.
Did
I
interpret
what
you
were
saying
very
correctly:
yeah.
H
Completely
I
think
that
would
be
the
best
way.
That's
just
tutorials
for
those
who
haven't
phenome
they're
markdown
files
which
live
in
a
git
repository,
and
so
we
can
add
additional
scenarios
as
and
when
required,
based
on
the
content,
and
they
can
be
separate
and
completely
isolated
from
the
other
learned,
kubernetes
basics.
So
we
don't
have
to
touch
or
change
those
or
modify
those
to
get
this
to
work.
Instead,
we
can
add
interactive
scenarios
which
talk
to
be
very
distinct
youth
cases.
E
Yeah
I
follow
that
we
can.
We
can
absolutely
do
that
and
that
would
allow
us
to
customize,
not
not
customized,
but
make
the
flow
a
bit
more
unique
to
maybe
some
to
be
more
in
line
with
what
somebody
coming
from
the
role
of
Java
would
be
would
be
interested
in
like
like
using
the
coupe's
to
put
on
a
humanity
and
existing
application,
which
you
know
the
current
flow
doesn't
that
it
doesn't
do
so.
That
could
be
interesting
yet.
D
So
Michael
I
mean
what
it
makes
sense
may
be
to
try
an
offline
work
a
little
with
Ben
and
see
how
this
would
work
as
you
try
and
prototype
this
bull
request
sure
it's
anybody
on
the
call
have
concerns
with
us,
trying
to
add
a
new
and
a
tutorial,
its
interactive.
That
kind
of
handles
a
use
case
that
I
don't
know
if
a
lot
of
people
on
this
call
run
into
a
lot.
But
we
do
know
a
lot
of
folks
that
you
know
that's
their
world.
D
A
Makes
sense
to
me
I
think
from
an
information
architecture
standpoint.
Would
it
be
learned,
kubernetes
basics
with
Java
that
would
fold
under
that
tutorial
or
would
it
be
need
to
have
the
same
fixed
elements
that
you'd
have
it
in
a
different
runtime,
or
would
it
be
an
entirely
different
tutorial
that
you
would
be
building
out.
E
You
know
open
to
suggestions
could
be
separate
if
we
find
that
the
flow
is
drastically
different
from
the
existing
ones,
and
that
would
probably
make
sense.
I
will
happily
go
through
all
of
the
existing
content
and
figure
out
if
it
fits
on.
You
know
in
one
area
more
so
than
the
other.
If
nobody
has
strong
opinions
at
the
moment,.
G
So
it
for
me
it
at
first
glance.
It
looks
like
maybe
this
would
go
under
the
the
more
full-bodied
tutorials
that
are
outside
of
kubernetes
basics
when,
when
I
look
through
our
kubernetes
basic
sets,
I
don't
see
anything
that
it
really
makes
it
a
node.js
thing
versus
a
job,
a
thing.
So
anyway,
that's
that's.
G
My
first
first
thought
on
that,
and
then
the
other
thing
I
wanted
to
mention
is
that
the
people
to
work
with
on
this
or
Cody
Clark,
because
he's
working
on
this
whole
idea
of
getting
more
more
little
interactive
windows
into
our
kubernetes
Doc's
in
general,
and
he's
working
with
the
Andrew
Chen
on
that.
H
Yeah
I'm
already
speaking
to
those
sites
to
dimension
it
so
they're,
basically
for
my
understanding,
looking
at
taking
film
of
the
existing
formats
and
seeing
how
they
can
make
existing
content
and
making
it
more
interactive.
So
I
haven't
some
separate
conversations,
I'm
sure
those
and
updates,
as
and
when
there's
something
to
show
and
from
since
working.
D
A
That
makes
sense
to
me
I
think
I
mean
considering
the
right.
Yes,
thank
you.
I.
Definitely
like
I'm
already
on
like
step
two
of
like
where
we
gonna
fit
this
content
in
and
that
I
didn't
even
say
like
this
content
sounds
great.
You
should
totally
make
it
so
so
I
think
yeah.
Let
me
let
me
make
my
yeah,
but
that
clear
I
think
this
won't
be
a
good
idea.
D
A
That's
so
good
I
think
I
was
just
a
plus-one
in
your
initial
comments
and
like
yes,
it
sounds
great.
We
should
do
it
and
I
think
there's
a
larger
question
of
where
this
fits
in
our
information
architecture,
but
I
think
we're
not
gonna
have
good
answers
that
until
we
see
what
the
prototype
looks
like
so.