►
From YouTube: Kubernetes 1.14 - Week 10 - Burndown 2019-03-14
Description
A
A
C
C
C
C
B
That
I
will
take
that,
for
it
awesome
yeah
speaking
of
I'll
post
a
link,
and
if
you
can
everyone,
please
add
your
name,
not
sure.
If
the
these
lists
of
names
ever
get
used
by,
like
some
machine
learning
algorithm
to
determine
you
that
the
best
attendance
or
anything,
but
you
know
it
it
does-
you
want
to
be
on
it
so
I.
C
B
Thank
you
yeah,
so
today's
March
14th
11
days
till
the
actual
release
is
cut.
Hopefully
thank
you
all
for
coming
just
a
reminder.
Its
meaning
is
being
recorded
right
now,
and
thus
you
are
expected
to
follow
the
community's
code
of
conduct,
which
basically
boils
down
to
don't
be
a
jerk,
so
first
up,
as
always,
is
enhancements
with
Claire.
How
are
enhancements
going
good.
D
B
A
A
lot
better,
so
thanks
to
so
the
crates
accordingly,
one
job
is
failing
a
master
clock
in
for
flaking,
two
filling
in
114
blocking
a
five
flaking
master
upgrade
every
day
there
I
think
there
are
two
jobs
failing
and
all
of
them
blocking
put.
The
good
news
is
that
a
lot
of
the
a
lot
of
the
flakes
a
lot
of
the
film
jobs?
Are
they
just
need
a
couple?
More
runs
to
start
cleaning
up
and
there's
they.
There
are
a
lot
of.
A
A
They
an
issue
with
different
resources
and
master
great
a
has.
The
last
two
ones
were
clear:
I
think
so
we're
just
gonna
keep
on
observing
and
and
see.
If
anything
comes
up
other
than
that,
we
are
still
monitoring
a
couple.
Pairs
have
jet,
we
merge,
and
hopefully
these
PRS
will
help
make
as
a
desperate
a
lot
work,
a
greener.
The
first
two
at
the
first
two
are
related
to
jobs
in
master
credit,
which,
as
I
mentioned,
is
a
lot
of
a
lot
of
purple
and
a
lot
of
red.
A
But
if
we
give
it
some
time
to
run,
hopefully
it's
gonna
work
out
and
be
and
go
back
to
normal
and
then
the
other
big
one
is
another
Pierre,
that's
open!
So
that's
the
last
one,
a
six
six.
Seventy
eight.
We
were
hoping
that
that's
going
to
resolve
some
ingress
issues
that
have
been
showing
up
in
a
master
in
the
master
in
the
block
in
the
blocking
jobs
as
related
to
interest
resources,
a
I
think
timing
out
and
again
just
when
a
just
waiting
for
a
for
it
to
get
it
for
it
to
be
merged.
A
B
C
E
F
E
Unfortunately,
there
isn't
much
we
can
do
right
at
this
moment.
The
first
I
mean
the
main
thing
that
we're
waiting
for
is
to
get
a
list
of
download
from
112
one.
Once
that
is
available,
we
have
to
update
the
rules,
underscore
go
basel
thingy.
I
left
some
notes
on
sig
testing,
I.
Believe
me
and
James.
We
were
talking
about
what
are
the
list
of
things
to
do
so?
C
Think
so
I
guess
a
part
of
me
feels
like.
Maybe
we
should
have
an
issue
open
to
represent
migrating
to
112
one
cuz.
It
sounds
like
you
dumped
a
bunch
of
useful
info
and
slack
I'm,
not
sure,
there's
an
open
issue
for
that
correct.
Yes,
because
the
other
thing
I
feel
like
we,
we
should
plan
for.
So
we
should
hope
for
success
here.
I'm
like
can't
even
believe,
they're
releasing
go
this
early
for
us,
but
if
it
doesn't
work
out,
I
feel
like
there
is
a
list
of
commits
that
need
to
be
referred.
C
It's
not
going
to
be
immediately
apparent
and
we
may
just
want
to
have
that
list
available
to
understand
how
much
time
is
involved
in
reverting
back
to
the
language
lesson.
If
that's
the
path
that
we
have
to
take
to
better
give
us
an
understanding
of
like
our
cutoff
date
or
if
we're
still
attempting
to
troubleshoot
and
troubleshoot
and
troubleshoot,
and
it's
not
working
by
this
cutoff
date.
We
just
have
to
revert
to
go
111
and
we
go
with
the
plan
that
we've
developed
ahead
of
time.
Yeah.
C
E
Use
so
yeah
the
biggest
problem.
There
is
the
cool
format,
stuff,
I,
think
or
there's
some
lint
or
Gohan
one
of
those
we
had
to
patch
things
up
that
that
would
be
the
one
which
will
cause
the
you
know,
Marge
issues
when
we
are
doing
at
work,
because
things
have
more
on
from
there
from
where
it
was
before.
Right,
because.
C
B
Chaos
and
when
we
get
back
to
the
notes
awesome
is
there
any
other
discussion
on
CI
signal
questions.
Comments,
concerns,
awesome,
I,
think
you
know,
training
from
red
to
yellow
is
always
nice,
so
good
job
team
next
up
is
bug
triage
Nico,
how
you
doing
hey,
Mike,
I'm,
fine
and
you
I'm
doing
well
so
early
for
me
and
I'm
a
little
tired
but
I'm
doing
pretty
well.
Thank
you
for
asking
good
morning.
G
G
B
Question
but
this
looks
great
it's
so
you
guys
clearly
do
a
lot
of
work
over
the
last
few
days.
I'm
getting
these
issues
down
and
it's
awesome.
That's
good,
yeah
I'll,
stop
sure
for
sure.
So
if
there
are
no
questions
next
up
is
testing
for
I,
don't
know
is
I,
don't
see.
I
don't
think
omits
here.
Is
anyone
else
from
testing
for
here.
H
B
C
On
the
comms
network,
I
know
that
I
think
like
weave
me
more
or
less
half
the
police
blog
post
on
that
right,
I
haven't
actually
caught
up
on
the
previous
recordings,
yet
I
just
thought
so
one
of
the
other
things
that's
supposed
to
go
out
before
the
blog
post
is
a
set
of
key
messages
for
the
media,
sure
doesn't
sort
of
like
the
cliff
notes
for
like
what's
important
about
this
release.
So
what
can
people
do
in
this
release
that
they
couldn't
do
before
and
what's
different
about
this
release?
I
All
good
over
here,
nothing
really
new.
The
next
plant
cut
rc1
is
next
Tuesday
and
also
try
to
be
available
as
good
as
I
can
to
do.
Things
like
yesterday
do
a
quick
branch
ffs.
If
we,
if
we
feel
we
need
to
so
yeah
I'll,
try
to
stay
up
to
date
than
the
sick
release
channel
and
otherwise
just
ping
me.
If
you,
if
you
want
to
have
the
release
114
fast
forwarded.
B
Nice
I,
while
your
update
was
truly
excellent,
honest
I
think
everyone
is
being
a
little
distracted
by
the
dog.
That's
on
the
desk
behind
you
and
Maria,
but
that's
awesome.
Rc1
is
going
to
be
super,
exciting
glad
that
things
have
been
going
so
smoothly.
This
release
with
branch
management,
which
is
a
big
change
in
big
improvement
from
two
or
three
releases
ago,
and
this
for
sure
wasn't
the
case.
B
Awesome
release
lead
updated
Aaron's
here,
so
do
you
need
to
do
easily
look
later?
The
only
thing
I'll
add
with
regard
to
release
lead
stuff,
I'm
going
to
be
starting
a
new
job
next
week,
so
I'm
not
gonna,
be
around
on
Monday
and
potentially
Tuesday
mornings
to
be
in
the
meeting.
So
just
want
to,
let
you
all
know,
but
you
know
I'll
be
around
for
sure
throughout
the
week
Aaron
do
you
want
to
do
that?
Really
sweet
updates.
C
The
key
thing
that
I'm
trying
to
keep
track
of
here
is
not
necessarily
all
of
the
technical
details.
You
all
were
doing
a
wonderful
job
with
that
I'm
just
trying
to
make
sure
that
we
have
our
key
timelines
in
mind.
So
there
there
is
a
very,
very
tiny
amount
of
buffer
built
into
the
schedule
in
case
something
crazy
comes
up.
This
might
be
to
something
crazy,
I,
still
kind
of
don't
know
until
it
actually
happens.
C
Historically,
it's
better
to
just
like
push
it
back
once,
rather
than
playing
a
game
of
chicken.
So
that's
what
I
feel
like
is
on
the
table
right
now.
That's
why
I
feel
like
it's
important
to
have
the
plans
in
place
and
on
this
will
keep
you
sort
of
in
sync
on
that.
But
the
idea
is
the
reason
the
RC
is
tied
up
as
tied
up
with
code
thaw.
Is
that
way?
It's
a
build
of
like
what
was
in
the
release.
114.
C
I
probably
sound
like
Daft
Punk
right
now,
sorry
for
the
terrible
internet,
okay,
I
think
my
internet
is
back.
So
the
second
item
I
wanted
to
raise
was
I
realized.
We
don't
actually
do
scalability
reports
and
we
haven't,
since
one
mine
and
I
feel,
like
that's
kind
of
unfriendly
to
users
who
try
to
run
their
clusters
at
scale.
I
noticed
this,
because
a
number
of
the
tests
that
CIA
will
have
been
chasing
got
removed
from
the
jobs
by
having
disabled
for
a
large
clusters
tag
applied
to
them,
which
okay
great.
C
That
means
the
tests
no
longer
run,
so
they
no
longer
break
its
scale
but
like
where,
and
how
can
users
find
documentation
of
these
behaviors
that
aren't
expected
to
work
at
scale
so
traditionally,
I
feel
like
in
the
past.
That's
what
the
scalability
validation
report
was
for.
It
was
something
that
was
authored
by
six
scalability
where
and
they
defined,
like
the
exact
set
up
of
the
cluster,
that
we
did
our
scalability
testing
on
to
prove
that,
yes,
this
release
of
kubernetes
meets
our
silos
and
SL
eyes.
C
I
feel
like
it
would
really
be
nice
to
have
it
again,
give
them
number
of
test
cases
I've
seen
punkin
due
to
that.
That
said,
even
if
the
last
one
of
these
rolled
out
in
1:9,
if
I
don't
see
it
like,
they
have
I'm
not
going
to
block
the
release
waiting
for
it,
but
I'm
really
hopeful
that
we
can
get
that
thing
done
any
questions
there.
I've.
I
C
We
ask
them
to
do
it.
They
have
a
template
that
they
write
their
report
using
the
template
or
at
the
report,
and
my
understanding
is
it's
basically,
a
description,
readable
description
of
the
job
configuration
that's
used
to
run
the
performance
and
correctness
jobs,
but
no,
this
is
not
like
this
is
by
no
means
additional
set
of
responsibilities
for
the
release
team.
We
are,
do
you
have
enough
going
on?
This
was
just
the
collection
of
an
artifact
for
missing.
C
C
Yeah
the
thing
is
for
those
of
you
who
are
to
attend
today's
community
meeting.
If
this
is
today's
cat
t-shirt,
that
means
cat
t-shirt
is
I,
don't
know
a
cat
blowing
bubbles
of
cats,
because
I
was
getting
really
happy
about
us
actually
making
a
release
and
I
didn't
actually
have
my
other,
like
code,
freeze,
themed
cat
t-shirt
available
with
me
today,
so
you're
getting
this
one.
Instead,
cats
in
the
cloud,
so
Mike
I
will
be
planning
with
thinking
at
least
update.
Today,
my
nail
ability
is
still
going
to
be
a
little
bit.
C
Spotty
I
think
you
all
have
done
a
fantastic
job
of
escalating
making
decisions
as
appropriate.
But
if
you
do
find
you
need
somebody
fee
escalation
point
of
last
resort
or
to
play
bad
cop.
Please
give
me
a
ping,
and
slack
and
I
will
triage,
as
appropriate.
I
took
care
of
a
couple
PRS
that
just
seemed
like
they
didn't
belong
in
the
milestone
anymore
and
happy
to
apply
that
pressure
as
needed.