►
From YouTube: Kubernetes 1.14 - Week 10 - Burndown 2019-03-15
Description
A
C
A
A
You
are
at
the
kubernetes
114,
burned
down
meeting
with
your
host
Aaron
of
cig
beard
and
we're
all
being
recorded
and
adhering
to
the
kubernetes
code
of
conduct,
so
we're
all
not
being
jerks
and
we
can
watch
ourselves
not
be
jerks
on
YouTube
later,
all
right,
so
I
think
I'm,
like
mostly
recovered
from
whatever
plague,
took
me
out.
For
most
of
this
week,
it's
been
an
exciting
week.
Let's
start
with
Claire,
to
update
us
on
enhancements.
G
A
B
H
There
isn't
a
lot
of
news
since
yesterday
we
have
won
the
ingress.
Job
is
failing
in
both
master
blocking
and
run
14
blocking.
It
has
been
failing
for
in
a
couple
of
days
now,
and
it
has
a
PR
open
that
is
being
actively
worked
on.
It
seems
to
be
close
to
LG
TM,
so
I'm,
not
feeling
particularly
anxious.
H
Yet
on
that
one,
and
then
the
the
two
failing
muster
up
great
jobs
are
to
the
best
of,
as
far
as
we
can
tell
related
to
the
:
regression
and
we
hope
to
see
them
resolved
with
them
up
to
112
one.
These
are
the
main
things
that
I'm
keeping
an
eye
on,
and
then
we
have
a
number
of
open
issues
for
flakes
that
have
had
fairly
good
response.
H
A
H
H
H
These
were
the
ones
that
had
problems,
and
all
of
these
have
been
tree
asked
to
the
upgrades
failing
Midway,
which
was
then
trade
triage
to
the
112
regression.
There
are
upgrade
tests
are
flaky
earth.
Some
non
upgrades,
I
guess
so
that's
a
whole
other
track
of
work
that
we're
looking
at
but
again,
I'm,
not
I'm,
not
seeing
any
other
consistent
failures
that
we
haven't
connected
to
112.
H
F
A
Then,
at
some
point,
I
believe
that
my
attention
is
going
to
turn
back
to
you.
Can
we
actually
kind
of
are
the
flake
rates
good
enough
that
we
can
get
three
passes
in
a
row
where
we
need
that
to
happen?
So
it
falls
through
the
ingress
job,
and
then
that
falls
back
over
to
the
flakiness
of
the
default
job.
A
H
I
Nick
was
not
here
today,
so
I
will
try
to
do
our
report
so
far.
It
is
the
core
status.
Is
okay,
be
around
green,
yellow
compared
to
yesterday
we
have
some
more
openness.
Recipe
are
about
issues
we
are
around
7:00
now
and
about
8:00
for
PRS
the
most
important,
maybe
one
of
the
most
important
players
about
going
to
go.
One
point
one
point
one
is
going
forward
and
we
have
posted
a
list
of
all
many
PRS
for
this
cycle,
so
it
is
okay.
A
A
So
if
we
haven't
like
this,
we
should
be
booking
people
daily,
assuming
we're
doing
that
great
I
poked
a
couple
of
these
yesterday
and
we'll
try
to
follow
up
here
to
help
out.
But
if
you
feel
like
you're,
finding
PRS
that
are
not
responsive,
please
do
escalate
those
here
on
Monday
or
escalate
them
in
the
sake
release
channel
as
appropriate.
A
J
Yeah,
so
just
a
quick
update
from
distance
FRA,
we
most
only
eight
years
in
the
last
two
days,
which
is
a
good
send
at
me
and
going
full
speed
ahead
after
good
freeze
and
then
now
go
one
12.1
image
should
be
out
today.
Hopefully
I
just
checked
it's
not
out
yet
so,
but
the
rules
go
bezel
rules
go
changes
are
so
we
are
just
waiting
for
the
official
docker
image
to
be
published
and
after
that,
I
will
do
the
needful
for
pushing
the
test
images.
Okay,.
A
A
K
Mode
I
got
a
meeting
with
the
shadows
later
on
today
to
rally
the
troops
before
the
weekend.
We
should
get
everything
in
by
Monday
this
one.
The
deadlines
have
everything
ready
to
merge
and
also
wanted
to
announce.
I've
nominated
a
lead
for
the
115
docks
role
as
Barney
and
Barney's
been
awesome
and
been
on
the
past
two
release
cycles
with
so
welcome.
Barney
and
that's
all
I
got.
C
Yep
they've
had
to
go
for
a
quick
family
emergency,
nothing
too
bad.
So
we
have
a
new
PR
in
for
the
current
draft
for
release
notes
and
it
is
essentially
a
copypasta
from
the
current
working
doc,
which
I
have
linked
in
the
team
meeting
notes.
That
is,
that
working
doc
is
what
we
were
working
off
of
right
now.
That's
where
we're
pulling
in
new
changes
and
putting
them,
and
that's
where
the
editorial
part
of
release
notes
is
happening.
So
we
are
all
good
to
go.
Things
are
moving
along
smoothly.
L
L
A
A
M
A
Okay,
Oh,
what
my
current
status
is
also
all
of
the
colors
I
should
probably
do
something
about
that
real
fast.
My
status
remains
a
yellow
eye,
I
mean
I,
guess:
I
am
wearing
like
yellow
and
red
and
green
on
my
shirt,
so
maybe
I
should
change
it
back,
but
I
feel
I'm
feeling
good
and
hopeful
and
optimistic
that
they
go
112
change
will
help
us
out.
I
feel
like
if
we're
going
to
make
a
call
about
code
file
being
pushed
back,
we're
going
to
make
that
decision
on
Monday.
A
That
decision
is
going
to
be
made
either
because
we
couldn't
get
far
enough
along
with
go
112
1
or
we
did
get
far
enough
along,
but
it
has
not
actually
resolved
problems
to
our
satisfaction,
so
I'm
really
hopeful
that
we
can
get
that
way
at
it.
So
we
can
sort
of
let
the
tests
soak
for
a
while
this
weekend.
In
order
for
that
to
happen,
Honus
we
may
need
like
just
randomly
in
case.
We
might
need
some
more
fast
forwarding
today
to
help
out
with
that.
Is
that
cool
with
you?
That's.
M
A
N
A
So
I
agree
with
that,
so
basically
I'm
suggesting
that
cutting
of
the
RC
is
pretty
much
tied
up
with
code
thoug
as
well.
I
want
the
RC
to
represent
the
code
as
best
as
we
understand
it,
without
any
additional
cherry
picks,
because,
hopefully
we
don't
even
need
any.
It
should
actually
be
what
we're
gonna
have
go
out
the
door
and
so
I
want
us
to
understand
which
version
of
code
we're
using
to
build
it
before
we
make
that
decision
right.
N
N
Right
week,
I
yesterday
I
kind
of
missed
a
step
that
was
the
problem.
So
rules
don't
go,
we
we
planned
for
it,
but
then
I
forgot
that
we
needed
the
official
docker
image,
so
so
I
I
think
we
need
to
plan
to
move
our
other
release
candidate
and
the
tall
a
couple
of
days,
at
least
so.
We
can
either
go
back
or
go
forward
and
if
we
don't
get
a
one
twelve
one
image
today
and
we
get
it
on
Monday
early
in
the
morning,
then
we'll
still
need
a
couple
of
days
to
try
it
out.
N
A
Agree
with
that
I
feel
like
at
this
point,
it's
unclear
to
me
how
many
days
we
would
need
to
push
it
back,
so
I'm
inclined
to
suggest
that
I
message
to
kubernetes
that
that
heads
up
you
feel
that
a
delay
in
code
law
is
very
possible,
but
we
will
not
know
for
sure
we'll
have
more
information
available
for
you
on
Monday.
Do
you
feel,
like
that's
a
fair
statement?
A
That's
fair
and
we
can
spend
some
time
hashing
out
exactly
what
that
might
look
like,
if
maybe
that,
just
that
statement
alone
is
enough,
for
maybe
I
need
to
provide
some
more
detail
because
I
guess
it
would
be
helpful
to
understand
upper
and
lower
bounds
of
what
we're
thinking
about
in
terms
of
slippage
there.
One
of
the
things
that
I
find
valuable
is
the
idea
of
letting
a
build
soak
over
the
weekend.
A
That's
the
most
ideal
way
for
us
to
get
three
green
passes
in
a
row,
so
things
we
could
toy
around
with
are
things
like
shortening
the
window
between
code
thaw
and
cherry-picks,
or
maybe
we,
you
know
squinch
everything
back
by
a
day.
Those
are
the
things
we
can
do
to
preserve
letting
things
so
over
the
weekend.
Assuming
we
can
get
things
clarified
anyway,
I
guess
we
can
talk
about
that
offline.
D
A
Yes,
there
you
are,
she
is
hopefully
accepted.
My
nomination
for
release
League
for
115,
so
Claire
has
done
an
amazing
job.
This
release
cycle
and
I
can't
wait
to
see
what
she
does
for
the
115
release
cycle.
She
will
be
helped
out
by
Tim
pepper,
who
is
already
being
super
helpful
by
taking
notes,
and
he
will
be
serving
as
a
release.
Shadow
for
115,
alongside
Claire,
so
I'm
super
excited
for
that.
A
I
also
want
to
get
a
huge
thanks
to
everybody
who
has
followed
up
either,
based
on
me,
posting
in
slack
or
Stephen,
sending
out
an
email
and
suggesting
your
nominations
for
lead
roles
for
your
positions
on
that
issue.
I
will
open
up
a
PR
today,
based
on
the
like,
confirmed,
accepted
things
I
see
on
that
issue.
This
is
the
sort
of
thing
where
I
can
either
leave
the
PR
up
until
we
get
all
the
weeds
filled
or
we
can
virginia
terry
will
hash
that
alcohol
that
issue
there.
A
E
N
N
One
was
going
from
one
eleven
five
to
one
twelve
zero
yeah,
and
then
we
were
going
to
go
from
one
1202
112
one,
but
then
yesterday
they
did
release
one
eleven
six
I
think
okay,
so
that
is
the
other
wrinkle.
Do
we
go
back
to
what
we
had
before
or
do
we
go
back
to
the
new
one
11x
that
came
out
yesterday,
but
then
we'll
have
to
find
the
images
for
that
too
and
see
if
they
are
wrong.
N
I,
we
don't
know
that,
so
that's
so
that's
another
problem,
so
we
need
to
identify
the
list
of
reverts
and
then
we
have
to
kind
of
like
prepped
for
it
there
are
changes
both
in
Destin
from
as
well
as
KK.
If
you
have
to
do
the
reward
and
the
other
one
other
PR
that
comes
to
mind
is
the
X
net
dependency.
A
C
N
Good
good,
good,
okay,
so
so
that's
that's
the
worst
case
scenario.
We
we
we
first
published
yeah.
Do
we
do
we
need
to
publish
a
new
cross
image?
Yes,
if
we
are
going
to
go
back
to
111
six,
then
we
need
to
publish
a
cube
cross
image
for
it
and
then
that'll
be
the
change
in
KK
and
then
we
go
to
test
and
FRA
and
change
all
the
references
to
the
Q
cross
image
to
that
image
and
then.
A
N
A
Like
it,
my
preference
would
be
if
we're
going
to
revert.
Let's
actually
revert
to
known
behavior
than
reverting
to
known.
Behavior
is
111
five.
If
we
revert
to
111
six,
that's
not
really
a
revert,
that's
rolling
to
yet
another
version
of
go
who's
performance
characteristics.
We
don't
yet.
We
don't
know.
Yeah
agreed.
N
A
A
A
N
N
N
N
And
it
only
shows
up
in
the
upgrade
job
at
this
point,
so
what
little
boomer
and
Justin
figured
out
was
you
know
that
it
was
failing,
and
then
we
looked
at
the
git
repository
for
cooling
and
we
figured
out
there
was
a
patch
in
flight.
That's
how
we
figured
out
that
we
needed
to
wait
for
112
one
and
that
fix
doesn't
actually
change
the
go
side
of
the
things
it
changes,
something
deeper
inside
Lobo.
Do
you
want
to
talk
about
so.
F
A
Right
we
certain
to
be
explicit
about
the
options
we
have
where
I'm
just
like
kind
of
agnostic
about
the
change
in
general,
so
cut
all
is
currently
scheduled
for
Tuesday
and
then
there's
a
two-day
window
for
any
last-minute
cherry-picks
until
indicate
Thursday.
And
then
that
gives
us
Friday
and
all
of
the
weekend
for
everything
to
soak
and
look
nice
and
green.
And
if
we're
happy
with
it,
we
get
something
out
the
door
on
Monday,
March,
25th,.
A
So
the
buffer
we
have
here
is:
we
can
shift
everything
back
by
a
day,
so
code
thought
could
happen
on
Wednesday
and
we
still
give
ourselves
that
two-day
window
between
code
thaw
and
leaving
room
for
any
last-minute
cherry-picks,
and
then
we
still
have
a
weekend
to
let
things
soak.
We
could
also
just
really
hope
that
there
aren't
any
cherry,
picks
needed
whatsoever
and
shorten
that
window,
so
we
can
hold
code
fall
back
until
even
like
Thursday
or
Friday.
A
If
we
wanted
to
that's
not
super
ideal
but
possible,
and
that
still
gives
us
that
window
of
letting
it
run
over
the
weekend,
any
delays
beyond
that
are
going
to
start
to
have
rippling
implications
for
communications,
because
Monday
is
the
communicated
release
date.
We
have
four
days
in
that
week
that
we
could
slip
back
on
if
we
had
to
so
that
we
can
still
say:
we've
released
kubernetes
at
the
end
of
q1,
but
it's
going
to
require
a
lot
more
communication
legwork
to
make
sure
we're
all
aligned
on
the
release
Tim.
A
E
N
So
I
tried
I,
there's
two
people
on
that.
I
pinged
on
twitter,
but
I
don't
know
anybody
else
and,
and
I
ping
them
on
the
pull
request
as
well.
So
those
are
the
two
two
methods
that
I
know
of
that
I
used
already,
but
it
might
be
just
that
they
don't
want
to
be
a
release
on
Friday
unless
they
know
somebody
else.
N
C
C
C
N
A
A
Yeah
I
have
no
idea
what
levers
I
can
pull
there.
Maybe
there
are
some
available
to
me
that
I'm,
not
aware
of
so
I,
can
try
to
help
from
that
angle,
but
I
think
you
are
right
in
parallel.
Let's,
let's
build
in
the
image
that
downloads,
what
version
the
conversion
of
go,
that
we
need
and
see
if
we
can
get
things
compiled
that
way.
Okay,.
N
J
C
E
C
N
The
Basel
one
actually
most
of
the
CA
jobs
passed
I
tried
on
two
different
PRS
one
from
Jordan
and
one
from
me,
so
the
Basel
stuff
seems
to
work.
It's
just
that
we
can't
get
the
Basel
stuff
easy
enough
on
the
upgrade
job
right.
Okay,
so
that
that's
the
problem.
So
let's
hack
the
dockerfile
for
the
cross
I
mentioned
then
yeah.
A
I'm
gonna
open
up
an
issue,
that's
equivalent
to
the
one
called
one
issue:
call
it
the
111
5
revert
issue
and
make
sure
that
we
have
the
appropriate
steps
documented
in
there.
Hopefully,
we
don't
have
to
use
it,
but
at
least
that
way
the
plan
is
out
there
and
I
will
also
be
sending
something
out
to
UK
dem
today
to
give
them
the
heads
up
that
we
may
be
pushing
code
back
by
a
couple
of
days
and
I
have
more
information
for
them
on
that
on
Monday.
N
M
N
A
My
my
plea
would
be
to
continue
to
use
the
go
112.
One
issue
is
the
rallying
point
for
communication
about
the
plans
and
next
steps
related
to
getting
us
on
going
112,
one
so
I
think
a
lot
of
the
stuff
you
articulated
Timms.
When
you
make
sure
that's
that's
in
a
comment
on
that
issue,
but
I'll
help
keep
everybody
on
the
same
page
right.