►
From YouTube: k8s 1.16 - Week 6 - Release Team Meeting 20190805
Description
Release details: http://bit.ly/k8s116
A
A
A
Ok,
if
you
would
like
to
take
notes,
please
place
your
name
at
the
top
they're
fantastic
and
this
meeting
is
being
recorded
and
it
will
be
uploaded
to
YouTube,
and
all
conversations
are
subject
to
the
kubernetes
code
of
conduct,
which
states
please
treat
everybody
with
respect
and
be
excellent
to
each
other.
So
please
make
sure
that
all
our
conversations
are
in
that
vein
and
spirit.
It's
wonderful
to
see
you
all!
Let's
get
into
the
agenda!
First
to
kick
off
today
we
have
the
enhancements
update
with
the
enhancements
lead.
Kendrick
take
it
away.
Kendrick
yeah.
B
How's
anybody
going
asks
everybody
doing
and
how's
everything's
going
there
we
go.
Thank
you
got
that
one
figured
out
so
right
now
everything
is
looking
pretty
good
I
only
listed
as
yellow,
because
we
only
have
two
little
minor
things
to
kind
of
talk
about
right
now,
after
enhancement
freeze,
we
had
two
exceptions.
Rollin
one
was
approved,
one
was
denied
so
right
now
we're
sitting
at
39,
which
is
pretty
good,
I'm,
actually
happy
to
see
ten
sitting
stable.
B
The
other
thing
that
we're
waiting
on
that
locky
kind
of
brought
up
last
week
was
there
was
some
conversations
that
were
happening
with
sig
instrumentation,
where
there
were
an
enhancement
or
two
that
were
was
currently
being
worked
on,
but
was
not
being
tracked,
and
this
is
I
think
just
lack
of
knowledge
of
the
process
and
stuff
like
that.
So
I
know
Bob
is
started
initiating
some
of
those
conversations
and
so
we're
still
awaiting
some
feedback
to
figure
out.
If
the
issues
are
gonna
be
opened
and
added
into
it.
C
Morning
afternoon
evening,
everyone
Oh
first
off.
Let
me
start
with
the
usual
the
updater
wiki,
which
week
is
essentially
a
snapshot
of
the
CI
signal
project
board,
and
you
can
see
the
link
right
underneath
my
name
below
that.
If
you
wanna,
if
you,
if
you
want
to
get
a
cool
bedtime
story
for
your
family,
there's
the
one
the
see
a
signal
report
was
sent
early
this
morning.
Actually
it's
actually
it's
not
a
precise
bedtime
stories,
it's
good!
C
For
any
occasion,
if
you
wanna
see
what
the
kubernetes
community
is
working
on,
so
you
know
good
for
any
type
of
pattern
and
then
B
now
that
we
actually
get
to
test
grid
updates.
Today
we
are
making
history.
Never
in
my
shorts,
kubernetes
life
have
I
seen
test
grid
green.
This
early
in
the
release,
master
blocking
I.
Don't
have
anything
interesting
to
tell
you
all
about
it
master
informing.
C
C
So
it's
timing
out
and
I
believe
there
is
a
reason
why
that
job
is
failing,
but
this
is
a
coal
issue
for
anyone
that
is
interested
in
a
cluster
of
life
cycle.
Aq,
radium,
Europe.
If
you
want
to
debug
it
look
at
it,
you
understand
it.
You're
gonna
have
to
learn
a
couple,
a
couple
things
about
your
EDM.
Besides
that
we
have
some
flaky
reboot
tests,
we
have
not
been
successful
in
finding
someone
who
has
both
the
time
and
expertise
to
be
able
to
deploy
it
to
the
bog
and
GC
cause
a
base
test.
C
C
C
Besides
that,
the
first
rule
that's
to
open
issue
for
the
release,
managers,
I,
believe
a
are
so
many
of
the
upgrade
downgrade
skew
jobs,
and
you
can
get
me
and
you
can
get
the
same
story
from
the
see
a
signal
report.
They
are
failing
because
we
have
not
properly
been
updating.
They
released
that
we
see
release
channels
in
the
past,
so
just
bringing
a
bringing
it
up
again
to
see.
C
If
anybody
has
any
news
on
that,
besides
that
there
are
some
jobs
that
are
failing
in
a
bootstrap
in
a
cluster
and
make
a
making
an
upgrade,
those
are
new.
So
we're
we
see
a
signal
and
whoever's
interested
in
helping
we're
just
gonna.
Look
through
the
failures
make
sure
the
tightly
try
to
figure
out
the
underlying
underlying
cost,
see
if
it's
something
related
to
the
infrastructure,
a
the
release
channels
or
something
is
something
awesome.
Kubernetes
just
broke
yes
well,
as
would
get
their
information
will
share
with
everyone,
and
there
was
also
the
last
bullet
point.
C
There
was
also
a
job
AGC
new
master
upgrade
master
that
one
has
a
ton
of
different
they've
a
test
failing.
So
then,
for
that
one,
a
we're
just
gonna
give
it
a
little
bit
more
a
little
bit
more
time.
Maybe
a
couple
tests
to
see
things
stabilized
a
as
soon
as
something
stabilizes
and
whilst
are
looking
into
one
or
a
water
were
sprung,
and
with
that
I
like
to
win
my
update
and
open
the
floor
for
anyone
that
has
any
comments.
Questions
concerns.
D
So
there
are
a
few
on
the
the
master
informing
that
are
my
fault.
The
install
Deb's
and
rpms
ones
are
consistently
failing,
they're
targeting
a
okay,
so
they're
targeting
a
they
were
initially
targeting
and
make
target
that
didn't
exist
because
it
was
pending
a
PR
that
wasn't
merged,
yet
the
PR
was
merged,
but
the
so
the
make
target
assumes
that
you're
going
to
run
the
install
Deb's
are
the
build
Deb's
and
build
ups
and
build
rpms
packages
are
targets
within
a
system
that
has
docker
on
it.
D
So
the
images
that
the
images
that
are
being
used
for
those
for
those
jobs
do
not
have
docker
on
them
after
testing.
After
adding
docker
to
these
images,
I
realized
wait
that
is
kind
of
silly,
because
when
we're
doing
docker
docker
on
on
CI
and
it's
kind
of
not
acquired,
so
I
need
to
refactor
the
scripts
so
that
they
don't
necessarily
need
to
use
docker,
it'll,
bail
out
or
say,
like
you,
containerize
is
yes
right,
then
use
docker
right.
D
So,
if
you're
on
your
local
system-
and
you
want
to-
and
you
want
to
run
it
in
in
containers-
you
can
do
that.
If
not,
then
do
something
else
right,
don't
run
it
and
docker,
so
that
needs
to
be
done
on
the
CI
side.
I
probably
have
to
both
change
the
the
make
targets
and
the
scripts
that
are
doing
it
so
pending
my
availability,
I
think
it's
faster
for
me
to
do.
It
then
talk
about
it
and
have
someone
else.
Do
it
so
I'll
get
to
that
this
week,
but
don't
mind
those
jobs.
A
Fantastic,
if
there's
no
other
question
George
in
the
CI
signal
team,
it's
great
to
see
all
that
wonderful
progress
and
things
clearing
up
in
master,
blocking
and
master
informing
across
the
board.
So
let
me
know
if
I
can
be
of
any
assistance,
but
it
looks
like
you:
have
it
well
in
hand,
so
take
a
moment
to
celebrate.
Take
that
screenshot
of
the
green
board
and
put
it
as
your
wallpaper.
E
So
we're
here
for
another
update
regarding
the
number
of
fish
fillets
PRS
we
have
so
for
the
issues
we
have
82,
which
is
three
more
than
we
had
at
the
last
meeting.
We
have
65
PRS
open,
which
is
two
more
than
we
had
at
the
last
meeting,
and
our
total
number
of
issues
we
have.
It
could
be
decimated
and
place
rated.
He
said
96,
which
is
the
same
number.
We
had
the
last
time
beside
that
we
have
worked
it
on
a
beta
t,
but
we
appreciate
a
little
bit.
E
So
what
we
have,
if
you
take
a
look,
you
will
see
that
there
is
the
number
of
mismatch
like
there
are
46
issues
and
in
the
blink
fuse
for
the
document
there
like
how
much
we
have
82
so
looks
like
we
don't
accrued.
We
only
crude
kind
bug
issues
in
the
spreadsheet.
Is
this
something
that
is
it
added
and
so
or
something
that
we
want
to
change
a
care
the
same
very
everywhere,.
E
Sounds
good
got
a
dead
and
I
have
been
looking
at
the
PRS
and
issues
we
have
like
they're
around
when
your
25
PRS
that
I
would
say
that
they
are
at
risk,
because
many
of
them
have
been
just
moved
within
milestone
in
milestone
like
for
114
to
115
up
to
116
and
haven't
been
updated
for
a
long
time,
and
it
is
considering
there
is
no
activity.
It's
mostly
like
that
we
would
have
to
move
them.
It
come
when
time
comes,
but
I
was
thinking.
E
Maybe
I'll
keep
an
eye,
keep
an
eye
on
them,
but
maybe
like
when
we
start
the
burn
down
for
two
weeks,
maybe
to
start
pinging
such
reissue
fbi's
little
bit
earlier
to
see
someone
interested
to
finish
that
it
maybe
get
to
time.
So
nobody
has
to
hurry.
We
once
the
code
free
starts,
but
this
is
only
a
proposal
if
you
have
any
idea
regarding
dead
and
then
his
suggestion.
It's
welcome.
E
D
A
E
A
I
would
I
would
probably
prefer
you
ping
them
earlier
and
just
say:
hey
these
have
been
hanging
around
and
we're
trying
to
get
this
cleaned
up,
because
you
might
find
that
a
lot
of
them
get
closed
up
or
no
longer
relevant,
I'm,
not
too
sure
the
outcome
of
them.
But
you
may
as
well
ping
people,
in
my
opinion,
early
and
often
rather
than
wait
till
code
freeze,
because
it
at
least
then
we
can
say
we
did
enough
as
part
of
the
release
team
to
get
action
on
those
PRS
because
burn
downs.
A
A
G
Hi
everyone
so
for
this
week,
for
the
dog
sting
I,
don't
really
have
any
major
announcements
or
updates,
but
one
thing
is
the
shadows
and
myself:
we
are
tracking,
enact
the
announcement
and
reaching
out
and
they
also
providing
updates
in
our
in
our
locker
room
and
also
on
the
the
dog
released
channel,
oh
group,
and
also
we
have
a
couple
PRS
against
1.16.
We
have
about
to
open
PR
and
two
of
them,
as
will
merge
against
our
1.60,
but
we
are
also
reaching
out
you
know
talking
to
talking
to
the
owners
about
about.
G
You
know
about
con
tomate
submitting
like
the
pr
against
our
1.16
website
now.
One
thing
also
is
a
I'm,
also
continuing
the
the
practice
of
actually
merging
master
like
magic
master
into
1.16.
The
reason
why
we
do
that
is
because
of
you
know,
couple
of
releases
back.
We
usually
burn
into
this
show.
You
know,
merge
conflict
during,
like
you
know
the
last
phase
of
the
release
cycle
so
to
prevent
that
we
have
we've
install
this
practice
of
just
continuously
merging
master
against
the
the
currents
are
release
branch
and
so
far,
and
what
we
never
change.
G
That
process-
and
it
sends
doubt
before
the
process
involved
the
release
leak.
The
dock
released
lead
to
actually,
like
you
know,
just
submitted
PR
direct,
so
actually
push
out
the
object
to
one
point
system
branch.
Well,
in
this
case,
we
made
the
change
in
the
sense
that,
instead
of
pushing
that
directly,
you've
sucked
some
of
it
PR
and
the
PR
got
merge,
and
that
allows
for,
like
things
like
transparency
and
also
provides
a
very
good
documentation
for
the
next
release,
the
next
leak
for
next
circle.
So
that's
why
I
did
so
far.
A
A
H
Happy
Monday,
everybody
I'd
have
just
a
brief
update
this
week
we
have
gotten
quite
a
few
updates
from
the
different
SIG's
I'm
going
to
be
coming
out
in
116
kind
of
looks
at
the
cups,
and
so
once
we
get
some
of
the
final
items
to
trickle
into
that
document.
We've
pasted
the
Lincoln
into
the
meeting
notes
so
that
everyone
can
see
that
team
day
that
might
be
of
some
help
to
you
as
well
in
terms
of
kind
of
just
so
you
don't
have
to
ask
for
that
information
again.
H
Hopefully,
that's
a
little
bit
helpful
once
we
get
all
that
information
together
from
all
the
different
SIG's
we're
gonna
reach
out
and
kind
of
pool
together
with
all
of
you
and
see
what
things
are.
You
know
what
the
messaging
should
be
for
116
other
than
Maxo.
It's
it's
going
very
well
we're
green
right
now.
A
A
H
A
Things
around
the
ridges
as
you
you
know
we're
landing
this
in
116
I
always
go
back
and
make
sure
there's
something
enhancements,
and
then,
when
that
thread,
isn't
there
I've
noticed
that
some
some
PRS
have
landed
in
between
releases
and
some
don't
have
an
enhancements
tracking
issues
which
is
kind
of
the
steal
thread
to
get
everything
tracked
on
the
spreadsheet.
So
just
keep
keep
your
eye
and
ear
to
the
ground.
Everybody
I
always
cross
reference
comments.
H
Absolutely
No,
thank
you
so
much.
That
is
what
we're
looking
to
do
to
is
to
either
tie
that
to
a
cup
or
an
issue,
we're
looking
for
some
kind
of
URI
to
cross-reference
that
to
as
wellit's,
but
so,
if
you
see
us
reaching
out
or
any
of
our
shadows
and
our
team
reaching
out,
that's
that's
our
nefarious
plan
that
work
will
work
in
a
cool.
I
D
D
I
Yeah
cool,
so
the
other
update,
the
the
removing
old
jobs
and
adding
new
jobs.
Yeah
we
currently
have
two
I
believe
had
the
wrong
schedule
on
the
timeline,
so
we
have
an
issue
and
the
pr
opened
and
we
are
looking
for
volunteers
for
these
tasks
too,
and
next
thing
is,
after
we
created
the
release,
116
branch.
I
I
A
Okay,
thank
you
very
much
for
the
update
young
I.
Think
I'm
okay
de
Waal
had
reached
out
about
merging
we're
updating
the
schedule
for
the
removal
of
the
112
jobs
at
the
same
time
as
116
I
will
get
that
updated
and
get
the
PRS
approved.
The
only
thing
I
will
ask
is:
does
that
make
it
more
work
or
less
work?
I
assume
it's
less
work.
A
A
A
D
Really
quick,
yes,
there's
nothing
on
the
agenda.
Unless
people
have
questions
for
myself
or
Josh,
what
I
guess
what
happened
most
recently
in
cig
release
world
is.
There
is
now
a
release
engineering
meeting,
which
happened
immediately
prior
to
this
call.
There
is
also
a
new
time
for
the
cig
release.
Team
meetings,
say
sorry,
sig,
release
meetings,
the
official
meetings
for
the
sig,
which
are
will
be
alternating
weeks,
so
it'll
happen
immediately
prior
to
this
meeting
as
well.
So
that
is
carry
the
one
subtract.
The
eleven
eleven
Pacific
time
and
3:00
p.m.
UTC
I
think
I.
A
A
D
So
there
is
a
doodle
that
went
out.
There
was
a
doodle
that
went
out
last
week
and
most
of
you
have
voted
on
it.
So
you
should
be.
You
should
know
the
new
time
there's
also
calendar
invites
and
all
that
stuff
so
that
anything,
that's
the
big
sig
release
change
any
questions
about
sig
release
stuff
in
general.
Let
me
know.
A
Cool,
thank
you
Steven
and
Josh
release.
It
lead,
update,
so
I
think
we've
gone
over
most
of
these
things
tomorrow
is
August
6th.
We
have
alpha
3
going
out
tomorrow.
We
also
had
scheduled
the
removal
of
112
jobs.
I've
put
a
note
there
that
we've
deferred
it
to
the
next
week
as
that
make
better
sense
for
the
release
engineering
team
to
do
it
an
all
in
one
fell
swoop,
while
they're
in
there.
A
That
means
it's
a
big
week
next
week
for
this
released
813,
we
have
the
creation
of
the
116
branch,
which
coincides
with
b20
going
up.
We
have
the
116
release,
job
creation
and
the
removal
of
the
112
jobs
as
well.
The
other
thing
that
I
needed
to
mention
specifically
was
there
was
one.
So
there
were
two
enhancement
extensions
Kendrick
mentioned
one.
We
denied
the
extension.
He
probably
saw
them
on
the
mailing
list,
the
other
one
we
granted,
which
was
building
kubernetes
without
intrigue
cloud
providers.
A
So
the
testing
for
team
and
Ben
elder
has
been
leading
up.
This
work,
which
we
agreed
to
allow
the
extension
because
it
helps
subsequent
releases
and
the
removal
of
the
entry
cloud
provider
code.
So
we
kind
of
want
to
expedite
and
make
sure
we
have
all
the
infrastructure
in
place
and
then
put
together
a
pretty
good
exception
for
that.
So,
if
you're
interested
go
check
the
mailing
list,
the
themes
need
to
be
built
out.
A
This
is
on
the
week
six
kind
of
need
to
know
which
Taylor
is
doing
and
that's
basically
going
through
all
the
SIG's
and
all
their
associated
enhancements
and
what's
going
to
land-
and
this
gives
us
a
full
picture
of
what
1:16
looks
like,
which
leads
all
the
comms
blogs
information
that
goes
out
of
that
1:16.
So,
as
I
said,
keep
an
eye
out
for
things
you
hear
in
the
community
of
hey
we're.
Adding
this
to
116,
always
go
back
and
cross-reference
the
enhancements
and
ask
people
questions
because
there
is.
A
There
is
a
route
or
two
where
people
can
land
changes
in
the
release,
and
we
don't
know
about
them.
We're
trying
to
get
people
to
follow
kind
of
create
an
enhancement
issue,
and
we
track
that.
But
there's
still
our
folks
getting
used
to
that
process
in
the
community.
So
I'd
ask
you
to
keep
your
ear
to
the
ground.
That's
it
from
the
release
lead
update.
Do
we
have
any
anybody,
have
any
questions
for
me.