►
From YouTube: Kubernetes 1.18 Release Team Meeting 20200203
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
All
right
so,
as
everyone
knows,
this
meeting
is
under
the
kubernetes
code
of
conduct,
which
basically
simplifies
to
you
gonna,
be
excellent
to
one
another.
I
am
dropped
the
agenda
in
the
meeting
notes,
so
please
check
that
out
and
add
your
name
to
it
as
an
attendee.
If,
if
you're
here,
if
not
don't
worry
about
that,
actually
so
to
kick
us
off
today,
let's
go
to
enhancements.
B
Hey
happy
Monday,
so
last
week
was
enhancements.
Freeze
on
Tuesday
we
had
a
number
of
people
file
for
exceptions
to
enhancements,
freeze
my
open
to
PR
to
the
118
release
folder
with
a
list
of
those.
In
summary,
we
had
six
that
were
filed,
one
five
of
them
were
approved,
one
of
them
was
not
approved,
and
that
leaves
us
with
50
tracked
items
for
the
release.
B
19
will
be
new,
alpha
features,
15
will
be
beta
and
our
sorry
16
will
be
beta
and
15
will
be
graduating
to
stable
dope,
so
the
enhancements
tracking
spreadsheet
has
been
updated.
We've
removed
everything
from
it
that
didn't
get
an
exception
or
deferred
so
like
it's
just
all
the
track
things
now,
so
it
should
be
good
for
the
doc
people
to
go
ahead
and
start
working
off
of
that.
C
Yep,
so
we
are
yellow
this
week,
so
it
looks
like
that
national
blocking
is
looking
pretty
good,
which
has
been
pretty
consistent.
So
that's
nice.
One
thing
to
point
out:
it's
not
part
of
the
actual
release
board.
Is
this
pool
kubernetes
end
in
GCE,
which
has
been
flaking
pretty
bad,
but
there
has
been
some
work
done.
This
PR
the
references
to
help
determine
what
the
actual
issue
is
happening
there.
So
we'll
continue
to
push
forward
on
that
and
hopefully
get
resolved
soon
and
informing.
We
do
have
a
number
of
tests.
C
Failing
this
primary
one,
GCE
cost
master
reboot
is
a
sync
cloud
provider
test
failure,
so
we
followed
up
on
the
issue
and
have
now
reached
out
to
them
and
slack
today.
So
hopefully
we
can
get
some
feedback
there.
The
GC
windows
container,
D
master.
That
test
is
a
work
in
progress,
so
we're
not
paying
attention
to
that
right
now
and
then
we
have
a
number
of
windows
issues
which
we
are
informed
in
slack
this
morning
that
they
were
being
investigated.
So
hopefully
we
get
some
resolve
on
that.
But
overall,
looking
pretty
good
awesome.
D
Up
what
up
we
are
currently
green?
We
have
open
test
flakes.
We
are
down
for
from
last
week
to
52
we
have
prayer
priority
critical,
we
are
remaining
even
at
five
priority.
Important
soon
is
down
122.
We
have
open
PRS.
I
am
the
cake,
a
repo
we
are
at
53,
that
is
up
to
from
last
week.
Priority
critical
urgent
are
remaining
the
same.
Two
priority.
Important
is
remaining
the
same
for
open
kk
issues.
We
are
down
three
272.
D
E
G
G
H
I
J
A
Cool
going
over
to
emeritus
lead
Lachlan
said
that
he
would
be
jumping
in
late.
We
still
have
our
meeting
going
about
half
half
and
half
way
into
the
hour.
He
said
he
just
gave
his
update
and
that
is
reviewing
Shadow
Man
release
survey
to
go
out
next
week,
yeah
and
then
I
don't
have
any
updates
for
you.
I
am
not
in
front
of
my
computer
right
now,
I'm
on
my
iPad.
So
if
I
could
get
your
help,
Jorge
is
far
some
of
the
next
upcoming
milestones.
I'd
appreciate
it.
F
F
That,
since
we
already
sorry,
I,
was
trying
to
remember
what
I
whatever
so
it
last
week
we
just
went
through
enhancements
frisk.
This
is
one
important
milestone
for
the
for
the
current
release.
If
you
have
any
comments,
questions
suggestions
regarding
the
processes
that
your
team
or
some
other
team
went
through,
please
remember
to
go,
go
check
out
the
release
retrospective
document
for
118
it's
over
a
it's
a
during
the
readme
for
their
release.
118
in
the
sequel
is
repo.
A
F
Don't
think
there's
anyone
from
six
scalability
but
they're
blocking,
but
the
blocking
issue
is
one
that's
been
it
that's
been
in
the
works
for
a
for
a
while.
They
are
work
and
they
issue
is
about
making
it
making
cluster
upgrades
a
little
bit
less
hectic
a
that's
the
TLDR.
They
say
the
issues
really
cooled
off.
If
anyone
wants
to
learn
all
the
ins
and
outs
of
a
cover
natus
in
the
queue
API
server,
that's
a
good
one.
A
F
C
K
M
A
F
F
F
Cool,
that's
done
next,
one
investigate
automation,
to
facilitate
tracking
spreadsheets.
F
A
B
B
F
F
Okay,
that's
it,
then
we
okay,
so
that
was
reviewing
progress
in
progress
track.
Enhancements
document
reason
for
a
document
reason
for
inclusion.
Let
me
start
with
this
one.
Anyone
from
CI
signal
that
wants
to
help
out
on
this.
They
I
created
that
document.
With
a
lot
of
information
hey,
we
need
to
update
it
because
I
haven't
updated
in
a
couple
of
weeks
and
polish
it
to
make
it
readable.
F
Sweet,
let
me
use
my
superpower.
What's
your
github
hash
dan
I
knew
you
had
a
hash.
Thank
you,
okay,
sweet
118!
That's
it
track
enhancements
leap
across
multiple
releases
and
Jeremy.
Seven
days
ago,
I
did
a
first
pass
of
disaster
117
on
the
last
bus
after
code
freeze
for
118
and
%
directions
around
through
this
meeting.
So
I
guess
this
will
stay
in
progress
right,
yep.
F
N
F
F
And
yeah
sorry.
K
F
M
F
F
M
M
J
F
F
M
F
M
So
yeah,
so
if,
as
your
I
would
say,
take
a
look
at
both
this
one
and
the
117
100
an
update
on
the
117
one
I
essentially
have
to
turn
it
into
this
prettified
version
of
it,
so
that
it's
easier
to
check
up
this
work.
But
essentially
locky
should
be
bugging
all
of
you
throughout
the
cycle
to
close
issues
like
this
to
make
sure
that
we're
actually
trying
down
on
the
stuff
that
we
said
we
were
going
to
for
the
previous
retrospective
cool.
F
I,
like
it
again
sure,
released
in
with
and
work
okay,
so
this
one
is
about
making
sure
that
they
released
in
handbook.
It
makes
a
mention
of
the
retrospective
and
I
just
commented
on
it
a
some
hours
ago,
and
this
is
also
something
easy.
They're
gonna
be
working
on
it
this
week,
then
we
have
the
117
retrospective,
so
I'll
book
a
like.
M
F
M
So
for
everyone
I'd
like
to
request
that
everyone,
at
least,
if
you
don't
feel
like
commenting
on
it,
that's
fine,
but
everyone
should
at
least
take
a
look
at
that
proposal.
There's
more
work
to
be
done.
There
I
think
it's
missing
some
key
things,
but
please
this
is
a.
This
is
a
topic
that
affects
everyone
and
the
low
esteem
affects
everyone
and
well,
maybe
not
this
releasing,
but
I
think
that
every
person
on
this
really
seemed
has
valuable
input
for
the
idea
of
doing
the
yearly
support.
M
F
M
Yeah
so
from
people
with
your
handbook
updates,
don't
feel
like
this
is
something
that
you
should
wait
until
the
end
of
the
cycle
to
do,
or
do
only
once
the
handbags
are
living
documents.
So,
every
time
you
walk
through
the
process
and
you
notice
something
that's
broken.
Please
take
a
moment
and
it's
it's
it's
so
much
easier
to
do
it
if
you're
like
oh
well,
this
line
is
no
longer
right
and
you
and
you
send
out
a
one-sentence
PR,
then
waiting
until
the
end
of
the
quarter
and
having
to
review
the
entire
document.
M
F
F
F
P
M
It's
so
we
have
to
if
we're
gonna
do
something
like
this.
We
have
to
also
decide
like
exactly
what
the
format
of
every
handbook
is
going
to
be.
I.
Make
sure
that
every
like
we
were
close
with
all
the
handbooks,
but
like
everyone
will
need
to
have
the
same
exact
details
in
it.
Right
like
this
isn't
useful.
Let's
not
wait
for
everyone.
F
So
what
I,
what
I,
what
I
was
thinking
about?
This
one
is
at
least
from
the
release
team,
lead
yeah.
You
have
to
create
the
schedule,
and
you
know
you
a
week.
One
way
we
create
jobs
week.
Seven
we
release
kubernetes
week,
nine
we
take
coronaries,
one
can
fix
it
and
the
like
most
of
that
information
I
think
it
changes
a
very
little
it
drop
releases.
M
What's
a
me
I
guess
the
readme
for
the
release
and
where,
instead
of
I
mean
we
would
continue
to
kind
of
use
that,
but
the
each
of
the
sections
had
denoted
some
milestone.
It
could
break
out
in
own
readme
type
thing
right
or
link
to
another
page.
It
says
like
Oh
entries,
you
know
this
role
should
be
doing
this
really
Stanley
should
be
doing
this
enhancements.
League
should
be
doing
that
right.
M
E
E
M
F
Right
now,
this
one's
good,
so
I
can
take
it,
at
least
as
an
action
item,
to
write
down
everything
that
you
said
put
in
this
issue
and
I
guess
we're
going
possibly
a
Taylor
and
Bob.
We
can
work
on
this
yeah
sure,
sweet,
so
action
item
I'll
update
it
with
everything
that
was
said
right
now,
but
for
the
time
being,
let's
move
on
yeah
to.
F
M
M
Okay,
alright,
so
we
should
say
team
think
about
you
might
want
to
present
to
external
users
about
the
reading
process
so
that
we
can
start
to
marry
with
some
of
that
stuff
into
the
contributor
site.
I
think,
eventually
what
I'd
like
to
use
I'm,
probably
bare
minimum
into
stuff.
That's
in
then
k
community
contributor,
guide,
slash,
Rick,
sig
release
to
also
go
into
that
contributor
guide.
That
might
be
one
of
the
sub
directories
that
is
already
planned
to
go
in
there,
but
I,
don't
know
much
about
how
that
site
is
structured.
So
right.
K
M
E
K
K
A
F
Cool
awesome
so
I'll
take
it
as
an
action
item
to
go
back
to
the
issue
and
know
better
with
the
pertinent
information
from
what
we
just
said
next
issue.
This
I
do
know
procedure
for
jobs
entering
and
leaving
blocking,
ie,
actually
initially
plus
cycle
proposed
a
plan
to
cannot
tackle
this,
give
it
to
try
a
hands-on
experiment
and
see
what
useful
information
we
could.
Actually,
we
call
actually
put
into
writing
a
book
recently.
There
was
an
request
for
comments
for
a
seasonal
sub
project
and
I.
F
M
We
yeah
I
would
ever
toss
it
to
the
backlog
and
wait
until
we
spin
up
a
board
for
the
I've
got
a
squad.
I've
got
a
quash
some
some
topics
for
discussion
within
that
RFC,
but
once
we
have
a
separate
CI
signaled
project
board.
Well,
we
kind
of
do
right
now,
but
I
don't
want
to
throw
off
the
flow
of
the
CI
signal.
Release
team
relative
to
you
like
the
larger
CI
signal
sub-project.
M
F
F
F
Q
M
M
I
would
I
I
would
want
to
say
the
same
and
I
would
I
would
defer
closing
it
to
two
David
until
you
a
better
idea
of
what
we
want
to
do,
I
think
that's
I
think
we
should
defer
to
all
of
our
non-us
release
team
members
to
make
a
decision
on
this.
If
you
want
this
to
happen,
you
need
to
be
a
part
of
making
a
proposal
for
this
and
and
then
putting
forth
ideas
about
how
we
can
do
that.
F
Q
F
F
F
P
N
Release
notes
I,
can't
personally
say
that
I've
actually
taken
too
much
of
a
look.
I
could
but.
F
D
F
In
that
case,
would
you
be
in
favor
of
keeping
it
or
closing
it
sneaky
bet,
sweet,
yep,
so
Louis
or
dira
sign,
and
should
we
keep
David.
M
F
G
F
You
so
much
and
we
made
it
to
the
with
stay
with
18
minutes
to
go.
So
let's
go
to
backlog,
or
at
least
let's
straight,
to
go
through
its.
How
many
issues
we
can
go
trip
so
shadow
in
retrospective
I
feel
like
this
will
be
an
interesting
thing
to
take
off
with
lacking.
Are
you
on
the
line
yep
happy
tonight.
R
M
To
so
we
had
talked
about
this
I
think
we
still
all
should
get
together
and
from
you
know,
I
think
between
the
leads
and
believe
it
took
forgot.
How?
Because
we've
got
so
one
of
the
idea
was
having
a
separate
shadow
retrospective.
Another
idea
was
having
a
set
of
a
release
team
retrospective
prior
to
the
public
retrospective,
like
they're,
a
bunch
of
different
ways
to
slice
this.
So
let's
figure
out
what
we
want
you
before
moving
on
it.
So
if
y'all
on
a
schedule
call
they
can
do
that.
M
Of
how
we
communicate
in
the
team
overall
right
like
there,
we
want
to
everything
that
entity
lead
can
be
pushing
the
shadows
towards
feeling
that
they
can
speak
up
in
any
form.
That's
the
point
of
the
overall
retrospective
right
so
throughout.
So
this
is
part
of
it
open
for
the
the
mid-season
shadow
surveys
that
we're
going
to
be
doing
the
the
more
frequent
check-ins
to
the
shadows,
the
the
shadow
kind
of
orientation
sessions
and
all
that
stuff.
M
F
Next
to
the
next
couple,
issues
at
action
record
release
notes,
process
need
to
define
a
process
by
which
we
create
action,
require
release,
notes
that
do
not
have
an
Associated,
PR
or
issue.
Anyone
from
release
notes
that
wants
to
anyone
from
release
notes.
That's
on
the
call
right
now
and
wants
to
take
this
up,
which
again
I
can
add
up
sweet.
M
F
L
K
I
think
this
one's
gonna
get
on
the
road
a
little
bit,
we'll
sort
of
see
what
happens
after
things
at
AMS.
So.
M
M
E
M
E
F
K
F
F
It's
done
still
in
the
line,
nah
I,
don't
know
well.
Oh
me
well
make
sure
I
could
see
a
signal.
People
nice
on
this
air
release,
team
selection,
doc
the
release
team,
the
release
team
selection
dough
contains
some
outdated
information
on
job
selection
criteria
if
they
updated
include
any
fine,
only
final
criterion
to
have
extensive
section
on
shadow
selection
and
every
single
person.
Everyone
in
the
release
team
is
assigned
to
this
pretty
much,
and
this
has
been
open
since
June.
M
F
F
M
M
F
You're
assigned
to
it
so
moving
on
the
steam
freeze
here,
the
TLDR
for
this
was
essentially
a
no
from
cig
testing
and
I
just
really
created
this
issue
to
keep
track
of
the
conversation,
and
if
people
had
any
comments,
questions
suggestions
put
it's
been
open
since
December,
10,
2009
teen,
and
even
before
that
there
was
a
lot
of
conversation
was
like
so
hey.
What
do
you
all
want
to
do
with
this?
One.
M
I
would
say
anyone
who
thinks
they
want
to
do
something
with
that.
One
read
through
the
working
group
LTS
at
first
that
one
is
going
to
have
implications
on
the
testing
side
that
will
affect
where
we
can
do
something
like
this
or
not.
I.
Think
the
answer
I
think
the
answer
is
no,
no
I
think
that's
how
many
talked
about
this.
E
M
F
Okay,
cool
comment
for
later
on
and
that's
gonna
stay
in
the
backlog,
Godfrey's
scalability
test
for
beta
releases,
I,
don't
think
this
has
had
any
commentator
and
she'll
probably
ask
six
scalability
to
take
a
look
at
it
again,
because
it's
mostly
a
question
for
them
food.
Let
me
go
back
and
check
yeah,
nothing
there
so
well!
Assign
myself
I'll,
take
this
up
with
a
I'll
keep
Bob
and
Taylor
like
I'll.
Keep
you
all
up
to
date,
then
we'll
ask
scalability
to
take
some
to
comment
on
it
and
shadow
application
feedback.
M
R
F
Sweet
yeah
and
actually
I
was
just
gonna
say
it.
I
was
just
gonna
say
that,
because
of
time
zones
we
might
have
some
people
actually
do
have
feedback.
We
are
not
on
the
line,
so
that
sounds
good
and
we
have
four
more
minutes.
Let's
see
which
ones
are
good
to
go,
they
were
into
advisor,
mini
notes
and
a
is
some
and
then
we
have
increase
couple,
ladies
or
window
to
one
year,
access
for
that
doesn't
matter
and
the
same
phone
charge.
Okay,
so
a
couple
one.
F
So
we
can
go
through
and
lucky
you
want
to
go
to
a
married
to
supply.
Sir,
that's
not
like.
Do
you
want
to
go
to
that
issue?
Yes,
it's
sweet
and
it
looks
like
colder
than
that.
Those
are
all
the
issues
that
we
have
so
enhance,
but
let's
go
through
your
issue.
First
memory
to
supplies
are
MIDI
notes
in
a
ice.