►
From YouTube: Kubernetes SIG Release for 20230530
Description
Kubernetes SIG Release for 20230530
A
Thank
goodness
I
thought
that
my
my
audio
was
was.
A
A
Monday,
too
I
feel
like
everything
or
it's
a
Tuesday,
not
a
month,
all
right.
It's
Monday
yeah,
it's
Monday
for
us.
For
me,
we.
A
A
A
A
E
A
Hey
welcome
nice
to
see
you
folks.
We
have
a
few
different
ways.
You
can
be
involved
in
Sig
release.
The
release
team
is
one
Avenue,
but
we
also
have
a
lot
of
tooling
and
stuff
that
we
maintain
under
the
release
engineering
subproject.
So
hopefully
you
get
to
hear
a
little
bit
of
updates
on
both
of
those
things
and
understand
a
little
bit
more
about
where
you
can
contribute.
A
B
B
That
means
the
crowd
is
up
to
date
to
to
sign
the
blobs
and
binaries
with
the
cosine
V2
and
currently
I'm
working
on
the
promo
tools
to
upgrade
that
that
is
a
failure
in
the
end-to-end
testing
I'm
trying
to
fix
that
but
looks
like
today.
The
AKs
Pro
cluster
is
not
happy
or
something
is
not
not
going
good,
because
none
of
the
jobs
that
uses
that
cluster
is
running
at
least
the
ones
I'm
trying
to
Grant.
B
F
Yeah
as
far
as
another
cluster
is
okay
in
the
classes
that
we
have
problem
is
the
gke
cluster,
because
that
one
is
again
having
problem
without
education.
Just
like
we
had
the
last
time.
There's
an
issue
open
on
GitHub
been
testing
for
raffle
I
will
share
it
on
link,
but
it
indeed
this
there's
some
problem.
F
I
tried
migrating
some
job
today
from
game
release
to
eks
on
a
cluster
on
ABS,
but
they
didn't
work
because
that's
different
stock,
none
of
the
jobs
are
passing
on
gke
and
it's
not
possible
to
migrate
anything
okay.
A
Oh
apologies:
any
questions
for
the
release
engineering
team.
We
have
specific
updates
on
the
OBS
stuff
in
the
open
discussion,
so
we
can
hold
anything
there
until
Marco
takes
that
for
us.
G
G
G
Cool
and
then
we
are
planning
for
our
first
cut
today,
there's
a
fail
test
that
has
to
do
with
sick,
Windows
SO
waiting
for
them
to
clear
that
and
then
we're
not
just
gonna
execute
the
cut
so
so
waiting
for
sick
windows
on
that
and
then
Buck
triage
and
CI
signal
is
going
to
merge
for
1.29.
We
are
starting
a
docs
update
right
now
with
the
handbook,
but
we
don't
have
an
official
name
for
that
merge
team.
F
Yes,
I
have
a
question:
I
could
be
looking
at
the
release
calendar
and
as
far
as
I
say,
we
have
Alpha
release
coming
out
today
and
we
have
Alpha
2
release
coming
out
to
Tuesday
June
10th,
which
is
20
days
from
now.
I
wanted
to
kindly
ask
this
is
related
to
the
OBS
update
that
we
have
later
on
if
it
is
possible
to
fit
in
one
more
Alpha
release,
maybe
next
week
or
we
can
call
so
that
we
give
OBS
a
try
so
that
we
try
to
build
up
a
release.
G
F
Okay,
I'm
also
happy
to
try
the
release
myself.
Is
that
any
concern?
I
will
anyways
be
there
to
monitor
this
talk,
because
that
will
be
the
first
release
where
we
actually
use
OBS
so
yeah,
but
I
wanted
to
bring
it
up
as
a
possibility,
because
we
were
not
able
to
get
it
ready
for
today,
but
I
think
that
it
should
be
ready
this
week.
So
we
can
do
maybe
next
week,
probably
two
weeks
as
we
do
another
Alpha.
A
G
F
A
Release
cut
Mark
Rossetti
is
Shadow
Eden
him
this
time.
A
All
right,
thanks
Marco,
that
was
a
good
good
question
to
bring
up
all
right
and
since
you
just
spoke
about
OBS,
do
you
mind
giving
us
some
updates
on
on
how
OBS
is
going.
F
Yeah
sure
so
I
would
first
like
to
start
with
a
kindly
asked
for
stickerless
leads.
If
you
can,
please
opt
in
the
enchantment
that
we
have
for
OBS
because
it
got
removed
when
127
cycle
ended,
so
it
will
be
nice
to
obtain
again.
That's
the
first
thing.
The
second
thing
about
General
progress
is
that
it
is
effective
going
very
well
what
we
did
so
far
and
what
is
done
it
already
merged
is
that
we
have
crowd
OBS
specs
command.
That
is
basically
taking
care.
F
You're
providing
the
package
you
provided
the
like.
What
version
do
you
want
from
there
to
download
that
it
is
going
like
to
build
the
package
specs
and
to
create
an
archive
that
has
all
the
binaries
that
is
needed
by
OBS
to
build
the
package?
This
is
completely
done.
There
was
some
minor
refactor
going
on,
lastly,
kind
of
plastic
to
make
this
code
possible
to
test
and
I
think
that
Sasha
and
Carlos
approved
the
pr.
F
So
it
is
only
stuck
in
merge
queue
because
that
gke
brow
cluster
is
not
working,
so
tests
are
pending,
but
as
soon
as
that
is
sold,
DPR
should
be
matched.
This
is
speaking
of
done
part,
the
part
that
is
in
progress,
but
most
of
that
it
is
scroll,
OBS
stage
at
creel,
OBS
release.
Those
documents
are
basically
going
to
be
integrated
in
existing
crowd
stage.
You
can
release
workflows
and
they're,
going
to
take
care
of
basically
releasing
packages
and
I
actually
possibly
release
packages
PLC
channel.
F
That
is
how
that
looks
like
I,
can
share
logs
in
chat
as
well
quickly.
This
is
basically
how
it
is
going
to
look
like
now.
This
link
can
only
be
accessed
by
release
managers,
but
it
looks
like
that
there
is
one
more
Step
at
the
end
that
is
basically
taking
care
of
realistic
packages
and
actually
I
tried
the
wall
workflow,
which
can
be
seen
on
128
build.
Let
me
share
some
more
projects,
so
this
is
build
project,
and
this
is
the
release
project
where
you
can
actually
install
stuff
from.
F
It
is
basically
the
devil
if
it
works
and
that
packages
are
built
successfully
that
we
actually
have
a
tooling
project.
Now.
Two
imported
parts
that
are
coming
up
is
testing
and
tooling
to
manage
projects
and
packages
and
waiting
for
builds
like
this
is
another
thing
that
is
in
the
project.
F
Work
started
working
with
tooling
that
we
manage
projects
in
a
similar
way,
for
example,
how
we
manage
other
stuff
via
yaml
files,
but
that
might
take
some
time
because
I'm
planning
to
go
on
vacation
next
week,
I
mean
not
really
allocation,
but
yeah
and
I
will
try
to.
It
will
probably
suffer
in
tune
than
with
that.
But
what
I
said
earlier,
I
believe
if
we
get
to
merge,
for
example,
OBS
stage
aquarium
OBS
release
this
week
or
next
week.
F
After
that,
we
can
do
another
Alpha
see
if
it
is
going
to
work
and
if
it
is
going
to
work,
you
basically
have
the
core
implementation
to
be
adapted,
something
that
I'm
looking
for
feedback,
and
that
says,
there's
a
few
of
us
who
can
provide
such
feedback.
E
F
And
that
I
added
with
PRS,
so
that
we
actually
make
sure
that
it
is
functional.
The
other
tests
that
I
planned
is
a
very
simple
rundock
equity
and
you
try
to
install
packages
if
it
works,
it
works
if
it
doesn't
yeah.
Okay,
but
now
this
is
a
bit
new.
I
was
thinking
about
adding
a
third
type
of
test.
That's
got
more
going
to
be
on
the
fat
test
that
is
actually
going
to
provision
a
cluster
use
those
packages
for
provisioning,
a
cluster
so
that
we
pull
from
OBS.
F
F
Now
that
part
about
third
test
is
something
that
I'm
not
sure
how
to
do,
because
the
way
I
was
how
I'm
testing
it
right
now
is
that
I
use
a
tool
that
we
did,
that
we
made
it
kibramatic,
that's
basically
bringing
the
cluster
up
over
an
SSH
like
you
provide
distances
you
create,
for
example,
on
abs,
and
you
create
these
this
and
it
brings
up
like
uses
the
package
system,
server,
Secrets
test
and
so
on
and
I
thought
about
informatics.
Something
like
that,
maybe
even
using
that
tool.
F
D
E
F
D
G
F
A
F
F
D
I
mean
so
I
think
one
of
the
things
that
we
need
to
think
better
is
what
we
want
to
put
on
the
GitHub
release
pages
people
I
feel
that
folks
usually
expect
the
artifacts
to
be
there
and
before
coupon,
lasts
in
before
Amsterdam
I
was
discussing
with
Carlos
that
maybe
we
should
start
thinking
on
how
I
secure
process
to
move
well,
not
to
move,
but
to
replicate
things
that
we
have
released
can
make
their
way
to
those
GitHub
release
pages.
D
So
I
think
it
would
be
I
mean
we
could
start
thinking
on
how
I
have
good
kubernetes
release
would
look
like
on
those
GitHub
Pages
just
because
people
expect
them
to
be
there
like
just
as
a
mirror
of
the
official
release
locations.
But
I,
don't
know
if
people
have
expectations
to
find
stuff
in
there.
Maybe
we
should
react.
Maybe
asking
the
community
would
be
a
good
idea,
but
the
the
what
whatever
we
decide.
D
We
need
to
think
first
on
how
we,
because
right
now,
we
that
double
we
just
copied
from
Krill
over
there
and
then
but
then
maybe
we
should
think
on
ways.
If
we,
if
all
of
the
communities
releasing
to
the
buckets,
then
maybe
providing
the
whole
community
of
a
way
to
safely
move
authenticated
artifacts
over.
There
would
be
a
good
idea.
F
I
have
to
agree
with
that
I
mean
at
least
if
you
can't
move
artifacts.
Even
if
I
like
extend
to
read
me
and
point
to
stuff
like
where
you
can
better
navigate,
the
stuff
might
be
helpful,
but
I.
Don't
think
that
is
a
block
here
for
the
pr
that
you
mentioned
before,
like
I,
think
dropping
turbo
should
be
fine
because
it
was
announced
that
I
don't
think
it's
going
to
break
anyone,
hopefully
not.
D
I,
don't
I
mean
I
I've
been
asking
both
in
meetings
and
since
you've
gone,
I
mean
well
not
recently,
but
I
don't
know
about
a
year
ago.
If
anybody
depends
on
that
turbo
and
no
one
seems
to
know
anybody
or
its
main
purpose,
because
it's
not
a
it's,
not
a
source
code.
Really
it
it's
a
source
code,
but
a
bunch
of
manifests
so
yeah.
Maybe
we
can
just
drop
it
and
see
and
see
if
anybody
reacts,
but
we
we
have
a
prayer.
D
We've
had
the
beer
open
for
a
while
and
and
without
any
comments,
so
yeah,
I,
I,
yeah
I
claim
responsibility
for
renaming
that
thing
to
kubernetes
source
code.
Just
because
I
assumed
it
was
a
social,
but
it
turns
out
it
wasn't
just
the
label
on
the
thing
when
we
rewrote
Grill
but
yeah
I
mean
we
should
definitely
do
away
with
it.
If
no
one
knows
what
it's
for.
A
Make
it
so
all
right,
I
had
two
quick
ones
to
put
on
the
agenda
today:
I'm
gonna
regenerate
the
zoom
links
after
this
meeting
is
done.
I
try
to
start
doing
it
on
Friday,
but
I
couldn't
get
into
one
password,
because
one
password
is
actually
hard
to
log
into
if
you
haven't
logged
into
it.
In
a.
B
C
A
My
offline
backups
were
super
secure,
so
I
got
into
one
password
this
morning,
so
I'll
be
able
to
regenerate
stuff
so
be
on
the
lookout
for
that
Grace
I'll
send
you
host
codes
for
the
the
release
meeting
and
then
I'll
update
all
the
invites,
because
I
have
calendar
access
too,
just
as
an
FYI.
A
Please
don't
share
links
to
zoom
meetings
with
passwords
in
them
on
Twitter,
because
things
get
scraped,
I
think
we've
been
pretty
lucky
like
nobody,
Zoom
bombed
us,
but
in
the
in
the
old
times
like
in
2021
2020,
it
was.
It
was
real,
real
uncomfortable
for
a
little
while
with
people
Zoom
bombing
and
doing
bad
things.
A
My
second
topic,
I
opened
a
PR
a
little
while
ago
to
reconstitute
the
LTS
working
group
looks
like
it's
got
approvals
from
most
of
the
sigs
that
we
identified
as
immediately
responsible
like
every
Sig
could
potentially
be
responsible
or
impacted,
but
Jordan
and
Micah
and
I
kind
of
narrowed
it
down
to
a
small,
smaller
still
pretty
large.
It's
like
a
lot
of
cigs
that
are
no
matter
which
direction
that
goes.
If
anything
goes
like
those
things
will
be
impacted.
A
Other
cigs
are
potentially
impacted,
so
the
last
two
that
I
think
we
need
approval
from
and
I
think
dim
is
approved,
but
hasn't
approved
is
sick
release.
So
if,
if
Sasha
Veronica
Carlos
Adolfo,
if
you
could
take
a
look
at
that
and
provide
any
comments
or
feedback
that
would
be
most
appreciated.
A
E
E
Him
in
creating
a
PR
in
this
case.
A
I
think
Jim
is
here
Jim.
Do
you
wanna
speak
to
that.
C
E
A
Sorry
I
was
saying
that
brings
us
through
the
rest
of
our
agenda,
so
we'll
go
ahead
and
call
it
a
meeting
unless
anybody
has
any
really
quick
topics.
You'd
like
to
go
through
all
right
sounds
good,
be
on
lookout
for
updated,
Zoom
links
shortly.