►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20220318
Description
Kubernetes Release Team Bi-Weekly Meeting for 20220318
A
All
right,
hello,
everyone!
This
is
a
kubernetes
124
release
team
meeting.
It
is
week
10
friday,
the
18th
of
march
2022.
My
name
is
james
lavrock.
I
am
your
host,
I'm
the
police
lead
for
124.
A
as
a
note
of
housekeeping
this
meeting,
as
with
all
of
our
meetings
is
covered
by
the
kubernetes
and
cncf
code
of
conduct.
So
please
refer
to
that
for
all
your
interactions
here
today,
but
it
can
be
summarized
as
please
be
excellent
to
each
other.
Can
I
also
ask
everyone:
who's
here,
live
with
us
to
add
their
their
name
and
if
they
feel
comfortable,
pronouns
and
title
to
sorry
releasing
well
to
our
attendees
list.
A
Moving
on
from
that,
I
put
in
a
couple
of
open
discussion
items
well
very
quickly.
We
are
nearly
a
month
to
the
day
to
go.
We
release
on
19th
april
is
18th
march,
so
we
are
getting
close.
We
are
two-thirds
of
the
way
through
the
release
now,
which
is
you
know,
exciting,
and
then
I
was
gonna
say
something
here
and
I
got
halfway
through
writing
it
and
I
have
forgotten.
So
I
guess
we'll
come
back
to
that.
If
I
remember
moving
on,
let's
go
to
updates
from
enhancements,
I'm
saying.
B
So
I
mean
there
is
nothing
you
know
different
than
in
a
previous
time
like
a
wednesday
meeting,
so
we
are
less
than
two
weeks
away
from
the
code
phrase
and
we
are
reaching
out
to
the
enhancement
caps
that
we
have
is
in
the
pipeline
and
the
majority
are
at
risk
but
you're
keeping
the
finger
crossed
that
they
will
pass
yeah.
A
That's
all
all
right,
yeah,
that's
pretty
standard
for
this.
This
point
in
the
release.
I
think
one
quick
question
we
reported
yesterday
at
the
meeting
that
we
had
66
tracks
for
a
68
here.
Is
that
a
difference
in
counting
like
not
counting
the
defecations
or
something.
B
A
It
up
just
to
make
sure
that
we're
counting
things
correctly,
yeah
sure
all
right
any
questions
for
enhancements
for
anyone.
C
That's
yeah,
that's
that's
totally
like
collect,
so
no
wallets
so
yeah.
Currently
we
have
eight,
I
mean
one
fellaini
test
and
eight
flag,
it
does
in
the
master
blocking
and
one
failing,
descended.
I
think
nine,
so
you
open
the
top.
So
I
can
see.
Let
me
see,
I
know
what
is
there
one
failing
on?
C
Ninth
like
you
know,
russian
farming
and
the
problem
is
that
the
issue
1.8309
and
we
are
looking
for
some
help
on
this
issue
right
now
and
I'm
kind
of
worried
this
might
be
a
release
blocker
for
that
next,
really,
we
discussed,
which
is
like
in
I
guess
three
days
so
yeah
we're
actually
working
on
it
and
the
last
one
is,
I
think
you
add
it
leo
this
sentence.
Yes,.
D
Yes,
I
I
quickly
added
the
last
point,
so
we
have
next
week
the
release
team
retro
and
we
scheduled
a
day
before
a
ci
signal
internal
retro,
because
at
the
start
of
the
release,
we
set
out
some
some
tasks
that
we
want
to
accomplish
and-
and
I
thought
it
would
be-
a
good
idea
to
think
before
the
release
team
retro
to
discuss,
discuss
how
everybody
is
feeling.
So
I
will
also
put
this
on
the
release
theme
retro
dogs
to
discuss.
A
Thank
you,
sorry
was
it.
I
thought
you
offered
anything
else.
A
With
this
issue,
so
you're
thinking,
this
is
a
released
blocker.
For
this
thing,.
E
C
Yeah
I
did
in
inner
cli
and
release
channel.
D
And
jim
are
also
informed,
I
pinged
them
yesterday,
okay,
so
I'm
we're
waiting
for
a
response.
Maybe
it's
not
a
blocker
okay.
A
D
A
Yeah,
we'll
we'll
wait
to
hear
back
from
then,
but
probably
possibly
need
to
put
the
release
bucket
label
on
it,
but
we'll
we'll
wait
for
release
management
to
make
a
determination.
I
suppose,
okay,
thank
you
very
much,
both
any
any
other
questions
for
ci
signal.
A
No
all
right
moving
on
bug
triage.
I
don't
see
any
particular
update
here,
so
I
presume
it's
the
same
as
the
last
time,
which
was
green.
Everything
looks
fine,
so
it's
pretty
good.
If
there's
no
one
here
for
bug
triage,
no
all
right,
docs
just
looks
the
same,
no
particular
update.
F
A
A
A
A
No
all
right,
thank
you
very
much
release
notes.
G
Yeah,
hello,
everyone,
so
the
status
is
green
for
us
as
well,
and
we
do
not
have
any
major
updates
from
the
past
meeting.
It's
just
that
we
are
waiting
for
the
alpha
four
cut.
The
prs
for
all
the
previous
cuts
have
been
successfully
merged,
so
no
problems
from
that
end
and
we
would
be
working
upon
singing
with
other
sub
teams
for
getting
the
major
themes
and
picking
up
a
pr
for
that.
A
A
Nope
all
right
comms,
I
don't
see
any
update
anyone
in
here
for
comms.
A
A
Nope
joseph
isn't
on
the
call
and
hasn't
given
me
a
particular
update
either
and
the
I've
actually
made
this
meet.
I've
actually
missed
like
two
weeks
of
these
meetings
between
illness
and
and
recovering
from
a
dentist
appointment
and
things
like
this.
So
of
course
I've
been
following
along
evernote
and
slack.
I
have
added
our
monday
meeting.
I
didn't
do
a
doodle
poll
this
time,
because
what
I
wanted
to
avoid
was
having
meeting
times
distributed
all
over
the
place
and
it'd
be
really
confusing.
A
So
that's
next
monday,
the
21st
other
than
that
nothing
particularly
to
to
report
we've
kind
of
gone
through
well,
my
feeling
is
we've
kind
of
gone
through
the
middle
bit
of
the
release,
which
is
a
little
bit
quieter
and
now
we're
ramping
up
to
the
later
part
of
the
release
where
everything
happens
at
once.
And
then
everything
is
is
on
fire
for
like
two
days
and
then
it's
that's
fine,
but
in
in
general,
things
are
looking
fine,
so
yeah.
A
E
Usually
have
a
conflicting
meeting
at
this
time,
but
since
that
put
over,
I
thought
we
don't
have
any
updates
I'm
following
up
on
that
release.
Blocker
issue
that
cs
google
has
right
now
and
I'm
trying
to
see
like
what
we
can
do.
For
example,
we
see
that
the
market
issue
is
solved
there,
but
the
complete
testing
suit
is
kind
of
failing.
E
Yes,
so
I
feel
like
we
should
pay
someone
from
six
cli
who
has
more
context,
but
looking
at
the
error,
it's
very
common
to
have
that
timeout
waiting
for
condition-
and
usually
I
have
seen
in
the
past
that
people
solve
it
by
increasing
the
dialogue.
But,
however,
I
am
not
an
expert
here,
so
my
opinion
probably
wouldn't
matter
much,
but
that's
what
I
feel
probably
there's
a
timeout
issue,
but
hey
it
can
be
clearly.
Success
should
reinspect
it
again
since
the
market
issue.
A
E
Yeah
worst
case,
they
will
look
at
it
and
remove
them.
A
E
I
haven't
seen
like
such
catastrophic
failure
failure
before
so
that's
why
I'm
just
saying.
E
A
A
Nope
all
right,
I
think
we
are
at
the
end
of
our
meeting.
Then
I
am
going
to
stop
the
recording.