►
From YouTube: k8s 1.16 - Week 4 - Release Team Meeting 20190722
Description
Release details: http://bit.ly/k8s116
A
Let's
see
if
that
works
connected,
wonderful,
okay,
let's
kick
this
off
hello
and
welcome
today
is
Monday
July
22nd.
It
is
week
four
of
the
1/16
kubernetes
release.
This
is
the
weekly
release
team
meeting.
Welcome
everybody
reminder
that
this
meeting
is
being
recorded
and
will
be
shipped
to
YouTube
after
this
and
all
conversations
fall
under
the
kubernetes
code
of
conduct,
which
says,
please
treat
everybody
with
respect
in
your
conversation.
A
Thank
you
for
adhering
to
that.
It's
wonderful
to
see
everybody's
faces.
I
know,
we've
got
a
we've
had
a
few
outages
on
the
internet
this
morning,
so
everybody
looks
to
their
faces.
Looking
a
little
long
and
certainly
week,
four
feels
like
I,
think.
The
theme
for
this
week
is
getting
down
to
business.
Seeing
the
enhancements.
Freeze,
roll
in
so
I'm
excited
to
hear
all
your
updates
a
couple
of
housekeeping
things.
A
If
we
could
have
a
note-taker,
you
get
the
prestigious
slot
of
putting
your
name
as
the
note-taker
at
the
top.
That
makes
it
super
easy
for
me
to
continue
with
the
agenda.
Yeah
get
hubs
having
problems,
Josh
and
Bob
was
just
saying:
zoom
was
having
regional
outages
earlier.
So
here
we
go
and
please
place
your
name
in
the
attendees
section,
along
with
your
role.
That
would
be
fantastic
and
without
further
ado,
let's
get
into
it.
We
will
start
with
the
enhancements
update
with
Kendrick
thanks
Kendrick
I'm.
A
Thank
you,
Bob
I
might
just
send
out
a
reminder
of
the
sig
leads
as
well
with
the
enhancements
link
and
just
say:
look
if
you
have
anything
on
here
that
is
in
the
it's
at
risk,
correct
in
the
at
risk
column.
Please
go
and
make
sure
that
it's
updated
accordingly.
Just
so
all
the
sig
leads
are
aware,
and
I'll
also
just
remind
them
that
7:30
next
Tuesday
is
the
enhancements.
Freeze,
thanks
for,
is
that
the
link
to
the
enhancements
doc
perfect.
Thank
you
very
much.
D
How
are
you
okay?
So
we
have
we
start
with
master
blocking.
We
have
nine
passing
tests,
which
is
like
better
scenario
than
last
week.
Two
failing
one
of
them
has
been
an
ongoing
issue,
although
all
of
this
information
has
been
updated
in
document.
So
these
issues
the
same
as
last
week,
it's
about
a
nodes
resizing
test,
failing
I,
think
that
the
last
update
that
we
have
is
that
it's
up
for
a
triage,
but
no
updates
are
available
yet
and
also
we
have
a
newer
one
that
we
have
just
begun
investigating.
D
Also
failing
it's
an
issue
that
the
Alpha
features.
There
hasn't
been
a
follow-up
issue
yet
because
get
help
was
down.
I,
don't
know
this
title
yeah,
but
as
soon
as
we're
done
with
this
meeting,
and
if
github
is
available
now
we
will
be
able
to
to
send
a
full
of
issue
and
well
so
that's
for
the
failing.
So
that's
good
on
the
blocking
side,
and
we
have
three
flaking,
nothing
too
wrong,
nothing
to
worrying,
and
then
we
have
on
the
master
informing.
D
So
it's
not
too
worrying
yet,
but
since
it
is
new
and
it
has
been
failing
consistently,
yes,
we
should
keep
an
eye
on
it
like
for
now,
just
in
case
it
becomes
failing
and
then
finally,
on
the
release,
miscellaneous
everything
seems
like
reason:
we
have
five
passing
non
failing
and
three
flaking
again,
nothing
to
worry
about.
Everything
has
been
like
consistent
just
one
recent
and
the
same
story
like
we
should
keep
an
eye
on
it.
It's
just
in
case.
D
It
goes
wrong
and
finally,
following
up
with
the
scalability
issues
that
we
have
been
having
with
scalability
Elina,
did
a
follow-up
document
with
some
of
the
issues
that
concern
both
scalability
and
CI
signal
and
the
link
is
there
and
the
updates.
Basically,
there
are
four
issues.
One
is
closed.
Now
two
of
them
are
blocked
for
investigation,
and
one
of
them
is
being
like
actively
I
mean
the
the
three
of
them
are
actively
being
investigated,
but
one
of
them
is
more
actively
relying
with
more
concrete
solutions
and
the
other
two
are
blocked
for
investigation
like
officially.
A
A
D
A
D
D
A
E
F
A
F
Two
minutes:
okay,
so
a
lot
of
the
a
lot
of
the
failing
jobs
that
were
on
informing
before
that
were
related
to
up
debt
upgrade
downgrade
tests.
Those
are
basically
the
ones
that
we
identified
that
didn't
have
an
owner
and
have
consistently
not
had
an
owner,
so
we
created
a
new
secret
least
orphan
board.
So
what
will
happen?
Is
things
will
live
on
that
board
for
a
little
bit?
If
we
determine
that,
no
one
is
going
to
own
those
things.
It'll
get
dropped
off
at
the
end
of
the
cycle
or
something
that's
my
current
guidance.
F
We
might
change
that.
We
might
do
it
sooner
since
the
upgrade
downgrade
ones
have
been
consistently
not
touched,
but
if
you
want
to
see
the
PR
for
that
I
linked
it
in
the
notes
and
then
the
board
is
also
linked,
so
so
I
think
that
took
care
of
eight
of
the
things
that
we're
failing
on
the
informing
board.
G
So
first
some
of
the
informational
statistics
about
how
are
we
staying
right
now
we
have
about
75,
not
flaky,
shows
up
in
adidas
milestone
along
with
61,
open
PRS,
and
the
total
number
of
fishers
is
91
it
compared
to
the
last
week.
I
don't
have
exact
numbers,
but
it's
I'm
Sookie
and
one
question
related
to
that.
For
now
should
I
add
those
numbers
to
the
document
or
just
links
are
okay.
It
might
be.
A
G
Adam,
okay
from
our
side,
considering
that
it's
still
early
before
the
code
phrase,
we
think
that
everything
is
okay
and
I
would
probably
say
that
we
are
green
from
the
bug
triage
and
beside
that
we
have
the
spreadsheet
now
available
and
you
can.
There
is
a
link
in
the
document
and
I
have
also
a
question
regarding
debt.
How
often
do
we
want
to
refresh
that
one,
because
the
Refresh
has
to
be
triggered
manually?
G
E
A
H
All
right
so
for
ducks
it's
still
like
Ellen
the
release
to
for
most
of
our
tivities,
but
right
now
we
are
mostly
tracking,
then
an
announcement
sheets
so
split
it
in
between
us
and
and
just
divided
between
the
shadows.
So
far,
so
how's
everything
looks
good
so
far
we
don't
have
anything
major
blocking,
but
I
believe
as
time
progresses
in
the
release.
We
have
been
some
more
like
no
more
detail
objects,
but
so
far
everything
is
going
good.
I
F
A
Just
going
to
say
is
there
anything
we
can
do
to
broaden
that
message
about
how
the
docs
need
to
be
the
doctor
is
that
what
you're
referring
to
session
was
this
Doc's
metadata?
That
needs
to
be
added
to
pay
us
so
that
we
generate
things
correctly?
Is
that
what
you're
referring
to
or
can
you
clarify
please.
I
Yes,
this
is
our
SPR
has
been
merged
last
week,
so
we
expect
the
first
documentation
enhancements
like
this
in
the
next
couple
of
weeks.
I
think
so,
and
but
we
are
referring
to
that,
we
want
to
change
to
release
notes
which
are
auto-generated
from
the
pull
requests
directly
at
the
contributor
odds,
contributors
release,
notes
line
at
the
PR
at
the
bottom,
so
that
we
don't
have
any
manual
effort
between
auto-generating
and
putting
it
on
the
website
anymore
is.
A
F
Yeah
yeah
I
think
that
this
is
something
that
should
feed
into
whatever
documentation
we
have
so
maybe
the
communique
community
developing
are
developing
some.
You
know
the
documentation,
that's
there
about
submitting
pull
requests,
as
well
as
the
any
information
that
BOTS
spit
out
about
how
to
do
certain
things.
So,
there's
a
release,
notes
I,
think
there
is
a
mention
from
Kate,
see
I
bought
the
KCI
Reba
or
something
that's
or.
F
So
the
docks
related
thing
I
sent
a
note
out
to
ke
dev
before
merging
that
PR
about
the
addition.
So
there
are
instructions
there
and
the
instructions
basically
link
back
to
the
PR.
The
PR
includes
the
the
new
the
the
new
github
PR.
Template
includes
instructions
on
how
to
do
the
note
properly.
So,
hopefully,
those
are
clear
enough.
I
think
we
like
shedded
a
little
bit
on
them
to
make
sure
that
they
were
clear
enough.
So
hopefully
that's
all
good.
A
F
F
F
L
Happy
Monday
everybody.
This
update
is
short
and
simple.
We're
green
we're
taking
a
look
at
the
alpha
release,
features
this
week
and
then
we're
going
to
be
reaching
out
to
these
cig
leads
for
items
and
interest,
and
it's
kind
of
starting
to
create
those
meetings
to
see
what
should
be
on
the
which
would
be
in
the
spotlight
for
this
coming
release
other
than
that
no
blockers,
just
just
communicating.
A
L
M
Hello,
happy
Monday
so
for
release
branch
manager
management.
We
released
the
first
offer
last
week
and
thanks
to
Steven
we
have
the
two
parts
of
the
video
for
the
for
the
cutting
process
on
YouTube.
So
anyone
interested
please
watch
the
videos
we
have
upcoming
cards
for
the
alpha
2
scheduled
next
week,
next
Tuesday.
M
F
F
So
we
are
so
the
story
there
is
I
can't
grant
anyone
access
yet
because
we
essentially
have.
We
essentially
have
one
role
in
GCP,
which
is
like
the
god
mode
role
to
be
able
to
do
all
of
the
stuff
or
nothing
right.
So
I
recently
got
owner
access
to
our
GCP
instance
project.
So
I
can
start
dumping.
The
I
can
start
dumping.
The
I
am
creds
our
privileges
and
building
a
role
that
is
more
closer
to
like
a
viewer
role
for
release
manager
associates.
F
F
We
still
have
to
figure
out
how
we're
going
to
handle
that
across
the
cycle
and
like
what
are
the
steps
and
hurdles
that
people
have
to
jump
through
to
be
granted
access
for
that
so
again,
I'm
sorry
that
I
can't
just
like
we
can't
just
give
it
out,
but
we're
not
we're
not
there.
Yet
I
do
encourage
anyone
who
is
interested
in
viewing
the
process
to
one
watch
the
videos
that
was
part
of
the
point
of
doing
the
videos
so
that
we
can.
F
A
Technically,
here
Steven:
is
it
worth
the
release
engineering
team
just
to
see
if
they
can
find
a
candidate?
Can
you
actually
dot
dry
run
through
the
process,
pre
pre
pre
game
day
and
then
make
sure,
because
I
think
the
only
thing
is,
if
you
require
access
like
how
do
we
on
board
more
associates?
I
guess
is
the
overarching
thing
that
is.
A
On
Tuesday,
where
we
risk
you
know
granted,
the
alphas
are
really
early
and
not
really
on
a
fixed
time
schedule.
It
would
be
really
interesting
if
we
could,
you
know,
get
somebody
all
the
access
prior
to
Tuesday.
If
we
wanted
to
have
somebody
else,
because
what
I
can
see
happening,
is
you
and
young
going
through
the
whole
release
and
not
onboarding
any
associates
only
because
it's
so
flippin
hard
to
get
them
the
correct
access
on
the
day
ya.
F
F
E
Okay,
we're
going
to
have
a
shadow
meeting
or
actually
we're
going
to
have
to
shadow
meetings
14
hours
apart
in
order
to
accommodate
the
various
time
zones
as
much
as
possible,
and
so
this
is
just
to
talk
to
the
shadows.
Collectively
the
answer
Annie,
what
I?
What
should
I
be
doing
questions
and
we're
going
to
run
through
kind
of
a
checklist
for
that
and
I
sort
of
established?
E
The
orientation
I
mean
we're
in
week
four
now
so
a
lot
of
people
have
already
started
their
stuff,
but
not
everybody
will
have
particularly
for
roles
that
tend
to
be
more
heavily
loaded
towards
the
end
of
the
release
cycle,
which
is
about
half
of
them,
so
so
I
posted
that
in
the
notes,
the
exact
time
one
of
those
is
in
just
about
eight
hours,
seven
and
a
half
hours
yeah
and
the
one
is
14
hours
after
that.
So
between
those
two,
we
should
be
able
to
catch
people
in
the
various
time
zones.
So.
F
I
would
say
for
anyone
who's
on
the
call
or
watching
it
later.
If
you
are
a
release
team
shadow
or
you
need
to
the
role
in
general
I,
we
are
going
to
cover
it
within
the
shadow
meeting,
but
I
would
I
would
say
if
you
haven't
seen
the
onboarding
doc
that
we
have
please
take
a
moment
to
take
a
look
at
that,
hopefully
cut
through
some
questions.
I
will
link
it
in.
C
A
A
I
am
going
to
send
out
to
the
mailing
list
just
a
reminder
to
all
the
folks,
with
the
enhancement,
spreadsheet
and
anything
that's
in
at
risk
to
be
identified
and
get
the
caps
updated
as
appropriate
and
everything
in
place
so
that
people
at
least
have
a
week
lead
time
to
get
that
in
shape.
Also
next
Tuesday
7:30
is
alpha
2,
so
we
just
discussed
that
briefly.
F
A
note
for
the
enhancements
phrase
I
would
say:
send
that
to
sig
leads
to
ke
dev
and
mentioned
to
Paris
our
community
at
kubernetes
I.
Oh,
that's
that
should
go
in
the
sig
leads
need
to
know.
I,
don't
know,
I,
don't
remember
the
schedule
that
those
things
go
out
but
a
blast.
So
that's,
basically
the
summary
of
like
hey
sig
leads
here's
what's
going
on
and
those
go
individually
to
sigelei
it's
as
opposed
to
any
mailing
list.
So
it's
possible
that
you
may
pick
up
more
people.
There.
A
Okay,
thank
you
that
moves
us
to
open
discussion.
I
have
the
the
first
item
so
II
you
friendly
or
rest
of
the
world
friendly
release.
Meeting
team
I've
went
through.
The
survey
asked
everybody
to
get
back
to
me
by
last
Wednesday
I've
taken
a
look
at
the
results:
the
results
by
popular
vote
here,
11:00
to
12:00,
UTC,
Tuesday
Thursday
starting
week,
ten
and
having
them
weekly,
which
pretty
much
matches
what
we've
done
in
previous
releases
around
burned
down.
So
the
weekly
burn
down
start
on
Tuesday
Thursday
I
will
work
with
the
release.
A
Team
leads
to
get
that
staffed,
but
there
wasn't
too
much
appetite
for
having
weekly
release
team
meetings
in
an
EU
friendly,
timezone
prior
to
burn
down
and
getting
to
the
weekly
burn
down
part.
So
if
anybody
has
any
questions
or
concerns
about
that
who
is
affected
by
this
decision,
let
me
know
otherwise.
I
will
work
to
get
them
scheduled
later
in
the
release.
That's
about
five
weeks
out.
A
F
Sure
so
real
quick,
we
just
did
a
these.
These
things
always
creep
up
on
us
every
quarter,
but
we
did
the
community
update
for
cig
release,
so
every
every
every
quarter
SIG's
are
required
to
present
at
the
community
meeting.
So
we
did
ours.
Last
week
the
slides
are
available
there,
as
well
as
the
video
time-coded,
exactly
where
we
start.
I
think
that
this
is
I
put
required
and,
like
a
question
mark
but
I,
think
it's
something
that
everyone
on
this
call
should
watch
it
some
of
the
stuff.
F
You
are
already
aware
of
in
terms
of
what
we're
doing
on
the
release
team.
What
we've
done
last
cycle,
what
we
plan
to
do
for
the
next
few
cycles,
but
specifically
around
the
release,
engineering
work
and
some
of
the
things
that
are
going
to
be
changing.
We
kind
of
lay
out
what
our
grand
vision
is
for
release
engineering
in
the
next
few
cycles
and-
and
it's
like
I've
had
enough
of
the
conversations
with
with
several
people
individually.
F
That
I
think
that,
like
just
go
check
out
the
recording
see
what
we're
up
to
also
check
out
the
release.
Engineering
brainstorm,
which
is
also
linked
there
and
it
walks
through
essentially
like
Tim
and
I,
sat
down,
and
we
brain
dumped
over
a
few
zoom
calls
for
like
six
hours
or
so
talking
about
like
what
are
the
things
we
think
we
need
to
do
in
on
the
release
engineering
side.
F
So
this
cover
is
like
where
we,
what
we
host
on
what
artifacts
are
generated,
the
way
we
we
build,
publish,
release,
build
release,
publish
kubernetes
and
all
of
those
associated
artifacts.
So
if
you
have
questions
feel
free
to
ask
me,
but
most
of
them
are
answered
in
that
already,
so
please
check
out
the
video
check
out
the
slides
check
out
the
release
engineering
brainstorm.
The
brainstorm
will
become
a
set
of
caps.
It
will
be
like
an
omni
cap
that
describes
like
the
state
of
releasing
kubernetes
in
general
and
will
break
out
into
okay.
F
Well,
how
do
we
do
artifact
generation?
How
do
we
do
publishing
of
images?
How
do
we
do
signing
of
our
Deb's
and
rpms
things
like
that?
So
there
will
be
multiple
caps.
There
are
a
few
caps
already
around
this
stuff
which
again
are
in
the
slides,
but
we'll
go
deeper.
Will
summarize
some
of
the
stuff
that's
existing,
as
well
as
adding
adding
the
content
from
the
the
engineering
brainstorm
to
that.
So
please
again,
please
please,
please
check
that
out
and
let
me
know
if
you
have
questions.