►
From YouTube: Kubernetes Community Meeting 20161103
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
No demo; Client-go plan; Releases - 1.4.6 November 11th, 1.5 update, 1.6 planning and goals discussion; Road to Kubecon.
A
Okay,
good
morning,
everyone
good
afternoon
good
evening.
Thank
you
for
joining
us
in
whatever
your
local
time
is
today
is
Thursday
November.
Third,
and
this
is
the
Cooper
ninnies
community
meeting
the
week
before
KU
gone,
so
we
will
see
you
all
or
many
of
you
all
in
person
next
week
and
I
totally
look
forward
to
that.
Anyway,
as
I
mentioned
a
moment
ago,
we
have
no
demo
this
week,
so
we're
going
to
jump
right
into
the
meat
of
the
agenda
and
for
that
I
believe
a
head
up.
A
B
Either,
what
I'm
just
going
to
make
a
short
notice,
I
I,
had
already
said:
I
announce
that
we're
going
to
my
word.
You
use
title:
you
must
week's
community
meet
us.
We
forgot
to
imagine
that
there's
a
condom
from
cause
I'm
challenges
when
when
developers
wants
to
Jared
here,
because
my
greeting
to
think
about
the
huge
PR
and
it
will
be
merged
into
the
master
branch
when
we
unfreeze
the
one,
my
vibrant,
so
Tara,
pic
after
that,
terrific
back
to
the
105
branch
well
experienced
on
friction.
B
So
so,
when
interpret
borrow
your
pear
back,
you
will
need
to
change
from
using
version
object
to
to
use
on
version
2.x.
Our
internal
version
object,
and
there
are
some
other
frictions
like
the
list.
Options
are
different
in
a
person
thi
and
in
Twitter
API,
so
things
like
that,
nothing
too
difficult,
but
I
expected
it
will
require
some
human
moment.
Many
changes
thank.
A
If
they're
going
to
yep,
okay,
so
reach
out
to
chow,
and
then
we
can
make
sure
that
you
know
what
it
is
is
what
are
you
as
you're,
trying
to
putting
the
1.5
cherry-pick
know
what
the
impact
might
be,
and
then
you
can
scope
to
work
on
that
as
well
with
chops,
that's
awesome!
Thank
you.
Are
you
also
a
just
like
that
out
to
affinity,
stove,
yeah.
C
Okay,
awesome:
can
you
just
clarify
exactly
when
the
change
is
going
to
win
the
notes?
Doc
says
it's
going
to
happen
during
the
code
freeze,
but
you've
mentioned
twice
and
out
verbally
that
it's
going
to
be
after
the
freeze
lips.
So
can
we
just
clarify
exactly
when
the
change
will
go
in
and
when
cherry
picks
will
become
complicated
after
after
the
freeze,
lift
it
will
be
merged?
Ask
a
crispier
excellent.
D
I
could
clarify
that,
basically,
what
we're
planning
to
do
is,
during
the
code
freeze
period,
we're
not
going
to
touch
anything
we're
not
going
to.
Let
chose
change
in
we're
just
going
to
have
bug
fixes,
go
in
at
the
end
of
the
code.
Freeze
period
that'll
be
november,
18
we're
going
to
fast
forward
the
1.5
branch
to
pick
up
all
the
changes
that
happen
in
master
during
that
that
code
freeze
period
before
we
unfreeze
we're
going
to
get
a
few
pr's
that
are
really
contentious.
Contentious
in
things
like
Chou's
client
go
code.
D
So
that's
going
to
go
into
master
and
at
that
point
any
further
changes
that
need
to
go
into
1.5
will
require
cherry
pick
and
now,
since
Xiao
Qian
jizz
are
going
to
be
in
master
and
they're
not
going
to
be
in
1.5
the
ariad
after
a
code
freeze
to
when
we
released
1.5,
any
cherry-picks
that
need
to
be
done
will
be
a
little
bit
more
challenging
than
usual.
Okay,.
C
A
Thank
you,
and
maybe
you
to
you
and
sod,
can
work
on
the
language
to
make
sure
that
we
have
a
really
clear
timeline
when
the
email
goes
out.
Thanks.
Thank
you
all
right,
hooray
for
getting
in
the
clay.
You
go
changes,
that's
awesome
and
thank
you
for
the
workshop,
all
right.
That
was
our
first
item
and
then,
as
we've
been
already
speaking
about
releases,
we
are
going
to
continue
in
this
path
because
we
have
a
lot
of
in
parallel
releases
happening.
So
the
one
point
for
point
releases.
A
The
next
one
point
for
point:
release
is
one
point
four
point
six
and
will
be
released
on
November
11th.
So
you
can
reach
out
to
Jessie
about
anything
that
you
think
should
be
part
of
that.
But
that
is
the
plan.
As
it
stands,
a
1.5
release
odd.
Let's
see
we
had
a
couple
of
topics
from
sodden
Caleb
and
then
also
eat
so
who
wants
to
start
first
I.
D
A
feature
complete
date
is
this
Monday,
and
that
does
mean
that
all
your
features
need
to
be
lgtm
would
test
written
and
submitted
in
the
submit
cube
by
6
p.m.
on
monday
code?
Freeze
will
be
in
effect
on
tuesday.
Any
changes
related
to
features
that
need
to
go
in
after
that
date
will
need
to
go
through
the
future
exception
process.
I
sent
out
an
email
earlier
this
week
detailing
and
what
that
looks
like,
so
please
take
a
look
at
that.
It
is
for
extraordinary
cases.
D
D
The
1.5
branch
cut
is
currently
in
progress.
This
is
something
we
wanted
to
get
started
early.
It's
running
into
some
issues
with
the
build
that
we're
working
through
at
the
moment,
hopefully
we'll
have
that
before
the
end
of
the
week
at
some
point
and
then
Chris
on
our
side
is
going
to
help
set
up
the
test
infrastructure
on
the
1.5
branch.
So
we
can
start
getting
a
signal
from
for
the
branch
and
I
think
I'll
hand
it
over
to
Garrett
to
talk
about
the
next
item.
E
Talking
to
Don
and
a
few
others
earlier
this
week
and
there
seems
to
be
some
review
bandwidth
limitations.
So
a
number
of
people
have
a
lot
of
PRS
assigned
to
them
with
the
code
written,
but
they
may
or
may
not
get
a
chance
to
lgtm
by
Tuesday,
which
is
a
little
bit
disconcerting,
but
we
need
to
be
prepared
for
for
how
we're
going
to
handle
that
and
given
that
this
release
pressures
up
so
close
against
the
holiday
I
think
we're
gonna
have
to
stick
with
the
feature.
E
D
So
my
two
cents
on
that
are
that,
let's
remember
that
there
is
going
to
be
a
subsequent
release.
Like
Garrett
mentioned
the
dates
on
this
particular
release
or
where
we're
selected
so
that
we
don't
go
into
the
holidays
right,
we
want
to
make
sure
that
nobody's
working
through
the
holidays
and,
more
importantly,
let's
make
sure
that
the
release
that
we
do
cut
is
stable.
It
goes
out
on
time
and
its
high
quality.
If,
if
you
miss
this
particular
release,
there
will
be
another
one.
So
don't
worry.
A
A
F
A
F
Retargeting
this
monster
on
some
I'm
going
to
double
check
it
and
possibly
kick
off
some.
Some
of
these
features
to
the
next
milestones
I'm
going
to
work
on
that
after
Monday's.
After
the
actual
code
phrase
will
happen,
sriracha
code
appears
that
generated
a
targeting
these
features
and
the
consolidated
spreadsheet
it
collects
information
to
the
endless
features
yeah.
It's
also
main
competence
will
have
for
my
information
after
mounting.
Okay.
A
Thank
you
for
and
remember
that,
so
this
is
our
last
community
meeting
until
after
the
u.s.
thanksgiving
holiday,
because
next
week
is
coop
con,
then
we
have
a
week
of
a
meeting
moratorium,
so
we
can
all
recover
from
khoob
khun
and
get
some
work
done.
Having
lost
a
week,
do
face-to-face
meetings
and
awesomeness
and
then
the
following
thursday
is
thanksgiving
holiday.
So
we
will
all
be
rest
up
like
turkeys
and
doing
turkey
things
yeah.
A
D
G
D
D
D
G
D
A
D
F
C
H
Of
me,
just
a
sort
of
reiterate,
key
horse
requests
from
a
release
notes
perspective.
You
were
mailed
a
question
about
like
what
we
could
do
to
make
the
release
notes
process
better,
and
I
suggested
if
we
frozen
all
the
features
that
all
the
feature
owners
could
conceivably
put
together.
Release
notes
right
now,
which
could
at
least
become
like
the
skeleton
of
a
description
for
what
the
beta
is
supposed
to
look
like.
So
we
know
what
features
we
get
to
go
run
and
play
with,
as
my
understanding
is
like
the
communities.
H
A
A
H
I
A
E
So
the
projects
I've
been
doing
exceptionally
well,
I
just
joined
a
few
months
ago,
but
it
sounds
like
we've
had
six
releases
in
a
year
and
a
half
and
that's
great,
but
that's
also
led
to
a
number
of
issues
in
terms
of
growth.
If
you
look
at
the
cooper
Nettie's,
the
main
repo
right
now,
there
are
4,500
open
issues.
There
are
a
number
of
tests
flakes,
and
so
what
I
was
proposing
is
doing
a
stabilization
release
for
1.6,
where
each
of
the
Stig's
actually
takes
some
time
and
address
their
own
kind
of
technical
debt.
E
J
A
You
and
that's
not
quite
what
we
said.
We
said
each
of
the
cigs
needs
to
look
at
the
work
that
they
have
scheduled
and
the
debt
that
they
have
accumulated
and
make
decisions
about.
Jude
ish
judiciously
make
decisions
that
lean
toward
paying
down
debt
issues,
moving
features
that
have
been
forever
alpha
into
beta
or
forever
beta
into
GA
moving
things
cleanly
forward
without
a
whole
lot
of
new
churn.
Okay,.
J
I
I
would
say:
let's
talk
about
this
like
fanatically
right,
like
our
job,
is
we've
added
a
bunch
of
features,
but
the
number
of
features
that
people
can
actively
take
you
know
use
or
how
healthy
their
cluster
is
is
also
of
importance,
and
so
putting
that
focus
a
little
bit
more
on.
Is
this
making
we've
added
stuff?
Is
it
useful
for
users?
Are
they
able
to
use
it?
That's
some
of
the
fixes
and
bugs
are
the
features
that
we
have
up
there.
Are
they
helping
people?
Can
we
push
them
along?
K
I'd
like
to
call
up
it,
sig
storage,
like
spent
all
15,
improving
tests
and
stuff
and
like
they
rocked
it
I'd
love
to
see
them
be
like
no.
We
paid
our
debt.
We're
gonna,
go
crazy
on
alpha.
If
someone
from
sig
apps
is
like,
let's
introduce
five
new
controller
type
time
be
like
no,
we
have
not
paid
down
our
debt.
We've
got
a
bunch
of
stuff
in
beta,
so
I
think
you
know
we'll
see
what
different.
L
Cigs
think
right
and
I
guess
from
my
standpoint
as
a
person
who
is
helping
to
do
some
of
this
triage
I
think
it's
rather
concerning
that
there's
still
open
issues
that
will
have
a
1.4
release.
Blocker
label
on
it
and
you
know-
are
still
open
as
we're
trying
to
cut
this
1.5
release,
and
there
are
a
lot
of
tests
flakes.
You
know,
associated
with
Federation
that
are
preventing.
L
You
know
us
here
from
building
on
top
of
that,
which
is
also
a
problem,
so
that
gets
to
the
point
of
you
know,
having
more
features
that
are
consumable
by
people
is
a
good
one.
One
of
the
things
I'm
going
to
try
and
do
I'm
working
with
sarah
is
making
sure
that
we
have
a
github
team
associated
with
each
of
the
cigs
Annika.
L
There
are
some
issues
that
have
no
assignees
and
have
been
open
for
basically
a
whole
month
or
even
longer,
I've
just
been
sitting
there
that
we
need
to
get
some
attention
from
from
the
relevant
cigs,
I
guess
suit
to
your
point
yeah.
We
would
definitely
be
pushing
it
to
the
six
to
try
and
balance
feature.
You
know
new
features
against
staples,
stabilizing
existing
features
and
paying
down
actual
technical
debt,
but
I
agree.
It
should
be
like
a
purse,
a
kind
of
process,
but
we
got
to
do
something.
G
This
may
be
a
dumb
question,
but
if
we
considered
ideas
about
feature
flags
and
maybe
masking
off
some
features
that
we
could
make
available
for
testing,
but
not
necessarily
for
general
consumption,
the
short
answer
is
yes:
where
do
you
have
that
in
practice,
alpha
features
are
supposed
to
be
disabled
by
default,
whether
it's
an
alpha
API
or
an
alpha
field,
effectively
specified
as
an
annotation.
All
those
features
are
supposed
to
be
disabled
by
default.
Okay,
thanks.
A
G
If
you
can't
tell
that's
worrying
sign
in
itself
like,
if
you
don't
know
what
issues
are
actually
relevant
here,
sig
or
what
tests
are
and
test
failures
are
relevant
to
your
sig.
If
you
don't
have
test
coverage
on
that,
those
are
good
signals
that
you
should
be
focusing
on
getting
some
toiletry
right.
A
K
A
Right
we
can
please
raise
those.
If
that's,
if
that's
the
case,
we
have
started
this
contributor
experience
working
group
and
try
and
fill
some
of
those
apps,
but
we
know
there's
more,
that
is
unknown,
so
this
is
also,
I
suspect,
going
to
be
a
big
topic
at
the
converted
es
developer
summit
coming
up
next
week
after
coupon.
A
So
please
bring
your
ideas,
your
thoughts
and
we
will
get
those
lists
of
questions
up
to
the
six
before
next
week,
so
that
some
of
the
face-to-face
meetings
might
be
able
to
also
have
some
of
this
conversation
because
face
to
face
is
so
much
higher
bandwidth.
So
my
hope
is
that
you
will
all
have
those
discussions
there
anything
else
on
1.6
release,
planning
and
goals.
We
have
a
timeline
yet
for
1.6,
which.
E
A
C
On
those
same
lines
with
stabilization,
given
it,
we
are
having
sort
of
feature
freeze
next
week
and
then
we
have
december
where
they're
sort
of
low
turn
happening.
I
would
love
if
people
could
take
december
and
start
paying
down
technical
debt
before
we
start
planning
for
the
1.6
released
via
next
year.
So
if
you
can
identify
things
can
be
fixed
things
like
improving
the
build
system,
triaging
issues,
all
that
you
know,
fixing
flaky
tests
like
december,
is
a
great
time
to
do
that
when
there
are
lots,
people
that
are
taking
the
kitchens
awesome.
I
I
was
gonna,
say
one
more
thing
on
this.
There
was
a
discussion
over
last
week
or
two
weeks
ago,
when
the
basil
stuff
came
up
about
there
really
isn't
a
cig
today.
That
quote
unquote
owns
the
build
process,
there's
a
lot
of
overlap
with
some
of
the
existing
cigs
and
I
kind
of
think.
You
know
we're
making
some
pretty
substantial
changes
to
you
know.
Basile
is
a
pretty
big
change
in
a
lot
of
respects.
A
H
They
all
are
responsive
when
necessary,
but
sig
testing
gets
pinged
on
pretty
much
everything
related
to
testing,
and
so
it
can
be
difficult
to
understand.
What's
the
most
impactful,
we're
build
blocking
honestly
and
I
think
that
I
would
love
to
see
more
of
their
attendance,
but
the
reason
that
we
don't
get
as
much
of
their
attention
is
because
they're
fighting
so
many
fires
and
we
can
really
use
a
lot
more
help
collectively.
So,
like
I,
would
reiterate
and
echo
your
request
and
amplify
it
to
like
sort
of
a
larger
team.
H
That's
more
committed
to
this
right
and
honestly
to
me
this
sounds
like
a
repeat
of
about
where
we
were
a
year
ago.
So
if
we
need
two
more
clearly
divided
up
the
line
of
responsibilities,
maybe
that's
a
great
discussion
to
have
I
think
another
one
I'd
love
to
have
next
week
overdue
colonists.
It's
how
we
start
to
transition
ownership
of
testing
and
build
infrastructure
away
from
a
couple
google
engineers
to
the
cloud
native
computing
foundation,
because
you
know
sort
of
led
to
believe
this
is
their
project.
H
I
Know-
and
the
other
part
of
it
that
I
did
want
to
reiterate,
was
we've
had
a
few
very
motivated
people
changing
the
builds
to
make
them
better,
but
we
also
have
had
some
concerns
about.
You
know
how
we
build
and
who
built
and
packages
and
where
those
could
just
go
and
are
we
we're
moving
forward,
but
are
we
cleaning
up
all
the
stuff
we've
left
behind
and
it
is
kind
of
people
making
efforts,
Herculean
efforts
without
a
lot
of
support
structure,
which
is
unsustainable,
he's.
G
A
G
I
mean
my
concern
about
in
their
pros
and
cons
and
I.
You
know
already,
and
it's
sometimes
hard
to
get
people
to
go
to
a
sig
meeting.
If
goes
to
the
issues
discussed
the
Mets
beginning,
you
don't
care
about.
On
the
other
hand,
I
am
concerned
about
critical
mass
yeah,
so
it
may
not
be
like
40
I
think
it
would
be
interesting
to
have
potentially
a
build
and
release
sick,
but
I
don't
know
that
we
have
critical
mass
to
do
so
yeah.
G
I
G
H
I'll,
just
yeah,
I'd
like
to
the
doc,
would
be
helpful,
but
just
to
echo,
like
the
contributor
experience,
working
group
has
probably
been
doing
more.
Improvements
related
to
build
and
release
and
test
and
sick
testing
has
for
quite
a
while
I
think
like.
If
we're
looking
for
a
laundry
list
of
good
ideas
to
do
to
make
the
project
more
stable
and
more
perform
it
over
December
I'm
sure
they
have
a
lot
of
great
ideas.
You
can
look
at.
They.
A
Do
and
we
would
love
more
activity
from
the
broader
community.
It's
been
really
strongly
led
by
a
couple
of
Googlers
and
attended
well,
but
not
necessarily
as
much
I
will
take
this
project
and
run
with
it.
Please
can
you
help
me
kind
of
work
from
the
outside
community,
so
more
of
that
we
can
get
the
more.
We
will
broaden
our
ability
to
move
forward
on
this
all
right.
D
One
thing
I
wanted
to
add
about
technical
debt
bug
fixes
bug
fixes
are
something
that
are
going
to
is
going
to
be
super
critical
during
the
1.5
stabilization
period
and
right
now,
caleb
is
going
through
a
heroic
effort
to
try
to
triage
the
hundreds
of
untriaged
bugs
that's
an
area
that
we
could
use
help
in.
If
anybody
can
help
us
to
triage
that
or
to
help
fix
bugs,
please
please
please
help
we
can't
do
it
alone.
Edgert.
A
For
any
and
all
of
you
who
have
who
don't
have
labeling
privileges,
which
is
a
lot
a
we're
working
on
tooling,
to
fix
that
but
be
feel
free
to
I'm,
going
to
just
open
myself
up
here,
ping
me
and
tell
me
what
labels
to
put
on
things
and
I
will
commit
during
this
really
cycle
to
put
labels
on
things.
It
may
not
be
the
super
fastest
turnaround,
but
when
I'm
King
did
github,
I
usually
do
make
the
github
action
unless
it
sounds
completely
insane,
in
which
case
I
ask
somebody
else.
L
A
A
So
thank
you
for
your
efforts
to
a
make.
Our
community
awesome
be
make
khoob
khun
and
cognitive
con
and
previous
day
and
open
tracing
afternoon
or
whatever
all
of
this
next
week,
great
fun.
We
have
a
bunch
of
special
interest
group
face-to-face
spaces
that
are
happening
awards
been
collecting
those
into
a
spreadsheet
which
is
linked
in
the
stock
and
are
in
this
agenda
doc.
A
If
your
sig
face
to
face
is
not
listed
on
their
sig
leads,
please
put
it
there,
because
that's
not
that
I'm
using
as
the
canonical
what's
going
on
next
week
for
cigs.
If
your
special
interest
root
is,
has
tried
to
schedule
a
face-to-face
and
has
not
found
space.
Call
me
I.
Think
half
the
hotels
in
seattle
now
know
me
my
name
and
I'm,
trying
to
find
groups
for
people
where
we
need
to,
and
the
wow
did.
I
just
opened
myself
up,
but
yes,
ASAP
being
the
key
point.
Thank
you,
Jason.
A
There
is
also
a
little
link
listed
in
here
for
hacks
and
cigs,
so
there
is
going
to
be
a
room
on
Tuesday
and
Wednesday
at
cloud
native
con
coupe
con
Prometheus
day,
the
branding
on
that's
got
to
get
fixed,
there's
going
to
be
a
room
that
has
tables
dedicated
to
topics.
So
many
of
you
have
been
to
us
com
before
it's
kind
of
like
tribe
tables.
Some
of
the
special
interest
groups
are
meeting
there
and
some
of
the
special
interest
groups
are
basically
holding
open
office
hours
for
users.
A
There
I
think
there's
going
to
be
some
meet
the
google
developers
time
this
going
to
happen
there,
because
the
Google
team
wants
to
have
his
face
that
we
can
put
some
of
our
developers.
I
think
the
technical
Oversight
Committee
from
the
cloud
native
compute
foundation
is
going
to
have
a
table
during
that
time.
A
So
if
you
have
a
special
topic
that
you
think
needs
a
little
space
and
once
and
you
want
people
to
know
that
they
can
come
talk
to
you
sign
up
for
time
on
the
hex
and
things
list,
they're
still
there
still
space
and
it
doesn't
have
to
be
multiple
hours
of
blocked
time.
It
can
be
just
a
short
bit
and
you
can
then
publish
it
with
whomever
you
think
should
meet
you
there
and.
A
Hectic
list
is
in
I:
have
it
linked
in
the
community
meeting
agenda?
Fantastic
bob
was
chasing
this
last
week
to
find
out
if
it
was
for
real,
it
is
for
real.
It
just
wasn't
getting
populated
very
quickly,
because
most
of
the
sig
meetings
were
different
than
what
the
heck
sensei's
idea
was
so
hacks
and
saves
is
more
meet
the
public
with
your
half
warrior
signor,
your
topic,
so
it
is
live.
It
is
real.
A
All
of
the
invites
are
out
at
this
point.
If
you
haven't
rsvp'd,
you
will
be
shamed.
If
you
show
up
but
will
probably
sell
at
you,
it
probably
no
guarantees,
but
so
the
invites
are
out.
The
schedule
has
been
posted
and
we
will
have
an
opening
session
for
about
a
half
hour.
That's
going
to
cover
what
we
want
to
get
out
of
this.
A
We
also
that
morning
will
be
giving
out
our
1.4
community
award,
because
we
are
now
almost
delivering
1.5,
so
we
have
a
community
award
that
will
be
given
out
that
Thursday
morning,
based
on
the
1.4
community
retrospective
meeting,
who
is
most
named
as
pivotal,
shall
we
say
in
the
in
the
community
giving
the
release
of
1.4
the
nut
that
held
it
all
together,
so
to
speak?
What
else
I
think
we're
on
to
notice
as
a
most
people
have
questions
about
anything
who
caan
or
coop
week
as
I'm?
Considering
it
these
days.
A
No
questions
I
see
one
question
that
came
to
me
privately
about
nominating
for
dev
summit
day.
Is
there
a
way
to
register?
Not
at
this
point
we
we've
hit
our
cap.
There
was
a
lottery
for
people
that
did
not
get
invites
it
would
be.
It
would
only
be
on
cancellations
at
this
point,
so
I
will
reach
out.
If
we
have
cancellations.