►
From YouTube: Kubernetes 1.13 Release Team Meeting 20181109
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Alright,
let's
get
started
hello,
everybody
welcome
to
our
burndown
113
bun
down
and
I
shall
release
lead
pink.
The
link
to
the
meeting
notes.
Please
add
your
attendance
there.
If
you've
not
done
so
and
the
usual
disclaimer
is
I
just
started.
Recording
this
session
and
I'll
go
on
YouTube
shortly
after
so,
please
be
mindful
of
what
you
say:
Creed
with
that.
Let's
get
started.
A
Okay,
the
big
agenda.
We
cut
our
beta
on
Wednesday
after
our
after
a
burn
down,
things
went
pretty
smoothly
now,
so
we
now
have
a
1:13
branch
and
coal
enabled
the
CI
signal
jobs
on
the
branch
we
did
have
some.
We
took
some
time
to
stabilize
it
mainly
because
some
of
the
jobs
run
as
Co
submits
and
which,
which
were
like
a
police
requisite
for
cube
a
medium
jobs.
To
finish
so
we
kind
of
figure
that
out
that's
how
things
go,
but
probably
will
update
the
test
in
from
handbook
to
make
that
more
clear.
A
But
as
of
now,
the
new
branch
is
alive
and
kicking
and
we
are
getting
C
a
signal
out
of
it.
Good
news
is:
there's
nothing
surprising
that
we
are
seeing
the
same
failures
that
we're
seeing
in
master,
and
that
said
every
day
we
are
planning
for
our
fast
forward
by
default.
Unless
master
is
kind
of
broken,
then
we
will
not
do
a
fast
forward
into
1:30,
Doug
and
Hennis
and
young
they
would
be
alternating
and
taking
turns
to
do
the
fast
forward.
10
today
will
be
around
5
p.m.
A
every
day,
but
if
any
of
you
see
any
issues
or
are
waiting
for
critical
PRS
that
you
want
us
to
hold
off
the
phosphor
on,
please
ping
me
or
Doug,
and
then
we
can
coordinate
that,
but
I'll
be
watching
master
before
the
phosphor,
which
tape
the
next
big
thing
is
code.
Slash
it's
starting
today
at
5
p.m.
I
think
we
are
it
that's
on
track
because
for
for
all
practical
purposes,
it's
just
adding
one
more
really
a
much
blocking
criteria
too
tight.
A
So
I
will
be
also
watching
closely
PRS
that
we
are
waiting
on
that
don't
have
the
four
labels
so,
which
is
the
sake
kind
priority,
and
if
you
so
buck,
triage
owners
leads
shadows,
enhancement,
leash
shadows
or
any
by
our
CI
signal.
If
you
see
any
PRA
waiting
on
that,
doesn't
have
these
for
after
5:00
p.m.
today,
please
please
add
them
or
ping
me
if
you
don't
have
permission
to
add
some
of
those
labels.
A
B
B
C
D
C
Now
is
that
better?
Okay-
let's,
let's
hope
this
works,
because
I'm
basically
tethering
to
my
my
device
right
here
so
so
I'll
try
to
go
quickly
right
now.
We're
did
we're
in
decent
position
right
now,
there's
there's
seven
issues
that
are
at
risk.
One
at
limbo,
quickly,
going
through
these
CSI
is
kind
of
the
big
one
as
well
as
Windows
servers
these.
These
are
the
two
that
are
supposed
to
be
going
stable
in
this
next
release.
C
C
When
I
checked
this
morning,
they
just
had
some
work
being
done
just
a
few
hours
prior,
the
big
one
is
actually
waiting
for
the
one
day,
auto
spec
you
actually
be
merged
in
as
well,
and
then,
of
course,
there's
Docs
to
I
know
that
you're
more
up-to-date
on
the
stuff
for
Windows
Server
containers.
So
if
you
want
to
talk
about
that,
you
can,
if
not
I
can
I
can
try
to
go
on
and
hit
these
other
ones
real,
quick.
You.
C
Yeah,
so
then
you
got
the
next
one
going
down.
These
are
all
alphas
as
well
going
through
here
and
when
we
look
into
it
it
basically.
For
me,
it
means
that
they
are
options
to
be
punted
to
114,
and
so
the
in
this
one
right
here
is
the
the
one.
That's
in
limbo
is
the
CSI
block,
store
support,
and
actually
this
one
is
I
believe
beta
if
I'm
not
mistaken.
C
This
was
something
that
was
originally
taken
off
the
sheet
and
is
now
being
asked
to
be
back
at
on
to
the
sheet,
because
there's
a
new
dev
that
is
now
taking
care
of
it.
So
they
actually
have
a
lot
of
confidence
that
it's
gonna
make
it
since
it's
just
one
PR,
so
I
think
that
we
should.
We
should
talk
about
that
one
and
kind
of
see
if
we
let
them
go
along
with
it.
Just
because
I
know,
there's
a
lot
of
things
for
for
CSI
that
are
trying
to
happen
for
this
release.
C
C
Csi
inline
volume
support
there
is
progress
happening,
but
there's
a
lot
of
things
that
are
still
failing
and
with
code
freeze
coming
along
pretty
quickly,
we
should
probably
make
a
decision
of
what
that
should
actually
look
like
the
third
party
device
monitoring
plugins
this
one.
The
cap
is
still
even
open.
There's
no
PRS
attract.
C
A
E
I
should
get
in
the
habit
of
inviting
really
compelling
enhancement
offers
to
come
to
this
meeting,
because
if
they
are
trying
to
get
something
into
the
release,
they
need
to
be
here
to
talk
about
the
status
okay
themselves.
So
you
don't
do
all
the
running
around
because
I've
taken
out
here,
then
it's
not
shipping.
Okay,.
A
That's
that's
good
to
know.
Awesome
I
will
then
I
make
sure
that
theater
next
week,
spun
down
and
for
as
for
Windows
Server
again,
this
is
super
truck
tight
dough.
Patrick
was
confident
of
getting
this
in
and
he
said,
he'll
be
here
next
Wednesday
again
to
give
a
final
status
before
we
see
if
this
is
gonna
go
in
or
not
as
for
conformance
coverage.
I
synched
up
with
Aaron,
who,
who
was
in
was
sitting
on
the
sake.
A
Our
conversation
about
it
looks
like
conformance
coverage,
is
going
to
be
driven
by
windows
and
conformance
group
together,
and
it's
not
a
blocker
for
that
feature.
Going
GA,
so
I,
don't
think
conformance
is,
is
going
to
be
blocking
them,
but
they
have
other
lot
of
other
PRS.
Both
code
tests
and
Doc's
opened
that
that
might
not
make
it
in
time.
So
I'll
do
some
more
scrapping
of
this
and
hopefully
next
week
we
can
move
all
these
out.
As
we
see
any
more
any
updates
or
any
questions.
A
A
A
A
Okay,
so
we've
been
like
we've
been
closely
following,
see
a
signal,
especially
in
the
new
branch
and
on
master.
We
have
quite
a
few
open
issues.
We
try
to
bucket
it
there,
as
you
can
see.
Mainly
there
are
a
lot
of
CSI
related
failures
around
the
new
Alpha
features.
That's
been
added
and
also
on
a
couple
of
a
couple
of
new
flex
storage
feature
that
Scott
added
as
well
Michelle
and
the
storage
folks
are
on
top
of
it.
A
A
A
So
we
are
in
the
process
of
reverting
another
change
which
could
in
the
hope
that
will
bring
down
CPU
consumption
to
where
it
was
a
couple
of
weeks
ago,
and
then
we
do
have
some
a
few
issues,
both
the
tank
nodes
and
the
HPA
failures
for
which
the
PRS
have
merged,
and
we
had
at
least
one
clean
run.
But
we
want
to
see
a
few
more
clean
runs
before
we
close
close
them
out
and
a
couple
of
new
issues
that
cropped
up
were
the
cops
job.
Basically,
they
ran
out
of
account.
Kota
and
Justin.
A
A
The
downgrade
one
is
a
little
bit
concerning
because
the
job
was
reasonably
stable
and
it
started
started
failing
since
today
morning,
so
I'm,
following
up
with
again
the
cluster
life
cycle,
folks
to
hash
this
out
slightly
loosely,
and
then
there
are
a
bunch
of
cheeky
upgrade
failures.
Now
they
move
to
the
optional
dashboard
for
what
Evers
worth
I'll
be
pinging.
A
The
plant
tipping
DGK
on-call
folks
internally
to
see
if
they
want
to
take
a
look
at
this,
so
the
status
there
is
still
yellow
because
all
of
these
could
become
blockers
or
extend
into
code
freeze
and
which
we
might
have
to
cherry
picker
not
cherry-pick
have
to
include
during
code
freeze
timeframe.
So
that's
the
risk
with
all
these
failures.
There.
A
A
We
could
just
did
a
scrub
this
morning.
I
will
have
to
allow
to
follow
up
with
him
offline
and
take
a
look
at
these
to
see
which
of
these
issues
don't
have
associated
PRS
and
need
a
little
bit
more.
Pushing
one
quick
thing
that
we
are
tracking
closely
is
the
license
issue
where
there's
the
link
to
the
the
hickety
repo,
where
they
there's
a
there's,
an
upgrade
in
the
license
that
needs
to
happen,
which
then
we
need
to
pull
from
their
repo
down
to
kk.
A
F
A
F
What's
up
y'all,
meaning
things
to
note
today,
that's
different
from
Wednesday!
So
as
I
was
saying
on
Wednesday,
the
plan
is
for
on
Monday
we're
going
to
reach
out
to
sig,
leads
and
SiC
chairs
and
get
them
to
kind
of
review.
The
notes
that
were
provided
by
fellow
pers
from
there
sig
or
the
release
cycle
and
write
a
paragraph
pros
of
themes
of
what
their
signals
working
on
included.
Six
that
I
may
be
reaching
out
to
six
that
didn't
produce
any
release,
notes
as
well
throughout
thoroughly
cycle
justice.
F
Even
maybe
they've
been
working
on
stuff
out
of
tree
or
what
have
you
I
know?
A
few
sick
weeds
have
brought
up
that
they
wanted
to
be
included
even
though
they're
not
necessarily
working
on
injury
stuff.
So
that
is
an
on
track
for
Monday.
So
there's
two
things
that
you
can
review
if
you're
interested
in
this.
The
first
is
the
Google
Doc
that
we're
gonna
be
sending
cichlids.
That
has,
you
know,
notes
so
far
the
sections
they
need
to
fill
in
the
two
dues
of
what
needs
to
be
done.
F
That
Google
Doc
is
ready
in
it's
linked
and
more
words
here,
and
the
other
thing
is:
the
draft
comes
that
me
and
all
of
the
shadows
are
gonna
kind
of
we're.
Gonna
divvy
up
the
sick,
weeds
on
Monday
use
this
cons
template
as
a
guide
to
reach
out
to
the
sick
weeds.
So
if
anyone
has
any
feedback
on
any
of
that,
definitely
let
you
know
and
incorporate
it
over
the
weekend
and
then
on
Monday.
A
Thanks
for
putting
that
together,
Mike
yeah
I
think
makes
me
might
be
a
little
bit
early,
but
we
decided
we'd
still
send
it
out,
considering
people
might
be
out
for
cube
con
later
next
week
and
also
the
week
after
that,
so
we
just
wanted
a
slightly
longer
window
to
give
to
the
cichlids
to
fill
things
out
right,
yeah
and
enhance
a
kendrick
and
others
and
part
of
the
release
team.
If
you
want
to
take
a
look
at
the
release,
notes,
draft
and
point
out
if
something
needs
to
be
added
or
updated,
that'll
be
great.
F
She's
on
the
road
but
I'm,
one
of
the
shadows,
I
could
piece
in
the
notes
for
the
document.
Basically
the
same
thing
as
relief
smells
except
our
deadline
is
on
Tuesday
and
we
we've
got
everything
split
up
as
the
features
and
things
like
that.
So
that's
all
we're
planning
on
on
reaching
out
to
the
same
leaves
and
stuff
I
have
nothing
really
more
to
add
other
than
the
links
into
the
notes.
But
things
are
looking
pretty
good.
There's
a
handful
of
us
and
yeah
schedules,
nice
and
front-load
itself
as.
A
A
A
So,
whatever
works
without
adding
much
friction
to
to
drafting
more
people
into
the
team,
I
would
let
them
hash
that
out
cube
con
Shanghai
is
next
week
we
have
most
folks
traveling
right
now
and
in
the
course
of
next
week,
I
just
wanted
I
know.
Aaron
and
Josh
are
gonna,
be
out.
I
wanted
to
know
if
any
other
lead
is
planning
to
be
away
next
week
and
if
so
then
I'll
know
to
follow
up
with
the
shadows
or
available,
if
not
I,
think
it's
just
Adam
and
Josh.