►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200706
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
And
we
are
live,
welcome
everyone
to
another
installment
of
the
119
release
team
at
meeting
today
is
July
sixth
Monday
and
I
hope
you
all
are
doing
well
in
the
US
we
had
a
little
bit
longer
weekends
that
was
nice.
Hopefully
most
of
us
got
some
sleep,
but
if
not,
you
know,
there's
always
there's
always
today
and
tomorrow.
A
This
is
a
kubernetes
meeting,
so
we
abide
by
the
code
of
conduct
which
simplifies
down.
So
you
please
be
excellent
to
one
another
yeah
really
looking
forward
to
today's
updates.
I've
got
a
couple
things
for
you,
which
I'll
cover
in
my
section:
I'd
love
to
kick
it
over
to
nob
rune,
with
enhancements.
A
A
B
Oh
yeah
I
hope
everyone
is
having
a
good
Monday
so
far,
so
we
are
yellow
but
no
failing
jobs
on
master
blocking.
We
do
have
a
fair
amount
of
flaking
jobs
this
morning,
but
they're
all
kind
of
their
normal
amount
of
flakiness.
So
you'll
see
here
that
a
lot
of
these
just
had
one
in
the
last
nine
or
ten
runs,
and
we
have
issues
open
tracking.
All
of
them.
One
encouraging
thing
to
see
this
morning
is
that
both
of
the
kind
jobs
are
much
more
green
than
they
have
been.
B
In
fact,
the
ipv6
job
might
actually
turn
completely
green
this
morning,
so
that
would
be
good
to
see.
But
overall,
we
are
in
pretty
good
shape.
Just
some
updates
on
some
of
the
failures
we've
had
on
master
informing
that
have
now
persisted,
maybe
two
weeks
or
so
the
OpenStack
job.
They
made
some
updates,
but
they're
still
working
through
how
to
get
that
cluster
configured,
how
they
need.
B
So
that's
currently
not
running
and
then
I
reached
out
to
the
cluster
API
AWS
team
this
morning
for
their
conformance
test
and
they
and
to
address
this
they
kind
of
did
a
larger
overhaul.
So
it's
taking
a
little
bit
more
time,
but
they
said
this
morning
that
they
are
hoping
to
have
a
PR
merge
by
the
end
of
today.
You
can
see
a
link
there
to
the
specific
PR
and
that's
being
mentioned.
B
Windows
jobs
are
still
very
read
per
usual
and
we
also
have
quite
a
few
flaky
jobs
on
informing
and
you'll
see
that
a
lot
of
those
are
the
cube
admin
kinder
jobs.
So
those
were
pretty
read
over
the
weekend,
but
we're
starting
to
see
some
green
runs
this
morning,
which
there
hasn't
been
able
to
identify
from
either
us
or
the
cube
admin
team.
Exactly
what's
going
wrong
there
and
it's
strange
that
they
turned
green
without
any
code
changes
on
either
the
test
in
for
kubernetes
side.
B
So
we're
gonna
continue
to
look
into
those
and
just
also
want
to
give
a
shout
out
to
the
sea.
I
signal
shadows,
there's
a
number
of
them
on
the
call
right
now
who
have
just
been
doing
a
super
job
of
keeping
track
of
stuff
and
digging
in
improving
process
stuff,
so
their
big
reason
why
the
boards
are
looking
better
today.
A
C
Everyone
what
phase
Lois
I
hope
you
all
had
an
amazing
weekend
and
good
morning
afternoon
or
evening
so
coming
to
the
updates
enhancements,
is
correctly
read.
The
primary
reason
of
that
is
nearly
one
third
of
our
enhancements
are
at
risk
majorly,
because
we
feel
that
they
have
a
lot
of
work
pending
or
they
might
not
go
through
the
freeze.
Due
to
this
very
specific
reason
or
some
other
reason.
We
have
been
actively
communicating
with
all
of
those
announcements,
owners
and
trying
to
figure
out.
C
How
can
we
make
the
process
better
or
how
can
we
speed
things
up
or
if
they
want
to
defer
to
the
next
release
other
than
that
17
enhancements
have
already
like
act,
acknowledge
that
hey
we
are
done
with
the
implementation.
We
are
good
to
go
for
this
release.
Some
of
them
have
even
have
the
docs,
peer-reviewed
and
ready
to
much.
That's
an
amazing
thing
and
eight
enhancements
are
currently
in
the
process
of
like
we
feel
that
hey,
given
the
amount
of
work
left.
C
They
will
certainly
finish
the
work
before
Thursday,
which
is
code
freeze
or
like
plain
simply.
They
have
finished
the
work
and
they
are
yet
to
acknowledge
us
back
that
hey
we,
we
did
all
the
work
and
it
is
done.
That's
all.
On
the
enhancement
side,
we
are
constantly
reminding
all
of
the
pending
enhancements
that
you
have
just
three
days
left
to
freeze
and
if
you
don't
complete
the
implementation
and
you
might
have
to
find
an
exception
for
the
same,
that's
all
on
our
site.
Any
questions,
comments
or
concerns.
C
A
You
never,
and
yes,
one
comments
on
that
front
is
that
after
this
meeting,
I'm
gonna
be
sending
out
a
announcement
to
ke
dev
singer
release
and
she
was
a
release
team,
just
reminding
everyone
of
code,
freeze
and
kind
of
getting
the
spotlight
on
that
I
know:
you've
done
a
fantastic
job
in
terms
of
reaching
out
to
each
of
the
SIG's
and
making
sure
that
they
know
about
this.
I
know
we're
still
waiting
to
hear
back
from
some
and
then
obviously,
you
know
being
in
red.
A
I
know
that
they're
quite
a
few
right
up
to
a
crunch
time
that
we're
still
waiting
for
word
back
or
getting
those
features
completed.
So
absolutely
here
to
help
on
that
front,
and
we
can
we
can
definitely
you
know,
raise
it
up
to
four
raise
it
up
if
we
need
to,
but
no
thank
you
very
much
any
other
questions
or
comments.
One.
C
Other
thing
I
want
to
give
a
shout
out
to
all
my
shadows.
They
have
been
doing
an
really
amazing
work.
It's
not
just
me
alone,
Webb,
who
has
been
reaching
out.
Everyone
has
been
equally
proactive
in
also
since,
even
even
though
this
is
this
has
been
an
extended
weekend,
everyone
has
been
pushing
hard
and
great
work
to
all
the
shadows,
Thanks.
A
D
We
are
in
a
status
of
red
right
now.
This
is
probably
because
we
have
two
critical
urgent
issues
that
are
still
remaining
open
at
this
moment
in
time.
Both
of
these
have
been
escalated
to
the
appropriate
SIG's
and
they're
still
getting
comments.
I
know
one.
We
could
probably
use
another
follow
up
on,
but
yeah
we're
currently
red
with
the
code
freeze
coming
up,
we'll
pry
started
a
bump
of
things
that
then
to
the
next
milestone.
If
we
don't
hear
back
from
certain
people
on
a
variety
of
these
issues
back
to
you,
Taylor
awesome.
A
Thank
you
so
much
John
yeah,
it's
with
with
everything
coming
up
here
to
code,
freeze
and
seemed
quite
a
bit.
Usually
just
you
know
more
and
more
communication
is
usually
what
we'll
do
to
help
out
with
these
things.
I'll
keep
an
eye
on
these
as
well,
but
alert
the
police
lead
shadows
and
this
as
well,
and
we
can
follow
up
if
the
need
arises
and
we
start
to
get
into
crunch
time
any
other
questions
for
bug
triage
or
for
John.
E
We've
also
communicated
the
dogs
deadlines
to
them,
updated
talks
templates
to
them,
and
you
know
following
up
with
them
as
an
as
a
priority.
So
given
that
we
have
15
PRS
that
are
ready
for
review
today,
two
PRS
are
merged,
and
that
was
the
status
last
meeting
as
well,
and
14
of
our
PRS
are,
as
of
now
in
the
work
in
progress
state
and
we
reached
out
to
the
concern,
function,
slack
and
get
happy
ours
yeah.
So
that's
it
for
mind.
E
A
F
Up
date,
with
Max
hi
everyone
so
far,
we
are
in
the
well
kind
of
gap
weeks,
looking
forward
in
the
I
think
in
two
weeks,
communicate
with
the
official
release
block
outlining
or
then
down
the
outline
of
surgeries
block
was
seen
CF,
comms
team
and
beside
that
we
are
now
on
six
feature
blocks,
which
is
great,
so
we
have
maybe
one
one
backup
or
one
additional
yeah.
Yet
fantastic.
A
B
I'm,
not
the
another,
a
branch
manager
ooh-
oh,
that's
it
that's
right!
Yeah
I
I
can
give
an
update.
I,
don't
think.
There's
too
much
to
say
at
this
meeting,
I
need
to
check
the
the
channels
and
make
sure,
but
there's
there's
nothing
massive,
but
I
mean
to
let
you
know
if,
but
there
might
be
something
minor
that
I'm
missing
out
on.
So,
if
you
have
any
questions,
please
feel
free
to
follow
up
and
sly
I.
G
Quiet
here,
as
well,
not
too
much
to
say,
I,
really
appreciate,
number
and
shout
out
to
his
shadows.
I,
hopefully
were
getting
that
across
all
of
the
roles
where
folks
are
leveraging.
The
shadows
well
and
the
shadows
are
feeling
like
they're,
getting
the
opportunity
to
contribute
well
and
are
stepping
up
and
contributing
so
great
robot.
Angling
number.
A
Any
questions
for
Tim
or
just
for
the
emeritus
advisor
citrusy,
sir
pointers,
come
in
handy
all
right,
so
my
update
this
Thursday
and
the
day
Pacific
we
do
have
code
freeze,
so
it
should
be
a
quite
exciting
week.
I
use
exciting
in
quotes
if
you
can't
hear
them
the
next
deadline
after
that
is
going
to
be
July
16th
with
the
docks
deadline
that
should
be
docks,
are
complete
so
going
to
I'm
sure
that
will
there
be
a
lot
of
communications,
a
lot
of
fielding
of
issues
going
on
within
the
next
two
to
plus
weeks.
A
A
Scalability
updates
not
sure
if
that
is
the
call
I,
don't
see
the
only
ball
last
up
that
we
have
skill.
Billiards,
look
good,
no,
release
blockers
as
now
moving
it
into
open
discussion
again,
please
check
out
the
retro.
If
you
have
not
picture
issues
in
there
and
would
like
to
open
up
for
just
general
discussion
if
there
are
any
questions,
comments
or
concerns
from
the
group
before
we
sign
off
for
the
day.
A
All
right,
thank
you.
So
much.
Everyone
sincerely
really
appreciate
all
of
you.
We
are
seven
weeks
out
from
release.
Hope
that
you're
feeling
good
those
jitters
and
butterflies
in
your
stomach
are
goodson
I
promise
looking
forward
to
seeing
119
come
out.
Please
don't
be
a
stranger.
Let
us
know
if
you
need
to
anything
whatsoever
and
we'll
be
here
to
help
have
a
wonderful
Monday.
Everyone
see
y'all
soon.