►
From YouTube: k8s 1.16 - Week 11 - Release Team Meeting 20190913
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
A
We
just
released
our
c2
so
good
times
plenty
to
catch
up
on.
First,
let
me
remind
everybody
that
this
meeting
is
being
recorded
and
will
be
posted
publicly
to
YouTube
and
that
all
conversations
fall
under
the
kubernetes
code
of
conduct,
which
states,
let's
be
excellent
to
each
other.
A
lot
has
happened
in
the
last
24
hours.
I'm
sure
you
all
work
up
to
a
sig
release,
channel
of
full
of
messages,
we'll
try
and
catch
you
up
on
all
that
and
all
the
happenings.
Let's
get
into
it.
A
C
Everyone
in
the
world
will
see
a
signal
yesterday.
The
the
big
news
is
that
yesterday
we
were
trying
to
get
a
couple,
a
couple
cherry-picks
into
one.
Sixteen,
the
cherry-picks
were
constantly
failing
on
polka
polka
by
lady
skilled
mark
ii.
Between
each
is
he
big,
which
is
a
job
hosted
by
six
color
basic
scalability,
turns
out
that
a
recent
change
in
their
performance
testing
suite
a
essentially
was
they
was
the
big
recently.
C
It
was
a
big
reason
for
all
day
for
all
the
failures
and
thanks
to
Lumiere
in
jordan,
jordan,
we
join
a
jordan
cherry
j-jordan
managed
to
figure
out
the
PR
that
we
needed
that
we
needed
to
cherry-pick
into
point
into
one
sixteen
to
stop
all
the
press.
Okay,
all
day,
please
all
the
cube
mark
piece
of
wits
from
failing,
also
world
intervention.
This
was
a
strictly
related
to
any
anything
anything
I
wanted
to
get
into
the
116
branch,
all
the
priesthood
and
all
the
cube
mark
resubmits
for
master.
C
That
way
they
were
so
coming
back
to
the
story.
Coming
back
to
the
story,
Jordan
Liggett,
they
figure
out
the
solution.
Also,
the
people
from
six
scalability
open
a
new
issue
on
kubernetes,
perfectest
and
797,
which
are
linked
under
the
nori
notable
events.
They
are
proposing
a
couple
avenues
to
prepare
to
prevent
this
from
happening
right
now.
C
It
seems
that
the
preferred
solution
is
to
version
a
perfect
test,
so
to
prevent
a
resubmit
from
breaking
in
release
branches
and
other
than
that
they
now
go
a
now
going
with
the
usual
CI
signal,
update,
116,
balking,
116,
informing
all
tests
are
passing,
is
one
note
and
116
blocking.
We
have
a
AGC
cause,
kubernetes
beta
slow
that
is
marked
as
failing.
This
is
actually
just
this
is
this
is
due
to
a
1,
a
1
or
failure
to
happen
happened
yesterday.
C
The
for
a
formulated
fronts
have
been
completely
a
completely
green,
so
not
a
right
now
not
in
to
worry
on
that
in
and
FY
FYI,
because
this
has
nothing
to
do
with
the
116
bodies,
which
were
just
throwing
it
out
there.
Something
the
sky
signal
is
going
to
pursue.
Is
that
the
master
scale
correctness
a
job
is
right
now
a
labeled
as
failing
because
of
a
signet
way
because
of
a
failing,
Sydney
Sydney
networks,
network
test,
and
that
is
it
for
today's
is
a
signal
update.
Anyone
has
any
questions.
Comments,
concerns.
D
Yeah
so
one
for
me,
I,
so
I
was
looking
at
some
of
the
tests
yesterday
and
notice
that
the
cube
mark
test
was
not
on
our
blocking
board,
because
that's
something
that
we
want
to
do
like
I
started
a
PR
to
drag
the
things
that
are
set
up
as
presubmit
blocking
and
pretty
submit
informing
into
our
boards.
Does
that
make
sense.
C
As
first
I
know,
that
will
be
a
new
way
of
organizing
things,
but
put
those
make
sense?
Don't
you
normally
the
way
that
you
have
to
go
for
the
way
that
you
have
to
look
for
this
ones
is
that
you
had
to
explicitly
go
outside
of
the
synchronous
dashboard
and
into
the
presubmit
dashboard
and
then
and
then
a
monitor,
monitor,
Peaks,
but
yeah
I
mean
that's
a
possible
thing
to
do.
We
can
just
a
copy
over
all
the
pork
in
pre
submits
it
taps
into
our
yeah.
D
C
Just
just
once
about
a
small
note
that
came
to
my
mind,
I
think
at
the
at
some
point,
I
actually
I
actually
asked
about
this
back
in
my
junior
CI
single
days
and
in
the
argument
in
the
argument
was
a
monitoring
piece
of
meats.
It
was
not
strictly
within
the
scope
of
CI
signal
and
it
was
a
sick
testing
kind
of
thing,
and
that
was
the
argument
for
keeping
those
two
dashboard
separate
it
take
me
technically.
It
is
something
that
affects
their
release,
whether
we
can
merge
PRS
or
net,
so
it
makes
sense,
but
yeah.
A
Yeah,
the
only
other
thing
I
want
to
add
is
we
really
should
pursue
that
versioning,
because
if
you
go
back
and
look
at
any
of
the
stable
release
branches
there's
those
four
unsure
those
things
are
failing
in
all
those
release.
Branches
that
now
need
to
be
cherry
picked
back.
Rad
changes
that
are
only
in
master
cradles.
D
Yeah
so
I
yeah,
so
I
asked
Jordan,
and
this
is
that
change
specifically
was
only
introduced
in
116.
The
one
that
got
all
crazy
yesterday
was
only
introduced
in
the
116
time
frame,
so
it
only
needs
to
be
it
only
needed
to
be
cherry
pack.
Cherry
picked
back
to
that
branch,
but
but
yeah
in
general,
I,
don't
think
our
dashboards
match
up,
and
a
lot
of
that
is
due
to
the
lack
of
config
for
core
annotations
on
some
of
those
shops.
There's
also
something
I
would
like
George.
D
It
also
removes
the
it
removes
the
sig
release,
orphaned,
dashboard
and
the
tests
that
were
on
that
one
because
they're
again,
unmaintained
we've
reached
the
end
of
the
cycle,
so
it
doesn't
make
sense
to
keep
them,
but
that's
a
combination
of
things
that
are
running
on
GC
that
may
not
necessarily
be
under
the
scope
of
provider
GCP,
so
yeah.
I
want
to
get
that
merged
soon.
Yeah.
That's.
C
C
As
far
as
far
as
I
know
ray
so
so
right
now,
the
to
my
current
knowledge,
this
is
not
something
that
we
should
worry
about,
but
yeah
DC
I
will
check.
I
will
check
in
with
sig
scalability
and
post
all
these
things
on
slide,
so
a
gel
can
keep
up
with
it,
keep
up
and
stay
up
to
date
with
the
conversation,
but
essentially
this
this
failure
as
far
as
per
second
as
far
as
I've
been
looking
at
it.
C
He
he
came
from
the
change
from
all
the
peers
emerged
right
after
right
after
code
talk
and
he
might
possibly
chose
you
might
possibly
be
a
failure
with
the
weight
of
the
test.
You
know,
though,
I
still
have
to
don't
take
my
word
on
that
still
investigating,
but
way,
but
we'll
follow
up
on
that
and
tell
you
if
they
feel
a
if
it
is
something
that
wish
that
we,
as
the
release
team,
should
worry
about.
C
D
Was
also
a
note
earlier
today
from
sig
scalability
regarding
they
opened
a
separate
issue
about
the
perf
tests,
repo
which
I
actually
didn't
know
existed
until
they
broke
stuff
about
if
they
should
change
their
versioning
scheme
for
purpose
or
set
up
additional
branches.
So
let
me
find
that
issue,
but
I
think
we
should
comment
on
it
as
well.
You.
E
Okay,
so
I
say
that
we
are
green
today,
which
is
a
good
sign
and
we
got
a
good
number
of
open
issues
we
have
only
one
and
that
one
is
issue
is
related
to
the
release
notes
umbrella.
So
this
is
good
to
go
regarding
PRS
we
can
follow
up
and
so
guys
d16
a
milestone,
but
as
far
as
I
know,
all
four
are
targeting
born
16
born
now,
I'm,
not
sure
I
have
not
been
there.
E
Yesterday
I
think
there
was
some
discussion
around
that,
but
not
sure
should
we
go
to
each
of
that
PR,
but
as
far
as
the
salt,
they
are
all
on
hold
and
they're.
Not
cherry
pick
the
fruit.
So
it's
mostly
like
that
they're
going
to
wait
for
the
release
and
then
get
much
it
after
me,
41
6,
the
modern,
recycle.
E
A
D
A
F
Hi
everyone-
this
is
a
Sunday,
so
for
dogs
update.
We
don't
really
have
anything
interesting
to
announce
which
is
good
I'm,
just
like
right
now,
I'm
trying
to
pull
together
all
the
necessary
PR
that
is
supposed
to
go
out
before
the
release,
but
one
cannot
I
also
need
to
talk
about
the
announcement
that
I
sent
out
yesterday.
F
That's
we
are
going
to
out
the
the
kids
website
freeze
to
insult
24
hours
before
before
my
I
think,
when
I
announced
that
someone
raised
something
very
important
that
the
release
might
be
delayed
by
two
days,
because
I
told
them
before
we
are
going
to
freeze
it
before
the
September
26
right.
So
without
new
information,
I
need
to
update
everybody,
but
if
I
do
that,
I
would
like
to
get
a
confirmation
from
you
from
the
from
the
team
before
I
go
ahead
and
make
that
kind
of
announcement.
Apart
from
that,
nothing
else
is
happening.
F
G
H
Happy
Friday
everybody
so
we're
still
seeing
sitting
nice
and
green,
no
major
updates
today,
just
a
few
little
ones.
We
have
some
tooling
improvements
or
a
tooling
improvement
PR.
That's
we
put
in
this
morning.
We
should
have
the
release,
notes
updated
for
our
c2
sometime
today,
we'll
also
be
working
on
moving
the
release,
notes
structure
over
to
the
new
templated
format,
as
well
as
just
update
it
to
the
page
size
on
the
Google
Doc.
So
that's
that's
it
for
today
any
questions
or
anything
I
missed.
G
Happy
Friday,
everybody
I've
got
some
bad
news,
we're
completely
red,
totally
blocked
just
joking
joking
we're
still
all
green,
hey
everything
is
looking
fantastic.
We
got
our
blog
draft
all
done
so
now.
It's
just
gonna
be
grammatical.
Updates
flow
changes,
simple
things
like
that:
I
posted
the
link.
If
you
want
to
take
a
look,
you
don't
have
access
just
request:
it
don't
get
that
taken
care
of
I'd
be
proud.
Everybody.
D
A
D
A
A
D
A
D
A
D
A
D
Emeritus
lead,
so
we
have
we've
gone
around.
We've
had
chats
with
a
bunch
of
our
lovely
leads
and
shadows,
I.
Think
everyone's
pretty
much
set
up
I
think
we've
got
one
more
role
pending
to
nominate
a
lead.
The
shadows
have
ideas
of
what
they
want
to
do
next
season,
which
is
cool
so
outside
of
that.
If
you
have
questions
comments,
concerns
for
us,
if
you
just
want
to
chat
talk
about
what
your
future
looks
like
in
cig
release
or
elsewhere
like
please
feel
free
to
reach
out.
A
A
So
just
milestones
to
get
everybody
on
the
same
page.
I
know
we've
discussed
I'll,
see
to
that.
It
went
out
today,
and
that
was
basically
to
address
some
regressions
and
some
critical
issues
to
give
people
a
fresh
foundation
to
test
on,
and
the
idea
is
that
we
make
it
more
stable
than
zero,
rather
than
pushing
all
these
commits
in
2.1
and
learning
a
dot
one.
Three
days
after
we
release
so
that
happened
today.
The
release
day
has
moved
to
918
I've
now
updated
the
calendar.
A
What
this
also
means
is
I
want
to
put
in
an
additional
two
burndown
calls
just
to
make
sure
that
we're
all
communicating
leading
up
to
the
release
there
may
be
quick,
but
that
will
mean
Monday
Tuesday
Wednesday.
Next
week
you
will
have
burned
down
meetings
up
until
that
date,
release
retro,
oh,
is
next
Thursday,
that's
919!
It's
during
the
kubernetes
community
meeting
at
10:00
a.m.
Pacific.
We
will
have
somebody
chairing
that
meeting.
I
put
the
link
there.
If
you
think
of
anything,
that's
been
challenging
that
we
should
address
in
future
releases.
A
We
should
at
least
talk
about
that.
That's
kind
of
the
retro
format
of
what
went
well,
what
didn't
go
well
and
what
are
we
going
to
convey
to
fixing
in
the
next
release
or
releases
so
make
sure
as
you're
thinking
of
things?
Please
go
and
add
them,
because
that
is
really
useful
for
subsequent
release
teams,
and
it
also
creates
a
flurry
of
issues
where
we
can
start
to
move
things
in
the
right
direction.
A
A
D
So
just
a
note:
can
we
also,
in
addition
to
updating
calendar
invites?
Can
we
also
make
sure
that
we
slot
the
rc2
and
the
move
date
in
the
release,
time
line
for
the
116
readme?
Just
so
that
we're
and
then
also
for
for
roles
in
general,
as
we
move
into
the
end
of
the
cycle
or
as
you
have
time,
please
take
a
look
at
the
things
that
you're
assigned
you
in
release
and
either
turn
them
down,
wrap
them
up
or
get
ready
to
assign
them
to
the
next
lead.
A
Thank
You
Steven
I
also
was
just
going
to
quickly
walk
the
milestone
to
see.
What's
left,
I
did
take
a
look
this
morning,
there's
only
five
open,
four
of
them.
A
cherry-picks
and
one
is
the
release,
notes
known
issues,
I'm,
not
terribly
concerned
that
we
have
to
walk
that,
but
I
wanted
to
make
sure
that
we
should
be
closing
at
that
milestone
at
the
end
of
this
release.