►
From YouTube: Kubernetes Release Team Weekly Meeting for 2020044
Description
Kubernetes Release Team Weekly Meeting for 2020044
A
All
right,
hello,
everyone
welcome
to
the
kubernetes
1.24
release
team
meeting.
This
is
april
4th
2022.
Please
be
aware
that
this
meeting
is
governed
by
the
kubernetes
code
of
conduct,
which
can
be
boiled
down
to.
Please
be
excellent
to
one
another
and
if
you
haven't
please
take
a
moment
to
add
your
name
to
the
list
of
attendees
and
we
will
get
started
so
first
thing
up
on
the
agenda
today
is
some
updates
on
the
go,
1.18
release
and
and
issues
that
throws
from
that.
A
B
B
B
So
the
second
one
is
the
one
that
we
are
worried
about
right
now,
for
we
have
a
temporary
workaround
for
our
ci
jobs,
which
involves
creating
an
environment
variable
for
ignoring
some
of
the
the
sha
based
certificate
stuff,
because
in
118
they
deprecated
it
and
they
are
trying
to
get
rid
of
it.
But
there
are
some
conditions
where
you
know
we'll
end
up
making
breaking
the
folks
that
are
that
have
kubernetes
clusters
in
the
wild
and
they
won't
be
able
to
update
to
it.
B
We
don't
know
exactly
when
there
is
a
1
18
1,
which
is
going
to
be,
which
is
scheduled
for
the
7th,
but
that
seems
to
be
something
that
has
a
higher
priority:
security
related
fix
and
not
the
one
that
we
are
looking
for.
So
I
left
some
notes
in
the
release
blocker
the
issue,
giving
laying
out
the
steps
that
that
we
need
to
go
through
to
get
to
the
point
where
we
can
make
a
release
out.
Mother.
Do
you
want
to
add
some
context
and
then
I
can
wrap
up.
C
C
Then
we
should
be
good
to
go
post
that,
but
provided
that
it's
not
included
in
118.1,
we
would
have
to
wait
for
go
118.2
to
be
able
to
pull
that
change
in
the
workaround
right
now
that
we've
employed
just
works
for
our
ci
and
will
not
work
for
folks
running
clusters
in
production.
As
of
today
and
as
jordan
also
summarized
on
the
thread
that
is
linked
in
the
sig
release
channel.
B
That's
where
we're
at
right
now,
thanks
yeah,
so
117
is
going
back
to
117
is
like
totally
out
of
question,
given
the
number
of
things
that
we've
landed
across
multiple
repositories
to
get
to
this
point,
so
that
is
definitely
not
on
the
table.
So
the
best
case
scenario
is
1
18
1.
When
it
gets
out
on
the
7th
we
cut
our
rc
0
and
not
try
to
rush
it
before
that,
because
I
don't
it's
better
not
to
do
an
rc0
with
two
release
blockers,
one.
B
It
seems
like
okay,
just
because
you
know
it
will
give
some
some
folks
something
to
try
in
their
environments
and
give
us
some
feedback.
We
already
got
a
few
good
feedbacks
from
different
people
in
the
last
three
four
days
and
based
on
that,
we
already
landed
a
landed
prs.
For
example,
one
was
around,
we
had
promoted
a
feature
to
beta
and
we
actually
rolled
it
back
as
of
this
morning.
So
we
are
getting
feedback,
so
it
will
be
good
to
do
get
an
rc0
out.
B
But
I,
when
one
118
1,
is
shipped
that
that's
our
recommendation
from
the
discussion
that
we
had
and
then
wait
for
118.2
we
will
jordan
and
others
will
try
to
contact
the
golang
team
behind
the
scenes
to
see
if
anything
can
be
done
to
speed
things
up.
The
reviews
on
this
change
is
very
slow
because
I'm
sure
they
are
distracted
by
something
more
serious
and
given
the
previous
experiences
when
there
is
something
really
big
like
that,
they
don't
try
to.
They
won't
try
to
like
merge
smaller
changes.
B
B
So
the
other
good
news
is
both
madhav
and
jordan
have
tested
a
custom,
build
of
golang
with
the
fix
and
master
golang,
and
we
are
certain
that
it
fixes
our
problems.
So
we
gotta
wait
for
that.
You
know:
change
to
land
and
master
in
golang
master,
then
get
cherry
get
picked
by
a
bot
as
a
backboard
to
golang,
118,
release
branch
and
then
118.2
has
to
be
cut.
And
then
we
can
ship.
B
B
D
D
D
B
A
E
F
Hi
everybody,
so
our
current
status
is
red.
We
see
no
failings
in
master
blocking
and
seven
flaky
issues.
A
few
new
ones
today
have
been
discovered.
We
are
looking
at
some
others.
We
are
checking
if
we
can
find
more
flaky
patterns
and
then
we
will
report
them
as
well.
We
have
opened.
I
think
this
was
on
friday,
a
new
issue
on
mars,
informing
and
six
flakes
right
now,
but,
as
you
just
heard,
they're
the
release
blockers.
F
G
So
our
current
status
is
red.
This
is
because
we
have
two
blocking
issues
that
we
already
talked
about
and
we
have
another
two
critical
urgent
prs
and
I
feel,
like
you
know
like
due
to
the
time
we
are
in
the
in
the
current
release.
Right
now,
I
I
was,
you
know
like
wait
between
red
and
yellow.
So
I
I
went
with.
I
went
with
red
because
of
these
two
criticals
and
two
plucking
issues.
H
A
J
J
E
L
I
I
We
did
have
to
remove
a
couple
of
topics
that
didn't
end
up
making
it
to
the
change
freeze
date
and
also
got
some
feedback
from
reviewers
a
little
bit
late
in
the
game.
The
hope
is
to
get
the
release
blog
out
or
actually
the
removals
blog
out
midweek
this
week,
but
a
lot
of
that's
predicated
on
people
actually
responding
to
github
comments,
which
is
a
bit
of
a
mixed
bag.
D
I
I
A
M
D
M
D
D
We
are,
you
know
in
theory,
like
a
couple
of
weeks,
a
couple
of
weeks
away,
which
is
you
know,
terrifying
as
a
prospect
also,
I
believe
I've
just
about
got
a
final
version
of
the
logo
and
theme
ready,
so
I'll
probably
start
circulating
that
around
in
a
little
bit
once
I've
got
kind
of
final
approval
from
secret
lease
leadership,
but
I
don't
suppose
there's
any
issues
there
and
then
we
can
start
working
into
the
bug.
The
release
block
and
things
like
this
so
yeah
getting
them.