►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20211130
Description
Kubernetes Release Team Bi-Weekly Meeting for 20211130
A
Just
want
to
welcome
everyone.
I
want
to
welcome
everybody
to
the
thursday
edition
week,
16
december
2nd
burn
down
meeting
and
our
fearless
leader
ray
won't,
be
here,
so
I'm
stepping
in
his
place.
This
is
just
a
reminder
that
we
run
this
meeting
under
the
cncf
code
of
conduct.
I
think
it
could
be
just
summarized
that
we
want
to
be
excellent
to
one
another,
so
I
want
to
just
get
right
to
it
and
I
don't
have
any
open
discussion
items.
A
Okay,
if
not,
then
we
will
move
over
to
enhancements
with
zander
who
I
don't
see
online,
and
I
don't
know
if
there's
anybody
from
the
enhancement
team,
but
I
assume
everything
is
good,
since
they
are
green.
I
think
you're
at
this
state
of
enhancement,
square
you're,
pretty
much
on
just
standby.
So
there's
any
questions
for
that.
We
can
always
bring
them
up
in
your
channel
or
I'm
sorry,
the
release
channel
for
enhancements.
B
So
our
current
state
is
yellow
due
to
a
few
failings
and
one
is
in
master
informing
and
the
other
one
is
in
release
cut
mastering
forming.
So
there
is
no
critical
failing.
You
know
test
right
now,
just
like
few
passing
jobs,
you
know
master
blocking,
moving
to
flaky
and
yeah
the
other
way
around
in
the
other
dashboards
yeah.
We
are
tracking
few
issues,
as
I
mentioned,
for
the
failing
the
tests,
nothing
especially
from
our
side.
We
are
looking
at
all
our
dashboards
so
closely
for
the
release,
cut.
A
All
right,
we
really
appreciate
it.
I
think
the
team
is
like,
I
said,
doing
a
really
great
job
with
this.
So
thank
you
for.
Thank
you
very
much.
Anyone
have
any
questions
for
hussein
or
the
for
the
team
overall,
all
right.
Well,
then,
we
will
move
over
to
broad
triage
and
we
have
shin
yoon.
I
apology,
if
I
say
your
name
wrong.
A
I
appreciate
it,
anybody
have
any
questions
for
the
bug,
triage
team,
some
of
the
issues
that
they
brought.
D
We're
looking
we're
looking
pretty
good
today,
I
can't
get
my
camera
to
work.
Sorry,
so
yeah
we
have
all
of
the
tracked
enhancement.
Stocks
pr's
are
reviewed
and
merged.
We
have
a
handful
of
knits
and
some
follow-up
things
to
do,
but
we're
looking
good
on
those
as
well.
Nothing
super
crazy.
We
didn't
miss
anything
major
and
oh
tim's
here
so
tim's
handling.
Quite
a
lot
of
that.
To
be
honest,
hi
tim,
thank
you
actually,
since
you're
here
I
could
just
say.
D
Thank
you
so
much
for
everything
you
do,
I'm
giving
you
a
big
thumbs
up.
A
Going
to
oh
no
go
ahead
all
right
now
I
was
going
to
say
great
to
see
tim
here.
We
always
appreciate
all
your
hard
work.
So
thank
you
for
the
appearance.
A
A
D
A
E
Our
status
is
green.
The
major
theme
pr
that
was
up
yesterday
has
been
merged.
There
was
a
mention
that
there
might
be
one
more
change
to
major
themes
in
the
release:
note
slack
channel
and
we're
waiting
for
that
other
than
that
all
good.
A
F
We
are,
we
are
yellow,
but
really
it
should
be
green
with
comms.
I
think
it's
just
we're
just
overly
cautious,
currently
we're
at
the
stage
of
finalizing
the
release
blog,
so
I
think
we're
waiting
for
another
contribution
from
ray
to
the
beginning
section,
just
to
describe
the
themes
and
aside
from
that,
we're
just
looking
for
anyone
else
who
is
interested
in
reviewing
the
release
vlog,
that
we
have.
A
Okay,
good
to
go
and
then
and
then,
as
far
as
like
all
the
other,
you
know
feature
blogs
all
that
scheduled
everything
looking
good
there
yeah
we
haven't,
prioritized
awesome
awesome.
That
is
great.
I
know
during
my
cycle.
Everything
came
in
hot
at
the
end,
so
great
to
hear
that
you
all
have
this
under.
A
G
Yes,
hello.
Well,
thank
you
again.
Cxx
ci
signal
for
all
the
hard
work,
just
we're
yellow
following
their
own
status.
We
also
yesterday
we
sent
the
communications
with
the
decision
to
stick
to
cherry
picks
for
the
remainder
of
123.
G
It
was
sent
to
kdev
to
the
mailing
list,
but
also
I
opened
a
github
discussion
in
case
anyone
I
mean,
I'm
I'm
sure
that
probably
everyone
in
this
call
is
already
very
familiar
with
this
discussion,
but
some
people
that
that
don't
participate
in
the
in
this
calls
were
were
concerned
and
even
yeah.
There
was
some
stress
given
that
the
communication
was
delayed
a
little
bit.
So
that
is
my
responsibility,
so
it
is
all
out
now.
G
So
please,
if
you,
if
you
see
any
contributors
or
or
or
anyone
concerned
or
with
questions
or
anything
around
this
topic,
please
refer
them
to
to
the
links
that
I
just
referenced
this
that
I
just
said
in
the
agenda,
but
I'll
add
the
links
for
both
the
mailing
list,
communication
and
the
github
discussion,
and
don't
forget
that
we're
that
this
is
just
for
the
therapeutic
discussion
it's
just
for
123.
G
for
now
and
on
the
retrospective
that
is
happening
on
december,
the
15th
I
think
at
10
a.m.
Pacific
time
people
are
welcome
to
to
give
their
opinions
around
this
topic
on
fast
forwarding,
the
branches
or
cherry
picking
or
whatever
you
want
to
share.
So
again,
this
is,
for
I
know
the
people
in
this
call
right
now
might
already
be
very
familiar,
but
if
you
see
any
discussions
around
it,
please
refer
people
to
this
and
I
think
that's
it.
A
All
right,
thank
you
for
that
explanation
and
also
setting
us
up
for
the
retrospective.
For
that
discussion
definitely
is
really
helpful
and
I
did
see
the
communication.
Do
the
mailing
yesterday
so
appreciate
you
taking
a
taking
that
on,
and
I
know
just
this
is
more
personal.
I
was
with
adolfo
like
about
a
week
and
a
half
ago
and
he
was
just
gushing
about
you
and
I've
heard
how
hard
you
guys
are
working
so
appreciate
everything
you're
doing
for
the
team.
So
thank
you.
G
Oh
yeah,
I
also
sorry
I
I
wanted
to
thank
navaroon
because
yeah
he
has
been
he's
the
branch
manager
shadow,
but
it's
more
like
branch
manager,
co-branch
manager
with
me,
so
he
has
been
working
really
really
hard.
So
just
wanted
to
acknowledge
that.
A
A
I
don't
think
he
did
not
leave
any
notes
for
us,
so
that
just
leads
us
to
just
an
open
item
which
I
think
was
brought
up
a
little
bit
earlier,
and
this
is
kind
of
like
one
of
the
last
things
related
to
the
major
theme
header
and
I
think
the
question
was
regarding
how
we
wanted
to
track
one
of
them
and
if
you
ever,
you
could
check
this
out
in
the
release
notes
for
the
meeting,
but
it
is
related
to
graduating
hpa
api
to
ga.
A
A
The
hba
v2
api
is
ga,
so
we're
considering
that
change,
and
you
know
moving
it
into
the
group
of
ga
major
themes
instead
of
like
deprecations,
since
what
is
tracked
is
the
graduation
to
ga,
which
is
a
result
of
the
beta
api
being
deprecated.
So
just
looking
for
any
comments
or
feedback
about
that
change,.
A
Anyone
else
have
any
comments.
A
A
To
warn
the
community
about
the
impending
freeze
that
we
have
coming
up
to
get
ready
for
the
release
and
ray
will
finish
up
working
on
his
release,
bug
draft
on
hack
md,
so
that
we
can
help
set
up
comms
to
get
that
going
and
ready
for
release
and
starting
tomorrow,
just
as
a
reminder
keep
an
eye
on
sig
release.
A
Slack
channel
everybody
just
so
that
you're
aware
of
that
we're
going
to
start
doing
the
go,
no
go
for
the
release
to
see
where
we're
at
so
each
day,
we'll
go
through
it
as
we
track
towards
launch
so
exciting.
Look
forward
to.
Finally,
all
of
us
getting
there
really
close,
and
so
just
appreciate
everybody's
hard
work
and
efforts
in
this.
So
thank
you
all
and
I've
had
to
say.
One
thing
for
everybody
is
just
be
good
to
yourself
today:
get
a
street
taco,
that's
my
advice.
So
have
a
beautiful
day.