►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200622
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
Hello,
everyone
and
welcome
to
the
monday
june
22nd
kubernetes
119,
release
team
meeting,
I'm
jeremy
I'll
be
your
host.
Today,
this
meeting
is
recorded
and
because
we
are
part
of
the
kubernetes
community.
This
meeting
is
governed
by
the
kubernetes
code
of
conduct,
which
essentially
boils
down
to
be
excellent
to
one
another.
I've
dropped
the
link
to
the
agenda
into
the
chat.
Please
add
your
name
to
the
attendees.
If
you're
joining
the
meeting
today
and
with
that,
we
will
kick
it
off
with
enhancements
with
naparoon.
B
Hi
everyone
hope
you
all
had
a
good
weekend.
So
enhancements
is
green.
As
of
now
we
are
tracking
43
enhancements
with
13
in
alpha
18
in
beta
and
12
in
stable
other
than
that
one
enhancement
got
deferred
today.
They
so
the
op
told
that
they
would
not
be
able
to
make
it
in
1.19
and
they
want
to
be
referred
to
1.20.
B
C
C
So
I
left
some
notes
here,
notably
conformance
ga
only
started
flaking
today,
which
I
think
hassan
who's
on
that
call
who's
on
this
call
opened
an
issue
for
that
initially
looked
like
it
was
failing,
but
then
it
recovered
so
we're
going
to
keep
monitoring
that
rob
has
been
looking
into
some
spiking
performance
on
cost
master
default,
and
so
I
think
we're
going
to
keep
looking
at
that
as
well
scalability
100
flaked.
This
morning
we
haven't
seen
too
many
of
those,
so
not
too
worried
about
that
one.
C
There
was
a
comment
on
ubuntu
master
container
d,
about
marking
a
a
cube,
ctl
test.
That's
been
flaking,
really
regularly,
it's
just
flaky
and
then
kind
of
not
worrying
about
it,
because
it's
basically
a
non-deterministic
test.
But
if
that's
the
case,
it
doesn't
really
make
sense
too
much
to
have
that
on
master
blocking.
C
So
I
think
that's
still
being
explored,
but
you
can
see
the
conversation
in
the
issue
there.
Gc
conformance
master
just
had
one
flake,
I'm
not
too
worried
about
that,
and
then
the
kind
tests
I've
have
gotten
increasingly
flaky
over
the
past
few
weeks.
They
are
being
monitored
and
they're
still
giving
a
decent
signal,
but
we're
going
to
try
and
get
that
a
little
bit
more
under
control,
especially
the
kind
ipv6.
C
That's
been
pretty
red
lately,
node
cubelet
master,
if
y'all
remember
a
few
weeks
ago,
was
having
a
lot
of
issues
and
it's
been
a
lot
better
since
then,
but
the
flakes
have
kind
of
started
to
pick
up
there.
Most
of
it
due
to
timeouts
signate,
has
kind
of
bootstrapped
its
own
testing
effort
over
there,
where
they're
doing
a
bit
of
kind
of
ci
signal,
work
and
investigation
on
their
end.
C
So
we
really
appreciate
that,
and
I
believe
they
are
looking
into
it
during
that
time,
which
I
believe
is
also
on
mondays
on
master
informing.
We
have
four
failing
jobs,
same
ones,
we've
been
talking
about
for
the
last
week,
openstack
job,
that
one
is
related
to
how
they're
setting
up
the
cluster
that
the
conformance
tests
are
running
on
and
that
is
being
investigated
in
their
slack
channel
cap.
A
there's
expected
to
be
a
pr
today
to
get
that
running
again.
C
A
Great
thanks
is
there
anything
that
we
can
do
to
help
you
guys
be
more
successful
anything
blocking
you
that
we
can
help
with.
C
I
don't
think
so
right
now,
we've
been
pretty
good
about
reaching
out
and
peeing
folks,
the
team,
the
ci
signal
shadows,
have
been
really
great
with
that.
So
we
appreciate
that
a
lot.
One
thing
just
to
note
spoke
with
sig
testing.
This
morning,
we've
kind
of
been
sig
testing
has
seemed
to
get
applied
to
a
lot
of
issues
that
aren't
necessarily
owned
by
them,
because
it
just
kind
of
feels
like
sort
of
a
catch-all
when
a
flakier
failing
test
is
observed
and
that's
definitely
not
a
sustainable
way.
C
A
Okay,
thank
you
so
much
daniel.
Let's
move
on
to
bug
triage
this
time
with
karen.
D
Hey,
we
saw
a
bunch
of
the
pr
issues
are
staying
or
the
pr
numbers
are
staying
the
same.
The
issues
jumped
over
the
weekend,
I'll
catch
up
in
slack
and
see
what's
going
on
there.
Otherwise,
I
think
we're
still
at
yellow
we
don't
have.
We
do
have
a
couple
critical
issues,
but
we
don't
see
the
numbers
going
down
overall,
that's
about
it.
A
With
mikhail.
E
A
E
A
All
right,
thank
you.
Let's
move
on
to
to
release
notes
with
adolfo.
G
Hi,
so
we're
green
since
we'll
be
pretty
much
waiting
for
the
next
unrealistic
up
and
there
have
been
no
changes
in
the
release.
Notes
from.
A
H
Hi,
this
is
kendall
rhoden,
I'm
one
of
the
calm
shadows,
so
I
can
cover
sure,
go
for
it.
Kendall,
yeah,
so
we're
still
green.
The
cncf
is
updated
in
accordance
with
the
new
release
timeline,
so
that
communications
happened.
We're
essentially
just
still
reaching
out
to
people
about
feature
posts.
H
So
if
you've
gone
ping
from
us
on
slack,
definitely
keep
you
know,
keep
that
in
mind
and
and
try
to
respond
to
that,
I'm
hoping
to
get
those
locked
down
within
the
next
week
or
so
and
then
we'll
get
drafts
later
in
the
process,
and
then
I
think,
officially
want
the
the
things
to
be
cleared
basically
on
the
release
timeline
and
then
got
the
first
input
for
the
release
blog,
so
everything's
moving
pretty
well
on
our
end.
A
Team,
great
release
branch
management:
sasha:
do
you
have
any
updates
for
us.
A
Great
moving
on
to
emeritus
lead
with
tim.
F
Hey
folks,
main
update
is
that
last
week
we
did
finally
hold
our
meetings
for
the
shadows.
Just
had
some
general
chat
about
how
things
work
and
kind
of
supplementing
folks,
knowledge
and
understanding
of
the
process,
with
release,
team
and
sig
release
and
fanning
out
into
kubernetes,
and
also
a
lot
of
talk
just
about
how
kind
of
you
you
grow
and
and
do
more
things
in
the
community
beyond
release
team.
So
yeah
just
having
those
sorts
of
conversations,
I
think
it
was
constructive.
Hopefully
everybody
got
something
out
of
it
and
that's
it
for
now.
A
Great
so
next
update
for
me
we
obviously
have
two
upcoming
deadlines.
The
first
will
be
monday
july
6th,
and
that
is
the
docs
deadline.
So
all
the
docs
should
be
ready
for
review
at
that
point,
and
then
that's
monday
and
then
on
thursday
july
9th
code
freeze
will
begin
so
we'll
need
to
have
all
of
the
prs
for
the
enhancements
ready
to
go
by
that
point.
A
Okay,
six
scalability
update,
looks
like
we
haven't,
had
one
since
last
meeting,
so
we'll
leave
it
at
that
and
with
that
we'll
open
it
up
for
open
discussion.
Just
a
quick
reminder,
if
you
have
encountered
anything
during
this
release
that
you
think
is
worth
mentioning,
the
retrospective
doc
is
open,
it's
great
to
add
them
now,
rather
than
waiting
till
the
end.
A
A
Awesome
with
that,
I
guess
we'll
just
end
the
meeting
early
today
and
give
you
back
some
of
your
time.
If
there
are
any
questions,
feel
free
to
reach
out
on
the
sid
release
channel
or
to
dm
taylor
or
bob
or
myself,
and
we
can
get
things
straightened
out
if
you
run
into
any
problems,
awesome
well,
everybody
have
a
great
afternoon
morning
evening,
whatever
it
may
be,
for
you
and
have
a
great
rest
of
the
week.