►
From YouTube: Kubernetes 1.14 - Week 10 - Burndown - 2019-03-12
Description
C
C
C
C
C
C
C
D
D
D
D
D
D
What
I
want
to
do
is
basically
I
think
we
have
a
pretty
decent,
representing
that
the
roles
here
from
what
I
can
tell
so
I
want
to
just
go
through
each
role,
quickly
and
kind
of
just
enumerate
what
what
has
changed
since
yesterday
and
what
kind
of
you
know
if
your
status
was
yellow
yesterday?
What
did
you
do
yesterday
to
kind
of
like
make
it
a
little
less
yellow
today
did
anything
go
wrong
yesterday.
D
E
So
no
change
in
number
of
enhancements
since
yesterday,
I
did
go
through
the
sheet
this
morning
to
see
for
all
the
issues
that
were
marked
and
left
out
recipe
has
they
had
open
PRS
all
the
three
of
those
have
had
their
PRS
merged
since
last
Friday.
Those
last
three
PRS
are
for
end-to-end
tests,
but
no
real
changes
on
the
enhancements.
Friends
right.
F
Not
too
bad
thanks
again,
not
too
much.
It
has
changed
since
yesterday.
The
main
the
main
things
that
we're
looking
at
is
that
we're
like
fairly
stable.
All
things
considered,
we
haven't
had
any
new
failures,
we're
working
down
flakes
in
order
of
impact
in
a
way,
so
we've
started
with
the
ones
that
have
a
cube
have
been
occurring,
the
highest
with
highest
frequency
and
working
your
way
down
to
lowest
frequency,
we're
seeing
quite
a
bit
of
change.
F
There
are
two
issues
that
are
open:
one
is
around
load,
balancer
timeouts,
which
is
causing
the
ingress
tests
to
fail,
both
in
the
blocking
dashboard
and
in
the
one
sorry,
the
master,
blocking
and
in
the
114
blocking
dashboard,
and
then
the
resource
usage
performance
test,
which
is
from
what
I
can
tell
I,
said
that
yesterday
I
think
it's
were
saying
more
hints
to
that.
It's
flaking
quite
heavily
passes
every
once
every
maybe
five
times
so
I
will
attend
sick
nodes,
catch-up
this
in
a
couple
of
hours,
I,
believe
and
see.
F
If
this
is
something
that
they
are
concerned
about
as
well,
it
is
something
we
could
get
fixed
or
I.
Guess
what
are
the
next
steps
for
this
one,
but
once
these
two
clear
out
nothing
we're
in
a
fairly
good
state
for
this
release.
It's
just
a
bit
hard
for
me
to
get
from
red
to
yellow
at
the
moment,
because
with
time
outs
and
failures,
it's
hard
to
know
if
there's
something
else,
that's
being
hidden,
so
I
feel
a
bit
red
for
now
sure.
D
G
Hello,
everyone
doing
great
so
couple
of
things
that
we
actually
need
to
make
some
decisions
on
are
some
of
the
items
are
still
blocked
and
we're
not
sure
what
to
do
with
them.
So
we
had
the
dynamic
configured
switching
to
beta,
there's
still
a
couple
of
PRS
that
have
been
put
on
hold
by
allegation
by
also
Erin.
So
we're
not
sure.
What's
this,
you
know
with
the
decision
on
these:
are
the
canopy
dropped
from
the
milestone
or
not,
yet
one
of
them
has
been
rebased
already.
G
G
There
is.
There
is
also
another
issue
that
Liggett
is
handling
which
is
related
to
fraud.
Above
there
doesn't
update
some
stale
features.
It
is
also
still
not
resolved
and
we're
not
sure
if
it's
gonna
be
resolved
in
time,
the
third
one
that
is
also
still
what
not
really
sure
about
it.
Also
is
it
gonna
be
released
with
with
114
or
not,
which
is
related
to
to
Azure
cloud
provider,
which
is
an
out
of
three
provider,
but
it's
also
planned
to
be
released
with
114
and
it's
still
not
resolved,
but
it
might
be
delayed.
G
Also,
so
that's
one
thing
to
take
note
of
the
the
last
two
things
are:
there
is
a,
but
with
cute
proxy
it
I
think
organ
is
working
on
it,
but
also
it's
still.
We
still
need
confirmation
if
it's
gonna
be
done
in
time
for
this
release.
I
think
there
was
an
issue
with
some
of
the
tests
and
that's
holding
this
one
too.
D
D
So
I
mean
it
doesn't
even
seem
like
it's
a
matter
of
like.
Are
we
gonna
be
mean
and
kick
it
out?
It
seems
like
it's.
A
matter
of
this
doesn't
seem
like
it's
gonna
land
like
let's
just
get
it
out
of
the
milestone
in
the
reassess
when
it's
gonna
be
delivered
or
something
but
I'm
sure,
if,
like
the
people
who
are
working
on
it
have
some
other
opinion
of
it.
But
it
looks
pretty
far
off
to
me.
Yes,.
G
D
D
G
D
I
feel
like
we
should
leave
it
in
the
milestone
until
people
either
come
to
a
conclusion
that
it's
like
not
reproducible
and
like
will
close
the
issue,
because
not
reproducible
or
until
it
gets
fixed
or
until
we
know
that
like
a
good
issue.
But
it
doesn't
need
a
fix
and
we'll
move
it
to
the
next
milestone.
But
we
should
definitely
come
to
some
like
conclusive
conclusion
on
what
the
state
of
the
issue
is.
G
G
D
G
So,
as
Tim
says
in
the
issue
there
wasn't,
there
is
an
older
issue
in
the
1.8
release
that
started
this
whole
discussion,
and
this
was
to
be
a
continuation
of
that
it
I
don't
think
that
is
something
and
we
can
achieve
in
a
short
time.
To
be
honest,
it's
very
significant
and
require
a
lot
of
effort
and
I'm,
not
sure
if
there
is
still
like
there
are
PRS
for
a
lot
of
things
to
go
and
to
use
disturbance,
especially
for
out
of
tree
stuff,
but
also
that
such
one
we
need
to
decide.
D
Yeah
yeah
I,
don't
think
this
is
I
mean
this
tree
only
I
just
finished
reading
the
comments
and
I
just
saw
a
mixed
comment
on
it
at
the
end
and
I
agree
like
I.
Well,
let's
see
if,
let's
see
what
kind
of
response
we
get,
some
mixed
comment
and
I
think
I
agree
with
the
sentiment
like
I
think
this
is
great
but
like
when
we
want
to
do
stuff
for
114.
We
don't
just
like
slash,
milestone,
114
and
say:
let's
get
it
done
like
we
have
to
like
articulate
some
kept
for
it.
D
G
D
C
Here
everyone,
this
should
be
pretty
quick.
We
have
passed
our
ducks
deadline
for
Monday
to
have
everything
be
on
draft
into
a
ready
to
review
form.
We
still
have
the
two
outstanding
draft
mode:
Docs
left,
one
being
Windows,
one
being
server
side
apply,
been
in
constant
communication
and
putting
us
at
a
yellow
status
right
now.
C
I,
don't
fear
that
anything
is
at
risk
at
the
moment,
as
long
as
I'm
still
talking
everybody,
everything
seems
good
and
then
plan
I,
workout
today
or
I-
guess
this
upcoming
week
with
the
shadows
on
getting
everything
ready
to
go,
approve,
merge
and
to
the
dev
114
branch
ready
to
drop
for
the
release,
because
the
next
deadline
is
Monday
March
18th
to
have
everything
merge
into
that
dev
114
branch.
So
so
far,
all
good
thanks.
I
D
A
D
We
have
to
make
decisions
on
and
I
want
to
make
sure
that
we
are
that's
represented
and
in
there
we're
making
progress
on
that.
So
if
there
are
any
other
Reds
throughout
the
rest
of
the
group
that
I
feel
like
the
release,
lead
should
be
read
to
so
so
I'm
going
to
read
today.
For
that
reason-
and
hopefully
you
know,
we
can
continue
to
nail
these
things
down
and
seems
like
things
are
going
well
in
this
last
week,
but
let's
just
you
know,
keep
going
and
get
things
done
and
hopefully
I'm.
D
B
Didn't
quite
catch
you
when
you
cool
out
earlier
on
yeah
I
mean
having
too
much
to
add
I.
Think
the
number
of
Murphy
ours
is
slightly
risen
since
yesterday,
174
in
the
last
week
yeah.
The
only
other
thing
to
note
is
there
are
some
changes
rolling
out
to
the
GUI
front-end
deck
for
prowl
in
order
to
start
collecting
metrics
on
CPU
and
memory
usage,
so
that
we
can
try
out
rolling
forward.
So
the
humanities,
API
machinery
changes
that
were
done
a
couple
of
weeks
ago
and
potentially
introduce
some
performance
regressions
at
the
time.
B
I
think,
as
of
just
me,
looking
on
dev
stats
now
it
says
in
the
last
week
to
date
and
that
will
be
I
guess
in
my
local
timezone
KMT
there's
been
a
hundred
and
seventy-four
I
need
to
double
check
because
haven't
said
there
was
151
yesterday,
but
I
need
to
verify
that
he's
checked
in
the
same
way
as
me.
Unless
there
was
a
big
rush
last
night,
yeah.
D
Yeah,
that
would
for
sure,
be
interesting.
Maybe
we
can
chat
about
that
just
tomorrow,
Thursday
or
something
it's
like
how
freeze
is
affecting
the
rate
at
which
PRS
merge,
because
I
think
that
would
be
some
kind
of
valuable
empirical
data
about,
like
the
efficacy
of
code
freeze
and
its
effect
on
coven
aid
contributions.
Yeah.
B
B
D
Green
to
mean
to
frighten
things
up
a
little
bit
but
awesome.
Thank
you.
Sorry,
mr.
Sirtis
James,
but
that's
great
thanks.
Okay,
cool
yeah,
so
recently
update
yeah,
like
I,
said
princess.
Read
that
many
weeks
ago
burn
down
meetings
every
day.
I
am
looking
forward
to
talking
to
y'all,
either
later
tips,
big
release,
meeting
or
at
tomorrow's
burn
down.
Were
there
any
open
discussion
items
that
anyone
wanted
to
bring
up
and
chat
about?
Well,
while
we
have
some
time
left
at
the
end
of
this
me.