►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20220408
Description
Kubernetes Release Team Bi-Weekly Meeting for 20220408
A
All
right,
hello,
everyone
and
welcome
to
the
friday,
the
8th
of
april
weekly
burn
down
meeting.
My
name
is
max.
I
will
be
your
host
for
today
as
usual.
This
meeting
is
under
the
kubernetes
code
of
conduct,
which
falls
down
to
be
nice,
awesome
and
friendly
to
each
other,
and
we
please
you
to
follow
this
beautiful
code
of
conduct,
jumping
right
into
the
updates
to
enhancements
with
hotline.
B
Hello,
everyone,
so
we
are
actually
green
now.
So
no
any
update
from
my
site-
or
I
just
asked
grace
if
there
is
any
update
from
her
side
beside
just
one
topic,
just
got
resolved
yesterday.
Regarding
cap
2876
cece
just
wrote
that
yeah
this
cap
wasn't
it's
not
supposed
to
be
resolved
in
124,
it's
postponed
to
125,
and
that
was
the
outcome.
So
that's
it
from
our
side.
A
All
right
moving
forward,
ci
signal,
hello,
everyone
so
overload
status
is
red
and
we
have
two
failing
tests
and
eight
flag.
It
is
in
master
blocking,
but,
as
you
can
see,
most
of
the
problems
are
caused
by
false
costs.
A
The
problem
has
been
already
addressed
and
the
failures
and
the
problems
seems
to
be
resolved
like
two
hours
ago,
so
it
should
be
fine.
I
mean
those
tests
should
pass
soon
and
we
have
one
fellaini
test,
which
is
also
related
to
pascals
and
seven
flag.
It
is
in
master,
informing
okay
yeah,
so
we
will
see
in
the
next
one
two
three
hours
if
the
tests
are
successful.
A
D
Yeah
hi
we've
had
a
little
movement
since
yesterday
and
I
think
we're
a
little
less
yellow
and
a
little
more
green
today
than
we
were
yesterday.
We
have
no
no
caps
that
need
docks,
that
don't
have
a
pr
right
now
and
there's
only
one.
That's
still
in
draft
pr
state
and
that's
our
sort
of
overall
docker
shim
removal,
one
so
that's
kind
of
the
umbrella
one,
so
we're
actually
kind
of
on
track
at
the
moment.
D
So
we
have
10
ready
to
review
30
completed
and
five
no
docs
required,
and
we
just
have
all
the
docs
have
to
be
done
in
four
days.
So
we
do
have
a
bit
of
work
ahead
of
us.
I
think
that's
about
it.
Any
questions.
D
E
Hi
everyone
we
are
from
comms
here,
so
we
are
green,
like
the
comms
have
been
sent
regarding
the
removable
reputations
blog
and
there
were
some
follow-up
changes
here
has
been
voice
now
and
yeah.
We
are
working
on
future
blog
ps,
we
are
checking
the
status
and
we
don't
have
any
more
updates
on.
You
know,
selecting
the
major
themes
it
will
all
be
done
like
we
are
aiming
for
the
future
blog
thing
to
be
ready
by
the
end
of
next
week.
Also
yeah.
F
Hello,
so
I
missed
yesterday's
meeting
and
apologies
for
that.
I
had
a
work
conflict.
I'm
gonna
go
over
the
minutes
in
a
moment
to
see
if
there's
anything,
but
I
think
I'll
be
pinged
on
things
already,
I'm
going
to
send
an
email
about
a
potential
release
delay
I'm
going
to
have
a
a
draft
of
that
in
the
channel.
F
Shortly
this
we
were
talking
about
whether
given
the
the
delay
to
go
118.1
with
the
fix
that
we
can't
release
without
there
you
know,
are
we
going
to
have
to
delay
the
release
and
how
that
works,
and
I
think
the
kind
of
main
line
from
steven
here
is
that
we
should
we
shouldn't
advertise
a
new
fixed
date
and
we
should
advertise
a
potential
delay
and
then
make
a
decision
when
we
know
more.
So
that's
probably
what
we're
going
to
do.
F
I
also
need
to
respond
to
an
email
about
the
test.
Freeze,
exception
request:
that's
for
web
triage,
which
we
decided
no
to
we're,
not
we're
not
gonna,
let
it
in
we're
gonna,
wait
until
one
twenty
four
one.
The
goal
here
as
another
thing
is
really
some
stability
and
I
don't
take
into
account
the
fact
that
might
be
a
release
delay.
I
think
if
it
is
a
release,
delay,
that's
not
a
reason
to
let
in
anything
we
wouldn't
otherwise,
because
the
point
of
the
release
delay
is
to
try
to
stabilize
everything.