►
From YouTube: Kubernetes Release Team Meeting 20211122
Description
For more info, see https://git.k8s.io/community/sig-release
A
There
there
you
go
starbucks.
B
That's
right,
yeah!
I
do
just
wanna
welcome
everyone.
This
is
a
this
week.
Is
week
14,
so
we
only
have
two
more
weeks
left
in
the
release
cycle
this
week
next
week.
This
week
is
not
a
really
full
week
for
us
folks
in
the
u.s
it's
vibes
thanksgiving
next
week's
last
four
week,
then
we
have
a
few
days
in
up
to
december
7..
B
So
did
this
week
like
I
mentioned
it
is
u.s
thanksgiving
holiday,
so
I
canceled
the
thursday
meeting
is
and
the
friday
meeting
is
the
eu
apac
meeting
a
lot
of
folks
here
in
the
us
have
that
day
off
as
well,
but
since
it
is
more
of
more
targeted
for
the
eu
apac
friendly
time
zones,
so
we're
still
having
a
friday
meeting,
so
it
did
cancel
that's
on
the
invites.
So
hopefully
that's
not
that's
not
on
your
calendar,
all
right,
just
one.
B
I
want
to
give
some
some
praises
to
the
ci
signal
team.
There
was
a
failure
and
master
blocking
over
over
the
weekend
and
thank
you
for
everyone
in
ci
signal,
especially
hussain,
for
alerting
that
leonard
for
triaging
that
and
jordan
leggett
for
creating
the
pr
to
fix
it.
So
we
did
have
failure
over
the
weekend,
but
it
was
fixed
pretty
quickly
relatively
quickly.
So
thank
you
very
much.
The
ci
signal
team,
great
job.
A
C
Yeah,
so
we're
still
green,
I
believe
at
this
point
all
of
the
pending
exception.
Requests
have
been
resolved
and
their
their
have
merged
within
the
deadline.
So
at
this
point
the
the
sprite
sheet
should
be
fairly
up
to
date.
We
don't
have
any
more
red
at
risk
on
there
anymore,
which
is
nice
to
see
green
across
the
summer
dawg
being
loud.
So
it's
it's.
C
It's
green
across
the
board
now
other
than
the
ones
that
have
been
removed,
so
the
the
numbers
that
you
see
here
under
metrics
should
be
fairly
up-to-date
yeah.
At
this
point,
I
think
we're
just
kind
of
holding
to
see
if
any
more
exception
requests
surface
and
we'll
go
from
there.
A
B
Yeah
we
want
to
keep
kk
quiet
because
we
do
have
the
release
cuts
for
tomorrow.
So
you
want
to
make
sure
nothing
gets
in
today.
D
Hello,
everyone
fossen
from
cs
signal
team
and
thank
you
ray
for
your
nice
comments.
You
know,
I
think
it's
a
great
teamwork
with
all
my
shadows.
They
are
doing
interstellar,
job
and
yeah.
It
gives
me
also
the
motivation
to
also
work
with
them
and
yeah.
That's
really.
You
know
nice
teamwork.
D
So
currently
we
are
yellow
due
to
three
failings
in
master
informing,
but
after
blocking
apart
from
the
weekend,
we
got
a
failing,
but
the
next
commit
fixed
that
so
I
mean
like
next
pull
request
on
the
master
branch
fix
that
so
nothing
yeah
concerning
regarding
master
blocking,
so
we
have
few
flakies,
but
we
are
tracking
them
in
master
informing.
We
have
one
new
failing
job
in
this
week,
so
yeah
I
just
put
it
there,
the
the
failing
job
link
and
but
the
shadows
already
opened
the
github
issue
for
that.
D
So
we
are
tracking
also
closely
beside
that
yeah.
D
As
obviously
I
seen
all
team
members
mentioned
when
the
shadows
were
reporting,
so
the
ci
signal
tool
improvements
are
going
forward
so
just
feel
free
to
take
a
look
at
our
ci
signal.
Project
board
feel
free
to
drop
your
comments.
Any
suggestion
everything
is
appreciated
and
we
are
looking
forward
to
deliver
a
nice
and
improved
monitoring,
stack
and
also
ci
signature
report
tool
for
the
next
release.
So
that's
all
from
my
side.
A
A
B
So
marshall
slack
that
barsha
was
sick.
Today
is
there
anyone.
B
All
right,
varsity
did
add
in
the
updates,
so
I
could
read
right
there.
I
think
it's
supposed
to
be
green
because
they're
and
for
there's
only
four
open,
non-test
flick,
kkk
issues,
there's
no
critical,
urgent
issues,
there's
no
important
student
issues
so
which
is
great,
and
there
is
two
priority
important
soon
prs
I'll,
take
a
look
at
them,
but,
like
I
mentioned
before,
since
we
don't
so
these
are
just
issues.
I'm
sorry.
These
are
pr's
I'll.
Take
a
look
at
them.
We,
ideally
we
don't
want
anything
in
kk.
B
We
won't.
I
prefer
or
we'd,
be
preferred
to
have
the
the
branch
be
kind
of
stable
a
day
before
the
release
cut
and
then
I'll
talk
about
that
and
a
little
bit
more.
A
E
Yeah,
hey
joseph
and
hey
everyone
and
the
current
status
for
dogs
team
is
green.
The
integration
branch
is
healthy.
All
the
draft
board
requests
were
submitted
before
the
deadline
last
november
18th.
So
it's
a
a
good
news
and
tomorrow,
as
a
heads
up
tomorrow
on
november
23
is
the
deadline
for
getting
these
draftport
requests
ready
for
review.
We
are
following
these
pull
requests
very
closely,
so
in
order
to
to
get
ready
and
right
now,
the
numbers
are
11
drafts
and
12
ready
for
review.
A
F
Cece
yeah
hi
cece
here,
so
our
status
is
growing
and
we
got
around
the
shadows
and
demon
take
over
the
beta
on
their
release
card
and
he
did
a
great
job.
So
we
are
pretty
much
ready
for
the
next
release
card
and
also
we
have
sent
out
the
reminders
to
all
of
the
six
for
the
major
same
collections
and
the
discussion
is
going
on
in
the
discussion
board.
So
I
think
the
process
there
is
also
great
yeah,
we're
just
waiting
for
maybe
a
couple
more
days
like
for
the
more
mature
same
topic
coming.
A
All
right,
I
appreciate
that
I
did.
I
took
a
look
at
the
discussion
so
yeah,
so
you
said
you're
going
to
keep
the
issue
open
for
how
long
couple
more
days.
F
Yeah
with
the
reminder
we
sent
out
to
each
six,
we
hope
they
will
add
the
topics
before
on
24th,
so
we
will
still
so
then
then
I'll
start
to
write
the
major
themes.
Yeah.
A
G
Hello,
we're
still
filling
out
our
notes
with
links
and
things,
but
we
have
five
feature
blogs
in
pr.
Our
status
is
green.
Those
are
all
due
tomorrow.
We've
got
two
more
that
we're
still
waiting
on
and
we'll
make
sure
to
get
those
links
in
object,
storage
and
volume,
popular
data
source,
we're
finalizing
the
publish
dates
for
the
feature
blogs
today,
and
we
have
a
draft
of
the
release.
Blogs
started
that
we're
waiting
on
leads
for
release,
themes.
A
All
right:
well,
that's
good!
That's
good
to
see
all
those
feature
blogs
in
pr.
I
know
during
my
cycle.
I
was
not
that
at
that
state,
so
good
for
you
any
questions
for
the
cons
teams
from
anybody.
B
Just
one
comment
that
I
will
look
at
at
the
release
blog
you
saw
this
the
I
have
the
link
from
the
slack
thread.
So
take
a
look
at
that
this
afternoon.
B
A
We're
waiting
for
ray's
update,
we'll
be
watching
it
closely.
H
Hello
how's
it
going
well
as
ray
and
other
people
have
already
mentioned
tomorrow.
We
have
the
branch
cut
so
since
the
team
is
pretty
much
distributed
at
this
time
like
I'm
in
europe,
and
we
have
india
and
we
have
america,
so
stability
and
reliability
is
pretty
much
appreciated.
Like
more,
I
mean
it's,
it
always
is,
but
right
now
a
little
bit
more.
So
thank
you
for
your
hard
work
and
yeah.
As
everyone
has
been
saying,
the
ci
signal
has
been
doing
a
stellar
job.
H
You
will
never
know
how
easy
you
make
our
job
now
like
we
we're
always
gushing
about
it,
but
really
just
being
able
to
see
everything
in
our
report
and
not
even
with
the
fancy
tool,
the
automated
tool
that
that
hopefully
will
help
at
some
point
for
all
of
us,
but
just
the
organization
and
reports,
just
in
slack
makes
a
lot.
H
It
makes
it
a
lot
easier,
so
very
grateful
for
that
from
the
organization
and
that's
it
so,
hopefully,
everything
wear
yellow,
because
the
eye
signal
is
yellow
and
also
because
the
other
day
that
taylor
caught
our
better
release.
We
were
like
yeah,
everything
is
great
and
then,
obviously
in
the
morning
everything
went
down
and
we
had
the
failure,
the
the
master
failure
and
many
other
things
so
just
in
an
abundance
of
caution,
we're
yellow.
But
if
we
were
to
cut
today
it
would
be
good
to
go.
I
Yeah,
I
have
one
so
just
as
a
reminder
of
regarding
branch
stability.
Remember
that
any
prs
that
get
merged
and
any
enhancements
that
go
in
the
last
minute
they
take
a
while
for
the
virtual
markets
to
to
update.
So,
if
you
were
to
merge
something
today,
I
think
today,
yeah
probably
they
won't.
They
won't
get
into
the
alpha
version,
because
version
markers
take
a
while
to
to
update.
So
keep
that
in
mind
when
playing
in
las
vegas.
A
All
right
well,
then,
we'll
move
right
into
our
release,
lead
section
with
ray.
B
All
right,
like
veronica's,
mentioned
tomorrow's,
the
first
release
candidate
will
be
cut
with
that
it
brings
several
milestones,
but
I'll
talk
about
those
a
little
bit.
I
do
want
to
first
touch
on
major
themes.
I
added
a
few
major
themes
last
night
for
dual
stack:
ipv4
ipv6,
going
to
stable.
I
feel
like
that,
should
be
one
of
the
big
major
themes.
Also
pod
security
mission
controllers
go
into
beta.
I
feel,
like
you
know.
Those
two
are
really
good
major
themes
to
have.
B
I
did
cc
folks
who
are
who
are
more?
I
guess
are,
I
guess
they
worked
more
with
those
enhancements,
so
just
want
to
get
some
feedback,
because
I
I
created
the
content
myself,
so
there
might
be
some
changes
with
that
I
do.
I
took
a
look
at
some
of
the
features
that
made
code
phrase
so
might
add
in
a
few
more
what's
what
topology,
where
hints
to
beta
and
personally
I
like
ephemeral,
containers
to
beta.
So
some
might,
I
think,
some
sig
node
and
signet
work
about
that.
B
The
third
one
I
put
on
the
agenda
qubit
crs
cubelet
cri-
supports
beta
that
was
actually
added
by
sasha
already,
and
so
that's
actually
key
to
remove
docker,
shim
and
124.
So
without
the
cubelet
ci
support
going
into
beta,
we
would
not
be
able
to
remove
docker
shim
in
124.
B
so
back
to
the
release
cannon
cut
tomorrow
with
that
it
brings
in
additional
milestones.
So
one
is:
is
we
also
have
test
phrase
where
we
don't?
We
don't
allow
any
more
tests
to
be
changed
unless
it
is
release
blocking
or
there's
some
exceptional
reasons.
So
after
test
freeze,
the
goal
is
just
to
we.
We
should
just
only
fix
reverts
or
fix
failing
tests,
so
no
tests
or
no
changes
to
tests
or
are
done
less
unless
needed.
B
There
are
coming
milestones
once
with
the
release,
candy
cuts.
We
also
make
the
release
123
branch
also
and
the
release
123
jobs
as
well
and
tomorrow
is
also
some
deadlines
for
the
docs
ready
for
review.
I
know
there's
about
11
docs
that
store
in
draft,
so
we
should
make
sure
that
those
prs
are
at
more
mature
states
for
by
tomorrow
or
by
end
of
day
tomorrow.
B
Also,
the
release
blog,
which
I
do
have
the
link
to
the
draft,
so
take
a
look
at
that.
Let's
see
what
else
thursday's
holiday
for
in
the
u.s,
so
yeah
there's
thanksgiving
here.
I
did
cancel
that
meeting.
So
hopefully,
that's
not
on
your
calendars,
then
next
tuesday,
we,
the
feature
blog,
should
be
ready
to
review.
This
is
not
always
the
case.
The
feature
blogs
are
usually
ready
to
view
closer
to
the
release
date.
We
would
like
to
have
them
already
review.
B
I
think
the
five
are
at
a
really
good
review
states
I've.
So
I've
seen
like
100
over
100
comments
on
the
well
on
the
pod
security
blog
it's
off
and
the
dual
stack
blog
has
a
good
number
of
comments
already.
So
both
of
those
have
been
reviewed
quite
a
bit
then
after
next
week
we
we
have
the
well.
We
also
have
the
release
on
thursday
december
7th,
but
before
that
we
want
to
make
sure
that
the
release
notes
are
complete
on
the
thursday
before
the
release.
So
that's
december
2nd.
B
We
do
have
a
deprecation,
the
major
theme
and
it's
the
flex
volume
deprecation,
but
I
did
some
investigation
technique
was
actually
deprecated
last
year
in
2020,
but
it
wasn't
firmly
announced
it
was
not
targeted
to
be
removed
at
all.
Currently
so
do
so.
Currently
you
might
see
that
deprecation
in
the
major
things,
but
we
don't
have
that
tract
enhancements
because
it
was
actually
deprecated
last
year
at
this
time.
B
All
right
with
that,
then
we
on
friday
december
3rd,
I'm
going
to
ask
the
teams
for
a
go,
no
go
on
slack,
so
we
kind
of
start
that
go
no-go
phase
of.
Are
we
ready
to
officially
release
so
starting
on
december
3rd,
then
we'll
continue
that
on
mond,
the
following
monday
and
also
on
december
7th.
So
that
brings
us
to
the
release
date
and
so
yeah.
That's
pretty
much
it
and
we'll
have
the
red
show
the
following
week
after
that,
so
any
comments
or
questions.
A
It's
great
for
thursday,
being
it's
a
thanksgiving
holiday.
If
I
mean
we
look
good
everything's
looks
you
know
pretty
healthy,
we're
tracking
really
well,
but
if
anything
does
come
up
from
anybody,
is
there
anybody
on
standby
who's,
not
on
holiday,
like
obviously
you're
gonna,
be
on
holiday,
but
anybody
to
escalate.
If
there
is
an
issue.
B
Yeah
I'll
ask
max,
I
know
since
he's
over
in
germany
if
he
could
keep
an
eye
out
on
the
side
channels
to
see
if,
if
he
could,
you
know
triage
any
issues
and
well
thursday's
holiday
for
most
of
us
or
most
of.
A
All
right,
our
last
item
is
six
scalability,
which
has
been
marked
green.
So,
along
with
everything
else,
everything
seems
to
be
moving
along
really
well.
So
I'd
like
to
just
thank
everybody
for
the
updates
today
and
we're
at
kind
of
an
exciting
time
so
appreciate
everybody's
participation.
So
everybody
have
a
great
great
day,
great
afternoon,
good
or
great
evening,
wherever
you're
at
we'll
see
you
next
time.