►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20211118
Description
Kubernetes Release Team Bi-Weekly Meeting for 20211118
A
Cool
hello,
kubernetes
people
and
welcome
to
this
released
human
burndown
meeting
on
this
lovely
thursday,
it's
the
18th
of
november.
My
name
is
max
and
I
will
be
your
host
for
today
and
as
a
short
reminder,
this
is
the
kubernetes
project
runs
under
the
code
of
conduct
of
the
cncf,
which
includes
also
this
release
team
meeting
and
basically
the
code
of
contact
boils
down
to
just
be
awesome
to
each
other.
A
So
let's
get
the
whole
thing
started
for
today
we
have
two
open
discussions
both
placed
from
ray.
I
think
we
should
can
also
place
them
in
the
end
right
or
they
would
like
to
keep
it
now
running.
C
Yeah,
so
we
had
code
freezes
past
had
a
a
nice
little
get
together
after
that
to
go
over
all
of
the
enhancements.
I'm
sure
this
was
talked
about
yesterday,
a
little
bit
too,
but
after
code
freeze,
we're
currently
tracking
38
keps
that
that
had
all
their
prs
merged
and
met
the
criteria
and
right
now
we
have
six
marked
at
risk.
C
That
represents
caps
with
an
approved
exception
request,
and
I
need
to
go
through
and
double
check
those
today
to
make
sure
that
we've
got
that
accurately
reflected
on
the
spreadsheet,
because
I
think
that
number's
kind
of
in
flux
at
the
moment
so
I'll
do
a
rundown
today
and
make
sure
that
those
are
are
tracked
correctly
and
we'll
we'll
continue
to
update
as
the
exception.
The
approved
exception,
requests
kind
of
flow
through.
A
A
D
Hello,
everyone,
so
our
current
status
is
yellow
yep
due
to
two
failings
that
we
have
in
mastering
forming,
so
body
master
blocking.
There
is
no
failings
since
yesterday
there
are
a
couple
new
flakies
in
master
blocking,
but
we
are
watching
them.
So
if
they
continue
to
flake,
we
gonna
open
issues
beside
that
yeah.
There
was
a
one
failing
which
was
turned
to
green
today,
mastering
for
informing,
but
I
was
in
contact
with
the
storage
people,
so
basically
they
just
disabled
the
failing
jobs
in
that
specific
test.
D
Gce
cos
master
serial
and
they
said.
Okay,
please
keep
the
issue
open
so
till
you
fix
it.
So
that's
the
current
status,
the
other
issues.
We
are
tracking
them
in
master,
informing
the
failings.
So
that's
all
yeah
I
mentioned
leo
mentioned
this
yesterday
regarding
yeah,
we
are
all
in
talk
with
siginfo
regarding
hosting
the
new
cs
signal
monitoring
stack
as
soon
as
we
get
place
or
yeah
name
space
there
on
the
cluster
or
yeah
anything
you're
gonna
start
testing
there
beside
that
yeah.
D
The
project
board
of
ci
signal
is
open
for
everyone.
Please,
if
you
have
any
ideas,
any
discussion,
you
want
to
start
with
ci
signal.
Please
just
go
on
the
board
and
yeah
feel
free
to
to
start
it,
and
also
next
week
we're
gonna
continue.
The
discussion
in
the
engineering
meeting
on
tuesday
so
feel
free
to
join
yeah.
A
Very
cool
awesome:
if
you
need
any
assistance
with
the
discussions
towards
the
sick
infra,
please
don't
feel
free,
don't
feel
free.
B
A
Great
work
great
to
see
those
two
moving
bactriage.
I
haven't
seen
christoph
on
the
line
do
with
anyone
else
from
bactriage.
E
Hello
we,
after
after
the
code
freeze,
we
are
yellow,
still
we're
looking
quite
a
bit
better
than
we
did
yesterday.
The
integration
branch
is
healthy.
We
had
a
pr
go
in
without
incident
yesterday,
so
that's
good.
We
are
actually
we
are
now
tracking
44
enhancements,
of
which
the
the
the
keynote
here
is.
Six
are
tracked
and
needs
docs
that
don't
have
placeholders
that's
down
from,
I
think
17
yesterday.
E
D
E
That's
up
from
five
drafts
yesterday,
so
I
think
we're
moving
moving
right
along.
A
Very
cool,
very
great
also,
if
they're,
if
you're
running
late
a
little
bit
in
the
communication
or
something
doesn't
report
back,
someone
then
just
also
there
raise
your
hand
so
that
we
can
give
a
double
ping
from
from
the
really
sleek
side
I'll
pass
that
along.
Thank
you
perfect.
Thank
you
cc
was
the
release,
notes.
F
Yeah
currently
they're
green
and
thanks
to
luka's
awesome
work
on
offer.
Four.
We
are
now
ramping
up
for
offer
four
and
working
on
beta0
release
card
and
also
there's
an
issue
for
tracking
the
major
cm
collections.
We
already
reminded
like
most
of
the
six
and
most
of
them
like
are
working
on
the
major
sims.
So
hopefully
we
will
see
like
more
major
sims
candidates
coming
in
this
discussion.
Yeah.
Thank
you.
G
Hey
we
are
kind
of
yellow,
so
we
have
seven
feature
blogs
that
have
opted
in
and
we've
gotten
polar
requests
from
three
of
them.
I'm
still
waiting
to
hear
back
from,
for
I
think
the
auto
delete
stateful
set
pvc
is
supposed
to
be
on
track.
We
haven't
gotten
a
drop
yet
haven't
heard
anything
from
object,
storage,
api
and
then
yes,
not
sure
the
status
is
for
the
first
two
but
yeah.
G
I
am
pushing
our
team
to
hopefully
get
a
drop
soon,
since
we
need
to
have
a
draft
for
the
release
blog
itself
next
tuesday.
That
being
said,
I
started
the
draft,
so
I'm
gonna
I'm
working
on
that
with
my
team
and
then
we
are
still
working
on
the
ordering
of
the
dates
that
we're
gonna,
publish
the
blogs
and
I'm
hoping
to
lock
that
down
by
tomorrow.
B
Thank
you
very
much
and
the
auto
delete
statements.
Save
both
sets
pvc.
They
they
had
a
lingering
kk
code.
Pr
emerge
it
finally
merged
yesterday
and
they
just
and
they
also
made
the
placeholder
doc
placeholder
vr.
So
hopefully
they'll
start
working
on
the
feature
blog
as
well,
because
it
sounds.
G
A
A
All
right
cool,
reese
branch
management-
I
haven't
seen
anyone
on
the
line,
but
I'm
also
not
aware
of
anything
which
currently
should
be
communicated
from
from
this
site.
You
maybe
have
seen
there
were,
I
think,
yesterday
or
tonight
better
to
say
these
from
my
time
zone
perspective
and
some
minor
releases
of
kubernetes
pushed
out.
A
B
Hello,
so,
as
you
probably
saw
the
first
beta
release,
the
one
and
only
beta
release
was
cut
yesterday
with.
B
That
also
is
the
first
time
we
have
salsa
level
one
compliance
in
this
beta
beta
release
and
also
in
their
other
patch
releases
as
well,
might
actually
highlight
that
in
one
of
the
major
themes
or
highlight
that
in
the
release
notes
that
that's
something
new
going
forward
in
the
releases,
I'm
going
to
go
back
up
to
the
open
discussion
topic,
so
there
was
a
and
we
have
a
possible
acceptor
request
needed
for
structured
logging.
B
This
is
from
sig
instrumentation
yeah,
so
there's
some
kprs
that
merge
with
this
with
this
related
to
this
enhancement
during
the
time
of
this
release,
but
they've
never
really
opted
in
to
being
tracked
for
this
release,
so
they,
the
structured
logging
efforts,
is
pretty
much
like
like
an
umbrella
issue
of
there's
several
logging,
several
things
that
need
to
be
changed
for
infrastructure
logging,
so
I
did
see
a
few
that
were
merged
somewhere
still
and
they
do
have
a
dock.
B
Placeholder
pr
deadline
is
doc,
placeholder
pr
created
as
well
for
the
k
log
deprecation.
B
So
I
think
we're
going
to
ask
for
an
exception
request
and
I'm
leaning
towards
that
had
previous,
because
this
is
they
are
deprecating
log.
So
I
think
we're
going
to
ask
instrumentation.
Well,
I'm
not
going
to
say
I
think
we
are
going
to
ask
it's
like
instrumentation
for,
for
an
exception,
request
for
structured
logging,
any
comments
or
feedbacks
or
questions
about
this.
B
All
right,
so
I'm
going
to
send
that
request
right
right
away
to
to
the
sig
chairs
or
to
at
least
to
the
six
slack
channel.
Moving
on
to
the
rest
of
my
updates
today
is
doc's
placeholder
pr
deadline,
which
is
which
is
actually
pretty
good:
six
not
having
it
is
actually
a
pretty
pretty
decent
number
to
have.
B
So
we
had
a
big
increase
in
the
doc
placeholder
prs
just
from
just
from
a
day
ago,
other
than
that
the
next
deadline
for
major
milestones
is
next
tuesday
is
where
the
first
rc
is
cut,
with
that
the
release
branch
will
be
created
and
the
release
jobs
will
also,
or
the
123
jobs
will
also
be
created
on
tuesday.
But
next
week
is
a
little
bit
tough.
It
is
a
big
holiday
week
here
in
the
u.s,
with
the
u.s
thanksgiving
holiday
on
the
following
thursday.
B
So
hopefully
we
hopefully
we
get
everything
done
on
tuesday.
So
with
that,
it's
also
test
freeze
and
the
doc
should
be
ready
for
review
being
that
that's
also
a
tough
one
as
well.
Since
we,
we
asked
quite
a
bit
for
sigdoc,
so
there
were
viewers
to
review
these
prs
in
the
week
during
during
a
major
u.s
holiday
week.
Then,
with
the
first
release
candidate
cuts,
we
also
can
start
the
final
draft
of
the
release.
Notes
as
well.
B
Also
we'll
you
know-
hopefully
the
release
blog
will
be
ready
to
review,
or
at
least
while
underway
by
tuesday,
and
that
next
week
thursday
is
u.s
thanksgiving
holiday.
I
have
yet
to
cancel
that
meeting
on
thursday.
I
will
do
it.
You
know
hour
after
this
meeting
and
then
the
following
week.
We
on
tuesday
is
the
feature.
Blogs
are
ready
to
review.
This
may
not
happen.
B
B
I
guess
then,
thursday
december
2nd
release
notes
are
complete
and
merge
and
the
following
the
the
friday
after
this
december
3rd,
I'm
going
to
ask
for
a
go
no-go
from
all
the
teams
to
see
if
you're
ready
to
be
to
release
on
the
following
tuesday.
So
fridays,
I'm
going
to
put
it
on
the
secretly
slack
channel,
just
where
I
give
a
go,
no
go
from
all
the
teams,
so
that's
important
dates
as
well.
B
It's
not
exactly
a
milestone,
but
we'll
have
that
on
friday
december
3rd,
then
shortly
december
7th
on
tuesday,
we
are
scheduled
to
release
kubernetes
123.
with
that,
I
think
everyone
for
their
time
and
their
commitment.
No
time
is
very
precious.
But
thank
you
for
everyone's
work
on
this
release.
So
I
have
a
few
more
weeks
to
go,
but
we're
very,
very
close,
and
I
know
we
have
a
lot
of
things
to
do
in
the
last
few
weeks.
So
all
right,
that's
it
for
me
any
comments
or
questions.