►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200806
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
B
All
right
welcome
everyone
to
another
119
release
team
meeting
today
is
thursday
august
6th,
I'm
taylor
dolezal
your
release,
lead
and
very
happy
to
be
here
today.
It's
thursday
we're
almost
at
friday.
B
C
Hey
everyone
hi,
so
enhancements
is
green,
we're
tracking
34
announcements
in
total
nine
graduating
to
alpha
15
graduating
to
stable
and
10
enhancements.
Oh
sorry,
15
announcements
graduating
to
beta
and
10
announcements
graduating
to
stable
sorry
for
the
mess
up
on
call
week.
No.
D
Hey
folks,
we're
yellow
today
two
notable
events
I
mentioned
one
of
them.
Yesterday
the
cube
control
skew
tests
are
using
the
wrong
version
markers.
I
have
some
pr
open
to
address
that
by
updating
the
flags
past
from
the
build
jobs
which
publish
and
update
those
version
markers.
So
I'm
just
waiting
for
reviews
on
those
it
should
work
like
the.
The
idea
is
that
the
existing
flags
that
are
being
passed
would
work
yet
apparently
push
build
is
ignoring
them,
so,
as
opposed
to
trying
to
figure
out
why
it's
happening.
D
I
just
went
with
using
the
new
flags,
so
we'll
see
if
that's
the
decided
route
or
we
need
to
go
back
and
fix
that
or
maybe
follow
up
with
that,
but
hopefully
we'll
get
that
addressed
today.
D
Other
issue
mentioned
here
is
we'd
like
for
the
pod
info
json
file,
to
also
be
published
when
jobs
have
pod
scheduling
timeouts,
because
right
now
it
just
basically
reports
that
there's
a
pod
scheduling
timeout
on
the
proud
job,
but
we
have
no
idea
why
that
might
be
why
it
wasn't
able
to
be
assigned
to
a
node.
So
hopefully
we
can
get
some
more
information
there.
D
Looking
at
the
dashboards,
we
are
a
little
bit
more
flaky
today.
Most
of
them
are
things
that
we've
seen
before
trying
to
think.
If
there's
anything
here,
that's
super
notable
bazel
build
master,
had
two
failures:
not
on
pod
scheduling
timeouts
but
on
pod,
pending
timeouts,
which
we
don't
see
frequently
so
going
to
be
looking
at
that
a
little
bit
more
also
on
kind
ipv6
master
parallel.
D
There
was
a
cube
control
conformance
test
that
failed,
there's
been
an
issue
open
for
this,
but
it
was
moved
out
of
1.19
to
120
because
it
was
deemed
not
release
blocking
and
it
hadn't
happened
for
a
while.
It
was
actually
open
for
another
job
originally,
but
since
it
is
a
conformance
test,
we
definitely
want
to
look
at
that.
D
So
considering
bumping
that
back
into
1.19,
see
if
the
cli
folks
can
look
at
that,
everything
else
is
pretty
much
as
it
has
been
one
thing
to
note
on
master
and
forming
that
cap
g
job
is
still
failing,
and
that's
due
to
the
missing
python
3
modules.
Those
were
originally
added
which
broke
other
things,
so
we
reverted
it.
But
there
is
a
pr
open
to
add
back
python
3
with
the
pi
yaml
fix,
which
should
theoretically
enable
them
to
have
that
job
passing
again,
so,
hopefully
that
pr
gets
merged.
D
Today
I
saw
dems
pinged,
aaron
and
ben
for
review
there
this
morning
and
hopefully,
once
that
gets
in.
We
can
follow
up
with
the
cluster
api
folks,
but
overall,
a
little
more
flaky,
but
nothing
too
concerning
here
awesome.
Thank
you.
So
much
dan.
B
Awesome
thanks
again,
jan
let's
move
on
to
bug
triage.
B
If
we
don't
have
someone
from
bug
triage
on
the
call,
we
can
jump
back
there
if
somebody
else
joins.
I
think
it
was
yellow
yesterday,
but
we
could
follow
up
with
them.
Let's
move
on
to
docs.
A
B
B
All
right
release
nets
with
whoops
jumped
at
offer.
E
Yeah
yeah,
so
we
are
currently
green.
We,
I
think
james
generated
the
draft
when
the
last
rc
was
cut,
and
I
think
next
monday,
we'll
start
editing
and
compiling
the
the
themes
we've
gotten
from
the
from
hc
into
the
final
document
and
the
final
edition
of
the
final
release
notes
argument.
B
Fantastic,
any
questions
for
release,
notes.
B
All
right
no
worries.
Let's
move
on
to
release
branch
management
with
sasha
hey,
we
are
cream
and
we
don't
have
any
updates
since
yesterday,
fantastic
any
questions
for
release
branch
management,
awesome,
awesome,
tim
is
now
able
to
join
us
this
morning.
B
Moving
on
to
the
release
lead
update
today
is
cherry
pick
deadline
and
test
freeze,
so
that
will
be
exciting,
it'll,
be
in
a
day,
pacific
and
then
rolling
into
next
week,
both
next
week
and
a
week
following
week
leading
up
to
kubecon
and
we
during
kubecon
we
won't
be
meeting
synchronously,
so
we'll
be
meaning
asynchronously.
A
few
most
of
us
are
green
in
in
different
sections
and
areas.
B
I
know
there's
still
quite
a
few
tests,
both
flakes
and
and
you
know,
we've
got
go
115
as
one
of
the
things
we're
juggling
qos
and
just
a
whole
bunch
of
other
things
going
on.
If
you
see
something,
please
say
something,
so
we
can
address
that
if
there's
anything
that
would
put
you
in
a
yellow
or
red
status
as
we
are
leading
up
to
the
release
on
the
25th.
B
Obviously
you
know
just
make
sure
that
that
we
know
about
that.
We
can
adjust
accordingly,
we
will
resume
our
meetings
on
the
24th,
which
is
a
monday
proposed
releases
on
a
tuesday,
so
we'll
still
have
a
check-in
to
to
make
sure
that
everything's,
where
we
want
it
to
be,
and
if
we
need
to
push
out,
we
need
to
push
out
make
sure
everything
is
good.
So
should
be
good.
B
On
that
front,
I
don't
have
an
update
from
sig
scalability,
but
no
there's
still
quite
a
few
things
getting
worked
out
with
those
tests
and
let's
move
it
into
open
discussion.
Lori.
Did
you
want
to
kick
that?
One
off.
F
Yeah
and
I
just
have
to
find
a
tab
with
the
agenda.
Why
did
I
do
this
to
myself,
but
I
think
I
remember
them
anyway.
So
basically,
I've
added
links
there's
a
lot
of
project
boards,
I'm
looking
at
at
the
moment.
So,
as
you
know,
there's
a
ci
policy
improvements
effort.
So
I'm
just
watching
that
space
to
see
how
those
items
are
moving
across
the
board.
So
we're
done
just
seeing
how
how
it
goes
then
pretty
much
done.
Revising
the
release.
Engineering
board.
The
revisions
are
temporary.
F
We
have
a
lot
of
things
are
marked
in
progress,
but
I
haven't
really
had
movement
in
a
few
months,
so
at
the
next
release
engineering
meeting,
I
hope
to
just
walk
the
board
with
the
group
and
see
what
what
we
might
do
there
and
then
I've
also
created
some
columns
for
high
priority
themes
that
we've
talked
about
like
the
golang
updates,
debian
based
images
and
then
also
for
120.
F
Looking,
we
wouldn't
be
able
to
start
now
so,
but
it's
a
coming
for
that
cycle
krell
and
then
for
the
release
team
proper.
F
I'm
gonna
work
on
that
board
tomorrow
and
also
look
at
sig
release
board
and
then
take
the
items
make
sure
that
the
items
that
we
talked
about
when
we
met
in
those
prioritization
sessions
or
in
probably
the
sig
release
board,
because
they're
going
to
be
longer
term
so,
but
it
will
make
your
your
feedback
on
what
is
important
like
we'll,
have
a
we'll
have
a
tracking
mechanism
to
start
pulling
that
into
a
tighter
workflow,
and
I
think
that
was
is
that
it?
F
I
think
that
was
it.
Oh
there's
also
the
user
stories
that
I
sent
out
in
the
email
the
other
day.
The
link
is
in
the
agenda.
So
now
we
have
savita
divya
and
max
all
working
on
the
docs
topic
that
was
hugely
important
for
making
the
onboarding
experience
easier
and
contributor
experience
easier.
So
I
guess
they
will
be
taking
a
look
at
that
as
a
work
package
and
then
on
their
terms
and
schedule
breaking
that
down
and
making
movement
on
that.
F
B
Awesome.
Thank
you.
So
much
lori
lots
to
untangle
there
for
sure
a
real
gordian
knot
of
stuff
to
look
at.
B
Thank
you,
lori.
Any
questions
for
laurie.
B
Awesome,
thank
you
laurie.
As
always,
if
anything
comes
to
mind
that
you
liked
didn't
like
want
to
improve
with
future
releases
and
just
commentary
about
119,
the
retro
link
is
live
and
looking
for
comments
and
more
things
added
to
that
document.
Other
than
that,
I
don't
think
I
have
anything
other
than
excited
for
friday.
B
Excellent,
well,
I
wish
you
all
a
fantastic
thursday
to
those
of
you
on
call.
I
wish
you
a
lot
of
caffeine
and
hopefully,
a
lack
of
alerts.
Other
than
that.
I
will
see
you
all
tomorrow,
friday,
enjoy
talk
to
y'all
soon
have
a
good
one.
Have.