►
From YouTube: Kubernetes SIG Release Meeting for 20221206 (1.26)
Description
Kubernetes SIG Release Meeting for 20221206
A
A
A
We'll
kick
this
off
by
allowing
anybody
that's
new
to
introduce
themselves,
but
it
looks
like
we've
got
a
cast
of
familiar
folks
here,
so
pause
for
just
a
second
I
think
everybody's
been
around
before
so
go
ahead
and
we'll
jump
into
sub-project
updates
and
we
can
start
it
off
with
released
engineering
Marco.
Do
you
want
to
you
want
to
kick
us
off
with
and
talk
about
the
the
go
update,
stuff,
yeah.
B
So,
okay,
let's
get
started
first
of
all,
is
Jeremy
just
announced.
Go
updates
are
planned
for
today
those
are
going
to
be
security,
patch
releases
for
1.18
and
1.9
team,
and
we
are
expecting
those
releases
today.
We
will
offer
those
releases
throughout.
We
will
have
more
idea
about
what's
exactly
the
vulnerability
and
for
yeah
what
actions
you
need
to
take.
We
are
whoever
planning
to
do
patch
releases
for
kubernetes,
125,
124,
123
and
122.
on
Thursday.
B
We
intentionally
delayed
those
Specialists
for
one
day
so
that
those
are
now
on
Thursday
so
that
we
can
include
those
whoop
actually
that
they're
coming
out
today.
So
now
that
I
said
those
for
petrolysis
for
kubernetes
doesn't
coming
out
to
Thursday
and
we
are
also
doing
one
hopefully
final
122
release.
It
is
going
to
include
the
registered
change.
B
It
is
also
going
to
include
one
important
regression
Peaks
that
was
introduced
with
latest
security
fixes
in
kubernetes
and
also
there's
going
to
be
LCD
update,
because
the
LCD
maintenance
are
recommending
that
update
because
of
some
data
consistency,
issues
that
they
have.
That
would
be
mostly
it
when
it
comes
to
releases.
B
Also
126.0
is
scheduled
for
Thursday.
I
would
like
it
to
release
team
to
provide
update
regarding
that,
but
it
is
also
going
to
include
the
go
update
that
is
coming
out
today.
Additionally,
what
I
would
like
to
mention
is
some
of
the
work
that
we
did
over
the
past
seven
days.
First
of
all,
we
managed
to
triage
some
stuff
when
it
comes
to
each
promotion
and
we
we
fixed
some
bug
when
it
comes
to
the
identity
that
is
being
used.
So
we
are
signing
images
with.
B
Identity-
and
we
also-
we
have
some
more
stuff
and
more
issues
that
we
have
with
promotion,
I
summarized
everything
in
the
following
threads.
So
if
anyone
interested
want
to
take
a
look
prefer
to
do,
if
you
want
to
help,
please
reach
out
to
me
and
Adolfo
on
release
manager,
and
then
we
will
be
happy
to
sign
and
share
if
there's
anything
else
that
they
know
about
this
or
to
provide
some
pointers.
Additionally,
some
updates
about
the
open,
build
service
profile
that
we
were
working
on.
B
And
we
showed
them,
how
are
we
doing
what
we
came
up
so
far,
and
it
turns
out
that
this
is
solid?
They
provided
some
feedback
to
us
and
was
very
important.
We
talked
about
scalability
concerns
that
we
had
about
the
traffic
and
all
the
other
stuff,
and
there
are
some
solutions
to
that.
They
think
it
should
be
fine,
but
even
if
you
run
into
some
problems,
it
is
also
possible
for
us
to
cost
some
mirrors,
and
that
should
be
pretty
much
stayed
forward.
B
We
are
going
to
document
all
that
as
part
of
the
cap
update
that
I'm
working
on
I
hope
that
I
will
be
able
to
finish
it
by
the
end
of
this
week.
If
not
yeah
beginning
of
next
week,
we
will
have
it
for
sure.
In
meanwhile,
I'm
going
to
share
in
Zoom
chat
the
meeting
notes
from
our
meeting
from
Wednesday.
So
you
can
also
take
a
look
at
that.
B
A
A
So
I
wanted
to
just
have
a
quick
chat
or
Noah
looked
at
it
and
asked
if
we
wanted
to
merge
it
before
or
after
your
PR
I'm,
in
the
process
of
updating
the
branch
manager
handbook
to
add
that
as
a
branch
cut
task,
because
we
didn't
have
it
anymore,
so
it
just
didn't
get
done
as
part
of
that
and
then
there's
another
unrelated
change
that
I'm
working
on
in
the
in
the
handbook
to
change
how
we
update
the
the
publishing
bot
rules,
there's
like
a
script.
That
does
that.
A
So
we
can
avoid
copy
and
paste
errors
and
stuff
later
on.
So
I
have
changes
in
the
handbook
that
are
ready
to
go.
But
I
wanted
to
link
to
an
example
PR
for
the
variance
update.
So
I
was
curious.
If
you
wanted
to
merge
this
PR
to
create
the
126
variant
for
cube
cross,
and
then
we
can
rebase
your
PR
on
top
of
that
to
bump
the
Go
version,
or
do
we
want
to
wait
until
yours
goes
in
and
then
we
can
do
the
the
126
variant
edition
either
way
is
Finds
Me.
B
Yeah
I
think
it's
going
to
be
easier.
If
we
merge
that
we
are
down
and
then
I
will
base
other
PS
because
I
think
was
to
be
the
of
the
cube
Quest
image
is
published.
We
also
need
to
update
in
in
community
such
communities,
and
we
can
do
that
with
the
1pr.
So
it's
going
to
be
easier,
so
let's
get
it
merged
and
then
we
can
I
will
base
my
PR
and
that's
it.
Okay,.
A
A
C
Hello
yeah
I
can
I
can
give
an
update.
So
from
our
side
everything
right
now
looks
kind
of
good.
So
we,
as
we
already
heard,
we
changed
the
release
date.
We
communicated
this
over
a
lot
of
different
channels.
The
original
discussion
was
in
release
management.
It
was
basically
a
barcode,
dropped
or
wrote
the
note
about
the
colang
changes,
and
then
we
had
quite
a
lengthy
discussion
and
right,
so
we
reach
out
over
the
to
the
community,
so
everybody
is
aware
of
that.
C
So
hopefully
this
goes
well
today.
We
also
send
out
over
six
release
a
message
about
go
or
no
go
status
updates
from
each
team.
Right
now
everything
looks
good.
Nobody
is
has
like
any
big
concerns,
so
probably
the
only
thing
would
now
be
the
diversion
changes
or
the
version
bumps
from
golang,
so
depending
on
that
all
the
other
teams
are
kind
of
kind
of
in
a
good
shape.
So
that's
great.
C
You
know
to
the
Retro
that
we
should
discuss
Doc's
ready
for
reviewers
the
deadline,
because
at
the
moment
it's
not
really
a
deadline
and
it's
kind
of
tiring
to
chase
other
folks,
and
maybe
we
can
improve
on
that
or
it
would
be,
would
be
good
to
improve
on
that,
and
also
the
sick,
docs
chairs
and
folks
agreed
on
this
point.
So
besides
that
comms
is
also
looking
good.
We
scheduled
now
all
the
blocks.
There
is
currently
a
discussion
up.
C
C
That's
a
Tuesday
I
think
so
from
a
common
site.
Also
everything
good
I
have
also
a
couple
of
like
journalists
who
are
interested
about
the
release,
so
I'm
I'm
in
in
sync,
with
them
too
and
right
then,
there's
I
think
the
last
point
about
the
next
team.
The
next
release
team
I,
don't
know
if
if
no
room
wants
to
talk
about
this,
but
so
the
1.27
release
team
gets
also
assembled
right
now
and
I
propose
Xander
as
next
release
date.
Okay,
that's
it
for
my
site.
A
A
C
Sure
right,
this
one
is
about
the
release
team
enhancements
tracking
project
board.
So
this
release,
we
use
the
GitHub
project
board
for
the
first
time
and
we
want
to
use
it
also
next
cycle
and
right
now
we
have
basically
two
options
to
proceed
with
this:
either
we
reuse
or
use
the
existing
project
board.
So
this
is
I
think
like
option,
one
which
I
wrote
down
so
reuse,
the
existing
enhancements
project
board
next
cycle
and,
like
add
new
views
to
it
and
so
on
or
create
a
new
project
board.
C
I
can
maybe
I
should
I
just
read
out.
Basically
my
minuses
and
question
marks
and
classes,
okay,
so
for
for
the
for
the
option,
one
reuse,
the
existing
project
boards,
so
having
multiple
views
is
a
bit
a
bit
messy.
So
you
have
basically
all
the
tabs.
Then
you
need
to
see
okay,
where
is
1.26,
where's,
1.27
and
so
on,
and
we
have
multiple
views.
C
So
it's
basically
every
cycle,
a
bunch
of
new
views,
also
there
might
be
I'm,
not
sure,
might
be
limits
from
a
GitHub
that
you
only
have
like
maybe
a
thousand
entries
in
a
project
board
and
eventually
we
will
run
out
of
out
of
Records
basically
and
also
we
cannot
have
multiple
caps,
for
example,
in
the
same
project
board.
So
if
you,
for
example,
postpone
an
issue
to
the
next
cycle,
you'll
a
little
bit
lose
the
record
that
you
also
wanted
to
have
it
in
maybe
the
second
before
so.
C
C
Basically,
it's
a
little
bit
cleaner,
so
it's
a
clean
cut,
but
we
need
to
duplicate
the
enhancement
project
board
and
at
the
moment,
there's
no
automation
to
it.
So
we
manually
need
to
click
it
up
or
maybe
build
a
new
tool
to
duplicate
the
project
board.
So
but
I
wanted
to
kick
this
off,
because
this
is
important
for
the
next
release
because
enhancement
starts
before
the
cycle.
Even
so,
we
should
get
this
resolved
hopefully
soon.
D
Hey
so
carrying
forward
the
conversation
that
we
had,
so
there
are
multiple
reasons
we
may
need
to
just
bite
the
bullet
right
now
in
copying
over
things
and
choose
a
new
Port.
The
reason
is:
if
we
look
at
history,
the
enhancements
tracking
spreadsheets
were
also
used,
some
kind
of
an
archive
of
like
what
went
in
a
release.
D
That's
one
thing,
so
we
will
lose
archival
functionality
if
we
continue
using
the
same
project
but
and
I
do
agree
with
your
point
that
thinking
of
the
evolution
of
a
cap,
it
will
be
in
Alpha,
One,
In,
One
release.
It
will
be
in
beta
in
another
and
stable
in
some
other
release.
We
can't
track
that
evaluation
in
the
same
board,
because
the
issue
can
be
there
only
once
the
other
thing
is
even
if
let's
say
we
try
to
archive
in
some
way
history
in
the
same
project
board.
D
D
To
essentially
like
ask
them
like,
what's
in
the
roadmap
and
give
them
feedback
of
what
we
need
and
felt
lacking
in
GitHub
new
projects,
but
I
would
not
really
hope
that
this
would
yield
results
in
the
short
term
and
result
in
anything
for
1.27
or
maybe
even
1.28.
This
will
be
probably
a
six
month
kind
of
timeline
thing
thinking
very
pragmatically
here,
but
just
as
a
point
of
information.
E
D
D
C
D
A
A
All
right
sounds
like
that.
So
sounds
like
we'll
take
that
as
the
action
going
forward,
Luke,
Xander
and
Mark
him
to
that
since
they're,
not
here
cool,
any
other
open
discussion
topics,
otherwise
I'm
inclined.
Oh,
go
ahead.
Those
are
the
topics
of
the
action
item.
Are
we
assign
it
to
anybody
to
take
action
for
review
for
comment?
A
A
A
If
you
have
any
questions
or
comments
or
concerns
feel
free
to
reach
out
on
Sig
release,
slack
Channel
and
good
luck
to
everybody.
That's
cutting
releases
this
week,
it's
going
to
be
exciting
on
Thursday
easy
week
easy
week
busy
week,
go
better
Jeremy
thanks,
I
feel
better.
Okay,
see
you
later
everybody
bye-bye.