►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200629
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
All
right
welcome
everyone
to
another
installment
of
the
kubernetes
119
release
team
meeting.
My
name
is
Taylor
Dolezal
and
yeah.
Let's,
let's
get
right
into
it.
This
is
a
kubernetes
meeting,
so
we
do
abide
by
the
kubernetes
code
of
conduct,
which
simplifies
down
to
please
be
excellent
to
one
another.
B
A
A
C
Everyone
good
morning,
so
we
had
yellow
the
reason
we
had
yellow
is.
We
went
through
all
of
the
announcements
that
are
being
tracked
and
found
out
several
of
them
to
be
exact,
twelve
of
them
that
we
think
that
they
might
miss
miss
code
freeze.
So
we
marked
them
as
at
risk
right
now
we
will
talk
to
the
sig
leads
and
the
respective
assignees
of
the
announcements
about
what
is
the
progress?
How
is
it
going?
C
A
Thank
you.
Never
in
yeah
it's
as
we
go
through
this
week.
I
can
you
know
we
can
all
help
out
with
tick
and
look
at
those
and
seeing
what
actually
makes
it
into
the
release
and
if
there's
anything
we
can
help
out
with
or
follow
up
on
that
front,
to
make
sure
that
we
have
a
good
count
there
and
that
everyone
knows
if
their
future
will
be
in
the
release
or
not.
C
D
Folks
hope
everyone's
having
a
good
Monday,
thus
far,
so
we
are
red,
it's
still
the
cig
scheduling
issues
the
PR
that
was
mentioned
on
Friday
got
merged,
but
unfortunately
it
revealed
another
issue.
So
there
is
a
PR
open
right
now,
it's
past
CI,
just
waiting
to
get
the
looks
good
to
me
from
the
cig,
scheduling
folks.
So
hopefully
those
will
clear
up.
That's
going
to
fix
both
of
the
failing
tests
on
master
blocking
kind.
Ipv6
is
also
failing,
but
it's
passed.
D
It's
just
super
flaky
and
then
also
a
number
of
the
failing
ones
on
master
informing,
including
the
cap,
G
job
and
GC
cost
master
Syrio.
Also
due
to
that
same
cig
scheduling,
issue
I'm.
So
hopefully
those
will
clear
up
the
other
main
things
that
I've
carried
over
from
last
week
on
the
OpenStack
PR.
We've
mentioned
this
a
few
times
now
they
were
not
running
a
multi
node
cluster,
which
was
causing
the
conformance
test
to
fail.
They
have
merged
PR
to
update
that
I'm.
D
To
be
honest,
I'm
not
exactly
sure
how
they're
their
job
configuration
works
over
there,
so
I'm
kind
of
having
to
rely
on
their
team,
but
that
was
merged.
So
hopefully
we'll
see
a
fix
there
soon
and
then
the
cluster
api,
AWS
PR,
has
been
opened
and
is
under
review.
So
hopefully
we'll
get
that
job
up
and
running
again
soon.
A
B
E
G
G
Also
for
the
release
block,
we
started
to
get
a
more
deeper
communication
with
CN
CF
checking
the
dates
check
the
dates
around
the
cube
con
that
we
do
not
collide
somewhere,
and
there
should
be
also
some
meeting
I
guess
in
at
least
in
two
or
three
weeks
with
you
together
also
and
to
lay
down
and
then
down
the
exact
dates
for
heaven.
Also,
the
interviews
and
analyst
calls
and
whatever
will
come
there.
A
H
So
branches
are
looking
good.
We
should
be
on
track,
for
the
I
mean
the
next.
The
next
cut
is
our
c0
I
believe
our
c0
right.
So
that
is
actually
the
branch
cut
so
be
aware
that
the
workflow
changes
once
we
hit
the
sopran
shot.
Usually
we
do
the
branch
cut
at
the
beta
0
beta
0
release,
but
we've
kind
of
shifted
our
tooling
to
do
the
branch
cut
at
RC.
What
this
means
is
that
people
looking
to
merge
PRS
into
the
release
will
have
to
start
doing.
Cherry
picks
at
that
point.
H
Wait
yeah.
We
should
think
about
that
a
little
bit
because,
because
that's
shifted
so
b2,
so
we
usually
do
a.
We
usually
do
branch
fast
forwards
between
once
we
hit
beta
0,
we
cut
the
x
dot
y
branch
and
then
fast
forward
master
into
that
branch
for
a
period
of
time
and
then
and
then
later
in
the
cycle
we
move
into
cherry
picks
only
for
the
branch
right
so
because
we've
moved
this
a
little
further
out.
We
need
to
talk
about
exactly
when
we
want
to
how
long
we
want
to
do.
Cherry
picks.
H
How
long
we
want
to
do
branch
fast-forwards
for
and
when
we
want
to
start
the
cherry
pick
period.
So
let
me
look
at
the
calendar.
Get
back
to
you,
I'll
synch
up
the
tailor
and
the
team
and
chat
a
little
bit
about
that,
because
I
know
we
said
we
wanted
to
do
it,
but
we
didn't
set
a
specific
time
that
we
were
going
to
start
doing
it.
But
outside
of
that
I'll
talk
about
some
go
stuff
in
the
open
discussion,
because
that
will
affect
this
release
quite
a
bit.
So
stay
tuned.
A
A
Thank
you
very
much.
I
know
that
Tim
is
not
going
to
be
able
to
make
it
and
I
he's
got
a
conflict
today.
He
said
he
put
in
the
notes
nothing
much
to
discuss.
As
always.
If
anyone
has
questions
about
anything
that
we're
doing
I'm
here
to
help
at
tea
pepper
on
slack,
so
please
be
sure
to
hit
tim
or
any
of
our
team
up.
A
If
you
have
any
questions
whatsoever
really
sleet
update,
so
we
have
on
July
6th
the
docs
PR
ready
for
review,
then,
shortly
after
that,
within
the
same
week,
we
have
code
freeze
happening
on
July
night.
Now
we're
going
to
be
talking
about
chair,
picks
and
a
couple
other
other
items
around
that
then,
after
that
we
have
July
16th
on
Thursday
Doc's
deadline,
and
so
those
are
the
milestones
that
we
have
coding
it
up,
don't
need
to
hit.
We
are
eight
weeks
out.
A
We
already
covered
that
in
the
intersection,
and
this
Wednesday
I
know
is
Canada
Day,
so
we'll
have
some
some
team
members
off
for
that
on
Friday
is
July.
4Th
observed
here
in
the
US
I
think
that
it
makes
sense
to
still
have
the
meeting
and,
if
you
know
no
pressure
to
join
because
it's
the
holiday,
but
if
anyone
has
any
updates,
I'll
still
be
around
and
collecting
that
feedback
doesn't
have
to
be
a
long
meeting.
A
A
All
right
moving
into
open
discussion,
as
always,
we
do
have
our
retro
link
live
and
are
always
happy
to
get
your
feedback
and
just
anything
that
you
really
appreciated
about
the
release.
I
felt
it
was,
you
know
more
friction
than
it
should
be
in
other
ways.
We
can
go
about
solving
problems
on
that
front.
We
would
love
to
get
your
feedback
there.
A
A
Keep
your
jeopardy
theme
song,
music,
okay.
Moving
on
to
Lori's
comment.
Reminders
leads
to
schedule
time
with
her
to
help
offload
work
now
that
Lori's
been
hard
at
work,
creating
that
document
and
kind
of
sourcing
feedback
and
getting
a
lot
of
action
plans
and
items
together
to
make
these
releases
easier.
So
please
check
that
link
out.
It's
in
the
docs
Lori
also
left
a
note:
release
team
Doc's,
editing,
upping
on
the
email
thread.
If
you
want
to
help
so
not
sure
if
you
wanted
to
add
anything
else
to
that
Lori,
but
no.
I
I
H
Big
thank
you
to
Lori
overall
for
all
the
work
that
you've
been
doing.
It's
been
a
short
amount
of
time
that
you've
been
here,
but
you've
already
made
tremendous
impact
across
the
sig
and
across
the
project
for
people
who
are
not
aware
have
not
met
Lori
before
Lori
is
awesome.
Lori
is
our
new
program
manager
for
sig
release,
so
she
is
going
to
be
working
on
a
lot
of
the
avera
teasing,
the
prioritization
and
an
issue
triage
work
on
that
she's
been
doing.
You
have
probably
seen
some
of
her
emails
and
slack
threads.
H
So
what
we
decided
to
do,
because
this
role
doesn't
really
exist
in
the
community
at
all,
Lori
is
going
to
be
kind
of
leading
the
charge
as
the
kind
of
the
community's
first-ever
official
program
manager.
What
that
means
is
there
are
lots
of
unknown
unknowns
and
it's
kind
of
one
of
those
things
where
you'll
be
defining
your
own
role,
as
as
we
kind
of
wade
into
this,
but
I
want
to
make
sure
that
I
want
to
say
this
and
have
it
recorded.
H
Please
give
Lori
your
attention
when
she
asks
you
to
do
something
if
you,
this
is
all
to
help
make
our
lives
easier
and
she's
really
good
at
what
she
does.
So
please
take
a
little
additional
time
if
it's,
if
it's
technical
versus
something
that
Lori
asked
you
to
do
please
prioritize.
The
thing
Lori
asks
you
to
do.
Is
it's
gonna
make
our
lives
better
overall,
so
thank
you.
Lori
welcome
to
the
team
welcome
to
the
sig
officially
in
an
official
capacity
and
looking
forward
to
more
from
you
thank.
I
A
A
So
good,
all
right.
Moving
on
to
the
next
agenda
item
go
115
did
I,
read
that
right,
mm-hmm
yeah.
H
So
so
we've
got
something
interesting
coming
up,
and
so
every
cycle,
or
so
we
play
this
dance
with
the
next
go
minor
version
deciding
exactly
when
to
update
it
if
to
update
it
at
all
for
that
for
the
dot
zero
release
and
how
exactly
to
do
it?
Who
needs
to
be
involved
all
of
that
good
stuff?
So
we've
gotten
we've
wrapped
our
hands
a
bit
more
around
the
process
and
the
last
few
cycles,
which
has
been
awesome
to
see
the
the
go
113
updates,
went
pretty
smoothly
pretty
smoothly
in
comparison
to
the
past.
H
The
114
update
was
pretty
difficult.
Gonna
be
honest.
That
was
a
PR
that
I
opened
in
February
and
only
merged
recently,
maybe
like
two
weeks
ago,
maybe
less
so
there
lots
of
moving
parts
when
we,
when
we
think
about
updating,
go,
and
it's
really
important
to
try
to
get
it
in
at
a
point
in
the
cycle
where
six
scalability
can
still
do
scale
testing
and
we're
getting
lots
of
good
signal
and
cleaning
up
bugs
related
to
the
new
version
ahead
of
time.
So
something
really
interesting
is
happening
for
114.
H
Now
that
it's
in
it's
almost
immediately
useless
there's
there
are
some
things.
There
are
some
technical
bits
that
we
have
to
worry
about
that
are
fixed
in
115,
so
we're
going
to
be
trying
to
get
go
updated
to
115
for
the
kubernetes
119
release
cycle.
This
is
going
to
create
variety
of
problems,
because
our
previous
release
branches
are
in
139
right
now,
which
means
we
not
only
have
to
figure
out
how
to
get
115
updated
quickly,
especially
being
given
the
fact
that
it's
not
released
yet,
which
is
exciting.
H
So
this
is
gonna,
be
the
first
time
that
we
are
attempting
to
do
to
do
updates
on
a
pre-release
of
go
so
expect
a
little
rockiness.
There
see
I
signal
and
bug
triage
beyond.
I
alert
for
for
certain
things.
Process
hasn't
started
yet.
I
need
to
I
still
need
to
look
at
a
few
bits
before
we
get
started
with
it,
but
essentially
there
are
there
gonna
be
there's
gonna,
be
go
weirdness,
there's
gonna,
be
a
basal
weirdness,
weird
weirdness
static,
check,
failures
that
failures:
lots
of
things
to
just
in
general,
look
out
for
I'll.
H
Try
to
keep
open
line
of
communication.
Can
consistently
update
the
team
on
what's
going
on?
This
one
is
going
to
be
interesting,
is
the
short
version
and
then
we're
gonna
have
to
figure
out
how
to
how
to
potentially
pull
it
back
into
previous
release
branches.
So,
given
the
go
release
cycle
and
given
the
kubernetes
given
the
goes
support
cycle
and
release
cycle,
and
given
the
kubernetes
support
cycle
and
release
cycle,
we
need
to
stay
pretty
close
to
goes
most
recent
end
version.
H
So
the
attempt
for
the
for
the
other
branches
to
update
that's
115
is
kind
of
important
because
we
essentially
need
to
skip
one
did
I,
say:
114,
115,
115
and
previous
release
branches,
because
we
need
we
probably
need
to
skip
1:14
and
the
Prevost
previous
ones,
and
we
need
to
keep
as
close
in
line
to
there
to
what's
going
on
upstream
there.
So
stay
tuned
for
lots
of
funkiness
I.
Think
it's
the
nicest
way
to
say
it.
Yeah.
A
All
right,
well,
don't
forget
that
this
is
the
final
countdown
everyone
that
we
are
eight
weeks
out.
Please
raise
up
any
questions.
Comments
concerns
to
your
team.
Your
leads
will
be
happy
to
help
out
otherwise
I
hope
you
all
have
a
happy,
Monday
and
no
matter
where
you're
at
with
your
day,
even
if
it's
almost
2:00
clothes
have
a
wonderful
week,
we
will
see
you
all
on
Wednesday.