►
From YouTube: Kubernetes 1.13 Release Team Meeting 20181203
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
Release.
113
blocking
is
still
passing
with
a
couple
of
flakes
release.
113
all
has
the
failing
test
that
we
already
knew
about
so
cereal
and
Seok
have
been
failing
for
the
documented
reasons
that
Michelle
figured
out
and
and
the
gke
tests
are
still
family
for
four
reasons
that
we
know
about.
So
everything
else
is
passing
with
approximately
the
same
level
of
flakiness
that
we
had
since,
like
Wednesday
of
last
week,
yeah.
B
Yes,
slow
is
flaking,
but
passing
it's
soaked,
that's
not
passing
okay.
This
is
the
all-cash
food,
so
yeah
yeah.
The
soaked
thing
is
exactly
the
issues
that
we've
documented,
which
honestly
all
seem
to
come
down
to
probably
event
messaging.
Its
entry
volumes,
its
resource
usage,
tracking,
its
max
pods
and
also
resource
usage
tracking.
B
B
So
look
for
messages
for
that,
because,
obviously,
the
sort
of
chronic
level
of
flakiness
in
our
test
jobs
is
becoming
critical
blocker
for
our
ability
to
put
out
kubernetes
and
look
for
that
one.
She
can
find
a
time
slot,
given
that
it's
not
we
didn't
have
anything
scheduled,
it's
gonna
be
a
little
challenging,
but.
A
So,
for
the
record,
are
you
okay
signing
off
on
1:13
for
release
today?
Yes,
right?
Yes,
okay,
anybody
else,
I
personally,
I'm
not
concerned
about
those
flakes,
mainly
because
we
mainly
we've
documented
them,
and
they
are
still
the
same
issues
that
we've
seen
over
this
release.
Anybody
else
has
any
concerns
around
those.
A
C
Slip
y'all.
So,
as
I
was
saying
this
morning,
we
realized
we
didn't,
have
the
external
dependency
sections
and
copied
it
from
1.12
and
then
I
and
a
few
other
people
went
through.
Each
of
them
went
through
the
code
identified.
What
the
version
bumps
were
for
this
release
commented
on
the
doc
I
just
finished,
incorporating
all
of
the
new
updates
into
that
PR.
C
So
it's
ready
for
review
and
merge
ASAP
and
then
the
other
thing
that
came
up
today
was
adding
in
a
release,
note
item
for
the
CBE
that
came
out,
which
Jordan
did
this
morning
as
well
as
a
PR.
That's
ready
for
merge
as
well.
So
if
anyone
wants
to,
if
any
approver
wants
to
slash,
approve
those,
that's
awesome
that
would
be
great,
otherwise
I
think.
D
A
C
The
I
liked
I
trust
the
content
of
them
to
be
pretty
true,
but
if
someone
wants
to
go
and
just
review
and
make
sure
that
it
all
looks,
looks
fine.
That
would
be
awesome
for
sure
I
think
also,
if
anyone
knows
of
new
external
dependencies,
because
we
copied
from
the
previous
release,
we
can
verify
versions
of
the
ones
we
had
previously,
but
that
won't
catch
any
ones.
Yeah.
C
Lossy
process,
it
seems,
like
I,
mean
there's.
Also.
There
were
a
number
of
things
that
were
in
the
1.12
external
dependencies
that
were
just
tybo's
like
in
correct
version
numbers
as
well
as
things
that
weren't
external
dependency
bones,
that
we'll
know
that
I
removed,
but
definitely
will
something
for
the
retro
is
to
try
to
come
up
with
a
less
lossy
way
to
diff
the
dependencies
from
released.
F
Yeah,
especially
since
all
those
most
of
that
information
comes
from
the
CI
a
really.
We
should
have
a
declarative
configuration
from
test
infra
of
what
the
eternal
events
you
saw
there
you
go
well,
yes,
but
it's
yeah.
The
process
is
like
go
look
at
the
output
from
in
in
test
grade.
You
would
hope,
there's
a
wave
on
many
on
the
front
end,
because.
G
F
Maybe
want
to
take
the
lead
on
that.
This
sounds
like
a
clustered
lifecycle
thing
that
you
need
to
specify
all
the
dependencies
your
cluster
is
going
to
check
like
you
think,
to
be
Emma's
kind
of
taking
the
lead
right
on
verifying
cluster
level
and
node
level
dependencies.
So
you
probably
have
more
of
a
formalized
in
spec
than
anybody
else
does
and
then,
in
addition,
I
think
that
specification
of
add
ons
is
also
a
cluster
lifecycle
thing,
although
I
could
be
wrong.
Yeah.
F
G
F
Right
that
that's
fair
thirteen
issues
here
one
is:
we
missed
us
that
staff
in
our
check
lists
to
actually
make
sure
we
have
an
external
dependency
section
and
that
we
vet
it.
But
I'm
saying
the
reason
this
task
is
impossible
because
we
don't
have
a
formal
way
of
declaring
any
of
these.
So
there
isn't
really
a
list
for
us
to
go.
Look
at
and
I
think
cluster
life
cycles
made
more
of
a
I.
Think
the
determining
what
that
manifest.
F
A
C
E
Ya,
don't
really
have
much
of
an
update
for
Justin
everything
looks
good.
The
queue
is
pretty
much
totally
empty,
I
think
there's
one
PR
in
it
right
now.
I
did
notice
that
there
is
a
bunch
of
PRS
to
the
release
111
branch,
but
that
shouldn't
think
this
not
Ivan
looked
up
with
those
few
hours.
Are
you,
okay,.
E
A
D
It's
definitely
on
the
greener
side
of
things,
just
finishing
up
some
dock
gemstones.
It's
not
ready
to
go
right
now,
but
hopefully
should
should
be
ready
in
the
next
few
hours
and
I'll
send
out
a
net
fight
preview,
the
slack
channel.
So
everybody
can
maybe
take
a
look
and
just
make
sure
everything's
cool
before
it
goes
out.
Okay,.
A
Maybe
this
is
a
good
time
to
go
and
discuss
the
line
of
things
for
today
and
any
of
you,
if
you
think
the
timeline
mentioned
there
against
each
item,
doesn't
seem
possible
or
is
too
aggressive.
Let
me
know
when
we
can
move
it
or
change
it
accordingly,
so
I
will
go
ahead
and
start
a
slack
channel
posters
specifically
with
leads
relevant
for
today's
tasks.
H
A
C
A
A
And
then
the
publishing
I
put
it
about
an
hour
after
seeing
the
trains
commish
and
then
I'll
sue
me
from
Google
agreed
to
build
the
Jets
and
our
teams
for
us
so
I'm
estimating
that
to
be
around
3
p.m.
and
then
jogs
and
then
would
be
publishing
the
talks.
Tim
just
3
p.m.
sound
possible.
Given
your
the
pending
items
on
your
list
right
now,
yeah.
A
Is
very
doable
okay
and
that
would
of
course,
if
we
have
any
feedback
when
you
preview,
then
we
can
go
and
address
that
I'm.
Assuming
this
one
has
to
wait
for
the
depths
and
rpms
to
be
built
out
right
or
can
we
go
along
with
it?
I
know
it
doesn't
matter,
but
then
I
just
want
to
know
what
how
we've
done
this
in
the
past.
A
A
Anyway,
we
hopefully
will
be
earlier
in
the
day
so
and
then
Caitlin
I
wanted
your
approval.
If
a
3
p.m.
release,
if
we
get
there
is
still
ok,
this
is
the
first
time
yeah.
That's
great!
Ok
and
oh
yeah
that'll,
be
when
we
published
a
blog
post
and
get
things
going
and
I'm
hopeful
I'm,
hoping
that
everything
will
wrap
up
by
4
p.m.
ish,
if
not
slightly
earlier,
and
that's
when
I'll
go
ahead
and
announce
the
release.
A
I
A
A
H
A
H
A
In
the
dogs,
okay,
cool,
so
angel
numbers
are
basically
numbers
with
like
repeating
patterns,
the
most
infamous
one
being
666,
and
so
all
of
our
releases
are,
of
course,
angel
numbers
because
of
the
repeating
ones,
but
I
found
this
specific
number
one
one
time
event,
mainly
because
of
a
couple
of
things.
A
this
number
signifies
new
beginnings
me
in
end
of
a
chapter
opening
of
a
new
chapter.
A
So
this
being
the
year-end
release,
it's
they
are
bringing
us
and
closing
out
we're
and
opening
us
to
new
processes
and
releases
next
year,
and
also
because
from
what
I've
seen
my
minimal
experience
in
the
release
of
last
three
cycles,
we
grown
and
come
a
long
way.
Be
it
early.
Ci
signal
responses
in
triage
change.
Shortening
the
code
freeze,
move
around
decoupling,
the
branch
manager,
responsibilities
out
of
Google
or
merge
with
child,
and
all
of
this
we've
done
a
whole
bunch
of
things
and
and
looking
at
20:19.
A
It
seems
that
cig
release
and
the
release
team
is
said
to
evolve
and
mature
to
scale
up
to
growing
humanity's
challenges
and
growing
humanity's
customer
base
itself.
All
our
new
patch
manager
initiatives,
that's
going
in,
are
exploring
LTS
or
also
exploding
feature
branches
to
make
our
releases
stable.
So
it
looks
like
we
will
have
a
bunch
of
fighting
things
coming
out
in
2019
and
that
that
is
something
that
I
look
forward
to.
A
So
that's
why
this
releases
they
won
one
three
angel
release
signifying
new
beginnings
and
transformations,
so
texture,
sorry
about
the
long
justification,
slash
right
yeah.
Hopefully
this
fits
into
the
leash
wag.
Unfortunately,
I
can't
get
it
in
time
for
cube
con,
but
there
are
more
cubed
cons
if
not
I'll
mail
it
out
to
all
of
you.
A
That
said,
setup
I'll
more
to
the
announcements
really
quickly.
The
retro
is
still
on
track
for
Thursday
at
the
10:00
a.m.
community
meeting.
There
have
been
a
lot
of
good
discussions
over
the
release
cycle.
Please
add
your
comments
and
feedbacks
with
retro.
We
will
make
sure
this
gets
folded
in
us,
which
is
possible
to
114.
A
The
next
big
announcement
is
frequency.
Adam
I
listed
a
bunch
of
sessions
there,
which
is
relevant
to
cig
release,
Tim
and
I
plan
to
do
cig
release
intro,
which
is
on
Tuesday
at
1:45
and
Josh
and
Chuck
will
be
doing
the
release.
Teatime
that's
on
Wednesday
and
then,
of
course,
Maria
will
be
organized
saying
a
chesty
flaking
session
Maria
when
you
have
that
finalized.
Please
drop
in
the
time
in
here,
and
apart
from
that
couple
of
fun
events.
As
we
discussed
on
Friday,
we
are
planning
for
a
release
team
lunch
on
Thursday.
A
This
will
be
at
the
events
center,
so
all
of
us
can
quickly
get
together
and
we
are
also
planning
for
a
social.
Sometime
later
that
evening,
we
decided
on
an
earlier
time,
slot
6:00
to
7:30,
so
that
folks
can
go
to
other
socials,
as
you
might
have,
please
expect
to
see
a
calendar
invite
only
for
both
of
things
by
end
of
day
today,
any
other
Co
concessions.
The
folks
want
to
call
out.
F
A
F
So
one
one
mention
about
cube
con
we're
having
pep
talks
and
say
p.m.
intro
and
deep
dive.
So
if
you
guys
want
to
show
up
to
that
and
drop
your
feedback,
that'd
be
cool
too
so
yeah.
So
the
shadow
selection
process,
we're
working
on
Josh,
put
together
lots
of
great
questions
around
how
to
choose
a
shadow,
whether
or
not
they'll
bill
all
and
time
zones
and
all
these
different
different
parameters.
Consider
so
what
I'm
working
on
right
now
is
essentially
turning
turning
a
lot
of
those
questions
into
a
survey.
F
F
So
the
fear
will
be
it's
I
I,
don't
want
to
say
lock-in
per
se,
but
it
will
be
the
initial
version
of
the
questionnaire
for
you
free
to
edit
and
as
need,
be,
and
then
we'll
roll
that
back
into
the
world.
That
back
into
the
survey
is
necessary.
It'll
also
include
some
updated
information
on
beliefs,
team
selection,
overall.
B
F
A
F
A
Cool
yeah,
if
you
could
link
to
the
PR
yeah,
we
can
get
the
consensus
going
there.
Yeah
thanks
Steven
yep
any
questions
for
Steven.
A
Okay,
that's
it
with
that.
We
are
through
with
our
agenda
I'd
really
like
to
thank
all
of
you.
Thank
you.
Thank
you
from
the
bottom
of
my
heart
for
all
your
hard
work,
support
and
passion
for
getting
130
now,
I
know
I've
leaned
in
and
in
in
so
many
of
you
right
in
the
release
team
and
outside
of
the
release
team
throughout
this
cycle,
and
it
was
an
honor
to
be
the
release
lead
for
the
cycle.