►
From YouTube: Kubernetes 1.13 Release Team Meeting 20181130
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).
A
Okay,
hello,
everybody
welcome
to
almost
our
last,
hopefully,
our
second
last
burndown
for
113
monday
is
still
targeted
to
be
the
release
date.
Everything
looks
green
I'll.
Let
Josh
handle
the
see
a
signal
section,
but
as
of
this
morning,
I'm
not
seeing
any
new
cherry
pick
requests
come
that's
critical,
urgent
and
we're
still
on
track
to
cut
our
C
to
later.
Today,
I
was
targeting
it
for
5:00
p.m.
A
B
B
That'll
be
lots
of
fun
for
Maria
and
others
next
cycle
if
it
doesn't
get
fixed
before
the
holidays,
the,
but
for
the
113
tests
blocking
his
past
sing
with
usual
quick
eNOS,
we
have
a
new
flake
in
the
soap
test
and
the
gke
tests
are
all
still
failing,
but
that's
nothing
new.
So
pretty
much.
What
we've
been
looking
at
for
the
last
week.
A
Especially
the
unmount
one
I'm,
seeing
it
in
places
probably
a
Maria.
A
good
thing
is
to
get
together
with
six
storage,
even
before
one
footing
kicks
off
to
get
an
ETA
on
what?
What?
What
are
the
PRS
are
spending
that
they're
tracking
for
these
and
then
get
an
ETA
on
that,
so
that
you
might
have
a
teener
114
to
begin
with
at
least
yeah.
C
A
And
yeah
you,
the
chronic
flake
spreadsheet,
will
definitely
help
at
least
seen
this
conversation
as
to
which
tests
to
look
at
one
uses
the
HTTP
to
HTTPS,
which
issue
GC
rolled
out
a
fix
yesterday
and
those
things
went
green.
All
the
tests
went
green
as
of
the
last
few
runs,
so
that
was
a
clear
of
GC
issue
and
the
load.
Balancer
affinity
I,
still
see
it.
Flake
yeah.
B
My
V
is
not
on
here
yeah.
You
can
see
the
issue
and
sig
networks
response
about
that.
According
to
them,
it's
a
known
flake
for
that
matter.
Looking
at
it
over
the
length
of
the
history
we
have
whatever
is
a
three
and
a
half
months
that
we
have
it's
not
actually
particularly
more
frequent
than
it
has
been
the
well
no
wait.
No,
that
is
the
one
that
is
more
frequency,
but
they
say
it's
because
we're
running
more
tests
in
the
same
job
and
not
because
any
pigment.
B
B
I
was
looking
more
over
time,
rather
than
which
branch
it's
attached
to.
If
you
follow
me,
yeah
yeah,
and
if
it
is
flaking
more
over
time,
even
in
the
old
branch
it
is,
or
even
in
an
old
branch.
That
would
be
another
argument
for
it
being
a
matter
of
changes
to
the
test
environment
rather
than
changes
to
the
code.
Unless
it's
something
that
went
in
in
a
path
release
but
Signet
work
is
convinced
that
it
doesn't
represent
a
change
to
the
load,
balancer
code,
that
this
is
strictly
a
testing
environment
thing.
B
I
was
wondering
it.
It
sound
like
you've
identified
as
cause
of
leakiness,
which
in
some
text
somewhere
do.
We
have
any
issue
open
to
track
down
and
identify
and
audit
our
tests
for
this
antimatter,
no,
not
yet
in
the
retro,
but
there's
no,
if
you
created
for
it.
Ok,
I'm
gonna
go
ahead
and
make
one
and
there's
definitely
going
to
be
an
ongoing
discussion
at
the
contributor
summit
about
code
health
tests
like
eNOS
and
project
I.
A
Yeah,
the
other
enhancement
P,
are
enhancing
the
just
PR
further
for
one
other
thing
that
was
there
in
the
critical
urgent
that
one
got
moved
out
to
mostly
a
patch
release,
but
I.
Let
him
in
Alexandra
go
through.
They
were
a
bunch
of
PRS
that
are
queued
up
for
the
patch,
so
Jim
I
leave
it
to
you
and
Alexandra
to
decide
when
the
first
patch
release
seems
possible,
given
that
it's
holidays
and
CI
is
also
not
stable
at
this
point
as
much
as
we
wanted
to
be
so,
yes,.
D
Yeah,
obviously,
is
a
concern,
but
we're
thinking
weighing
historical
time
delta
to
the
first
one
plus
Q
Khan
plus
holidays,
and
not
making
a
release
on
a
weekend
if
we
were
to
make
her
release
about
nine
days
after
on
December
12th.
That
would
kind
of
thread.
All
of
those
other
windows,
hopefully
but
see
I
would
be
a
major
question
and
still
there's
I.
B
Along
those
lines
and
I
guess
related
to
it,
Nicko
saying
like
I,
do
see
a
number
of
issues
that
are
open
with
the
V
113
milestone
yeah
many
of
them
are
of
kind
flake,
so
I'm
wondering
from
a
CI
signal
perspective.
If
these
issues
should
now
be
kicked
out
from
this
milestone,
because
they
pertain
to
the
masculine
friendship
only
or
if
they
should
remain
in
the
113
milestone,
because
they
are
pertinent
to
the
113
branch
only.
B
B
F
B
Performance
or
anything
yeah,
but
all
of
the
other
failures
exception
of
any
upgrade
jobs.
B
B
Because
you
know
in
other
cycles,
we
only
have
about
a
week
gap,
so
I
think
one
of
the
things
that
we
want
to
do
that
probably
Maria
and
I
want
to
do
immediately
after
coop
con,
if
not
sooner,
is
in
fact
file
issues
on
all
of
the
master
failures,
because
otherwise
you
know
some
of
them.
Nobody
will
even
look
at
them
until
mid
January,
which
won't
help
things
at
all.
B
A
As
part
of
that,
are
you
also
going
to
be
triaging,
the
ones
that
are
open
in
one
thirteen
and
then
move
it
over
I'm?
Assuming
yes,
right,
yeah.
B
I,
don't
think
we
have
that
many
that
are
1:13
specific
anymore.
The
those
those
have
largely
been
resolved.
A
problem
we'll
be
doing
is
changing
the
tagging
on
some
things,
because
a
lot
of
things
that
we've
tagged
it
was
1:13
as
milestone.
1:13
are
actually
general
flakes
that
affect
all
branches,
since
1:12
yeah.
A
B
I'm
gonna
argue,
though,
that
that
Aaron,
unfortunately,
this
is
effectively
not
a
low
activity
time
as
far
as
CI
signal
is
concerned,
because
we
got
a
bunch
of
PRS
merging
after
we
lifted
code
freeze
and
like
I
said,
some
of
them
will
clearly
destabilize
it
yeah.
No
sorry
I
was
talking
about
like
not
the
post
to
con,
got
it
well.
Okay,
yeah
be
massive
trough
that
we
see
every
year,
yeah.
A
B
G
A
D
B
A
E
I
It's
been
fun,
though,
for
sure
cuz.
This
is
when
you
get
to
interact
with
the
most
other
people,
which
is
always
super
fun,
but
there's
a
few
folks
that
are
very
active
about
tagging,
different
github
issues
and
stuff
that
come
up
that
need
a
known
issue.
Or
what
have
you
so
I
mean
from
a
release
notes
perspective.
If
the
release
was
cut
right
now
there
would
be
formatted
and
release
me
with
it.
I
So
right
now,
it's
kind
of
playing
defense
a
little
bit,
not
defense,
but
like
reacting
to
things
that
come
up
if
a
new
known
issue
pops
up,
hopefully
someone
pings
me
feel
free
to
ping
me
if
anything
like
that
comes
up
and
I'm
happy
to
edit
the
doc
and
usually
just
in
taking
one
run
through
the
whole
doc
the
day
and
trying
to
continue
to
copy
edit
as
much
as
possible
and
yeah.
If
anything
comes
up,
please
let
me
know,
but
so
far
so
good
ready
for
the
release-
and
you
know
always
pleasure.
G
A
And
on
that
note,
if
everything
looks
good,
I
was
planning
on
kind
of
starting
the
release
sometime
unknown.
This
is
like
from
the
discussion
we
had
even
last
retro
I
kind
of
don't
see
a
point
waiting
until
the
end
of
the
day,
so
yeah.
If
that
doesn't
seem
like
a
good
idea,
we'll
meet
a
call
on
Monday
and
cold
chest
in
from
sorry
I
kind
of
figured
hi
I
dropped.
You
from
the
agenda
figured
there
wasn't
much
again,
but
yeah.
F
A
A
Okay,
a
few
quick
things
thanks
to
Kendrick
for
updating
the
enhancements
handbook
yesterday,
which
reminded
me
that
we
should
probably
remind
others
to
do
the
same
so
leads
and
shadows.
Please
take
this
down
time
to
update
your
handbook
so
that
we
can
have
seamless,
handoff
I
plan
to
again
revive.
How
did
we
do
the
release?
Talk,
I
have
a
bunch
of
items
that
I
need
to
put
in
place
and
clean
it
up
a
little
bit
so
I'll
do
that
and
also
the
retro
is
now
still
targeted
for
next
Thursday
in
the
community
meeting.
A
Please
add
your
thoughts,
suggestions,
feedbacks
feedback
there
and
about
the
1:14
shadow
selection
process.
We
kind
of
have
all
the
leads
down
for
114,
Stefan
and
Josh
were
working
together
to
draft
up
a
light
await
sample
question
questionnaire
process
for
shadow
selection.
Josh.
Do
you
have
any
updates
on
this?
If
not
Steven
was
going
to
join
us
on
Monday,
no.
B
A
A
Release
theme,
I,
haven't
forgotten:
I
have
one
almost
ready
to
go:
I'm
still
waiting,
I'm
working
with
the
schwag
folks
to
make
sure
that
this
can
be
converted
into
the
schwag
that
we
have
in
mind.
So
I'll
get
an
answer
by
today
and
if
that
works,
then
Monday
I'm,
I'm
sure
to
announce
the
release
theme,
if
not
I
have
a
backup
thing
that
I
will
announce
on
Monday.