►
From YouTube: Kubernetes 1.10 Release Burndown Meeting 20180321
Description
A
Everybody
welcome
to
the
career,
Nettie's
1.10
released,
burn
now,
meaning
it's
Wednesday,
March
21st
2018
I
am
Jay
singer,
Dumars
your
host
and
release
leader
this
go-round,
and
if
you
want
to
follow
along
after
the
fact,
the
agenda
and
meeting
notes
are
available.
It
bit
ugly,
/,
kate's,
110
burnt
down
and
without
further
ado,
I'm
going
to
pull
the
engine
down
here.
B
A
We'll
again
talking
first
I
want
to
verify,
is
sad
on
the
call
or
anybody
from
six
storage
not
yet
because
they
have
a
thing.
A
A
A
D
Question
is
like
Leggett
pointed
out.
Jordan
pointed
out,
we
don't
know
whether
the
revert
is
a.
Is
the
right
thing
to
do
or
not
it's
a
bug
fix
it's
a
one-line
change,
but
it
did.
I
am
guessing
that
they
are
still
looking
and
the
last
I
saw
on
the
somewhere
were
maybe
on
slack
or
and
github
was
that
they
we
they
are
seeing
extra
for
29s,
HTTP
error
codes,
I,
think
yeah.
A
E
A
F
G
A
A
H
Well,
his
guitar
handle
is
randomly
and
he's
the
one
who
authored
that
PR
and
we're
waiting
for
him
to
it's
random,
okay
anyway.
So
yes,
so
we
probably
would
need
some
input
from
him.
But
at
least
it's
a
good
situation,
because
we
know
reverting
that
we
are
against
head,
takes
us
back
to
a
good
state
which
is
like
less
than
five.
H
Second
I
think
both
the
tests
had
close
to
four
point
five
seconds
of
like
Angie
posted
the
update
there,
but
we
had
like
close
to
four
point
four
per
second
latency,
which
is
good,
which
is
more
or
less
like
what
we
had
before,
and
so
there
we
were
kind
of
good
and
the
other
issue
on
flew
Indies,
getting
restarted
due
to
the
flu
and
descaler.
That
seems
to
have
like
the
release
blocking
part
of
that
seems
to
have
been
fixed,
so
there
is
still
part
of
the
issue
which
needs
to
be
fixed,
but
I.
H
A
H
H
So
yes,
so
there
also,
we
are
good.
I,
really
hope
we
don't
find
something
more,
which
brings
it
back
to
release
blocker
but
I
mean
overall
I.
Think
we
probably
kind
of
good
there.
And
you
know
there
was
another
scalability
issue
that
came
up
a
regression,
but
I
don't
think
we
are
worried
about
that.
For
one
point,
n
I
just
filed
a
bug
available.
It's
not
in
1.10
it's
in
1.11,
okay,
yeah
great,
so
yeah.
A
A
B
A
A
A
A
B
A
And
to
be
clear
that
the
impact
path
is
that
if
you're
you're
you
upgrade
to
the
security
path,
fixed
versions,
and
then
you
try
and
we
let's
say
we
don't
get
this
in
110
and
you
try
and
do
an
upgrade
to
110
in
place
and
you
get
the
that
sort
of
window
where
you're
affected
by
it.
You're
gonna,
it's
gonna,
add
caused
a
failure.
So
essentially,
if
we
get
into
110
this
particular
appear
in
a
110,
then
it
it
eliminates
the
number
of
possibilities
that
which
you'll
you'll
hit
the
problem
in
an
upgrade.
E
B
E
A
Yep,
and
also
on
a
mean
having
this
the
thing
about,
if
we
put
this
in-
let's
say
it
doesn't
ship
in
110
that
goes
in
1
10.1.
That
seems
like
a
really
nasty
thing
to
be
aware
of
in
terms
of
a
patch
release.
I
would
be
a
little
miffed
if
I
saw,
that
is
a
patch
release,
upgrade
issue,
so
I
think
it's
just
better
for
that
the
whole
ecosystem
to
get
this
in
the
110.
So
unless
somebody
disagrees
yeah.
A
B
E
A
A
A
E
A
Midi
might
be
back,
that's
great,
actually
so
Michelle,
if
hear,
if
you're
still
here,
sorry
now
I'm
going
back
to
now,
I
know
why
this
was
actually
this
was
in
here.
So
this
actually
is.
Release
currently
is
currently
is
this
fixed
by
the
other
PR?
Yes,.
B
A
A
A
C
G
G
G
Other
one
is
the
key
Badman
one,
nine
nine
ten
that
one
looks
consistently
bad
I
am
not
sure
why
this
job
is
in
one
pan
blocking
for
sure
that
one
being
when
I'm
blocking,
because
there's
no
like
equivalent
job
on
master.
A
G
The
other
one
is
from
the
num
lock
inside
the
GC
igce,
so
job
looks
bad
I
just
found
that
it's
not
blocking
so
yes,
I.
A
Yeah,
let's
keep
an
eye
on
that
because
it's
not
blocking
but
I
also
want
to
understand
what's
going
on
there,
because
sometimes
non-blocking
can
lead
to
blocking
so
yeah
great
okay.
Anything
else
said:
nope
all
right,
testing,
Fred,
I,
haven't
heard
anything
I,
don't
know.
If
anybody's
on
the
call
from
there
then
call
no
all
right
and
Jennifer
is
not
on
the
call,
but
was
gonna,
give
it
a
update
later
about
user
Doc's.
They
pretty
much
same
thing.
F
No,
not
necessarily
I
would
just
say
that
if
you
haven't
already
gone
into
the
document-
and
you
have
features
that
need
to
be
highlighted,
please
do
and
looks
like
networking
just
needs
to
have
the
language
around
the
DNS
plug-in
switched
accordion
s
reviewed,
and
we
need
a
little
bit
more
clarification
around
that.
A
Right
Nick
release
notes.
I
A
So
when
you
do,
when
you
look
back
at
like
the
release,
notes,
four
one,
nine
and
one
eight
and
so
forth
in
terms
of
length
and
density,
how
does
how
does
this
current
stuff
compare.
I
I
This
time
we
we
had
the
complete
part
down
already
and
we've
been
focusing
on
making
them
more
useful.
So
you
know,
rather
than
just
some
cryptic
message
about
you
know
some
fix
that
only
somebody,
deep
in
the
bowels
of
kubernetes
will
understand
we're
trying
to
give
more
context
on
you
know.
Why
was
this
fix
done
and
what
will
be
the
change
that
you
will
see
based
on
this
fix,
so
that
people
get
more
more
of
a
sense
of?
I
So
I
I
have
been
talking
with
Jennifer
about
what
we're
going
to
do
next
time
and
what
we've
been
talking
about
is
there's
there's
been
talk
about
having
sort
of
weekly
reviews
by
Docs
people
right
now.
The
docs
team
has
people
who
look
at
the
PRS
that
come
in
and
decide
you
know.
Do
we
need
to
worry
about
Docs
for
this?
A
A
A
All
right,
Wow,
impressive
work,
everybody
seriously.
Thank
you
so
much
for
all
your
hard
work,
and
this
is
III
think
we
have
a
very
high
likelihood
of
hitting
our
date
at
this
point.
So
this
is.
This
is
really
amazing.
Thank
you
all
everybody
and
have
a
great
rest
of
your
day
and
I
will
be
in
touch
tomorrow.