►
From YouTube: Kuberentes SIG Release Meeting for 20230606
Description
Kuberentes SIG Release Meeting for 20230606
A
Hi
everyone
welcome
to
the
Tuesday
June
6th
cigar
release.
Meeting.
My
name
is
Jeremy
and
I'll
be
the
host.
Today,
Marco
has
dropped
the
agenda
into
the
chat
if
you
could
go
ahead
and
add
yourself
as
an
attendee.
That
would
be
super
useful.
So
we
have
an
idea
of
who
is
here
and
if
this
is
your
first
time
we'll
invite
you
to
introduce
yourself
and
let
us
know
why
you're
interested
in
Sig
release,
but
before
we
do
that
this
meeting
is
covered
by
the
kubernetes
code
of
conduct.
A
So
please
be
mindful
of
the
things
you
say
and
treat
everybody
with
respect,
and
this
meeting
will
also
be
recorded
and
available
on
YouTube.
So
if
you
don't
want
to
be
on
camera,
those
are
your
warning
to
not
come
off
of
hiding
your
video
all
right
with
that
I'll
open
it
up
for
anyone
to
introduce
themselves
if
you're
new
to
Sig
release-
or
you
haven't
been
here
for
a
while
feel
free
to
unmute
and
introduce
yourself.
A
All
right,
if
anybody
wants
to
introduce
themselves
in
chat,
feel
free
to
do
that
as
well,
and
with
that
we'll
move
on
to
the
recurring
topics
and
we'll
start
with
sub-project
updates
and
the
first
one
up
is
release
engineering
Marco
or
no.
Do
you
wanna
give
any
updates.
I
can
also
give
some
updates
on
what
I'm
working
on.
B
Yeah
I
can
give
you
some
updates
so
from
the
OBS
side,
since
this
is
now
getting
it
a
popular
topic.
We
merge
the
core
implementation
last
week,
so
we
have
OBS
creel
stage,
Adobe
SQL
release
and
we
can
build
it,
publish
all
core
packages
like
qbdf,
cubelet,
Cube,
CTL
and
price
tools
and
kubernetes
cni.
That
part
is
hopefully
working
very
well
from
what
they
tested
and
what
it
was
able
to
test
with
we.
B
After
the
meeting
we
had
last
week,
we
discussed
about
having
Alpha
2
release
this
week
and
we
are
targeting
Thursday
for
that
one
after
we
hopefully
merge
the
goal
updates
that
Jeremy
are
working
on
I.
Think
that
yeah,
let's
see
fingers
crossed
I
hope
it
is
going
to
work.
Besides
that,
we
also
have
in
progress
updating
to
cosine
V2
Carlos
is
mainly
working
on
this
and
it
is
I
think
going
relatively
well.
There
are
some
issues,
but
let's
hope
that
we
will
able
to
solve
that
issues
in
an
easy
way.
C
B
A
Yep
go
updates,
I've
got
the
PRS
open
in
draft
form
and
non-draft
form.
One
of
them
is
waiting
for
the
go
release
to
happen
and
the
Upstream
images
to
be
released
so
that
we
can
use
them
once
that's
done,
we'll
retest,
the
the
first
PR
and
that'll
kind
of
set
off
the
wave
of
everything
that
will
happen
after
that.
A
B
B
Sounds
good.
Thank
you,
I
think,
there's
some
things
that
we
need
to
solve
on
that
side,
especially
when
it
comes
to
cry
tools
and
kubernetes
cni,
and
that's
like
the
biggest
issue
when
it
comes
to
how
we
publish
packages
but
I
think
we
will
figure
it
out
and
we
can
see
about
that.
I
am
on
officially
on
PTO,
so
I
will
be
not
working
for
a
week
or
two,
but
as
soon
as
as
soon
as
I
get
back.
We
can
look
into
this.
D
A
D
Yeah
I
mean
in
123
we
also
had
a
low
number
of
enhancements
very
early
on
as
well
and
I
saw
in
the
notes
from
last
week
that
you've
done
all
them
cons
outs,
reach
out
to
all
to
the
sick
channels
as
well.
I
also
tried
to
join
all
the
Sig
meetings
as
well,
just
to
remind
folks
and
I,
don't
know
if
that
was
helpful
or
not,
but
yeah
we
did
get
a
little
bit
of
a
bump,
but
it
could
just
be
timing,
wise
anyways.
D
E
A
C
A
There
is
currently
a
cve
that
is
flagged
on
on
those
images
when
you
scan
them
related
to
open
SSL,
it's
fixed
in
the
version
that
we
used
in
127,
so
it'll
it'll
be
fixed
in
the
version
we're
going
to
build
with
the
new
Go
versions.
But
how
would
people
feel
about
cherry
picking
that
change
back
to
the
older
release
branches
to
make
before
ahead
of
the
patch
releases,
so
that
we
can,
you
know,
maybe
make
things,
have
a
lower
cve
footprint
for
folks
that
are
consuming
them.
Downstream.
A
D
A
A
We
have
an
enhancement
for
that,
but
I
don't
know
if
anybody
has
worked
on
it
yet
so
I
don't
think.
We've
opted
that
in
as
well
previously
Carlos
was
going
to
work
on
that,
but
I
don't
know
what
the
status
of
that
is.
So
let's
take
it
as
an
action
item
to
Ping
Carlos
and
ask
him
if
he's
still
actively
working
on
that.
Otherwise,
maybe
we
can
find
somebody
that
would
like
to
help
contribute
that.
C
A
All
right,
well,
I,
hope
everybody
has
a
great
rest
of
your
day
or
evening,
depending
on
where
you
are.
If
you
have
any
other
thing,
you'd
like
to
discuss
after
this
meeting
is
over,
feel
free
to
start
a
thread
on
the
secretly
slack
Channel
or
reach
out
to
the
mailing
list
and
we'll
see
everybody
on
the
internet.