►
From YouTube: k8s 1.16 - Week 11 - Release Team Meeting 20190910
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
Fantastic
hello
and
welcome
to
the
1/16
release.
We
are
meeting
that
today
we
have
burned
down.
It
is
Tuesday
September,
the
10th
we
are
in
week
11.
My
name
is
Lachlan
Evensen.
Before
we
get
into
this.
Let
me
remind
everybody
that
this
meeting
will
be
recorded
and
posted
to
a
public
forum.
Youtube
and
everybody
must
adhere
to
the
kubernetes
code
of
conduct,
which
states
please
be
excellent
and
awesome
to
each
other.
Let's
get
into
it.
We've
had
an
event
for
24
hours,
so
I'm
interested
to
hear
all
the
updates,
starting
with
Kendrick
enhancements.
B
A
C
I'm
about
to
ruin
your
2/6
so
see,
I
see
you
know
everyday
everyday.
Everything
is
a
mess
today.
I
put
it
last,
you
know
because
right
we
don't
actually
know
it,
we
don't.
Actually
we
don't
actually
have
something
to
blame.
We
don't
know
to
say
we
don't
know
what
particular
thing
is
broken,
but
actually
before
we
get
into
the,
let
me
go
with
some
better,
a
some
slight,
a
some
better
next,
so
a
couple,
not
a
couple
dorable
events
I
went
down
the
wire
a
in
the
last
24
hours
a
so
there
is
82
532.
C
There's
a
that's
an
issue:
kubernetes
kubernetes
in
a
lot
of
people
from
the
signal
through
life
cycle,
they're,
gonna
start
working
on
replacing
a
lot
of
jobs
are
relying
on
cuba
with
cluster
api,
which
is
amazing.
The
other
remarkable
thing
is
it's
a
PR
on
testing
pro
14,
a
twenty
four
one
that
was
sent
by
stephen
yesterday,
he's
been
doing
a
lot
of
cleaning
around
testing
pro.
C
If
you've
been
keeping
up
with
the
mailing
list-
and
you
probably
saw
some
sound
like
a
five
or
10
emails,
when
they
were
going-
go
to
the
mailing
list
and
a
in
plus
in
the
last
couple
hours
so
far,
we
don't
we-
we
haven't
actually
been
able
to
see
a
pattern.
You
know
a
to
see
a
pattern
in
a
you
know:
the
failure.
There
are
a
handful
of
jobs
that
fail
if
we
would
simply
with
similar
a
with
similar
error
messages
and
I
post
in.
C
If
you
are
interested
I
post,
a
remote
holding
the
issue,
most
of
them
most
of
them
sound
like
there's
so
a
so.
For
the
most
part,
all
the
jobs
are
DCP
based
and
when
a
whenever
you
create
a
whenever
to
create
a
cross
run,
DC
page
you
have
to
you,
know,
get
a
get
a
get
a
DCP
project,
there's
a
there
for
the
most
part,
there
is
always
some
issue
a
handling
they
disappear.
A
chemically
doing
something
with
the
JCP
project
is
somewhere
along
the
way
in
so
many
some
other
jobs.
C
There
being
a
lot
of
time-
oh
and
I'm,
not
trying
to
reach
the
the
control
plane
for
a
control
plane
for
the
coaster,
but
again
so
far
we
don't
have
a.
We
don't
really
have
a
reason,
especially
because
a
lot
of
a
lot
of
those
actually
have
just
been
flaking
and
in
the
past,
in
the
past
couple
hours,
they
actually
has
some
green
drones,
which
looks
good,
but
that
is
actually
the
exact
same
thing
that
happened
yesterday.
C
A
there
were
a
lot
of
failures,
green
drones
and
then
lay
a
late
at
night
or
early,
depending
where
a
whatever
you
are
a
more
favorite,
more
failures
that
started
it
started
happening
and,
besides
that,
the
the
other
a
couple
things
that
I
and
I
have
to
mention
his
master
blocking
GCE
goes
master
Syrio
that
one
a
double
actually
it
last
couple
runs
fail
and
it
might
be
related.
Today
it
was
a
to
the
issue
that
we've
been
seeing
a
12-8
throughout
the
bore
a,
but
he
may
also
be
an.
C
You
may
also
be
there's
a
slight
chance.
You
may
also
be
an
issue
with
the
with
the
update
to
the
cluster
out.
Scaler
a
couple
PRS
a
when
you're
cutting
to
master
a
yesterday
in
the
day
before
so.
For
that
one
we
just,
we
just
need
more
information
to
make
sure
that
a
it
is.
It
is
a
cluster
autoscaler.
But
besides
that,
we'll
keep
a
table,
keep
an
eye
on
it
and
investigate
to
see
if
we
can
get
any
more
in
pay
any
more
definitive
information.
C
Other
big
thing
is:
there
is
a
failure
on
mastering
forming
on
Escalade
on
the
scale
performance
of
the
scale
performance
job.
This
one
is
new
failure,
so
we
need
a
prey.
The
preferable
thing
will
be
again
to
create
an
issue
and
get
someone
from
Cisco
ability
to
take
a
look
at
it
and
just
be
able
to
tell
us.
This
is
something
that
we
need
to
fix,
or
it
just
a
flake.
A
A
C
A
Just
looking
at
the
commits
there
I
think
that's
on
master
and
we
had
to
greed
and
runs,
but
yeah
I
think
maybe
we
should
I
should
ping
that
issue
owner
just
in
case
to
take
a
look
for
the
auto
scaling,
one
that
you're
calling
out.
But
the
interesting
thing
is:
is
it?
Is
it
failing
on
auto
scaling
problems?
I
need
to
go,
find
it
hang
on.
C
Yes,
oh
yes,
oh
I
forgot.
Yes,
so
that's
definitely
a
good
thing
to
mention
it.
It
doesn't
really
look
like
I
might
be
really.
It
doesn't
really
look
like
him
either
related
to
the
cluster
autoscaler
and
all
the
peers
of
when
a
were
specifically
related
to
the
cluster
or
scale
norther
Eris
cally,
at
least
not
a
no
other.
That
I
saw.
A
D
A
A
C
A
The
last
time
what
yesterday
morning
was
green,
there's
been
one
commit
going
to
master
and
we
had
48
hours
of
green
before
that.
Essentially
dims
are
saying
plus
one.
What's
everybody
else
thinking
what
a
word
she'll
gap
telling
you
George,
should
we
ship
and
I
see
one
based
on
the
current
CI
signal?
Well,
should
we
wait
another
24
hours
so.
C
C
We
I
will
say
that
it
doing
the
pushing
the
release.
Candidate
is
good.
They
only
put
the
patina,
but
then
again,
you
know
on
the
policy
Saturday
on
the
policy
set
of
things
and
actually
sticking
with
a
release,
blocking
criteria,
a
criteria
and
all
that
we
will
have
a.
We
will
have
to
wait
for
everything
to
wait
for
everything
to
go.
Greenwood.
You
know
a
general
just
forgetting
the
CI
signal,
just
forgetting
to
see
a
signal
thing.
C
A
A
E
C
Actually,
I
should
at
that
detail
into
a
in
the
issue
I
mentioned
in
the
conversational
day,
on
testing
ops
and
no
one
day.
No
one
seems
to
think
that
that
was
related
in
any
way
and
I'm
in
Katherine
and
everyone
from
six
testing
they,
you
know
they
are.
Ultimately
the
experts
on
the
experts
of
the
yeah.
A
F
A
A
A
A
Sound,
okay,
we'll
go
through
the
rest.
If
anybody
else
has
a
sorry
to
harp
on
about
this,
it's
a
it's
a
challenging
decision
to
make
so
I
appreciate
your
patience
thanks
George
and
thanks
for
all
your
continued
effort
in
kicking
this
along.
It
went
from
very
happy
to
extremely
on
fire
within
about
an
hour
yesterday,
bug
triage.
G
It's
just
I
had
triage,
so
we
have
a
couple
of
minor
things
that
came
up.
There
was
an
issue
that
was
filed
for
the
CI
signal.
Flakes
there's
also
a
reopened
issue
that
is
flagged
is
important
soon,
because
the
PR
that
had
been
submitted
for
it
doesn't
doesn't
actually
resolve
it,
but
another
PR
which
is
on
track
to
resolve
the
issue
has
been
filed,
there's
also
flag
important
soon,
but
it's
not
flagged
in
the
milestone
1.16.
G
A
A
E
I,
don't
think
it's
at
least
blocking
as
such,
but
we
might
cherry-pick
it
later.
That's
the
question.
I
asked
Tim
all
Claire
and
I
do
have
a
PRN
progress,
eight
to
five
one
four,
so
you
know
if
Tim
changes
his
mind,
then
we'll
see
what
we
can
do
about
it,
but
it's
very
localized
change
to
just
that.
You
know
exact
probe,
so
we'll
see
it's
waiting
for
a
team
or
player
to
you
know,
get
active.
I
haven't
seen
him
online.
Yet.
D
Everyone
so
for
dogs
today,
we'd
only
have
much
update
so,
which
is
good.
We
have
our
dogs
in
you're,
licking
them.
I'm
tracking
right
now
is
of
this
PR,
the
instruction
for
switching
to
iptables
legacy.
So
I'm
tracking
that
it
looks
like
the
person
that
submitted
it
is
very
active
and
I
just
about
to
messaging
right
now.
So
that's
the
only
thing
that
I
should.
I
spotted
a
1.16
milestone.
I'm
trying
to
get
in
the
pr
was
submitted
yesterday
evening,
I
think.
Never
we
shop
and
I'm
trying
to
get
our
dads.
A
A
D
You
still
be
just
seen
if
you
look
at
the
comments
that
you're
selling
told
me
this
needs
to
go
out
for
1.9
16,
but
one
thing
I'm
trying
to
do
is
I'm
just
keeping
it
house.
That
was
why
I
said
a
minor
thing,
I'm
trying
to
make
sure
you
know,
I'm
keep
an
eye
on
the
undie
on
the
PL
and
get
a
match
as
soon
as
possible.
Since
he
has
signed
a
ticket
to
me
and
I
already,
he
kind
of
implied.
D
It
should
be
part
of
the
one
point
sixty
mile
milestone
to
be
tracking
so
yeah.
If
you
look
at
you
know,
yeah
signed
out
to
Tolkien
and
also
to
dogs,
and
he
instructed
our
dogs
to
get
it
as
soon
as
possible.
So
that
was
my
I'm
tracking
it,
but
I
don't
think
it's
something
that
blocks
dogs
or
realities.
1.16,
announcement,
dogs,
yeah,
okay,.
A
E
H
Hi,
you
don't
have
that
big
of
an
update
so
we're
green
or
waiting
on
the
release.
Candidate,
deprecations
and
removals
have
been
collected
for
the
current
state
and
added
to
the
release,
notes
draft
which
I
provided
a
link,
so
people
can
start
adding
their
changes
and
then
the
issues
that
were
mentioned
yesterday
are
still
sort
of
relevant,
so
I
added
those.
A
A
I
So
we
don't
have
our
tailor
to
death.
I'm
filling
in
I
can
report.
Everything
is
green.
We
still
have
the
blog
content
coming
in.
So
we're
happy
with
that
and
Taylor
has
a
meeting
with
people
at
the
CNCs
just
to
make
sure
all
the
dates
that
we
require
for
the
blog
posts
are
all
in
line.
So
we're
green,
happy.
Okay,.
A
David
moving
along
here,
emeritus
leads,
don't
have
anything
there,
release
lead,
update,
I'm,
gonna
call
this
the
release
yellow,
even
though
we
have
CI
signal
and
in
red
I
would
like
to
see.
Green
CI
signal
obviously
looks
like
we
have
no
PRS
remaining
in
the
queue
to
go
into
master,
which
is
great,
and
next
upcoming
milestones.
A
It's
the
RC
one
today
codes
or
at
the
same
time
I
think
we
should
invoke
code
Thor
at
the
same
time
as
the
RC
one,
and
that
leaves
the
cherry-pick
deadline
still
at
nine
twelve,
which
we
may
give
another
day
back.
The
only
decisions
I
think
we
need
to
make
now
is:
if
we're
going
to
go
with
us,
he
one
is
anybody
advert
against
lifting
code
freeze
and
going
into
code,
though,
which
means
everything
will
then
need
to
be
cherry-picked.
A
A
Nope,
okay
and
I
did
actually
skip
their
update.
So
sorry
about
that
I
think
the
the
best
path
forward
is
I'll
ping
Jung
on
the
cig
release
channel
and
when
he
wakes
up
tomorrow,
we'll
have
him
cut
a
c1
unless
anybody
from
release
branch
management
can
do
that
today.
So
that
should
give
us
an
additional
12
hours
to
see
if
we
can
get
CI
signal
green
and
have
young
cutter
during
his
day
China
tomorrow,
which
would
be
our
evening.
A
A
No,
okay,
so
tomorrow
we
have
burned
down
again.
At
the
same
time,
Gwen
will
be
leading
it
for
or
as
unavailable
tomorrow
morning,
but
I
will
send
out
an
update
and
you
will
follow
release
updates
in
the
cig
release
channel
as
they
happen
for
the
next
24
hours.
Thank
you
very
much
for
everybody
being
persistent
at
this
phase,
where
it
went
nearing
the
end,
so
I'm
very
excited
to
see
1/16
making
good
progress.
If
you
need
anything
from
me,
feel
free
to
ping
me
on
slack.