►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200825
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
There
we
are
recording,
welcome,
welcome
everyone.
This
is
a
119
release.
Team
burn
down
meeting
today
is
august
25th.
This
is
a
kubernetes
meeting,
so
we
abide
by
the
kubernetes
code
of
conduct,
which
simplifies
to
please
be
excellent
to
one
another.
It
is
release
week.
Let's
kick
it
on
over
to
enhancements
and
go
through
all
the
statuses
and
see
where
we're
at
neverend.
Would
you
like
to
kick
us
off.
B
Sure,
hi
everyone
so
enhancements
is
green
right
now
we
have
34
enhancements
which
are
graduating,
this
release,
cycle,
of
which
nine
are
new
enhancements.
Coming
in
as
alpha
15
announcements
are
graduating
to
beta
and
10
announcements
are
graduating
to
stable
and
that's
all
we
have
for
now.
A
Awesome,
are
you
never
in
any
questions
for
enhancements.
C
Hey
folks,
we
are
doing
pretty
good.
Today
we
have
a
few
new
flakes,
but
we
are
coordinating
with
the
different
cigs
and
making
sure
none
of
them
are
and
actually
just
got
a
message
on
another
one
of
them
here
are
blocking
so
on
conformance
ga.
Only
there
was
an
m
structure
flick
this
morning,
so
obviously
none
blocking
there
ubuntu
master
container
d.
There
was
a
sig
storage
test
flake
and
they
got
back
to
us
and
said
this
is,
can
be
fixed
later
node
cube
master,
that's
the
one.
C
I
just
got
a
note
back
from
sig
leads
there
and
they
are
looking
into
it,
but
they
said
is
non-blocking
as
well.
So
that's
good
to
see.
We
have
one
more
sig
storage
test
on
kind,
ipv6
master
parallel,
assuming
that's
going
to
be
non-blocking
as
well,
and
then
last
one
here
is
on
integration.
Master
we've
been
green
since
we
reverted
those
infrastructure
changes,
but
there
was
a
sig
scheduling,
flake
that
popped
up
just
moments
ago.
Actually-
and
we
have
some
folks
from
six
scheduling.
C
Looking
into
that,
I
would
guess
once
again
that
it's
non-blocking
there's
an
issue
and
a
pr
that
addressed
it
earlier
on
that
I
took
a
read
through.
I
think
it
was
closed
20
or
so
days
ago,
and
it
didn't
look
like
a
huge
deal,
but
we're
going
to
make
sure
to
get
sign
off
from
from
them
before
moving
forward.
C
Otherwise
things
are
looking
pretty
good.
We
are
talking
with
sig
scalability,
just
because
we
wanted
to
get
some
runs
on
those
jobs
before
or
after
we
got
in
the
endpoint
slice
changes
yesterday.
So
we'll
continue
to
monitor
that,
but
in
terms
of
releasing
tomorrow
we
are
looking
pretty
good.
A
Awesome
fantastic
to
hear
yeah
I
saw
I
saw
a
lot
more
green
when
I
opened
my
eyes
this
morning.
It
wasn't
yeah,
it
wasn't
sunshine.
It
was
actually
the
the
passing
tests.
That
was
awesome,
cool
awesome.
Thank
you,
dan.
Any
questions
for
ci
signal.
D
Hey
we
are
green,
so
no
not
much
to
add,
but.
E
I
hear
I
guess
one
time:
yes,
my
teammates
step
up
and
he
is
willing
to
take
the
broad
fire
so
that
I
can
go.
Do
awesome
stuff,
the
I'm
grateful
for
him.
This
is
important
to
me
dog.
The
k
website
is
still
frozen
and
tomorrow
I
will
work
with
the
chairs,
because
I
need
I
don't
have
certain
level
of
permission
and
I
need
some
any
one
of
them
to
help
me.
E
Pr2
the
workaround
will
be
to
remove
the
label,
add
an
explicit
hole
to
all
the
prs:
remove
the
label
and
mars
release
pr
and
then
let
the
release
blog
go
through,
and
I
think
release
notes
or
something
like
that
comes
out
here
and
then
we
will
just
remove
all
the
block
hold
from
all
the
pr
so
that
that's
one
of
the
plan,
jim,
is
going
to
help
me
out.
E
Yeah,
that's
a
plan,
that's
it!
Thank
you.
A
Awesome,
thank
you
so
much
and
yeah.
Sorry,
I
missed
you.
I'm
glad
you're
able
to
make
it
any
questions
for
docs.
A
Wonderful:
let's
go
on
to
release
notes.
What's
adolfo.
D
Hi
everyone
so
we're
green
right.
Now
we
have
the
final
document
assembled
and
we
are
just
we're
only
expecting
minor
precisions
from
the
windows
folks,
and
I
also
saw
that
one.
Another
final
issue
came
via
the
known
issues,
issue
other
otherwise
we're
fine.
D
A
That's
awesome,
thank
you,
delfo
and
thank
you
thank
you
for
being
here.
Let's
move
on
to
comms
with
max.
F
It's
joseph
sorry,
I've
totally
got
it
just
got
done
caught
up
hey,
we
are
green,
everything
looks
good
and
the
pr
for
the
release
vlog
is
opened.
So
I
put
a
link
to
the
you
know
pr.
So
anyone
feel
free
to
take
a
look
at
and
review
and
give
us
feedback.
A
Awesome,
thank
you
so
much
joseph
I
have
the
blurb
and
I'll
plug
in
the
logo.
Probably
tomorrow
before
we
go,
live
but
I'll
get
that
blurb
in
there
and
I'll
just
put
that
in
as
a
suggestion
on
github
make
it
easy
to
put
in.
I
don't
have
bright
access,
so
I
can't
push
that
as
a
commit,
but
I'll
get
it
in
shortly.
Thank
you.
So
much.
A
Fantastic:
let's
go
on
to
release
branch
management
with
carlos
and
I
don't
see
carlos
on
the
line.
Anyone
from
release
branch
management
and
wants
to
give
an
update.
C
Yeah,
so
primarily
the
number
one
thing
that
we're
focused
on
is
the
1.19
release,
which
will
be
tomorrow
now
and
then
we
also
have
our
final
patch
release
of
1.16
coming
up.
So
you
can
check
the
schedule
for
that.
Otherwise,
no,
no
real
news
to
report.
A
Awesome,
tim
pepper
is
not
on
the
call
was
not
able
to
make
it,
but
again
it
gave
good
feedback
this
week
in
terms
of
kind
of
getting
that
schedule
together.
A
If
you're
curious
on
the
release,
schedule
and
just
kind
of
that
process
that
we're
going
to
go
ahead
and
follow
you'll
find
it
at
the
top
of
the
release
team
meeting
document,
which
I
don't
think
I
post
in
the
chat,
but
I
can
do
that
shortly,
so
my
update
as
far
as
go
no
go
I'd
say
that
we
have
enough
confidence
today
to
issue
a
go.
I
know
that
we're
still
gonna
take
a
look
at
some
things.
Obviously
you
know
if
anything
comes
up.
A
A
For
cool
the
release,
theme
name
has
been
added
to
some
of
the
documentation
out
there,
which
is
accentuate
the
positive.
That
is
a
pun.
I
hope
that
you
enjoy
it.
A
The
logo
will
go
hand
in
hand
with
that
or
paw
and
paw
with
that,
and
I'm
very
excited
to
share
that
with
everyone
in
terms
of
the
retrospective
that
was
originally
scheduled
to
happen
this
thursday,
but
with
just
a
little
bit
of
delays
and
vacations
and
and
just
wanted
to
take
a
look
at
giving
people
a
little
bit
more
time
for
some
feedback
after
we
get.
A
Everything
out
was
thinking
about
rescheduling
that
for
next
week,
thursday
and
wanted
to
open
that
up
to
discussion,
see
if
anyone
felt
differently
about
that
or
you
know
either
pushing
it
out
further
or
having
still
having
that
this
thursday
anyone
anyone
opposed
or
want
to
issue
feedback
for
moving
that
to
next
thursday.
G
A
Oh
I'm
sitting
the
ladder,
yeah
I'd
say
I'd
say
it's
been.
It's
been
good
for
sourcing
feedback,
thus
far
in
this,
in
my
opinion,
but
I
it's
been
good
for
sourcing
feedback.
I
think
when
it's
come
down
to
action
items,
that's
where
it's
falling
apart
in
some
respects,
I
think
we
still
have
issues
open
from
like
116
17
18
things
that
we
kind
of
need
to
to
you
know
actually
deliver
on
or
that
might
not
be
relevant
now.
A
It's
been
good
on
that
front.
We
the
way
that
the
format
is
now
is
that
someone
will
put
in
you
know
a
comment
and
then
put
their
name
after
that
or
just
you
know
more
than
more
than
able
to
put
that
in
anonymously
as
well,
and
then
we
can
just
kind
of
talk
on
it.
If
there's,
if
there's
no
owner
for
that
issue,
but
like
to
give
everybody
the
chance
to
you
know
they
put
an
issue
and
to
kind
of
talk
more
to
that,
provide
more
context
around
it.
G
A
It'd
be
great
to
do
a
relevance
check
on
that
and
see
if
there's
some,
that
you
know
that
or
if,
like
hey
this,
you
know
we're
seeing
we've
seen
the
same
issue.
You
know
yeah
n
minus
two
releases,
things
like
that.
A
Cool
cool:
well
let
the
motion
pass
I'll,
get
a
pr
out
and
we'll
schedule
that
for
next
thursday,
sig
scalability
update
no
changes
on
that
front.
We
still
the
817
scalability
jobs,
look
good.
I
know
that
we've
had
some
changes
since
then,
so
we'll
keep
an
eye
on
test
grid.
For
that
you
know
there
are
a
couple
flakes,
but
those
are
working
themselves
out
and
then
I'd
love
to
turn
it
over
to
lori
for
program
management.
G
A
Cool
cool,
thank
you
lori.
Any
questions
for
program
management.
A
Excellent
on
note
of
the
retro,
obviously
please
put
any
notes
in
that.
You
would
like
fully
I'm
seeing
a
lot
of
good
feedback
in
there.
A
lot
of
good
items
to
discuss
on
so
very
excited
about
this
retro
should
be
action-packed.
This
is
not
a
pay-per-view
event.
A
It's
free,
so
I
hope
that
that's
enjoyable
on
that
front,
any
other
open
discussion
items-
oh
there
was
one
thing
I
wanted
to
ask
in
terms
of
in
terms
of
tomorrow's
meeting
since
we'll
be
going
live
as
of
right
now
wanted
to
see
what
everyone
felt
about
not
having
a
meeting
just
to
kind
of
give
everyone
that
time
to
focus
on
getting
that
release
out.
But
you
know
if
anyone
feels
any
differently,
please
please.
Let
me
know
more
than
happy
to
schedule
a
meeting
for
tomorrow
to
you.
A
Absolutely-
and
we
do
have
the
zoom
room
that
we
can
open
up
ad
hoc
too.
It
doesn't
have
to
be
a
specific
time,
but
okay
cool.
I
will
I'll
leave
that
off
for
now,
but
obviously,
if
anything
changes
or
anything
on
that
front,
please
please
reach
out
to
me
and
I
can
get
that
scheduled
if
we
need
anything
for
a
specific
time.
Otherwise,
we'll
just
go
ahead
with
the
release
and
then
any
final
items,
questions
or
concerns
for
open
discussion.
A
Fantastic
well,
thank
you
all.
I
hope
you
have
a
wonderful
tuesday,
very
excited
about
the
release
this
week
and
tomorrow.
I
can't
believe
it's
it's
already
here.
Just
blink
and
the
time
goes
by.
Thank
you
all.
So
much
have
a
wonderful
rest
of
your
day
and
I
will
I'll
see
y'all
on
on
release
duty
tomorrow
have
a
good
one
and
yes,.