►
From YouTube: Kubernetes 1.14 - Week 10 - Burndown 2019-03-13
Description
B
C
D
A
E
A
Wishes
and
what-have-you
but
good
morning
today
is
March
13
2009
teen
we're
about
a
little
under
two
weeks,
I
think
twelve
days,
I
think
we
are
from
cutting
the
release,
so
you
know
getting
down
to
the
wire
for
sure.
Just
a
reminder.
This
meeting
is
being
recorded
and
thus
you
should
adhere
to
the
kubernetes
code
of
conduct,
which
basically
boils
down
to
don't
be
a
jerk.
So
we've
got
that
out
of
the
way,
let's
go
through
the
normal
kind
of
order
of
operations
of
things
going
through
each
roll.
D
Hi,
okay,
so
not
much
has
changed
on
test
great
since
yesterday,
so
we
at
the
moment,
we
have
two
fails
to
failing
jobs
in
master
blocking,
but
one
of
them
is
due
to
failures
in
time
that
we
had
earlier
today
are
still
failing
in
math
grade
and
one
in
114
blocking.
There
has
been
some
news
on
the
work
resultant,
though
so
I'll
go
into
that
in
a
bit
more
detail.
D
D
D
So
moving
on
to
the
other
failure,
so
the
other
one
is
both
in
master
blogging
and
in
114
blogging
are
the
ingress
jobs
and
those
tie
back
to
GC
load
balancer
timeouts.
They
have
an
open
PR
that
it
has
an
open,
PR,
that's
expected
to
solve
the
problem,
so
we're
just
monitoring
that
to
see
if
it
fixes
all
the
things.
D
D
So
one
thing
that
I
forgot
to
mention
in
in
the
upgrade
stuff
things
that
we're
doing
to
mitigate
the
fail
first
of
all,
try
and
see
if
there's
any
tests
that
other
things
own,
not
cig,
release
owned
ones
that
we
could
look
at
for
CI
signal
and
that
just
helps
reassure
me
a
little
bit
in
case
we
reach
a
week
from
now,
and
we
don't
have.
We
don't
have
this
resolved
results.
Yet
my
last
update
was
that
I
caught
up
with
sig
scalability
I
spoke
with
washtech
I
hope
I
pronounce
his
name
correctly.
D
The
context
for
that
was
that
some
of
the
sig
scalability
jobs
that
we
look
at
as
release
informing,
have
failed
recently
and
fairly
consistently.
So
I
just
wanted
to
see.
If
there's
anything
of
concern
to
them
there,
there
doesn't
seem
to
be
something.
Most
of
them
were
down
to
prowl
issues
or
infrastructure
changes
they
were
trying
out.
D
A
A
D
A
good
question
I
wouldn't
say
that
anything
likes
attention,
particularly
the
thing
that
worries
me.
The
most
is
the
upgrade
tests,
but
that
said,
I
don't
I,
haven't
seen
at
the
moment
something
broken
in
the
behavior
that
the
tests
expect.
If
that
makes
sense.
So
yes,
of
course,
the
tests
are
broken
and
we
need
to
fix
them
and
that's
going
to
be
our
main
focus,
but.
D
In
terms
of
color
I'm
trying
to
ask
myself
the
question,
like
would
I
feel
confident
releasing
something
today,
I
think
kind
of,
but
not
really
so.
I
probably
feel
red
at
the
moment,
or
very
bright
orange.
At
least
that's.
A
Fun
with
me,
I
mean
I'm,
a
huge
fan
of
you
know.
If
you
feel
in
the
middle
and
my
opinion
round
down,
you
know
because
nobody
wins
if
we
keep
rounding
up
and
then
it
comes
to
the
weekday
and
everyone's
like,
but
I
thought
you
were
creating
or
something
you
know.
So
that's
totally
fine
sounds
good
and
it
sounds
like
you
have
a
few
things
that
you're
looking
to
follow,
follow
up
on
with
some
specific
folks.
That
will
make
this
a
lot
better
yeah.
A
A
F
F
Right,
so
we
have
some
good
news
from
bug
triage.
If
we,
if
you
look
down
at
the
rundown
triage
report,
that
Nico
prepared
the
other
day,
something
on
Monday,
most
of
these
I
could
pretty
much
all
of
the
ones
that
are
technically
released.
Blocking
that
are
read
are
closed
or
move
to
115.
The
only
one
that's
outstanding
is
the
standalone
as
their
cloud
provider,
but
since
that's
an
out
of
tree
cloud
provider,
it
shouldn't
affect
the
their
release.
So
we
still
have
a
couple
of
low
priority
issues
on
this
list
to
track
down.
F
I
will
get
some
information
on
that
today.
We
still
have
a
number
of
issues
open,
though
in
our
metric
spreadsheet,
it
looks
like
we
still
have
about
40
issues
open,
so
these
need
to
be
triaged
a
bit
better
and
based
on
that
I'm
going
to
give
us
a
yellow
for
our
color.
We
need
to
spend
a
bit
more
time
going
through
these
non
highlighted
issues
now
and
going
through
the
rest
of
them
and
trying
to
get
that
down
as
much
as
possible.
F
F
F
The
moment
I'm
not
sure
I
need
to
go
through
the
listen
Steve
I
did
reach
out
to
the
signal
yesterday
and
some
of
the
major
issues
and
they
were
very
responsive,
I
think
because
they
realize
that
release
is
coming
up.
So
that
was
very
good.
We
got
a
lot
of
good
traction
from
that.
Sig
and
I
want
to
continue
this
like
momentum
and
try
and
close
as
many
of
these
issues
as
possible.
Sure.
A
Nice,
yes
for
sure
and
feel
free
to
ping
me
directly
or
Ben,
or
you
know
peanuts
and
citizens
or
anything
if
there
is
anything
that
you
need
us
to
weigh
in
on
or
play
back
cop
or
whatever
you
know,
definitely
see,
I
see
you
in
both
triage
or
definitely
what
I
think
we're
focusing
on
most
right
now,
so
we're
trying
to
that.
We
so
for
sure.
You
know
we're
here
to
help,
however,
possible
all
right.
Thank
you.
So
much
precision
awesome,
awesome,
Thank,
You
Nicholas,
as
always.
Next
up
is
her
way
down
here.
Yes,.
G
Yeah,
so
just
a
quick
update,
we
moist
about
21
peers
in
the
last
two
days,
which
seems
good
enough
on
the
slower
side,
because
after
because
they're
in
code
freeze,
so
that's
good
and
the
only
other
update
that
I
had
was
regarding
to
the
CI
signal
cleaners
that
Maria
said
they
might
be
related
to
go
and
drill
and
there's
something
in
the
sink
package
that
might
be
affecting
it
and
from
the
latest.
It
looks
like
there's
a
new
patch
to
go
and
well,
and
the
fix
has
been
ported
to
go.
G
H
G
H
H
H
I
E
J
A
J
J
J
A
Snap
through
this,
but
yeah,
it
seems
like
if
we
can't
get
some
sort
of
confirmation
that
one
that
told
that
one
is
going
to
come
in
like
the
next
five
or
six
days
that
we
might
have
to
go
with
the
issues
that
we've
already
released.
Instead
of
the
new
release
blockers
or
something,
but
we
can
talk
about
it
afterwards,
I
guess:
okay,
cool
it
was
there
anything
else.
We
won't
just
talk
about.
With
regards
to
testing,
sir
no
I
think
that's
okay,
cool.
A
E
E
A
K
K
K
Of
the
green
from
my
side
on
the
next
thing
that
we
will
cut
is
next
Tuesday,
the
first
release
candidate
other
than
that
we
cut
the
bitter
one
yesterday,
all
pretty
much
without
any
issues
except
one.
Super
super
tiny
small
issue
regarding
the
release.
Note
formatting
of
form
in
the
mail
that
has
been
sent
out,
I
opened
an
issue
for
that,
but
it's
just
a
minor
thing:
yeah
any
questions.
A
Thank
you,
Hannes
for
sure.
I
saw
that
release,
notes
issue
as
well
and
yeah
the
many
pros
and
cons
of
using
code
fenced
things
for
anything
really
but
I
awesome.
Thank
you
and
that's
it.
It's
me
now
sweet
updated
courtesy
of
Aaron,
my
beards,
not
nearly
as
robust,
but
I'll
do
my
best
I'm
gonna,
say
read
again
largely
because
even
though
CI
signal
and
buck
triage
seem
to
be
trending
up,
you
know
this
go.
A
112
issue
needs
consideration
as
well,
so
I
think
until
we
get
a
few
of
these
knocked
down,
these
things
will
be
going
well,
but
I
do
want
to
say,
like
you
know,
most
things
I
think
are
wrapping
up
really
nicely
towards
the
end
of
the
release.
So
I
think
we
just
need
to
focus
on
getting
these
last
things
nailed
down
and
make
sure
that
we
can
release
stable
boots,
could
and
I
think
we'll
be
good
were
in
the
homestretch
for
sure.
A
So,
but
you
know
just
so:
we're
vigilant,
I'm,
gonna,
put
down
red
I,
don't
have
anything
else
to
update
y'all
wrong
other
than
the
fact
that,
hopefully
we
can
nail
down
what
we're
gonna
do
with
this
go
issue,
and
then
we
talk
about
that
tomorrow.
There
is
a
meeting
tomorrow
at
I,
guess,
8
a.m.
Pacific
time,
the
United
States
9
a.m.
mountain
time,
11
a.m.
Eastern
Time
and
whatever
time
zone
that
is
other
parts
of
the
world.
Another
burned-down
meeting,
if
possible,
would
be
nice.
A
A
Great
well
like
I,
said
earlier.
If
you
know
the
goal
of
the
release,
we'd
shadow
in
my
opinion,
is
very
much
to
be
kind
of
like
a
utility
person
when
a
lead
has
certain
objectives.
They
need
that
they
can't
be
by
themselves
or
something
the
goal
through
sweet
shadows
to
just
pitch
in
wherever
it
is
needed.
So
towards
the
end.
A
The
release,
if
you
feel
as
though
you
need
assistance
in
order
to
get
something
done,
please
hit
up
me
and
Ben
in
Syd
release
and
weaping
wasn't
happy
to
help,
especially
while
Aaron's
not
doing
so
well,
and
with
that.
Thank
you.
Everyone
for
coming
have
a
great
Wednesday
talk
to
you
on
chat
and
I'll.
See
you
all
tomorrow.