►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200617
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
A
A
A
This
is
a
kubernetes
meeting,
so
this
does
a
bye,
bye.
The
kubernetes
code
of
conduct,
which
simplifies
down
to
please,
be
excellent
to
one
another
and
this
will
be
sure
to
YouTube,
so
be
mindful
of
that
as
well.
With
that
being
said,
I'd
love
it
I'd
love
to
kick
it
over
to
enhancements
with
Kirsten
hi.
B
Can
you
hear
me,
oh
cool
I,
see
nodding
heads
good
morning
good
afternoon
good
evening,
where
our
numbers
aren't
changed
from
Monday
and
we're
green,
so
we're
doing
pretty
well,
we
are
in
the
process
of
just
paying
all
of
the
LV
enhancements
to
let
people
know
about
the
code.
Freeze
change
just
to
keep
everybody
informed
as
well.
So
that's
all
that
we
really
have
to
update
for
today
and
that's
it.
C
Thanks
Sarah,
so
we
are
looking
pretty
good
here,
we're
yellow
just
because
we
still
have
some
flakes
on
master
blocking,
but
they're
pretty
much
all
under
control
still
having
some
issues
with
the
kind
tests
I'm
still
looking
into
those
integration
master
started.
Timing
out
semi-regularly
so
probably
need
some
further
investigation
there.
C
Most
of
these
flakes
are
related
to
timeouts
a
couple
notable
events,
so
I
bumped
static
check
in
kubernetes,
because
we
are
seeing
some
flakes
on
verify
master.
So,
hopefully
that's
going
to
help
with
the
the
pre
submit
test
as
well,
but
with
the
bump.
There
are
some
some
actual
static
check,
failures
that
are
introduced
by
the
different
checks
it
makes
now.
So
those
need
to
be
updated.
The
container
run
time
issue
that
DIMMs
fixed
for
us,
a
while
back
or
I
guess
I
was
just
last
week.
C
C
In
that
vein,
cap
G
was
failing
consistently
because
of
a
change
to
the
CI
script
over
in
their
repo,
but
that
has
been
updated
so
thanks
to
them
for
a
quick
response
there,
but
cluster
API
AWS
provider
is
now
failing
from
a
PR
that
was
my
gesture
day,
but
they
have
informed
us
that
they're
looking
into
that
so
overall,
looking
pretty
good.
The
one
other
thing
to
note
here:
that's
not
a
normal
thing,
as
the
OpenStack
job
is
still
failing
consistently.
We
don't
have
a
lot
of
ability
to
do
anything.
C
A
D
Hello,
everyone
copy
Wednesday,
so
our
status
is
current
yellow,
but
the
good
news
is
that
our
numbers
are
decreasing,
so
without
rhythm
were
expecting
to
go
green
next
week,
so
we
are
on
27,
not
test
Lake
equivalents,
for
this
is
useful.
This
is
like
to
less
than
Monday,
which
is
great
news
as
well.
D
There
is
only
two
critical
urgent
issues
and
13
important
soon,
which
which
like
as
well
from
muddy
for
PRS,
we
are
like
36,
which
is
like
one
less
money
as
well,
and
there's
no
PR
for
with
good
colors
are
labeled
priority
and
foreign
soon
be
ours.
We
are
on
17,
which
is
three
down
the
muddy
which
great
news
as
well
so
and
for
other
reasons
for
that.
A
E
Everyone
good
day
or
good
evening,
mrs.
where
you
are
so
our
status
is
currently
red
and
that's
mostly
owing
to
the
fact
that
we
haven't
received
a
draft
PR
for
three
of
the
enhancements
and
I've
noted
it
down
in
the
agenda
meeting
agenda
and
three
of
the
announcements
that
require
documentation.
They
haven't
submitted
a
draft
PR
yet
and
we
are
yet
to
receive
an
update
on
the
requirement
for
Phi
of
the
other
enhancements,
so
we
will
be
following
up
with
the
cig
leads
respective
cichlids.
However,
I
wanted
to
throw
it
up
for
discussion.
A
Actually
did
reach
out
to
number
in
in
myself
this
morning
and
kind
of
brought
this
up
a
little
bit.
I'd
say
we
might
check
in
a
little
bit
later
today
to
give
the
give
the
teams
time
to
respond
to
those
issues
and
get
those
pr's
in
if
they
have
not.
You
know,
maybe
this
afternoon,
we'll
try
to
set
a
time,
and
then
we
can
start
to
raise
it
up,
bring
it
up
to
sig
leads
if
we
have
to
and
then
you
know
just
keep
escalating
until
we
get
a
response
on
this,
but
no
definitely
agree.
A
A
G
It's
part
of
how
we
keep
this
release
team
sustainable
across
time,
make
sure
that
people
are
coming
in
and
being
productive.
So
so
that's
good
again.
I
want
to
just
encourage
shadows
to
use
that
opportunity.
We've
got
a
mailing
list
for
it
and
just
feel
feel
empowered
to
ask
questions
and
and
learn
about
the
project
about
the
cig.
Beyond
just
your
shadow
release,
team
role.
A
Cool,
thank
you
so
much
Jim
and
yeah.
It's
it
any
feedback.
Any
process,
improvement
I
just
want
to
give
you
a
huge
plus
once
it's
him
on
that
front.
It's
interesting
all
of
the
different
contexts
and
is
hard
to
recall.
You
know
some
of
them
within
certain
times
definitely
was
in
a
released
meeting.
I
know
as
soon
as
the
call
ends
I
usually
have
about
five
questions
myself,
so
huge,
plus
one
on
that
front.
A
Awesome
updates
that
I
have
for
you
for
this
Friday
June
19th
is
the
docks
deadline
for
the
open,
placeholder
PRS
as
one
of
the
deadlines
that
we
moved
out.
We
did
get
that
update
from
docks,
so
we
reaching
out
to
those
teams
if
we
don't
hear
back
from
them
today
and
help
with
that
deadline.
The
next
other
after
that
is
July
6th
on
Friday,
and
that
is
another
Doc's
dilemma.
I'd
double-check,
that's
Friday,
I,
don't
think
that's
right!
A
A
Moving
into
open
discussion,
one
thing
I
do
want
to
highlight
it's
kind
of
relating
to
the
note
about
shadows
is
the
the
end
of
the
cycle
we
have
is
at
the
end
of
August
and
I
promise
that
you'll
blink
your
eyes
and
will
be
there
already.
It
seems
like
it's
very
far
away,
but
it
will
catch
up
to
us.
A
I
promise
now
is
a
great
time
to
start
thinking
about
retrospective
items
and
getting
those
put
in
it's
always
great
to
put
those
in
when
they're
fresh
in
your
mind,
because,
obviously
weeks
in
time,
that
kind
of
degrade
on
that.
So
as
soon
as
you
have
an
idea
feel
free
to
put
it
in
there,
you
can
always
take
it
out
later.
So
I
definitely
welcome
that
and
definitely
a
good
idea
to
start
bringing
some
items
in
there
other
than
that
I
don't
have
anything
else
and
would
love
to
open
up
the
floor.