►
From YouTube: k8s 1.15 Burndown 20190606
Description
See https://github.com/kubernetes/sig-release/tree/master/releases/release-1.15 for more information
A
Cool
welcome
to
June
6th
burned-down
meeting
as
a
reminder
for
everyone.
These
are
being
recorded
and
will
be
posted
to
a
public
youtube.
So
please
observe
the
kubernetes
code
of
conduct,
which
basically
boil
sound.
You
don't
be
a
jerk
and
with
that
I
will
pass
it
over
to
Kendrick
to
give
an
enhancements
update.
No.
B
So
happy
to
finally
be
able
to
say
this
real
green
master
blocking
and
nothing
nothing
that
looks
too
bad
right
now,
115
blocking
say
same
story,
hey
what
was
the
only
thing
master
blocking?
There's
a
g-ghost
Master
serial
job,
a
the
latest
roll
there
were
a
bunch
of
tests
failed,
but
hopefully
that's
gonna,
that's
gonna
result.
It
was
a.
It
doesn't
look
like
an
actual
failure,
and
that
leaves
us
them
with
master
informing,
oh
just
okay,
just
to
keep
it
all
up
today,
with
master
informing
the
bunch
of
failures
in
desperate
they
have
before
sweet.
B
All
of
those
again
are
related
to
the
to
DC
based
test.
So
they're,
not
using
pubic.
You
ATM
to
stand
up
a
coaster
producing
QA
the
cueball,
a
bash
script
from
the
report.
Currently
there
being
two
avenues
of
trying
to
resolve
those
issues,
one
of
them
is
a
rebirth
from
accordion
s15
2
1
3
1,
which
which
was
a
person
a
we've
been
using.
Those
are-
and
that's
so
that's
one
PR,
the
other
one
is
to
actually
him
hey
to
to
actually
keep
the
latest
a
core
DNS
version,
1
5
and
have
a
new
config.
B
B
Besides
that
there
so
new
failures
that
I
mentioned
yesterday
from
a
fun
date
from
sick
scalability,
a
I
was
talking
with
some
folks
from
the
sig
and
their
failure
seems
to
be
related
to
prowl
a
something
is
something
about
we're
starting
pots
way
too
often
and
that's
causing
some
timeouts.
So
nothing
is
operating,
nothing
to
do
with
kubernetes.
They
just
the
testing
procedure,
kind
of
tests,
a
there's,
nothing
wrong
with
them.
I
just
wanted
to
mention
they're,
amazing,
they're,
looking
great
and
the
secret
life
cycle.
B
We
would
test
I
mentioned
those
yesterday
and
after
some
way,
after
a
couple
more
ones,
since
everything
is
okay
in
there.
But
we
we
easy
I
signal
are
going
to
label
them
as
flaky
issues
and
we're
gonna.
Try
we're
gonna
check
in
with
caustic
life
cycle
and
see
whether
there's
anything
that
we
can
do
to
make
it
to
do.
That
is
more
less
flaky
and
differently.
B
A
B
A
Given
the
current
state
of
how
CI
signal
is
looking
like
hypothetically,
if
we
were
to
want
to
release
tomorrow,
not
that
we
are
but
like
hypothetically
speaking
like,
would
you
be
comfortable
with
CI
signal
as
it
is,
or
would
you
want
those
mouth,
the
PRS
for
master
informing
to
be
merged?
First
I.
B
Will
be
comfortable
so
in
place
some
breaker
some,
if
somebody
knows
better,
please
correct
me,
but
must
a
master,
a
master
blocking
should
really
be
blocking.
They
must
must
be
informing
the
issue
with
Cordia
nearest
I.
Guess
that's
a
new
for
some
reason.
It
doesn't
get
resolved
and
we
could've
released
tomorrow.
I
think
that
should
be
something
that
we
should
inform
downstream
users.
B
You
know,
as
we've
been
testing
a
govern
a
day.
We've
been
testing
operates
in
communities
with
accordion
is
version.
1,
3
and
possibly
1/5
is
gonna
resolve
some
issues.
If
you
don't
run
in
with
large
clusters,
but
I,
don't
I,
don't
think
we
should
I,
don't
think
we
shall
consider
that
as
a
strictly
or
a
block
in
the
governor
districts.
A
C
D
D
C
The
main
question
was
whether
yeah,
whether
it
had
to
go
in
for
115
and
it's
a
little
unclear
whether
the
revert
is
gonna
happen.
If
the
revert
happens,
then
this
is
not
needed.
If
we're
okay,
shipping
150
the
current
version
of
core
DNS
with
Cuba,
and
it's
not
used
for
production,
and
we
don't
have
to
care
about
upgrade,
then
this
is
also
not
needed,
but
until
we
resolve
those
two
questions,
we
can't.
A
D
D
D
D
D
A
D
A
D
D
A
E
A
F
F
A
A
C
C
C
A
A
A
A
G
Think
the
other
thing
George
that
we
need
to
consider
is
some
of
those
themes,
may
now
now
be
stale,
given
that
half
of
the
enhancements
have
been
pulled
or
roughly
twenty
of
them.
So
we
need
to
go
back
and
rectify,
what's
actually
in
there
with
the
themes,
because
a
lot
of
the
themes
that
were
provided
by
SIG's
were
based
on
the
notion
that
enhancements
we're
going
to
land
so
yeah.
A
A
H
A
H
H
A
H
It's
it's
just
like
the
announcement
he
hates
kml
files
and
make
the
subject
that
kind
of
stuff
that
you
would
post
to
the
k
announced
Google
Group
like
not
really
too
important
of
a
component
in
the
release,
process
and
and
changelog
is
created
on
the
kuben.
A
repo
site,
I've
managed
to
use
that
in
order
to
post
Kay
announced
Google
Group
yeah
still
digging
into
that,
but
full
update
tomorrow
on
how
got
me
through
okay.
A
Remember
part
yep
put
it
them
in
the
repo
and
like
keep
in
mind,
we
are
getting
very
close
to
the
end
of
our
release
cycle
and
the
sooner
we
have
all
the
leads
lined
up.
The
sooner
we
can
send
out
the
shadow
survey
so
very
helpful
if
we
can
get
that
info.
All
slated
for
the
116
release
lead,
so
they
have
a
team
at
the
end
of
the
cycle
that
they
can
be
confident
about.
A
So
try
to
get
that
done.
Your
secession
plans
and
then
I
think
he
also
has
an
open
repo.
If
anyone
has
feedback
around
the
shadow
survey,
I
don't
have
links
to
either
on
me,
but
I
will
try
to
dig
them
up
and
post
them
into
the
notes
and
then
moving
on
to
my
update,
I'm
gonna
say
we're
yellow,
since
quite
a
few
other
groups
like
bug,
triage
and
comms
definitely
want
to
get
those
sorted
out.
A
A
I
think
my
only
open
calls
for
everyone
are,
as
you
have
feedback
about
the
release.
Please
put
it
in
the
retro
duck
and,
as
a
reminder,
I
think
we're
gonna
try
to
have
our
retro.
The
20
on
June,
20th
and
I
will
I
have
an
action
item
to
figure
out
who
a
good
facilitator
for
that
would
be
so,
hopefully,
I
will
get
somebody
who's
able
to
help
us
during
that
community
meeting.
A
Additionally,
had
one
other
thought
that
I
was
gonna.
Oh
additionally
leads
as
we're
also
nearing
the
end
of
the
cycle.
If
you
haven't
already
start
looking
through
the
handbook
and
making
any
edits
to
the
handbook
that
you
think
would
be
helpful
for
whoever
your
successor
is
any
items
that
maybe
have
changed
over
the
course
of
your
release
or
any
items
that
you'd
think
would
be
helpful
for
your
successor
or
future
successors.
A
To
know
about
also
thinking
that,
for
a
lot
of
shadows,
they
use
these
handbooks
to
kind
of
get
an
idea
of
what
the
role
is
like.
So,
if
you're
seeing
that
possibly
your
handbook
has
a
lot
of
its
lacking
content
around
what
the
shape
of
the
role
actually
looks
like
and
it's
stuff
that
maybe
gets
passed
from
lead
to
shadow
during
that
lead
to
shadow
process.
A
It's
also
possibly
worth
including
just
so
shadows
know
what
they're
signing
up
for
so
update
your
handbooks,
if
as
needed
and
lastly,
just
given,
who
is
able
to
attend,
which
burn
down,
call
we're
gonna
talk
tomorrow
about
dissolving
the
test
and
for
a
role,
there's
an
open
issue
for
it,
and
we
think
we
should
have
the
quorum
of
folks
who
care
about
that.
So
we're
going
to
do
that
during
the
open
discussion
session
and
tomorrow's
burn
down.
A
A
Looking
at
this,
there's
not
a
lot
of
details
in
the
issue
that
give
me
a
lot
of
confidence.
Given
how
close
we
are
to
the
end
of
our
cycle
that
there
might
not
be
issues
by
updating
the
CNI,
especially
as
we're
possibly
trying
to
revert
another
dependency
in
the
release
as
we
to
be
determined.
If
what
happens
with
the
core
DNS
but
I'm
a
little
a
little
concerned.
Given
CI
signal
is
just
starting
to
stabilize.
B
I
think
it's
I
think
it
is
a
big
concern.
I,
remember
CNI,
update
during
the
beginning
of
this
release.
Also
breaking
a
bunch
of
things
and
I
also
don't
have
I
also
don't
have
any
it
was
I
I
also
just
discovered
the
issue
that
Steven
Steven
created
I,
don't
have
any
information
to
say
whether
it
is
safe,
how
safe
or
something
but
I
know
at
least
I
know
that
CA
CNI
upgrades
have
broken
a
bunch
of
things
in
the
past
hey.
We
should
be
really
careful
with
that.
Yeah.
A
Yeah
I'm
leaning
towards
an
O
here,
just
because
or
about
a
week
and
like
a
couple
working
days
out
from
when
we're
actually
releasing,
and
that
does
not
give
me
a
lot
of
confidence
merging
merging
this
unless
there's
a
very,
very
calling
Roslin,
so
I
will
let
Steven
know
and
see.
If
steven
has
a
very
compelling
reason
why
this
must
be
merged
this
late
and
why
it
can't
be
deferred
to
either
a
patch
or
the
next
release.
G
I
think
that's
I
think
that's
the
right
move.
I
think
the
other
thing
to
consider
is
it's
a
minor
release,
not
a
patch
release
within
the
same
version,
so
changing
minor
versions.
It's
probably
not
a
good
time
to
do
it.
I
quickly
jumped
over
and
looked
at
the
release
notes.
You
know
there
as
long
as
my
arm,
so
40.8
and
0.8.1
was
cut
less
than
24
hours
ago.
So
they
would
all
be
things
that
weigh
in
to
support
your
decision.
Claire.