►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20220407
Description
Kubernetes Release Team Bi-Weekly Meeting for 20220407
A
A
B
Shall
we
get
shall
we
get
started.
B
Did
we
lose
cece?
Are
you
still
there.
B
I
feel
like
I
feel,
like
we've
lost,
I
feel
like
we've
lost
our
lead.
Do
we
have
any
lead
shadows,
we'd
like
to
say.
C
Sorry,
hello,
oh
hello!
Welcome
back!
I
didn't
know
that
I
am
not
being
here
previously.
I
switched
to
use
another
laptop.
I
think
maybe
something
wrong
with
my
current
laptop.
Can
you
hear
me
now?
Yes,
oh
just
give
me
one
second
and.
C
C
C
Give
me
one
second,
I
might
have
to
switch
the
sharing
from
here.
I
guess.
C
I'm
so
sorry
give
me
one.
Second,
I
might
need
to
claim
host
again,
maybe
if
I
want
to
start
sharing
from
another.
Oh
that's
so
weird,
I'm
so
sorry
about
that.
C
Okay,
cool-
maybe
let's
go
let's
do
this
way-
is
that
okay,
if
I
not
sharing
now.
C
I
think
somehow
the
website
of
zoom
just
disallow
the
sharing
from
other
participants,
and
I
was
not
able
to
change
the
setting.
D
C
Nice,
I'm
so
sorry
for
that
and
yeah
yeah.
Maybe
it
just
does
start
over.
We
are
at
like
a
week
on
13th
thursday,
7th
of
april
2022,
and
this
meeting
is
under
since
they
have
code
of
conduct
which
could
be
boiled
down
to
just
please
be
nice
to
each
other
and
the
only
the
small
update
from
me
is.
We
received
a
new
request
today
and
exception
requested
today,
and
we
are
reviewing
it
and
also.
We
are
waiting
for
the
go
1.18.1
b
card
which
is
expected
to
be
cut
today.
C
No,
I
make
sure
I'm
still
be
here
this
time.
C
Cool,
thank
you
I'll
assume.
Nothing
special
happened,
this
yesterday's
meeting
for
enhancement
team
and,
let's
move
to
ci
signal.
F
Hello,
everybody,
our
current
status,
is
yellow.
Actually,
just
now
I
saw
there's
two
new
failings
on
master
master
blocking
and
mastering
performing,
so
I
have
to
update
the
this
sheet,
but
before
those
our
services
basically
did
not
change.
Now
I
have
to
investigate
what
the
new
failings
are.
F
Besides,
that
we
still
track
two
flaky
tests,
and
we
also
still
have
two
open
failing
tests
on
math
and
forming
and
also
this
one
release
blocker,
which
we
are
talking
about
for
quite
some
time
now
right
and
besides
that
it's
looking
good,
I
will
look
into
the
new
failings
as
soon
as
this
call
is
over
and
then
I
will
probably
give
an
update
tomorrow
or
one
of
my
shadows.
F
C
D
C
D
Yes,
good
morning,
good
night,
everyone,
our
current
status,
is
yellow.
We
have,
we
still
have
blocking
issue,
which
is
the
golang
issue,
and
we
still
have
one
flaky
issue,
which
is
the
same
node
summary
api
that
I
I
mentioned
after
all,
the
queries
and
we
still
have
two
pr's
not
merged,
and
I
would
like
to
know
you
know
like
especially
for
the
two
pr's
how
these
supr's
is.
You
know,
like
are
important.
Do
we
need
to
sell?
You
know
like
include
them?
What
is
the
status
and
then
we
can?
C
I
think
the
first
pr
opened
is
against
the
again
the
golang
issue.
We
previously
had
a
workaround.
I
think
we
have
to
remove
it
after
go
on
1.18.1
being
cut
and
be
rendered
in
and
the
second
one
it's
what
I
talked
about
the
exception
request
for
so
they
have
raised
the
exception
request,
if
I
remember
correctly,
it's
for
the
second
pr
yeah,
so
we
are
still
discussing
in
select
channel.
Please
raise
your
opinions
if
you
have
any
on
the
discussion
but
you're
evaluating
if
it
should
be
approved
or
not.
D
E
Are
you
here?
Yes,
I'm
here
yeah.
I
just
moved
us
from
green
to
really
yellow
green
nate,
and
I
were
just
chatting
about
that
and
that's
really
just
because
we
only
have
we
have
one
one
cap
that
says
require
stocks
and
we
don't
have
a
even
a
placeholder
pr
for
it.
So
that's
there's
really
just
one
in
that
state.
E
It's
probably
not
anything,
a
big
block
or
anything,
but
still
that
that's
that
one's
behind
the
one
draft,
pr
that
we
have
one
where
it's
in
draft
state,
but
no
other,
but
not
ready
for
review
yet
is
actually
an
umbrella
pr
for
for
docker
shim.
So
that's
really
actually
that's
in
the
state
that
it
should
be
right
now,
because
there's
still
a
lot
of
work
going
on
with
the
docker
shim
documentation
other
than
that
everything
ready
for
review,
they're,
12
and
28
are
completed
for
no
docs.
E
The
integration
branch
does
need
a
rebase
and
nate's
going
to
be
working
on
that
today
and
our
next
docs
deadline
is
april
12th,
which
is
where
all
the
docs
should
be
ready.
So
we
have
about
five
days
to
get
to
that
state.
With
the
the
last
oh
12
13
prs
ready
to
go,
that's
about
that's
about
it!
Any
questions.
C
In
questions
for
dogs
team,
if
no
we'll
move
to
release
notes,
team
lucas.
C
I
didn't
hear
anyone
talking
because
I
do
saw
someone
editing
the
standards
previously
so.
G
G
You
lucas
for
being
with
me,
okay,
so
the
alpha
4pr
revisions
are
in
process
beta's
in
waiting.
There
was
an
issue
with
krell
where
it
did
the
release
notes,
but
it
didn't
generate
any
of
the
actual
release.
Note
mappings,
I
just
checked
with
my
shadow
and
that's
working
now
he's
generating
the
release,
notes
and
it's
making
the
mappings
now
and
we've
already
done
all
the
review
and
commentary
on
what
needs
to
be
done
so
we're
just
basically
copy
pasting.
At
this
point
we
figured
out
what
the
error
was
with
ssh.
G
Well,
we're
gonna
try
and
identify
like
how
to
fix
it.
The
issue
is
running
the
website
draft
pr
and
the
or
the
website
pr
and
the
draft
pr.
At
the
same
time,
and
of
course,
our
major
themes-
github
discussion
is
right
there.
So
if
you
are
in
any
other
cigs
and
you
think,
there's
something
worthy,
please
post
it
there
and
that's
it.
C
Cool
thank
you.
Thank
you
for
your
updates.
Yeah
thanks.
Everything
is
on
track.
Now,
let's
move
to
comms
mickey.
A
Yeah,
hey
folks,
so
the
removal
blog
finally
launched
today
we
are
probably
going
to
do
some
fast,
follow
changes
to
it.
Just
because
there
were
some
things
that
one
of
the
reviewers
wanted
to
see
added
on,
but
we
were
already
a
week
behind
schedule,
so
we
wanted
to
make
sure
that
got
out.
We
also
are
at
the
point
where
we
need
to
start
checking
on
the
status
of
all
the
feature:
blog
prs.
A
The
next
bit
was
taking
a
look
at
the
content
for
major
themes
and
also
known
issues
as
well.
So
you
know
thanks
to
the
release
of
team
lucas,
for
cutting
piers
for
that
or
discussions
for
that
we
need
to
start
finalizing
those
and
then
getting
those
into
a
draft
of
the
blog.
A
We
do
have
a
blog
draft
already
started,
but
we
need
to
start
getting
more
content
shoveled
into
there.
The
blog
will
probably
be
finalized
towards
the
end
of
the
week
last
week
or
maybe
next
week,
so
we
need
to
start
making
sure
this
content
is
good
to
go,
and
it's
actually
everything
we
want
to
include.
So,
just
as
lucas
had
said,
if
you
are
in
any
other
segs
and
you
want
to
get
content
in
for
major
themes
and
note
issues,
please
please
do
so
as
soon
as
possible.
C
Yeah,
thank
you.
Thank
you
for
raising
this
concern.
I
I
with
so
many
enhancements
tracked
in
this
release.
I
do
expect
a
lot
of
major
sim
candidates
been
there,
but
from
the
discussion
seems
like
only
sig
storage
and
six
apm
machinery
reads
the
sum
of
topics
there,
so
maybe
we
will
be
expecting
some
some
more
major
same
candidates.
A
I
mean
we
found
the
same
thing
with
the
feature
blogs
we
had
over
representations
from
like
sig
storage,
for
example,
and
very
little
from
anybody
else,
except
for
without
like
with
a
lot
of
prodding.
So,
ideally,
we
would
not
do
the
same,
because
this
content
really
should
be
decided
by
the
cigs
and
not
unilaterally
by
me.
C
Yeah
sure
maybe
try
to
pin
the
zigglies
from
the
sixth
channel
would
be
sure,
because
last
time
when
I
did
it,
ziggly's
generally
be
willing
to
help
on
that.
Thank
you.
Thank
you.
Do
we
have
the
release
branch
management
team
here?
C
C
No
james
may
be
also
not
here,
since
he
mentioned
he
will
be
not
available
on
this
meeting.
I
guess
we
are
just
looking
forward
to
the
monday's
rc
they
work
hard.