►
From YouTube: Kubernetes 1.13 Release Team Meeting 20181001
Description
A
A
A
A
So
for
those
of
you
who
don't
meet,
don't
know
me
I'm
ice
under
I'm,
going
to
be
your
1:13
release.
Lee
I
have
been
my
day.
Job
I
work
at
Google,
I'm
part
of
the
gke
Cubana
days,
testing
team.
So
a
lot
of
the
awesome
SEC
testing
introvert
that
comes
out
of
suggesting
it's.
Thanks
to
all
my
team
members
here,
I've
been
on
the
release
team
for
about
two
releases.
Now
I
was
the
CI
Li
for
111
and
the
release
shadow
for
112.
B
Everybody
I'm
aaron
kirk
and
Berger
I'm,
currently
on
the
kubernetes
steering
committee,
co-founder
of
kubernetes
sake,
testing
and
actively
involved
in
sick
release
and
say,
contributor
experience
and
sega
architecture.
I've
been
involved
in
kubernetes
releases
since
1.4,
having
felt
the
role
of
release,
notes,
I,
think
see,
I
signal,
I
believe
I
have
either
formally
or
informally
done.
Bug
triage
in
the
past
and
I
work
closely
with
the
folks
in
gke
testing
in
sick
testing
town
push
things
through
so
looking
forward
to
helping
with
this
release,
I
will
now
hand
off
to
you
Kendrick.
A
B
Oh,
that
would
be
why,
okay
all
right
sorry
I
was
just
checking
on
the
list
of
people
in
the
CI
signal
and
I
just
realized.
It
was
not
on
master
branch,
I'm,
Josh,
burkas
I'm
CI
signal
lead
for
this
release,
which
is
super
fun
because
I
should
I
have
swapped.
I
was
released,
lead
for
110
and
she
was
CI
signal
lead.
So
now
we're
going
to
swap
things
and
I'm
CI
signal
lead
and
she's
release,
lead
and
so
I
have
to
say
I
signal,
shadows,
Morton
and
Maria.
Do
you
want
to
introduce
yourselves.
A
D
D
E
G
G
H
I
Yeah,
so
hey
guys,
Mohammed
and
I
have
been
contributing
to
work.
Coco
Coco
gonna
do
for
about
four
five
months.
Now,
six
count.
Every
six
months
now
so
I
initially
signed
off
as
the
shadow
for
I
foresee.
A
signal
for
in
the
wonder,
wonder:
content
cycle
and
I
was
doing
I
had
a
chair
signal,
everyone
in
112
and
now
I'm
shadowing
the
petrache
under
30
from
a
day,
job
I
work
at
Red,
Hat,
so
I'm
software
engineer
there
and
I
work
with
developing
tools
around
open,
shipped
in
communities
to
hunt
developers
get
onto
it.
A
J
Yeah,
sorry
about
that,
my
name
is
not
soondae
I,
walk
on
the
DevOps
engineer
and
I'm
a
money
box
react
team
and
now
I
already
communicated
with
other
team
members
on
our
slack,
so
I'm
really
looking
forward.
So
these
I
walk
out
the
DevOps
engineer
my
day.
Job
for
the
company
and
easting
called
I.
Do
dough
so
I'm
really
looking
forward
to
this,
and
you
know
contributing
what
I
can
welcome.
A
Next
up,
Doug
Doug
couldn't
make
it
to
today's
meeting,
but
Doug
was
are
really
able
branch
manager
who
wrangled
a
lot
of
the
branch
manager,
tasks
last
release
and
he's
continuing
on
to
lead
as
the
branch
manager.
This
release
as
well
super
excited
to
have
his
expertise
on
the
team,
and
his
shadows
were
also
continuing.
Who
kind
of
did
a
lot
of
awesome
work
last
cycle
are
yang
li
and
Hanna's.
L
Folks,
my
name
is
Tim
I'm
do
developer
relations
at
M
lab
we
host
MongoDB
databases
based
in
San
Francisco,
although
I'm
from
Ireland.
Originally
she
recently
yeah
and
really
excited
to
help
out
I
was
shadowing
last
for
dachshund
last
release.
That's
a
really
happy
to
be
helping
a
little
bit
more
this
time.
I,
don't
think
anybody
any
of
the
duck
shadows
are
on
the
call.
Currently
we
have
GM
and
Zack
returning
from
the
last
release
and
we
have
Barney
and
Naomi
joining
us
as
well,
so
really
exciting
cool.
M
I
know
mostly
familiar
faces
here,
but
my
name
is
Mike
I've
been
shadowing
release,
notes
for
the
past
two
releases,
now
I'm
going
to
lead
it
for
this
one
and
yeah
looking
forward
to
it
seems
like
every
release.
We
learn
a
lot
about
the
release,
notes,
process
and
you
know
we've
been
doing
a
good
job
so
far
at
incorporating
what
we've
learned
into
the
following
year
releases.
So
I'm,
looking
forward
to
incorporating
a
few
things
that
we
just
learned
in
112
and
hopefully
making
it
a
smoother
process
for
everyone
involved
for
the
next
release.
M
N
Hey
everyone,
I'm
Caitlin,
Barnard
communications
lead
for
this
release,
which
I
also
did
for
1.12
I.
Also
work
for
CNCs
I,
don't
believe
any
of
my
shadows
around
today,
but
we
have
a
really
great
group.
We
have
more
shadows
this
time
for
comm,
so
I'm
super
excited
and
looking
forward
to
working
with
law
thanks.
A
P
I'm
Tim,
pepper
I
was
the
really
sleeved
on
112
and
I.
Think
so
two
things
to
know
well,
I,
guess,
first
of
all
so
I
work
for
VMware
I,
work
in
open
source
and
I
engineer,
but
I've
gotten
involved
in
kubernetes
around
contributor
experience
of
the
release
team,
because
I
see
these
as
ones
that
are
areas
of
growth
in
the
community
and
meeting
more
people.
So
I've
been
trying
to
help
with
continuity
and
bringing
more
people
into
the
release
team.
P
During
my
tenure
in
112
and
one
aspect
of
the
release
that
I
haven't
been
involved
with,
really
is
the
the
maintenance
the
support
portion.
So
volunteering
in
the
patch
release
manager
role
will
give
me
that
longer
tail
visibility
to
how
things
work
and
and
I
love
the
fact
that
Alexandra's
in
Warsaw,
one
of
the
things
that
I've
been
trying
to
do
is
broaden
the
involvement
across
time
zones
and
then
I
know.
Erin
is
passionate
about
worries
around
how
we
have
a
relief
team
that
starts
up
and
three
months
later,
they
completely
dissolves.
P
So
I
trying
to
I
personally
been
trying
to
stay
involved
and
have
some
continuity
there
and
then
also
the
patch
release.
We've
worried
that
that
becomes
something
that
burdens
people
out
since
they're
responsible
for
something
for
nine
months,
so
just
sort
of
the
general
of
the
looking
at
how
we
make
things
more
sustainable.
Q
Sure
I
think
that's
a
result
of
Kendrick
not
being
here.
I
will
be
enhancements,
shadow
together
with
Arnold
who
I
will
ask
to
speak
up
in
a
minute.
If
he's
on
the
call,
my
name
is
Guinevere
I
am
on
the
Pacific
coast
in
Seattle.
I
was
bug,
triage
lead
for
the
last
release
and
I'm
really
looking
forward
to
getting
a
more
of
an
overview
about
the
enhancements
for
this
release.
Cakes,
better
than
pie.
R
R
S
B
Hey,
oh
mama,
Caleb
Myles
I
worked
for
Google
in
Sunnyvale,
although
I'm
house
in
Berkeley
I've
been
involved
with
the
release
process
for
a
bit
now,
so
I've
got
some
context
for
how
some
of
the
the
parts
fit
together
so
I'm
here.
If
you
all
need
anything
of
course,
yeah
I'll
just
be
a
be
here
lurking
in
the
shadows.
Thanks.
F
A
F
T
U
V
V
A
Thanks,
ok
with
all
the
introductions
out
of
the
way,
I
quickly
want
to
touch
upon
a
few
things.
The
first
up
is
the
schedule
for
113
a
link
backed
off
of
the
minutes
there.
Most
of
you
might
have
seen
this
already.
It's
a
super
short
release
with
just
about
10
weeks.
The
key
dates
have
called
out
there.
The
main
areas
that
have
product
some
concern
is
the
shorter
code
thaw
and
cherry-pick
time
we
have
just
about
48
hours
to
Randall
the
cherry-picks
in
this
time
and
then
the
whole
enhance
planning
and
coding.
A
Time
is
also
crunched
to
about
three
and
a
half
weeks.
So
those
are
the
main
two
things
to
take
from
the
schedule
itself.
So
we
are
looking
at
a
very
tight
release,
which
means
we
need
to
stabilize
things
sooner
in
the
game
and
also
keep
the
enhancements
on
track.
So
I
leave
it
at
that,
but
if
any
of
you
think
this
I
mean
there's
room
for
improvement
in
the
schedule,
please
ping
me
and
then
we
can
work
through
it.
The
next
thing
is
our
weekly
meeting.
A
Right
now,
it's
said
to
be
I
sent
out
a
doodle
couple
of
weeks
back
and
11
a.m.
PST
seem
to
work
for
most
folks
again.
This
is
an
hour
later
than
what
we
are
used
to.
So,
if
any
of
you
feel
that
you
know,
since
you
replied,
this
timeframe
doesn't
work
for
you,
ping
me
offline
and,
if
there's
more
folks
that
if
this
doesn't
work
fault,
we
can
go
back
to
10
a.m.
and
looking
at
all
the
other
time
zones.
A
mainly
because
once
we
get
to
that
that
further
in
the
release
cycle,
I
thought
be
easier
to
have
them
it'd
be
better
to
have
them
early
in
the
day,
which
is
still
reasonable,
work
time
for
folks
in
the
East,
Coast
and
also
in
other
geographical
areas.
So
those
meetings
will
still
be
10:00
a.m.
and
I'm
hoping
we
can
still
get
the
most
critical
mass
there
and
finally,
I
have
a
release
team
contact
sheet
thanks
to
Tim
for
starting
this
in
point.
A
Well,
I
could
just
use
the
template,
so
this
has
the
github
handle
slack
and
some
primary
and
backup
email
ids
of
the
release
team
members.
So
this
is
for
cases
when,
like
the
standard
modes
of
communication
on
down
we've
had
this
happen
a
couple
of,
and
we
still
want
to
reach
out
to
folks.
Please
use
this
at
your
own
discretion
if
you
want
to
schedule
something
with
your
shadows
or
for
any
communication
as
such
feel
free
to
stop
me
anytime.
If
you
have
any
questions
as
I
go
through
the
agenda,
the
next.
A
A
Most
of
most
of
the
time,
the
link
there
kind
of
gives
the
gives
the
template
for
the
github
issue
that
needs
to
be
opened,
and
if
you
list
your
recent
contributions,
you
should
be
able
to
find
sponsors
for
your
case.
If
not,
penny
I
did
check
and
found
that
most
of
the
leads
for
the
release.
Team
are
already
kay
its
members
and
for
the
shadows.
If
you
need
sponsorship,
please
let
us
know
the
next
is
the
milestone
maintenance
privilege
this.
A
Next
up
is
process
talks
thanks
to
everybody
all
the
outgoing
leads
and
others
who've
been
diligently
updating
these
talks
throughout
1:12
and
also
in
the
last
couple
of
weeks.
Mostly
we,
these
dogs
are
now
fairly
up
to
date.
If
not,
there
are
open
issues
to
add
the
last
few
details
that
came
out
of
1:12.
My
request
is
for
all
the
incoming
leads
and
shadows
to.
Please
take
a
look
at
these
dogs
clarify
if
anything,
isn't
clear
or
ask
any
question:
that's
that
seems
out
of
place
there.
A
A
Next
up
is
1/12
retrospective.
We
have
that
schedule
for
the
community
meeting
this
Thursday
generally.
By
now
we
have
done
it,
and
then
we
can
have
some
good
items
that
come
out
of
it
rolled
into
one
thirteen,
but
we
we're
having
it
this
Thursday
and
I
would
look
into
whatever
action
item
that
comes
out
of
it.
A
These
features
go
plant
for
113
as
well
again,
there's
a
link
to
the
enhancement
spreadsheet.
Currently,
we
have
about
24
features
already
in
113
milestone,
and
these
are
mostly
things
that
got
deferred
from
112,
and
apart
from
that,
we
have
about
30
features
that
successfully
went
to
alpha
and
B
John
1:12.
A
We
still
haven't
heard
about
what
their
plans
for
113
are,
but
we
will
just
wait
for
the
owners
to
add
it
to
the
milestone
if
they
plan
to
graduate
it
for
them,
and
we
also
have
about
15
feature
that
were
deferred
from
1:12,
but
they
haven't
been
added
to
1:13,
so
they
have,
they
have
like,
have
the
label
of
track
No,
so
we
again
will
not
be
actively
tracking
these
unless
they've
been
added
to
1:13
by
the
owners
themselves.
Any
questions
on
these
before
I
proceed.
B
I
just
wanted
to
raise
visibility
on
one
feature
that
I
literally
just
filed
in
the
middle
of
this
meeting,
so
it's
probably
not
on
the
spreadsheet
yet,
but
I
am
using
this
release
to
push
forward
dropping
support
for
at
CD
2.
This
is
something
that
was
called
out
earlier.
I
have
links
to
all
the
context
in
that
issue:
I'm,
not
sure
that
this
is
necessarily
a
feature
per
se,
but
I'm
doing
this
thing,
where
I'm
being
paranoid
and
trying
to
raise
as
much
visibility
as
possible.
B
S
Honey
that
that
sounds
good
to
me,
I
just
wanted
to
note
that
since
you're
adding
a
feature
like
that,
I'm
also
adding
an
enhancement
four
which
is
sort
of
a
meta
enhancement
around
the
process,
so
that
is
actually
listed
as
an
enhancement
within
the
features
tracking
right
now
and
I'll
post
the
I
have
a
project
board
up
and
a
tracking
issue
for
it.
You
guys
want
to
see
what
it's,
what
that
process
is
going
to
look
like
yeah.
A
Q
No
I
was
just
wondering
if
we
have
or
should
have
a
cleanup
process,
because
what
Aaron
just
said
sounds
more
like
it
cleanup
and
less
like
a
feature,
but
that
might
just
be
me
in
my
head
trying
to
make
categories
that
don't
exist.
So
I
don't
want
to
create
more
paperwork
for
anyone.
That
was
all
I.
L
A
L
B
F
B
A
Yeah,
when
I
spoke
offline
with
few
folks
from
this
again,
there
was
no
specific
way
we
could
enforce
this
us
call
it
stability
release,
but
then
my
whole
idea
was
to
meeting
with
six
was
to
how
many
alpha
features
they
put
in.
You
know
if
those
features
are
really
needed,
or
can
they
wait
till
114
timeframe,
yeah
I
think
this
is
something
that
has
to
be
good.
Has
that
guy
kinda
evolved
on
its
own
when
sighs,
once
we
start
talking
to
the
different
SIG's
and
seeing
what
they're
planning
for
so.
S
B
I
absolutely
agree:
I
would
love
to
Corral
us
towards
a
process
where
features
kind
of
go
through
a
more
thorough
technical
review
from
cig
architecture
and
that
we
introduce
more
friction
into
the
process.
I'm
not
entirely
sure
that
I'm
advocating
for
that
during
such
a
compressed
schedule,
but
we
are
happy
to
introduce
any
changes
that
cig
architecture
would
like
to
can
like
just
reinforce
at
all
levels.
The
message
that
we
as
a
project
would
like
to
focus
more
on
stability
and
maintainability
and
reliability
kind
of
going
forward.
P
Think
it's
something
that
we
as
a
team
could
do
a
little
Marc,
proactively
or
aggressively
in
this
cycle,
without
bubbling
all
the
way
up
to
the
architecture
level.
If
we
have
a
little
bit
more
of
us
looking
at
the
features
as
they
come
in
to
say,
like
you
know,
this
is
maybe
one
we
we
should
try
and
push
back
on
a
little
more
I
would
like
to
see
us
do
that
a
little,
because
I
saw
this
in
112
as
well
that
we
had
some
things
where
I
was
like
well,
what's
happening
here.
P
B
Like
I
mean
long
longer-term,
right
to
Stevens
Point
I'm,
looking
more
for
checklist
of
objective
metrics
and
whatnot
that
we
can
use
to
get
features
promoting
from
alpha
to
beta
and
data.
The
stable
one
example
would
be
that
beta
features
can't
go
to
stable
until
they
have
tests
that
make
criteria
for
conformance
tests.
So
we
can
prove
that
a
conformance
test
covers
your
stable
feature.
Another
example
might
be
that
you
have
sufficient
test
coverage
that
is
sufficiently
reliable
or
non
flaky,
but
again
the
project
as
a
whole.
B
That
kind
of
is
one
big
broken
window
in
that
regard,
so
we
kind
of
need
to
clean
that
up
before
we
can
start
gating
individual
features.
So
these
are
the
sorts
of
things
I'm.
Thinking
of
a
couple
quarters
from
now,
but
I
just
think
to
Tim's
point
like
us
as
a
team
conceptually
rallying
around
the
same.
We
we
do
have
the
power
to
decide
what
goes
in
this
release
to
some
extent,
but
I
do
think
it
is
definitely
a
collaborative
effort
with
SIG's
just
feel
it's
important
to
message.
A
A
I
just
have
a
couple
of
points
there,
just
a
link
to
the
weekly
report
or
the
spreadsheet
that
you'd
be
tracking
things
on
so
that
way
you
could
also
link
it
to
the
release,
readme
and
then
I
looked
at
master
blocking
and
things
were
surprised,
any
green,
but
yeah
I'll.
Let
you
take
a
stab
at
it
whenever
you're
offering
next
up
is
buck,
triage
Nico?
Who
is
there
anything
you
want
to
add
here
or
we
can.
H
A
So
last,
one
that
I
wanted
to
cover
was
I
was
looking
more
for
suggestion.
/
feedback
from
the
team
itself
about
sending
in
weekly
update
to
the
community.
So
I
was
just
thinking
about
how
short
the
releases
and
to
all
the
points
about
keeping
things
on
track
and
stable
early
on.
If
there
was
one
thing
there
were
that
one
month
ago,
I
thought
that
good
Qaida's
was
over
communicating
through
this
release,
overcoming
eating
the
dates,
the
blockers,
the
testator's
and
everything
towards
this
I
was
thinking.
A
Well,
one
so
I
was
thinking
about
collecting.
If,
if
you
guys,
if
the
release
leads,
would
be
willing
to
add
these
as
a
weekly
report,
every
Monday
which
I
could
collate
and
then
send
out
to
the
community
on
Tuesdays
I'm
open
to
concerns
questions
around
this
I
know
it's
a
little
more
paperwork.
But
given
the
house
shot,
the
breezes
I
thought
this
might
help
us
in
the
long
run.
B
I
guess
I
will
issue
a
concern
that
I
want
to
make
sure
we
make
valuable
use
of
your
use
of
your
valuable
time
and
that
you
not
spread
yourself
too
thin.
Yet
there's
also
a
weekly
update
that
you
give
at
the
community
meeting
on
Thursdays
I
would
strive
to
kill
as
many
birds
with
one
stone
as
you
can
in
that
regard.
Yeah.
A
I
could
also
roll
it
up
into
a
single
update
in
the
community
meeting,
but
but
my
aim
here
was
to
like
send
it
out
in
like
an
email
form,
so
that
folks
can
actually
read
given
given
the
experience.
What
CI,
signaling
111
I
thought
that
got
a
lot
of
traction
when
people
kind
of
saw
something
in
their
inbox
on
a
regular
basis
that
they
could
then
track.
A
P
Thoughts
from
112
I,
like
the
idea
I
thought
I
like
having
a
sort
of
template
structured,
so
the
readers
understand
consistently
what
they're
being
told
in
the
community
meeting
I
think
it's
definitely
valuable
to
give
an
update
there.
I
feel,
like
not
enough
of
the
state.
Leadership,
is
present
consistently
enough
there
to
get
the
message,
but
it's
a
it's
one
avenue
to
give
information
and
then
I'd
also
say
when
I
said
two
separate
emails,
one
to
ke
dev
and
one
to
the
the
cig
leads
list
and
fairly
consistently.
P
I
got
signal
that
the
cig
leads
weren't.
Reading
the
email
but
I
didn't
stop.
Because
of
that,
because
I
think
it's
important
to
as
many
opportunities
that
we're
missing
the
eyeballs
I
feel
like
and
putting
it
out
there
in
multiple
places,
as
it
stands
a
little
bit
better
chance
and
the
the
message
I
did
get
a
number
of
thanks
on
the
messages
to
kata,
where
people
are
we're.
Finding
that
secrets
have
been
so
useful,
so
I
would
say,
keep
it
up,
keep
it
going
and
having
a
structure
to
it,
make
some
sense
for
the
readers.
P
B
We're
gonna
include
the
CI
signal
updates.
I
was
planning
on
actually
doing
a
weekly
one
for
probably
the
first
five
weeks
and
then
after
that,
switching
over
to
daily
or
every
other
day,
as
it
becomes
time
critical
right,
we
get
the
usual
kubernetes
dev
and
discuss
the
I
as
well
as
since
I
actually
have
two
shadows.
We're
also
gonna
try
to
hit
cig
meetings
where
it's
possible.
It
clearly
owns
a
test,
but
only
in
the
second
half
of
the
release
cycle,
because
otherwise
things
are
a
little
bit
slower
pace.
Okay,.
A
P
I've
ping,
on
slack
and
via
direct
e-mail,
to
see
we're
speculating
that
it's
a
national
holiday
week
and
likely
to
be
out
since
he's
in
china,
but
obviously
right
now,
it's
the
middle
of
the
night
to
know
so
I
just
I
said
just
a
ping
to
see
like
hey.
If
you
see
this,
can
you
let
us
know
what
your
plans
are
for
the
region
that
said,
I
was
just
looking
and
I.
Don't
see
open
issues
that
are
screaming
out
for
the
urgency.
W
Yeah
I
can
give
you
a
sense
of
the
urgency
so
right
now,
sono
boy
does
not
work,
so
nobody
doesn't
work
because
we
broke
something
so
I
have
a
PR
in
progress
and
a
cherry
pick
that
will
fix
the
problem
so
so
know
why
the
conformance
to
will
start
working.
So
we
need
to
ship
that
so
people
can
actually
perform
tests
in
their
own
clusters.
P
Makes
sense
yeah
I
mean
if
I
don't
know
how
quickly
we
get.
Adoption
obviously
is
starting
to
run.
Tests
is
a
first
way
of
understanding
if
you
need
to
open
bugs
and
things
like
that,
but
and
then
to
some
extent
there
are
certainly
possible
to
run
any
tests
in
the
conformance
sweet
without
sonobuoys,
so
I
don't
know
like
does
it
say
like
we
need
you
to
patch
in
today
versus
if
it
was
Monday
next
week
it's
considered.
B
The
de
facto
tool
for
any
vendor
to
certify
their
questions,
conformant
for
kubernetes
112,
so
as
much
as
I'd
like
the
I,
am
resolving
this
issue
separately,
where
why
are
they
using
a
tool
that
isn't
itself
part
of
the
project
like
we
were
rying
112
conformance
tests,
but
we
weren't
running
them
inside
the
cluster,
which
is
an
assumption
that
Sanne
boy
makes
so
we're
working
on
like
taking
ownership
of
that
process
and
that
artifact,
but
for
today
it
is
kind
of
an
urgent
thing.
Okay,.