►
From YouTube: Kuberneres 1.19 Release Team Meeting 20200803
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
welcome
to
the
week
18
kubernetes
119,
release
burn
down
meeting
today
is
august,
the
3rd
just
a
quick
reminder
before
we
get
started.
This
meeting
is
part
of
the
kubernetes
community
at
large
and
we
are
governed
by
the
kubernetes
code
of
conduct,
which
can
be
boiled
down
to
be
awesome
to
each
other.
This
meeting
will
be
recorded,
so
anything
that
you
say
will
be
on
the
internet
forever
and
with
that
we
will
kick
it
off
with
enhancements
with
kirsten.
B
Hi
all
happy
monday,
I'm
doing
the
enhancements
update
and
we
are
all
green.
We
don't
really
have
any
updates
since
last
friday,
so
we're
just
pulling
out
for
now.
That's
it.
C
Hey
folks,
happy
monday,
we
are
yellow
today
in
part
because
of
the
weekend
we're
having
some
issues
with
the
url
being
used
for
fast
builds,
which
all
of
the
master
blocking
jobs
were
just
changed
over
to
use
that
so
that
has
been
resolved,
but
a
couple
are
still
showing
flaky
that
don't
run
that
often
other
than
that
conformance
j.
Only
and
kinemaster
parallel
are
both
experiencing
pod
scheduling,
timeouts.
You
can
see
on
that
issue
that
that
is
going
to
have
to
be
fixed
by
adjusting
the
cluster
size.
C
So
we
need
to
rely
on
some
tests
and
for
folks
to
do
that
for
context
both
of
those
consume
an
entire
node
to
be
able
to
run.
So
you
can
imagine
that
it
could
be
pretty
frequent
that
they
have
pod
scheduling
timeouts,
because
there
isn't
a
full
node
available.
C
So
once
those
are
bumped
up,
that
should
be
good.
Otherwise,
some
of
the
other
flakes
are
also
due
to
pod
scheduling
issues
which
we'll
continue
to
see
as
we
continue
to
add
resource
requests
and
limits
to
each
of
these
jobs
and
we'll
adjust.
Accordingly,
there
was
a
flake
on
integration
master
this
morning
and
there's
already
a
pr
open
to
fix
that,
so
we're
looking
pretty
good
there,
no
other
real
updates.
C
Besides
the
cap,
g
job
was
had
a
pr
open
to
fix
it
last
week,
but
that
had
to
be
rever
reverted
over
the
weekend
because
of
an
issue
with
using
python
3
and
the
bootstrap
image
was
causing
verify
master
to
fail
because
it
was
using
the
pi
ammo
package
and
there
were
python
2
and
python
3
conflicts
there.
C
A
Great
thanks
dan,
just
a
quick
question
on
the
one
that's
failing,
and
you
said
the
test
info
will
need
to
fix.
Is
that
something
that
you
think
that
they're
going
to
get
to
today,
or
should
we
try
to
follow
up
with
them
and.
C
Figure
out
what
the
process
priority
for
that
is:
yeah,
aaron
and
ben.
Both
commented
on
this
issue.
That's
linked
here
on
the
pod
scheduling
timeout,
so
I
can
talk
to
them
out
of
band
if
needed,
but
they're
usually
extremely
responsive.
So
I
imagine
they
get
that
do
that
pretty
quickly.
Okay,.
A
Thank
you.
Any
questions
for
ci
signal
and
dan.
A
Okay,
thank
you
for
that
pretty
detailed
update.
As
always,
let's
move
on
to
bug
triage
with
vlad.
D
Hey
we
are
yellow.
We
have
one
critical,
urgent
issue
since
friday,
it
it
is
actually
fixed
in
119.
It's
not
closed,
because
there
are
three
cherry
peaks
open
for
116,
17
and
18..
We
have
also
not
seen
flakes
or
like
major
issues
related
to
115,
to
go
115
update
so
far
so
good.
I
would
say.
A
Okay,
thanks
again
vlad
docs.
E
Hello,
everyone
hope
everyone's
doing
good.
Today
we
are
green
on
the
branch
1.1.19
and
I
have
a
branch
sink
in
progress.
The
build
just
teared
out
after
I
put
all
the
thing
in
the
document
and
said
it's
all
green
and
happy
so
I'm
gonna
go
debug
that
in
a
while.
So
that's
all
from
me!
Oh
still,
we
are
good.
We
are
in
green,
so
any
questions.
A
And
for
me,
let
me
know
if
you
need
help
tracking
down
why
that
build
was
failing
or
anything
else
related
to
ducks.
F
No
release
notes
is
green,
we
believe
we
have
generated
release,
notes
and
everything
is
up
to
date
and
we
also
started
working
on
drafting
the
release
notes
for
the
primary
page.
Releasing
it
any
questions.
A
All
right,
thanks,
we'll
go
to
columns.
G
A
G
Hey,
we
are
still
staying
yellow
the
wreath
block
is
so
far
completed.
We
have
now
some
time
for
polishing
to
the
next
weeks,
but
we
are
on
the
yellow
track
currently
because
one
out
of
five
feature
blocks
just
have
delivered
something
so
far
for
sure
we
have
a
couple
of
more
weeks
to
go
but,
as
you
all
know,
a
coupon
jumps
into
the
middle
and
then
time
getting
short
and
then
it's
getting
stressful
and
we
release
and
then
needs
to
come
the
feature
blocks.
G
So
we
need
to
reach
out
again
and
to
get
some
more
input.
Input
here
and
also
I
haven't
heard
something
back
from
cncf
since
since
a
while
for
sure,
they're
also
quite
blocked
with
the
cubecon.
G
G
Yeah
and
also
this
week
we
will
ping
again
the
feature
block
the
contributors
and
the
sick
leads
and
also
will
directly
reach
out
to
eli
from
cncf
at
least
to
to
hear
that
they
are
still
alive
and
everything
is
fine,
and
if
till
the
end
of
the
week
we
haven't
heard
something
back.
Then
we'll
come
back
back
to
your
offer.
Okay,.
A
Sounds
great
keep
us
in
the
loop
and
taylor
and
bob,
and
I
will
be
happy
to
help
bob's
doing
his
on
boarding
for
his
new
job
this
week.
So
he's
probably
a
little
out
of
pocket,
but
just
give
us
a
shout
and
we'll
help
in
any
way.
We
can
sure
thanks
all
right
release
branch
management
with
sasha.
H
Hey
so
we
are
back
to
green
the
fix
regarding
when
the
domain
flip
has
been
merged
this
morning
and
yeah.
We
are
going
to
discuss
if
you
want
to
cut
rc4
tomorrow,
but
yeah
there's
actually
no
decision
yet,
but
I'm
pretty
sure
that
we'll
come
to
a
decision
close.
A
I
Into
this
yeah
there's
a
couple
things
there.
I
think
the
the
general
theme
is
planning,
as
we
start
to
get
towards
wrapping
things
up.
Everybody
in
terms
of
leads
and
shadows
very
much
focused
on
execution
right
now,
but
we
also
need
to
think
about
next
month
at
this
point,
and
a
new
cycle
will
be
starting
so
for
leads,
be
thinking
about
role.
Succession
you're
not
required
to
step
away.
I
If
you
feel
like
there's
things,
you
need
to
to
finish
like
changes
you
maybe
you're
driving
with
in
the
role
or
something
that
you'd
like
to
continue
on
for
the
next
one.
But
it's
also
a
good
idea
to
have
succession
across
time
so
be
thinking
about
that
that
the
120
team
needs
to
be
starting
to
form
and
be
reaching
out
to
shadows
both
your
current
ones
and
119,
but
also
potentially
prior
ones,
to
figure
out
how
to
start
getting
a
pool
of
candidates.
I
Similarly,
for
shadows
be
thinking
about
that
role,
succession,
the
120
team
is
gonna,
need
you
if
you're
available,
and
then
I
will
be
sending
out
a
survey
relatively
soon
for
leads
and
shadows
just
to
try
and
get
some
specific
feedback
on
the
the
leading
and
shadowing
process
itself
and
then,
of
course,
more
globally.
The
119
retrospective
for
all
the
things,
make
sure
that
you're
putting
stuff
in
that
document
so
that
we
can
go
through
and
talk
about
them
as
the
cycle
wraps
up
and
again
be
taking
that
feedback.
A
Okay,
thanks
again
tim,
so
the
next
updates
we
have
are
that
we
have
a
couple
of
milestones
coming
up
and
I
think
these
may
be
open
for
discussion
still.
We
currently
have
planned
for
the
cherry
pick
deadline
and
for
the
test
freeze
to
occur
on
thursday.
I
think
we
should
probably
discuss
this.
A
Maybe
we
can
do
this
in
the
secretly
select
channel
to
be
more
inclusive
of
the
people
that
aren't
on
the
call
right
now,
but
we
had
a
lot
of
tests
and
civilities
in
the
in
the
ci
signal
system.
It
seems,
like
we've,
been
making
some
progress
to
get
that
better,
but
it
still
looks
like
things
are
a
little
flaky,
so
I
don't
know
if
we
want
to
make
the
call
now
to
push
that
out
or
continue
it
but
open
to
any
discussion
that
we
want
to
have
on
that
right
now.
J
Most
of
the
there's
a
handful
of
prs
that
I
see
going
in
around
test
issues.
The
rate
of
those
has
dropped,
though
so
in
terms
of
cherry
pick
deadline
it's
starting
to
seem
reasonable
to
require
to
stop
automatically
fast
forwarding
towards
the
end
of
this
week,
so
that
that
doesn't
raise
red
flags
to
me.
A
C
A
Call
all
right
and
then
kubecon
is
coming
up
as
mentioned,
and
then
after
that
we
will
be
working
towards
our
aspirational
release
date
of
the
25th
it's
in
a
few
weeks
from
now,
so
we've
got
a
little
bit
time
to
go
still,
but
we'll
keep
keep
updates
come
in
there.
We
didn't
get
a
six
scalability
update
this
week,
assume
it's
the
same
as
friday's
update,
so
move
on
to
open
discussion
now,
any
anything
anyone
wants
to
add
that
hasn't
been
added
to
the
agenda.
A
A
All
right
well,
like
tim,
said,
start
thinking
about
secession
for
120.,
also
start
thinking
about
any
items
that
you
want
to
add
to
the
retro.
The
link
is
in
the
open
discussion.
Section,
definitely
add
them
as
you
think
of
them,
so
over
the
last
couple
of
weeks,
if
you've
noticed
anything
that
you
want
to
add
to
the
retro
to
discuss.
A
Please
do
that
now,
just
so
we
have
it
documented
and
have
it
ready
for
the
the
retro
in
a
few
weeks
and
with
that,
unless
anybody
has
anything
else,
we'll
go
ahead
and
end
a
little
bit
early
and
give
you
back
some
of
your
time.