►
From YouTube: Kubernetes 1.14 - Week 9 - Burndown 2019-03-08
Description
A
At
the
thing
today,
with
the
thing
and
going
and
being
social
with
people
and
I'm
celebrating
it
by
sitting
here
in
the
speaker's
lounge
with
you,
oh
I
totally
forgot
to
do
the
doobly-doo
last
time
so
I'm
just
gonna,
say
now
before
I
forget
hi
year.
All
at
the
kubernetes
114
release
team
meeting,
I
guess
it's
burned
out
meeting
today
is
Friday
March,
the
8th
and
you
are
all
being
publicly
recorded
and
will
adhere
to
the
kubernetes
code
of
conduct,
which
basically
boils
down
to
please
don't
be
a
jerk.
A
Let's
see
so
yesterday
was
super
fun.
I
must
have
watched
the
YouTube,
video
and
like
mouth,
along
to
the
lyrics
at
least
three
times.
It
was
pretty
cool
special
thanks
to
Claire
for
helping
sort
of
go
through
yesterday
and
start
to
poke
a
little
bit
harder
at
some
of
the
PRS
that
maybe
don't
make
sense
in
the
content.
A
A
D
A
E
E
E
E
A
E
E
Thank
you.
As
I
said,
there
are
two
new
failures
both
and
there
was
a
massive
logging
once
both
like
others
and
there's
nahban
fear
for
it
and
the
other
one
is
for
ingress
to.
It
seems
from
a
quick
look
that
the
layer,
7
controllers,
do
not
remove.
Rules
within
the
testers
is
expecting
I've
created
the
issue
a
few
hours
ago.
I,
don't
think,
there's
been
any
activity
yet
and
I
also
want
to
just
go
back
to
the
errors
and
see
whether
it's
a
problem
but
I'll
keep
an
eye
on
and
then
for
some
good
news.
E
The
top
flakes
in
terms
of
like
how
I
guess,
how
often
they
flake
are
getting
a
lot
of
attention
already
being
closed.
So
sometimes
it's
storage
and
there's
an
ongoing
one
from
Sigma
network
and
the
next
step
for
us
is
just
to
go.
I
guess
down
the
prayers
and
they
store
things
that
are
played
quite
frequently,
but
not
as
much
as
the
top
ones.
E
That's
part
1
and
part
2
at
the
same
time
just
keep
an
eye
on
the
ones
that
have
been
resolved
for
a
week
or
so
just
so.
We
can
see
that
there
is
that
there
indeed
like
there's,
been
a
significant
difference
in
stability,
but
that's
been
quite
in
person
to
see
the
the
only
one
there
that
has
not
been
market
is
the
one
from
sig
network
on
session.
Infinity
that
doesn't
hold
I.
Think
it's
only
waiting
on
the
milestone.
I
was
going
to
add
it.
E
E
A
Ok,
that
so
I
will.
My
focus
right
now
is
basically
because
I
have
a
history
of
having
done
CI
signal
and
bug
triage
in
the
past
is
to
help
chase
down
these
particular
failures.
So
the
two
continuous
family,
failing
tests,
like
you
said
verify,
looks
like
that's
been
addressed.
We
just
got
to
work
on
getting
that
through
and
the
interest
I'll
go
make
noise
and
then
I
will
go
make
noise
in
a
signal
as
well,
but
I
could
probably
use
help
anybody
else
in
the
Pacific
time
zone
wants
to
help
out
with
the
stuff.
Today.
E
E
A
E
A
E
G
G
Ending
issues
and
be
ours,
there
are
about
thirty
hours
in
total,
all
of
them
are
already
approved,
lgt
em
in
terms
of
yeah
stuff,
coming
up
from
features.
Everything
is
pretty
much
fine,
nothing
is
in
danger
and
the
the
only
thing
in
danger
is
the
CI
lots
of
critical
urgent
bugs
that
needs
thinking
and
Nicolas.
Lane
can
help
with
that.
Today,
I
will
scan
throughout
the
remaining
few
hours
from
Monday
onwards,
to
pick
anything
that
pops
up,
that
is
in
danger,
released
blocking,
etc,
but
other
than
that
everything
else
looks
fine.
H
Yassuh
destined
for
is
looking
pretty
green.
Now
we
merged
about
56
years
yesterday
and
the
code
freeze
was
pretty
successful.
I
didn't
see
any
PRS
without
the
114
Mustang
going.
So
that's
good
prowl
is
fairly
stable.
Now
we
we
are
still
seeing
some
intermittent
github
API
limit
limits,
but
that's
that
will
that's
going
to
need
some
important
soon.
Redesign
improv
there
is
nothing
critical
or
Center,
so
yeah
listen
file
is
looking
good
for
this
release.
A
A
I
Thanks
so
I
have
a
current
status.
Yellow
would
be
more
of
a
yellowish
green,
but
I
wanted
to
stick
with
one,
because
I've
been
going
to
yellowish
green
the
past
couple
times
now,
but
so
we
have
all
the
dachshund,
which
is
good,
the
two
late
ones:
either
the
instances
shifted
off
or
they
got
their
dachshund,
so
right
now
I'm
looking
at
a
new
metric
as
far
as
what
do
we
have
in
draft
versus
ready
for
a
review.
I
The
answer
to
that
is,
we
have
six
in
draft
currently
and
then
that's
out
of
22,
so
roughly
27%
are
still
in
draft.
The
problem
with
tracking
draft
as
a
metrics
is
that
there
could
be
a
vast
difference
between
us,
open
PR,
that's
blank
versus
you
know.
3/4
done
of
a
draft
here
just
need
to
do
some
minor
tweaks.
So
me,
along
with
the
shadows,
are
gonna
work
on.
I
A
J
A
Okay,
so
I
apologize
if
I'm
asking
the
exact
same
question,
I
asked
last
time:
I
feel
like
we've
talked
about
giving
y'all
an
editorial
voice
and
maybe
making
the
release
notes
a
little
more
friendly
to
users,
but
I
feel
like
what
I'm
seeing
here
here
is
a
lot
of
release.
Note
in
the
tract
anyway,
like
a
lot
of
release,
notes
that
call
out
each
of
the
individuals,
sakes
and
I
was
curious.
If
refining
on
changing
how
we're
doing
that
yeah.
J
That's
what
we're
working
on
now,
what
you
see
there
in
the
draft
document
is
kind
of
raw
notes.
We've
started
pulling
some
stuff
and
just
from
like
external
dependencies
and
working
on
that,
but
the
editorial
voice
part
you
should
see
more
of
that
next
week
and
when
we
submit
do
an
update
on
the
PR
to
submit
the
draft
release
notes
those
will
be
in
there.
A
Okay,
that
sounds
good.
I,
don't
have
the
best
memory,
so
I
apologize,
I,
just
kind
of
keep
asking
about
this
until.
A
K
Kaitlyn,
today,
okay,
so
we
have
the
first
draft
of
the
blog
post
that
I've
linked
to
in
here,
which
will
be
finalized
today
for
us
to
send
out
to
review
on
Tuesday.
Just
please
note
that
if
you're
viewing
this
document,
it
is
embargoed
until
the
release
time
on
March
25th,
meaning
this
content
can't
be
used
for,
like
other
blog
posts,
that
you
might
be
pushing
out
otherwise
before
that
date.
K
A
Yeah
this,
this
all
looks
reasonable
to
me,
I
think
I'm,
especially
looking
for
I'm,
not
seeing
Claire
jump
out
the
window
that
these
are
the
features
that
we're
talking
about.
I
think
we
talked
about,
maybe
try
to
find
a
way
to
talk
about
extensibility
as
a
common
theme
some
of
these,
and
that
feels
like
it's
not
a
strong
theme
amongst
some
of
these,
but
we
have
a
couple
things
that
can
speak
to
that.
K
Awesome
and
then
for
the
additional
notable
features
we
have
a
few
called
out
here.
We
can.
These
are
kind
of
just
one
sentence,
overviews
of
just
things
to
note
similar
to
the
release
notes
in
the
sense.
So
if
there's
anything
else,
people
want
to
call
out
here.
We
can
certainly
add
to
this
list
as
well.
K
A
K
And
then
for
the
five
day
series
it'll
be
those
four
features
that
were
leading
with
and
then
the
pod
priority
and
preemption.
The
other
thing
is
we're
not
limited
to
five
blog
posts
here.
So
if
anybody
else
wants
to
participate
in
this-
and
we
can
certainly
expand
it,
but
yeah-
that's
pretty
much
it
any
other
question.
I.
B
A
B
B
A
Yeah
lets
you
and
I
maybe
chat
offline
and
see
if
we
can
find
somebody
who
is
not
super
exhausted
of
writing
long
paragraphs
about
customized,
okay,
I
guess
a
question
I
had
for
you
Caitlyn.
Just
since
you
mentioned
embargo-
and
this
is
a
publicly
recorded
meeting.
I-
can
take
the
liberty
of
like
trimming
this
particular
portion
out.
If
you
want
me
to
I,
have
been
trying
to
not
be
super
specific
about
what
I'm
commenting
on
I
am
totally
open
to
your
distraction,
though
I.
K
M
C
Hello,
everybody!
Well,
we
are
looking
good.
There
is
nothing
really
new,
as
already
mentioned
this
week.
The
next
cut
will
be
next
Tuesday
for
Peter,
2
and
other
than
that.
A
bit
off
topic
for
the
burndown
meeting,
but
still
may
be
interesting.
The
artifact
generation
cap
from
six
year
lie
sorry.
C
cluster
life
cycle
has
been
merged
as
implementable,
and
there
is
the
outer
cap
for
package.
Publishing
I
will
try
to
follow
up
this
next
week
and
hopefully
get
that
much.
A
None
here,
okay,
so
thank
you,
everybody
for
your
updates,
given
everything
that
everybody
has
said,
I'm
feeling,
like
my
status,
is
a
yellow
I'm,
greatly
encouraged
that
we
all
mostly
chose
to
stick
to
the
stoplight
single
color
that
totally
warms
my
heart
and
most
of
huge
shows
green.
That's
also
really
encouraging.
I.
A
Think
the
main
thing
that's
freaking
me
out
is
our
CI
signal
at
the
moment,
because
everything
seems
to
be
flaking,
so
much
I
kind
of
am
sitting
here
having
this
only
vague
ambient
sense
that
we're
fixing
stuff
but
I
actually
can't
tell
if
we're
making
the
situation
better.
Can
I
also
can't
tell
if
we're
allowing
new,
bugs
or
regressions
to
sneak
in
so
I
do
appreciate
that
people
are
working
on
it.
A
That's
why
that's
sort
of
why
I'm
trying
to
continue
to
see
if
we
can
make
the
right
progress
there
I
think
the
big
question
I
had
for
everybody.
We
talked
about
this
I
believe
on
Monday
was
next
week.
Burndown
meetings
are
gonna
happen
every
day,
so
I
expect
every
person
here
to
either
be
at
this
meeting
every
day
or
to
have
a
shadow
at
this
meeting.
A
Every
day
to
give
readouts
similar
to
what
we
just
did
and
we'll
probably
spend
some
time
digging
in
on
a
couple
of
concrete
problems,
because
things
always
come
up,
one
thought
I
had
was
we
have
been
running
a
meeting
on
Tuesday
at
8
a.m.
Pacific,
hoping
that
that
would
be
a
little
better
for
European
contributors.
I'm,
not
sure,
though,
that
that
was
super
actively
attended,
but
we
could
try
to
continue
to
use
that
time
on
Tuesdays
and
Thursdays.
So
we
could
say
that
burndown
is
sort
of
the
Pacific
10:00
a.m.
A
G
A
A
I
E
A
Appreciate
everybody's
flexibility
here,
just
because
of
the
way
the
zoom
recurring
meetings
in
weird
stuff
work,
I
think
we're
gonna
have
to
use
like
a
slightly
different
zoom
link
for
Tuesdays
and
Thursdays,
because
it
is
at
a
different
time.
So
I
will
try
to
set
up
the
calendar
accordingly
and
both
of
the
links
are
called
out
as
such
in
the
dock
and.
N
Threw
one
thing
on
there
down
at
the
very
bottom
anything
not
on
the
agenda.
I
just
noticed
looking
through
test
grid
that
there's
a
oddity
in
scale
and
I
know
last
week
or
the
week
before,
there'd
been
some
scale
issues
and
the
scale
folks
were
looking
at
them.
But
this
one
seems
like
it's
been
an
issue
for
a
couple
weeks,
so
I
just
I
found
the
test
owner
or
I
labeled
that
in
the
issue
labeled
it
critical
urgent.
A
Yes,
thank
you
thank
you
for
pointing
that
out.
So
this
is
actually
something.
I
could
probably
use
some
help
with
from
somebody
in
the
European
timezone,
because
I'm
really
looking
hard
to
the
sig
scaleability
chairs
for
a
go/no-go
decision
on
whether
or
not
we're
still
comfortable
moving
forward
with
go
line
one
to
twelve
or
if
we
feel
like.
Perhaps
the
introduction
of
go
lying
112
has
changed
the
performance
characteristics
of
kubernetes
for
the
worse
and
because
this
job
continues
to
be
read,
it
was
read
before
we
introduced
go
line
112.
A
It's
still
read
now
it's
difficult
for
me
to
understand
if
we've
made
a
clear
decision
on
that,
so
Schama
is
one
of
the
chairs
and
he's
I
believe
in
the
Pacific
time
zones.
So
I
can
try
that
ankle,
but
Wojtek
often
speaks
with
a
little
more
emphasis
and
authority
on
this
sort
of
stuff
and
is,
if
I'm
not
mistaken,
in
Poland,
so
having
somebody
sort
of
reach
out
to
him
and
get
that
dialogue
going
on
Monday.
If
we
find
that
the
situation
is
the
same
on,
Monday
would
be
really
helpful
for
me
Maria.