►
From YouTube: Kubernetes SIG Docs 20190312
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 12 March 2019.
https://github.com/kubernetes/website
A
A
B
A
A
F
A
All
right,
let's
move
to,
updates
and
reminders.
Cody
Clark
is
our
PA,
our
there's
our
PR
Wrangler
this
week,
but
please
check
your
assigned
PRS
I
noticed
our
queue
is
getting
a
little
long.
That's
normal!
This
close
to
a
release
having
having
a
whole
bunch
of
Docs
PRS
in
the
queue
close
to
a
release,
is
standard
operating
procedure,
but
please
do
go
on
and
check
PRS
that
you
have
been
assigned
to
specifically
or
have
been
asked
for
review.
A
If
you
are,
if
you're
an
approver
it
just
it
helps
things
go
more
quickly.
We
have
a
Wrangler
to
facilitate
about
to
do
all
of
the
PRS,
but
to
help
make
things
go
more
smoothly
and
it
goes
more
smoothly.
If
we
all
keep
an
eye
on
our
PR
q
we'd
be
nice
to
get
that
back
down
under
a
hundred.
At
least,
let's
see
a
reminder
that
our
quarterly
planning
meeting
for
the
second
quarter
is
on
Thursday
the
28th
from
6
to
9
p.m.
Pacific.
A
G
For
me,
it's
just
interesting
topics:
new
stuff,
that's
coming
out
in
kubernetes
that
that
we
just
feel
like
we
don't
suitably
cover
in
the
docs
I
like
those
types
of
topics,
because
they
help
others,
because
we
make
the
docs
better
and
I.
Think
from
a
writing
perspective.
You
know
that's
kind
of
interesting,
so
you
know
whether
it's
you
know
operate
a
framework
or
whatever
is
coming
to
mind
that
those
are
the
kind
of
topics
that
that
we
want
to
make
sure
that
the
docs
are
really
getting
getting
fresh.
A
Obviously
we'll
go
over
things
like
like
the
goals
that
we
set
at
the
end
of
last
year,
we're
where
we
are
in
the
progress
that
we've
set
for
the
goals
that
we
agreed
on
and
we'll
go
plan
again
for
the
things
that
we
want
to
specifically
cover
things
that
we
want
to
be
things
that
we
would
like
to
say
are
true
at
the
end
of
the
second
quarter.
But
if
there
are
specific
things
that
you
would
like
to
hear
about,
or
talk
about,
just
drop
a
line
to
one
of
the
chairs.
A
H
H
No,
not
in
particular
I
just
care
to
keep
track
of,
what's
going
on
with
Doc's
we're,
quite
frankly,
24
hours
behind
and
updating
the
content
for
the
Windows
documents.
I
was
chatting
with
Jim
online
and
then
in
the
PR
for
our
changes.
The
Bacchus
coming
in
very
good
shape
now
and
I'll
begin
marked
out
wrangling
this
afternoon,
so
the
reviewable
update
is
will
be
here
and
it
will
have
had
lots
of
community
review
already
by
that
point.
So
hopefully,
the
deltas
from
here
will
be
small.
A
B
And
what
I
think
I
also,
could
you
suggest
we're
not
something
like
unpack
and
make
explicit
is
making
sure
that
those
new
features
get
documented
in
a
way
that
accounts
for
updating
older
content,
so
that
the
big
picture
with
the
new
features
in
it
is
always
fresh.
Am
I
over
interpreting
here
or
did
I,
hear
you
trying
to
me,
but
it's
moving
in
that
direction.
G
I
got
a
complete
I
think
that's
the
brilliant
idea
and
I'd
love
to
say.
Yes,
yes,
you
interpreted
it
perfectly
I.
Don't
think
I
thought
fully
about
that
at
that
level
of
detail,
but
I
I
agree
a
thousand
percent,
so
so
in
some
ways,
I'll
go
back
in
time
and
say
yes.
That
was
completely
part
of
my
idea.
Well,
I
just
is.
G
B
You
were
going
in
that
direction
and
part
of
why
I
wanted
to
unpack
it
a
bit
more.
Is
you
know
you
worked
on
what
is
kubernetes,
we
work
recently
and
I.
Think
we've
all
been,
you
know
really
want
to
keep
movement
on,
focusing
on
content,
so
I'll
stop
there
I
think
we've
got
enough
before
making
a
planning,
but
I
think
that
there's
some
willing
to
take
all
the
credit
for
it
Brad.
You
are
definitely
the
inspiration
for
it
well.
Thank
you
good.
G
A
A
If
that
is
a
terrible
idea
and
I
am
just
not
seeing
it,
I
would
love
to
know
if
there
are
better
ways
that
we
can
break
and
parcel
up
the
documentation
for
that
kind
of,
like
style,
guide,
style,
guide,
conformity
and
sake,
review,
I'm,
definitely
open
to
hearing
it.
But
I
would
like
to
move
us
forward
on
content,
review
and
freshness
for
for
the
docs
as
a
whole
and
sort
of
looking
at
it
in
like
that.
That
cig
level
ownership
kind
of
way.
A
B
Think
it
sounds
good.
It
also
sounds
a
bit
to
me
like
we're,
moving
into
like
sort
of
implementation
planning
for
the
principle
of
the
big
picture
stuff
that
Brad
wrote
on
so
so
yeah
but
I
mean
yes,
we
need
to
get
into
more
implementation
details,
but
that's
probably
not
this
meeting
is
probably
not
quite
the
right
place
for
that
I
think
bringing
it
up.
Yes.
Well,
look
I,
think
you've
said
what
you've
said
about.
You
know:
sort
of
the
the
interaction
between
cig,
docks
and
six
that
are
responsible
for
future
areas.
C
A
B
A
B
A
E
A
A
Twelve
nine
fifteen
asked
whether
feature
developers
should
be
using
the
feature
state
short
code
to
describe
feature
progression
in
in
future
releases.
I.
Think
it's
a
great
idea
and
I'd
like
to
see
that
implemented
consistently
across
our
across
our
documentation
set
right.
Now.
It's
really
inconsistent
and
I'd
like
to
see
us
move
towards
conformity,
not
obviously
not
in
114
Jim.
D
I
I
But
they're
not
really
alpha
beta,
graduating
they're,
just
new
to
that
tool.
Your
utility
and
I
ran
into
something
strange
where
we're
trying
to
badges
during
that
one
one
issue
that
came
out
thinking
back
ported
to
one
nine:
whatever
we
couldn't
figure
out
when
Q
ATM
introduced
a
feature
of
Q
a
DM,
but
it
really
wasn't
alpha
beta
or
any
of
the
above
would
be
awesome
to
have
that
dude.
That's.
A
A
H
A
D
Is
that
something
that
we
could
put
in,
like
the
lead?
Github
section
of
a
KK
P
are
kind
of
like
the
exact
same
way,
the
release
notes.
People
do
so
like
they
have
to
explicitly
say,
release
note
none.
You
could
just
say
like
as
another
comment
as
part
of
the
PR.
If
this
involves
a
feature,
this
is
the
shortcode
you
should
use
in
in
the
K
website
repo
or
we
could
make
it
as
part
of
our
PR
template.
A
D
A
F
Wonder
if,
in
general,
if
we
put
together
some
sort
of
checklist
for
PRS,
because
currently
the
the
contribution
guidelines
are
fairly
verbose-
and
my
guess
is
that
most
people
don't
really
read
them
that
thoroughly.
So
we
had
something
a
little
bit
shorter
and
more
succinct.
I,
don't
know
exactly
where
we
put
that.
But
maybe,
if
we
read
had
some
sort
of
checklist
that
might
be
more
digestible
for
people.
F
B
B
Misunderstandings
around
template
tagging,
for
example,
that
have
exit
broken
up
key
are
I
mean
not
the
docs,
but,
and
people
often
have
trouble.
I
mean
I,
think
we're
still
getting
people
like
adding
8:1
heads
to
their
markdown
and
then,
of
course,
their
constraints
places.
Ok,
you
can
also
you
know
various
basic
bits.
B
B
B
A
A
A
Basically,
it's
it's
a
seasonal
program
that
matches
up
like
technical
writing,
interns
with
specific
projects
and
mentors
for
them.
So
it's
basically
it's
a
path
to
training
in
technical
writing
and
contributing
to
open
source
code,
and
it's
specifically
for
open
source
contribution
and
it's
a
it's
a
compensated
internship
and
it
matches
prospective
interns
with
prospective
mentors
and
opportunities
to
contribute
to
open
source
projects.
B
But
at
least
one
person
asked
I
think
some
pretty
salient
questions
about
in
the
sort
of
what
is
the
relationship
between
writers
on
the
one
hand,
and
open-source
projects
on
the
other,
because
it
seems
like
the
initial
announcement
is
finding
those
as
not
overlapping,
Chemical.
Well,
and
so
there's
there's
a
little
bit
of
I
mean
I.
Don't
you
know?
Maybe
the
stuff
is
gonna
get
back
before
the.
B
A
E
I
need
to
run
off
early,
but
I
love
song
in
the
agenda
for
just
a
cubes
scheduler
documentation.
If
anyone
have
you
know,
wants
to
go
and
discuss,
it
further
feel
free
to
reach
out
to
me,
oh
and
also
there's
any
other
small
issues
or
something
like
that
to
get
resolved
I'll
be
around
awesome.
Thank
you.
Judy.
D
I'm
excited
for
this
okay,
so
we
have
a
lot
of
interest.
Well,
I
mean
relatively
a
lot,
I
think
about
13
people's
worth
of
interest,
even
documentation
of
kubernetes
security
and
a
lot
of
them
look
like
contributors
that
I've
never
had
a
pre-existing
relationship
with,
except
for
Jim
and
Jen
and
Steve.
But
that's,
oh
I,
think
that's
kind
of
exciting.
It
seems
like
it.
D
So
if
anyone
has
suggestions
to
me
personally
on
how
to
run
effective
working
groups
for
scheduling
meetings
or
finding
a
way
to
get
a
channel
on
slack
I,
think
that
would
be
terrific.
My
goal
is
to
have
our
first
meeting
to
kind
of
as
gold
and
and
what
I
think
a
task
list
should
look
like
already
written
out,
but
I
wanted
to
get
everyone's
feedback
and
then
proceed
and
actually
make
kubernetes
secure
again
or
at
least
easy
to
understand
how
to
make
secure
and
then
do
that
in
our
documentation.
A
D
Does
anyone
else,
I
guess
I
can
also
publicize
that
you
may
still
join
and
you
may
join
at
any
point
now.
I
admission
is
not
closed
just
because
we
started,
but
I
am
excited
to
get
started
and
I'm
really
excited
that
there
are
a
lot
of
people.
I
haven't
met,
yet
that
are
passionate
about
security.
So
what
are
you
going
to
talk
about?
First?
So
am
I
my
my
first
goal
on
this
list?
Oh
goals
is
basically
to
get
an
assessment
of
I
in
my
in
this
spreadsheet,
and
the
best
I
can
do
well.
D
Because
I
think,
when
you
say
I'd
like
to
secure
kubernetes
kind
of
like
chris
farley
does
on
Saturday
Night
Live.
It's
not
really!
That's
it's
not
just
that
simple
I
mean
it's
your
code
running
in
someone
else's
container
running
on
a
cluster
in
a
cloud
probably,
and
so
that
means
that
there's
a
whole
bunch
of
different
layers
of
security
to
consider
and
I'm
wondering
if
it's
worth
presenting
just
suggestions
and
guidelines.
So
the
big
specific
details
for
the
kubernetes
section,
but
so
Jeff
and
guidelines
of
like
Bulger
cloud,
isn't
secure.
D
B
B
Even
if
it's
at
least
initially
and
who
knows
for
how
long
a
lightweight
framework
that
says,
okay,
we're
going
to
talk
about
all
of
the
gnarly
details,
you
know
so
the
communities
related
security
bits.
But
here
are
all
of
the
other
things
that
you
need
to
take
account
of,
because
just
securing
communities
is
not
going
to
take
care
of
securing
your
deployment
with
a
small
D
ranks.
B
D
B
A
If
we
have
real
people
to
copy
just
saying
what
a
what
I
am
hearing
is
that
that
this
kind
of
overview
of
security
concerns
like
the
that
that
doing
that
kind
of
top-level
overview
of
like
exposing
different
layers
of
security
concerns
and
like
laying
out
the
map
and
saying
where
do
we
go
from
here?
That
sounds
right
like
a
neck,
excellent
place
to
start.
A
B
A
C
I
Quick,
maybe
question
or
comment
on.
You
know
the
overall
audience
for
this
I'm
assuming
operators,
but
at
what
level
of
security
or
technical
expertise
in
kubernetes
and
I
bring
this
up,
because
you
know
we
see
like
the
kubernetes
basics,
using
cata
coda
and
like
the
terminal
browser-based
sessions,
you
know
and
there's
things
that
exist
out
there
in
different
git
repositories
like
coupon
there
and
things
like
that
to
search
for
security
issues.
Is
this
more
like
education,
driven
example,
driven.
D
D
But
basically,
if
someone
is
looking
at
this
information,
they
have
the
following
minimum
requirements
and
essentially
it's
targeted
towards
people
who
have
set
up
a
cluster.
Essentially,
so
they
are
comfortable
with.
They
are
comfortable
with
the
concepts
of
kubernetes
like
I'm,
hoping
I,
don't
have
to
explain
a
pod
of
deployment,
but
I
am
expecting
to
explain
our
vac
pod
security
policy.
Service
accounts
tokens
things
like
that
things
that
are
specific
security
principles
that
exist
as
proper
nouns
inside
of
the
kubernetes
project
and
in
the
security
world
in
general.
D
I
Total
that
makes
sense
and
if
I
could
add
one
thing
if
we
could
potentially
add
where
it
sees
fit
like
some
sort
of
implementable
action
at
the
end
of
all
this
per
page
or
per
article,
you
know
how
do
you
know
your
our
back
is
secure
besides
knowing
of
our
back
or
how
do
you
know,
you
know
the
XYZ
sees
on
your
own
poster.
That's
reading
it.
Well
yeah,
it
sounds
awesome.
Well,
it.
D
Sounds
like
you
volunteered
to
make
tasks
for
people
to
well
validate
their
security?
No,
it's
actually
a
lot
easier
than
you
would
think.
Honestly,
you
could
just
run
that
you
can
make
a
little
app
and
it
just
attempts
to
do
multiple,
different
things
with
the
pod
and
whatever
it
gets
rejected.
You
just
basically
say
this:
is
the
audit
of
what
I
can
and
can't
do?
A
I
A
Work
is
working
with
highly
intelligent,
very
literate
people
and
learning
all
of
you,
cats,
cat
wrangling
shoot.
Oh
man,
that's
right!
So,
let's
move
on
JD
ducked
out
but
again
boosting
signal
if
you're
interested
in
cube,
scheduler
documentation
and
working
with
JD
to
interface,
with
six
scheduling
reach
out
to
him
on
slack
on
github
is
JD
Palomino.
A
J
Took
a
quick
look
at
JD's
issue
there
on
a
scheduler
and
I
didn't
have
time
to
read
it
all
the
way
through,
but
I
didn't
yet
see
any
acknowledgment.
That's
that
cube!
Scheduler
dock
is
auto-generated
so
with,
and
for
anybody
who
works
on
that,
we
just
want
to
make
sure
that
that
that's
understood
that,
if,
if
content
there
is
obsolete
the
place
to
fix
it
is
upstream
in
kubernetes
kubernetes,
so
that
the
generated
dock
has
the
yeah.
D
It
I
totally
might
have
missed
this
too,
and
maybe
Steve
you
can
answer
this
question,
but
is
it?
Is
it
possible
for
us
to
make
some
tooling
slash?
I
might
be
volunteering
for
this,
but
on
making
generated
documentation
a
bit
more
smooth
as
part
of
the
process
of
not
just
releases,
because
that
was
kind
of
a
pain
to
do
all
that
at
once,
but
even
if
there
are
incremental
updates
that
make
it
into
master
and
kubernetes
or
oh
no
way.
J
J
D
J
Yeah,
yeah
and
I
don't
know
what
the
CI
process
is
now
last
time
I
worked
on
it
there
there
had
been
an
umbrella
script.
That
would
run
all
the
you
know,
all
the
different
doc
generators
I
think,
except
for
things
like
API
reference,
but
it
ran
all
the
doc
generators
for
tools
now,
whether
we're
still
using
that
I,
don't
know
I'm
gonna,
add
my
backlog,
I'll
yeah.
K
Anything
more
hey,
I
am
I,
have
a
quick,
quick
question,
so
obviously
I'm
pretty
new,
but
I
just
we're
using
Travis.
Obviously,
two
examples,
checks
and
suchlike,
and
what
I
acknowledge
is
that
everything
works
brilliantly
before
us,
West
Coast
wakes
up
and
then
things
are
very
slow.
Now,
I
already
checked
before,
while
we
are
in
the
core,
with
sig
testing
and
I
understood
the
using
the
free
version
and
it's
not
managed
by
by
them.
So
my
question
is:
is
it?
K
Is
it
may
be
time
to
to
look
and
assess
whether
we
can
move
to
pro
rather
than
Travis,
unless,
obviously
we
all
want
to
kind
of
you
know,
shift
our
time
basically
and
into
it
while
us,
the
west
coast,
is
not
online,
so
to
speak.
Well,
what
was
the?
What
was
your
tool
suggestion
to
move
to?
What
I
suggested
is
using
crowd?