►
From YouTube: Kuberentes SIG Release Meeting for 20230627
Description
Kuberentes SIG Release Meeting for 20230627
A
B
Hello,
everyone-
this
is
ronit
Banerjee
like
this
is
my
first
ever
sick
release.
Meeting
I've
never
joined
it,
so
I'm
contributing
to
cncf
and
also
I'm
a
part
of
Google
summer
of
code
at
Wikipedia
Foundation,
so
I
have
been
contributing
to
open
source
and
since,
like
last
year
and
I,
have
also
been
to
conferences
like
open
source,
Summit
Europe
that
was
last
year
situated
in
Dublin
like
that
took
place
at
Dublin.
B
C
A
D
C
D
So
we
last
week,
I
think
we
merged
the
first
changed
to
the
the
test
grade
and
to
the
jobs
to
start
checking.
If
the
job
actually
works,
if
it
can
access
the
Registries
so
just
in
to
give
some
context
to
to
some
of
the
newer
folks
we
having
battling
were
the
last
few
months
or
so
with
rate
limits.
When
signing
the
images
that
we
release,
so
jobs
run,
try
to
sign
them
and
either
because
rate
limits
in
their
gcp
infra
that
the
project
runs
or
I.
Think
you
have
one.
C
D
D
And
not
in
others,
so
to
remediate
that
we
are
building
a
new
job,
that
checks
for
the
images,
consistency,
the
signatures,
consistency
and
eventually
will
also
fix
any
missing
signatures.
So
the
first
stage
is
we
created
the
new
jobs
that
run
every
four
hours.
I
think
check
the
latest,
I
I
think
it's.
They
check
images
going
back
a
few
days,
I
think
it's
five,
and
if
not
it's
supposed
to
report
back
and
right
now,
it
will
never
fail.
D
So
we
can
see
the
output,
but
it
will
never
turn
any
of
the
words
red
so
to
speak,
because
it's
it's
only
meant
to
check
something.
You
have
the
proper
access
and
the
code.
The
code
actually
works
from
from
the
from
the
job,
so
this
one
is
did
work.
So
the
next
step
is
I'm
going
to
change
those
those
jobs
to
ensure
that
if
they
find
anything
they
fail,
they
try
that
and
then
move
into
the
actual
job
to
to
give.
D
So
we
have
been
discussing
in
my
way
it's
mostly
me
whenever
I
find
Carlos
and
slack
or
whatever,
but
this
is
why
I
wanted
to
bring
it
to
the
whole
group.
We've
been
discussing
what
would
be
the
best
way
to
fix
them
like?
Should
we
just
let
the
job
loose
and
fix
it
automatically,
or
we
may
be
thinking
that,
perhaps
starting
with
a
more
controlled
approach,
where
we
merge,
like
a
grown
job,
that
we
can
know
when
it
runs,
and
we
can
observe
to
to
perform
the
signatures,
because
this
actually
utters
a
production
registry.
D
So
we
at
least
in
the
beginning.
We
want
to
be
super
careful
on
what
it
does
and
limit
any
blast
radius
in
case
it
does
something
weird,
but
so
right
now
the
processes,
the
process
and
it's
being
worked
on
to
ensure
that
we
get
signal
whenever
it
finds
inconsistent
signatures
and
then
we'll
go
into
the
fixing
the
phase.
C
A
Thank
you
for
this
update.
Another
thing
you
probably
can
mention
is
that
we
now
assign
everything
with
registry.kates.io,
so
the
stock
reference
the
latest
release
of
K
promo.
We
now
always
use
registry.kids.io
as
the
docker
reference
and
the
signature
so
I
think
Alpha
3
is
the
first
Alpha
release
which
has
this
change,
but
all
this
also
affects
all
other
container
images
which
get
get
promoted
through
kids.io.
A
A
A
Race-
it's
not
going
to
call
so
I
will
probably
read
out
what
we
have
here.
So
we
have
59
tracked
enhancements
out
of
68,
which
is
a
lot
so
I'm,
not
sure
about
the
about
risk.
This
incorporates,
but
it's
the
highest
rate
of
direct
enhancements
that
we've
ever
seen
in
the
kubernetes
release,
and
it
looks
like
that,
starting
from
129,
the
back
triage
team
will
be
merged
into
this
signal
team.
A
So
with
that,
we
are
at
the
end
of
our
agenda.
For
today.
One
thing
I
would
like
to
mention
is
that
the
maintainer
track
sessions
for
kubecon
got
open
and
like,
if
you're
interested,
to
give
a
talk
about
sick
release,
provide
an
update
about
security.
Is
I
want
to
speak
about
any
particular
topic
which
could
be
a
good
fit
for
the
maintenance.
Rack
then
feel
free
to
reach
out
to
to
any
any
of
us
leads,
and
we
can
speak
about
how
you
can
get
this
talk
at
kubecon.