►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200703
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
A
We
just
jump
right
into
things
drop
the
agenda
into
the
chat.
Please
add
yourself
to
the
meeting
and
before
we
get
started
just
a
reminder
that
this
meeting
is
covered
by
the
kubernetes
code
of
conduct,
which
could
be
boiled
down
to
be
excellent
to
one
another.
The
meeting
is
recorded
will
be
on
the
internet,
so
be
mindful
of
what
you
say
and
with
that
let's
get
started
with
enhancements
in
naba
room,
hello,.
B
Everyone,
so
this
is
kind
of
read
right
now,
the
reason
being
there
are
a
lot
of
enhancements
which
are
yet
to
have
significant
progress
and
by
significant
I
mean
like
they
have
a
lot
of.
Maybe
tests
are
remaining
to
be
completed
or
like
just
a
flaking
or
like
there
is
no
entity
named
or
approved,
or
they
are
far
away
from
like
even
merging
it
in
the
next
six
days,
other
than
that
13
enhancements
have
already
have
completed
all
of
the
requirements
to
four
code
freeze.
They
might
have
some
Doc's.
B
We
are
left
here
in
there
or
some
even
have
that
done,
and
11
enhancements
are
certainly
read
as
in
like
we're.
Certainly
thinking
that,
most
probably
they
will
miss
the
freeze
other
than
that
rest
of
the
enhancements.
We
are
actively
tracking
and
reaching
out
to
the
owners.
We
are
awaiting
replies
from
some
owners
regarding
what
is
happening
and
how
do
they
feel
about
pushing
it
before
the
code
freeze
and
other
than
that,
one
enhancement
from
six
storage.
B
A
B
A
You
for
that
pretty
detailed
update,
we're
gonna,
send
the
communication
out
on
Monday
I
think
with
a
reminder
of
the
code
freeze,
which
will
be
the
end
of
day
Thursday.
So
there's
still
some
time
for
the
changes
to
happen
here.
But
if
you
have
any
concerns
about
any
particular
issues,
you'd
like
us
to
help
reach
out
or
our
ping,
the
SIG's
try
to
Shepherd
some
reviews
along
feel
free
to
ping,
myself
or
Bob
or
Taylor
Tim,
be
happy
to
to
jump
in
and
help
as
much
as
we
can.
Any
questions
for
number
room.
D
Folks
hope
everyone
is
having
a
happy
Friday,
pretty
short
update.
Today
we
only
have
a
few
flakes
on
master
blocking
and
we're
looking
pretty
healthy
there.
Few
of
those
are
misnomers.
As
usual,
as
I
said
last
meeting
conformance
J
only
has
been
totally
green
at
dis
runs
twice
a
day,
so
it
takes
it
quite
a
while
after
it
has
a
failure
to
start
reporting
green
again,
GC
cost
master
default
that
one's
been
tracked
for
a
while,
but
we're
seeing
a
new
flake
this
morning
on
cig
instrumentation
tests,
so
I'm
gonna
reach
out
to
them.
D
Gc
cost
master
scalability,
that's
kind
of
been
we've
been
saying
flakes
there
for
while
and
it's
kind
of
expected,
so
not
a
big
concern.
There
I'm
G
see
a
bunch
of
master
container
D.
We
saw
three
consecutive
flakes
this
morning,
which
can
can
frequently
indicate
that
there's
something
wrong
besides
the
normal
flakes,
so
we're
gonna
keep
monitoring
that
and
see
if
we
need
to
take
action
other
than
tracking
it.
At
that
current
issue,
con
jobs
are
kinda
at
their
normal
level
of
flakiness.
So
so
that's
also
expected.
At
this
point
note
cubelet
master
once
again.
D
Sig
note
is
it's
kind
of
meeting
weekly
to
talk
about
their
tests
and
they're
doing
a
great
job
there,
so
having
some
inertia
per,
confer
concerns
with
time
outs
and
network
connectivity
over
there,
but
still
getting
pretty
good
signal
on
that.
So
overall,
this
is
probably
the
best.
The
board
has
looked
in
a
little
while
on
master
informing
just
some
updates
on
to
open
stacking
cafe
jobs.
D
Those
are
still
failing,
there's
still
folks
working
on
it.
We
did
not
reach
out
to
them
today,
just
to
respect
their
time
off,
but
you
know
they're
actively
being
addressed
there.
So,
hopefully,
early
next
week,
we'll
see
we'll
see
further
PRS
merged
other
sides,
that's
just
the
Windows
jobs
which
we're
trying
to
help
out
with
as
best
we
can
and
and
see.
If
we
can
get
a
little
more
a
little
more
green
over
there.
But
looking
looking
pretty
good,
this
Friday
cool.
A
E
A
F
F
A
A
G
A
A
A
H
A
Alright,
we'll
look
forward
to
that
next
week.
Nothing
from
Tim
the
emeritus
lead
updates
from
the
release
lead
team.
Again,
two
big
milestones
coming
up
are
the
code
freeze,
which
would
be
on
July
9th,
which
is
Thursday
there'll,
be
end
of
day
ish
and
then
Thursday.
The
16th,
which
is
the
week
after
will
be
the
docs
freeze
them
at
all.
The
docs
have
to
be
merge
at
that
point.
A
So
what's
code
freeze
comes
around,
we
can
circle
back
on
some
of
those
docs
things
and
try
to
push
them
forward,
see
where
extra
attention
might
be
needed.
6
scalability
update
looks
like
it's
the
same
one
from
previous
meeting,
so
no
change
there
and
then
we'll
put
up
for
open
discussion
items.
Does
anybody
have
anything
that
hasn't
been
on
the
agenda
that
they'd
like
to
bring
up
or
any
other
concerns,
as
we
go
into
next
week
with
the
code
freeze.