►
From YouTube: Kubernetes 1.18 Release Team Meeting 20200127
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
Okay,
recording
to
the
cloud
good
morning
evening
and
afternoon,
everyone
welcome
to
yet
another
meeting
of
the
kubernetes
118
beliefs,
team.
I.
Am
your
humble
host,
Jorge
Lacan?
If
you
haven't
please
open
up
the
please
go
to
the
invite
for
this
meeting
check
a
open
up
the
notes
and
please
put
down
your
name
for
January
27th
in
2020.
If
anybody
wants
to
take
the
prestigious
place
as
a
note
taker,
please
feel
free
to
do
so
and
before
we
actually
get
started.
I
have
to
mention
that
we
have
our
code
of
conduct.
A
B
Everyone,
so
the
current
enhancement
status
is
yellow.
We
are
tracking
a
total
of
51
enhancements
out
of
which
37
are
completely
tracked,
like
green
there
they
have
all
their
cap
requirements
complete
and
14.
14
of
them
have
some
requirements
incomplete.
We
are
currently
pinging
them
actively
over
the
github
issue
and
both
in
the
selection
and
also
grouped
by
SIG's.
We
have
a
PA
machinery,
one
kept
to
be
in
at-risk
auto-scaling,
one
six
CLI
to
network
to
scheduling
one
storage
six.
B
A
A
B
A
A
A
Okay,
I'll
keep
quiet
a
but
I'm.
Looking
at
the
notes
you
put
down
and
thank
you
very
much
that
is
it
that
actually
has
all
the
information
they
that
we
need
to
move
forward.
So
thank
you.
Thank
you
very
much
and
thank
you
very
much
to
all
the
enhancements
team.
You
all
have
been
doing
a
wonderful
job,
a
been
doing
a
lot
of
it
to
it
to
help
everywhere
to
help
everyone
get
their
enhancements.
In
with
that
CI
signal,
nicolo's
I.
D
Guess
I'm
taking
over
for
him
today,
so
John
Reese
CI.
So
you
know
shadow
I'll
be
doing
my
best
to
give
you
guys
an
update
as
to
what's
going
on
so
so
what
I
have
down
for
from
our
side
is
that
the
master
blocking
is
looking
pretty
good.
The
vast
majority
of
what
I
am
seeing
is
coming
from
master
informing
a
lot
of
it
around
that
the
cloud
providers
Asher
and
GCP.
We
have
a
lot
of
those
that
are
currently
in
a
flaky
status.
D
D
Gcp
group,
the
the
only
failing
test
that
that
I
was
able
to
really
find
was
relating
to
GCE
as
well,
but
the
developer,
who
wrote
the
test
that
it
was
a
test
that
was
a
work
in
progress
and
he
was
actively
looking
into
getting
that
up
and
running
from
an
anon
whip
state.
And
then,
aside
from
that
why
I
know
from
from
last
week,
we
spoke
to
a
lot
of
the
they
generated
tests
that
were
that
were
coming
back
as
flaky
or
no
ownerships.
D
A
few
of
the
the
flaky
tests
are
in
that
category,
so
we're
waiting
on
a
couple
PRS
to
get
to
get
merged
and
that
might
clean
a
few
of
those
up.
So
once
those
gets
merged
and
we
kind
of
take
another
look
at
the
generated
landscape.
But
from
from
that
point,
that's
kind
of
the
the
update
that
I
had
put
together
for
the
for
the
group.
A
D
A
I'll
going
to
actually
I
see
that
somebody's
taking
notes,
so
could
you
add
the
line
using
in
the
places
where
it's
pertinent,
please,
yes,
pressure
day
all
day
the
other
thing
and
I
just
I
just
noticed
array
that
this
is
happening
for
the
last
couple
runs
in
master
blocking
day
couple.
The
couple
do
star
flaky
and
I'm,
going
through
them
going
to
the
rest
of
them.
Put
the
jobs
are
flaky.
There
seems
to
be
something
funny
going
on.
Were
we
we
seem
to
be
running
every
single
test
two
times.
D
Of
the
tests,
I
am
unaware,
but
I
will
I
will
write
that
down
right
now
and
do
some
investigation
into
that
and
see
if
I
can
get
an
answer
for
you.
D
A
That's
good
if,
for
some
reason,
they
I
was
gonna,
say
that
for
some
reason
they
don't
reply,
we
might
also
propose
to
okay
I'm
thinking
about
a
for
some
reason.
No
one
a
from
provider
replies,
we
might
think
about
actually
removing
this
issue
because
they
I'm
pretty
sure
that
all
this
just
have
gone
a
month
in
for
away
for
a
long
time.
Hey.
D
I
was
gonna,
say:
I
I
had
noticed
that
and
a
few
of
the
other
issues
that
were
opened
as
well,
especially
a
lot
of
the
the
flaky
ones.
I
noticed
a
few
of
the
flakes
have
been
flaking,
eaten
for
four
previous
releases
and
they're
just
kind
of
still
continuing
as
we
as
we
go
from
release
to
release.
So,
if
we're
releasing
with
that
with
them
still
being
that
status,
then
again
they
are
they
really
providing
value.
Yeah.
A
The
only
the
only
other
chick,
the
only
other
thing
that
a
hopefully
see
a
hopefully
see
a
signal
can
help
provide
some
inside
a
insight
into
is
I,
mean
I,
know
that
there's
only
like
five
or
six
Tests
in
a
master
reboot
that
radar
warning
and
I'm
pretty
sure
that
some
of
them
I
don't
actually
even
had
anything
to
do
with
reboot,
or
is
there
a
a
we'll
get
somewhere?
Could
we
get
someone
from
say
no
to
a
look
over
them?
D
A
A
Information-
or
you
say,
or
is
it
just
kind
of
a
a
test
case
that
we
can
run
in
some
other
in
some
and
some
other
platform,
because
I'm
also
pretty
sure
that
the
GC
a
that
a
GC
master
reboot
tests
are
running
a
based
on
the
way
on
the
cluster
directory
from
kubernetes
which
for
everyone,
that's
listening
in
the
cluster
directory,
has
been
deprecated
for
years
and
something
that
is
not
really
my
a
isn't.
It's
not
my
name,
but
you
know
it's
just
being
we
use.
A
So
a
so
I'm
also
wondering
if
those
tests,
if
they
do,
provide
useful
information
if
we
can
run
them
in
a
cluster
in
some
closer
API
provider
or
something
else:
okay,
yeah.
Okay,
so
that's
it
for
me.
I'm
just
gonna
shut
up,
sorry
for
taking
so
much
time,
but
thank
you,
but
thank
you
very
much
for
the
update.
Anyone
has
any
more
on
with
questions
related
to
a
signal
by
months
twice.
E
So
this
is
soldier
for
bug
triage,
and
somebody
updates
will
be
very
brief.
We
are
still
in
the
early
stage
of
the
release
cycle,
so
we
are
green,
even
though
we
have
a
considerable
number
of
open
issues
and
NPR
still,
but
this
week
we're
gonna,
start
pinging
long
running
and
more
style
issues
and
pr's,
and
we
will
be
doing
this
this
week
and
the
next
week
yeah
and
then
we
will
take
it
from
there.
A
E
A
F
Yes,
we
don't
have
any
major
update.
We
were
just
I
was
just
by
doing
some
branching
cups
in
the
last
week,
as
I
have
dated
in
the
previous
Meetup,
so
like
I
am
planning
to
have
another
call
with
my
shadows
to
exchange
the
rules.
So
I
was
doing
the
branch
lengths
of
still
now
so
I
just
wanted
to
pass
it
to
some
other
guys
in
my
team,
so
they'll
be
taking
it
for
the
next
week.
F
C
For
this
week
we
were
green,
and
this
week
it
changed
from
my
team
generated
the
release,
notes,
draft
and
and
the
website
PRS
did
they
already
merged.
Both
the
in
both
both
wheels
were
generated
with
such
as
new
version
of
the
release
notes
tool
which
already
generated
that
the
release
notes
with
group
by
kind
and
everything
seems
to
be
going
just
fine.
A
A
G
Sorry,
yeah
Karen
ear
and
the
comms
lead
weird
green
I
think
we're
gonna
start
assigning
SIG's
for
the
shadows
to
reach
out
to
you
this
week,
once
enhancement
freeze
happens
and
otherwise
no
updates
we're
good.
H
A
A
H
A
H
I
Sleep
please
take
over
its
George
hello.
Everyone,
quick
update
from
me
all
shadow
orientation
calls
with
all
the
release
leads,
have
been
completed
if
you
shadow
and
don't
believe
that
you've
been
part
of
one
of
those
orientation
calls
either
reach
out
to
lead
and
say,
hey,
I,
never
was
part
of
this
or
reach
out
to
me.
So
the
idea
of
those
orientations
was
to
get
you.
I
You
to
the
team
and
make
sure
you're
familiar
with
the
roles
and
tasks
of
each
specific
role.
So
if
you
haven't
done
that
feel
free
to
ping
me,
the
next
big
milestone
for
me
is
I'm
going
to
be
pinging
folks
who
picked
up
issues
as
part
of
last
retro.
So
we
have
a
board
tracking
all
those
long
running
tasks
in
between
that
go
over
different
releases,
so
I'm
going
to
be
pinging
folks,
just
to
remind
them
that
I
have
some
obligations
there
and
I'm
going
to
send
out
shadow
survey
about
week.
Six.
I
A
The
you're
my
favorite
project
within
the
team
so
I
give
you
the
opportunity,
alright,
okay,
so
moving
on
to
myself,
I
guess
so
let
me
get
started
with
the
most
important
announcement
up
to
date
and
I
finally
have
a
team,
so
it
means
gonna
be
mr..
A
so
shadows
for
my
team
aren't
gonna,
be
mr.
Bobby
tables
and
Taylor,
who
is
present
at
this
very
moment.
Everyone,
please
say:
hi
to
Taylor.
G
A
A
Bob
Twiggs,
please
say:
you've
had
to
evolve,
so
this
is
gonna,
be
my.
This
is
gonna,
be
my
team
for
the
rest
of
the
way
there
release.
Finally,
a
fine
I
finally
get
around
to
that
and
the
next
order
of
business.
There
was
a
doodle
that
I
said
that
I
sent
out
last
week
for
a
proposing
a
new
time
for
the
released
in
meanings
that
were
in
there.
Please
check
out
the
release
notes
for
a
further
day
for
the
proposed
dates,
but
they
favor
one
a
actually
the
way
they
were.
A
What
is
it
five
proposed
dates?
They
have
more
or
less
the
same
bolts.
It
seems
to
be
that
the
best
option,
with
the
data
that
I
have
available
right
now
is
going
going
forward.
They
released
him,
meaning
is
gonna,
be
at
2
p.m.
in
the
u.s.
I
was
gonna,
say
Pacific,
but
today,
but
that
is
not
Pacific.
Us
Eastern,
which
is
a
p.m.
Central
Europe
I,
believe
in
a
12
a.m.
India
standard
a
standard
time,
and
that
is
preferred
because
at
least
I
sat
down
more
leads
are
available.
A
A
are
available
at
that
time,
as
opposed
to
the
other
proposals,
as
opposed
to
the
other
aid
to
the
other
proposed
times
so
with
that
announcement.
If,
for
some
reason,
that
time
is
completely
helpful
to
you
and
you
didn't
get
a
chance,
please
speak
out
a
showed
me
a
message.
A
shoot
me
a
DM.
Should
they
should
I
shoot
a
message
in
seek
release
a
sambar,
a
choosing
a
choosing,
a
choosing
either
one
or
a
either
one
of
the
other
tabs.
A
The
other
thing
that
also
Wade
also
wanted
to
throw
off
for
discussion
is
so
we
have
five
a
five
or
four
a
five
other
dates.
Will
people
be
interested
in
having
like
having
a
second
release
meeting
for
people
in
other
time
zones
to
catch
up
or
for
people?
Then
they
can
definitely
make
the
time
at
2:00
p.m.
us
Easter.
A
Okay,
I
was
looking
at
the
chat,
booth
and
nothing
a
nothing
on
the
meeting,
so
I'm
just
gonna
send
a
chat.
I'm,
just
gonna
shoot
a
message
on
seek
release
remind
reminding
you
all
that
that
might
be
a
possibility,
I
think.
If
and
if
anyone
is
interested
with
next
week,
a
meeting
and
2
p.m.
2
p.m.
use
a
u.s.
sister
and
other
than
that
of
coming
milestones.
A
A
Sweet
so
moving
on
to
scalability
and
scalability
wise
the
view
from
a
shelf
remember,
there
was
an
issue
with
the
performance.
A
taste
dashboard
from
last
week
that
seems
to
hey,
does
seems
to
have
been
fixed
right
now.
There's
still
work
going
on
on
fixing
issue.
What
is
it?
86
43
zero
on
KK,
and
this
is
related
to
rolling
updates.
Apparently,
it's
really
messy
to
give
to
kill
a
cube,
API
server.
A
So
if
you
wanna
check,
if
you
want
to
check
out
the
issue,
if
you're
interested
in
learning
all
the
all
about
kubernetes
and
how
it
works,
this
is
a
super
interesting
one
put
a
release.
Team
wise
people
are
working
on
it
and
we
are
not
present
in
a
disparate
moment
for
our
solution,
so
we're
good
before
moving
on
I
guess
anyone
has
any
comments.
Questions
for
scalability.
A
So
open
this
question:
there
isn't
a
lot
of
there
isn't
a
life
here.
There
is
only
right
now,
there's
only
one
link
that
I
added
in
there
for
a
again
for
anyone,
who's
interested
in
capsule
and
anything
related
to
caps.
They've
all
proposed
changes
to
how
caps
are
organized,
that
is,
a
trade
in
the
siekerka
tech
chure
mailing
list.
If
you're
interested
also
you
know,
take
a
look
join
in
the
conversation.
A
Would
a
last
I
check
I,
don't
think
there
was
anything
that
was
super
pressing,
a
further
way
for
the
release
team,
so
I'm
just
gonna
skip
over
it
and
again
some
chance
for
anyone
to
interrupt
me
before
we
move
on
to
projects
and
actually
walk.
The
touch
may
actually
want
the
dashboard
for
this
meaning.
A
Okay,
I
hear
nothing.
So
let's
go.
Let's
move
on
to
the
dashboard
good.
If
you
wanna
interrupt
me
some
a
somewhere
along
that
play,
please
feel
free
to
do
so
and
let
me
start
sharing
screen.
Hopefully
you
can
see
my
Ubuntu
and
let's
see
released
him
so
first
off
I'm
gonna
take
gonna
like
to
make
this
as
quick
and
painless
as
possible
because
it's
been
more
than
a
month
since
the
last
time
we,
since
the
last
time
we
went
through
the
dashboard.
So
let's
see
I
mean.
A
Shadow
retrospective,
an
actual
record
release,
notes
process,
I'll
check
on
them
later.
Let's
go
right
now
for
in
progress,
so
track
enhancements.
Sleep
across
multiple
releases
document,
reason
for
inclusion
of
release,
blocking
jobs
and
117
release,
notes,
known
issues-
let's
see
what's
in
here,
so
track
enhancement,
sleep
across
multiple
releases.
This
was
opened
on
November
13
and
it's
assigned
to
Jeremy
and.
J
A
C
A
Okay,
before
moving
on
any
more
a
anyone,
has
any
more
questions,
cool,
so
document
reason
for
including
collision
of
release
blocking
jobs.
Ie
had
okay
at
least
a
day.
Okay.
So
yesterday,
just
a
refresher
on
this
one.
We
have
a
bunch
of
ACI
blocking
jobs,
but
we
don't
really
have
any
where
we
don't
have
a
needle
commutation
on
a
why
we
have
them
a
what
useful
information
they
might
provide
and
that
so
I
started
a
a
writing.
A
A
draft
or
a
of
the
compiling
the
useful
information
for
at
least
for
the
blocking
jobs
and
I
want
I
wanna
apologize,
the
holidays
and
everything
a
maybe
made
me
drop.
The
made
me
drop
this
for
a
while,
but
I'll
pick
it
up
and
I
will
definitely
a
swing.
A
swing
by
the
really
see
a
channel.
It's
a
signal
channel
to
see
if
it
to
see
if
I
can
get
any
more
help
on
this.
So
I'll
update
that
later.
A
A
A
I
thought
I
heard
something
so
we'll
leave
this
one
and
let's
ping
people
later
on
that.
So
that's
that
release
117,
give
my
win.
I
think
we
can
do
much
from
that,
a
other
than
penguin
and
ask
so.
Let's
move
on
to
document
kubernetes,
release,
team
groups,
criteria,
shadow
halo
process
and
adjusting
PR
boilerplate
for
stuff,
so
document
coronet
is
released
in
Google
Groups
membership
criteria
created
January,
21
and
I
see
some
very
generally
turning
o
2019
okay.
So
this
one
is
a
bit
old.
Is
he
some
starless.
A
A
H
A
A
Ensure
released
in
late
handbook
includes
an
item
for
adding
they
released
retrospective
event
all
to
the
release
calendar.
Oh
I
cannot
forget
about
this
one,
but
this
is
a
quick
documentation
issue
and
can
take
a
can
take
it
over
its
assigned
to
me
anyway.
So
doesn't
matter
what
was
this
one
and
she
really
are
killing
handbook
okay.
So
next
couple
issues
117
release
retrospective
is.
A
K
A
K
A
A
A
A
A
A
So
the
important
process
is
more
or
less
done
right
now
we
have
to
go
through
the
off-boarding
and
there
are
some
funny
rules
about
keeping
their
release.
Team
leads
from
people,
you
say
from
people's
releases
around
in
some
older
files
and
some
other
interesting
places.
So
that's
yet
to
be
done,
but
in
progress
and
at
Cornell
it's
early
support
period
camp-
and
this
was
commented
5
days
ago.
So
this
definitely
seems
to
be
in
progress.
A
A
A
K
A
A
A
F
A
A
10
I
feel
like
I,
should
at
least
comment
on
the
comment
on
this
because
the
big
ideas
since
we
started
this
release
tip
this
relay
this
release
team.
This
cycle
is
that
they
released
the
release.
A
released
in
MIDI
notes
are
going
to
be
the
source
of
truth,
and
if
you
want
to
update
things,
people
everyone
should
be
should
be
making
decisions
of
what
a
whatever
is
in
the
latest
update
and
if
you're
an
a,
if
it's
not
possible.
A
A
If
you,
when
we
can
just
read
it,
we
can
just
read
it
or
something,
but
if
anyone
has
any
more
comments,
questions
suggestions,
any
ideas
that
you
wanna,
that
you
want
to
draw
the
trout
here,
please
feel
free
to
take
on
the
take
on
the
issue
top
come
a
comment.
Any
questions
comments
concerns
that
you
have
and
since
there
is
already
a
bunch
of
work
that
needs
to
be
organized
and
distributed
is,
will
anybody
be
opposed
to
for
us
to
just
enter
a
ended
with
going
through
in
progress
into
the?