►
Description
SIG Cluster Lifecycle - Cluster API Office Hours - 20210623
A
All
right,
this
is
the
kubernetes
cluster
lifecycle
meeting
for
the
cluster
api
subproject
of
23rd
june
2021.
Please
be
aware
that
we
are
fighting
by
the
cncf
conduct,
which
really
means
be
excellent
to
each
other.
If
you
want
to
erase
a
point,
use
the
raised
hand,
signals-
and
please
make
sure
you
put
your
names
in
the
agenda
and
we'll
get
going
start
off
with
a
psas
got
the
first
one
got
version,
zero
point,
four
point:
zero
release
candidate.
Does
someone
wanna
speak
to
that.
B
I
guess
I
can.
I
realized
this
yesterday.
There
was
a
delay
because
some
issues
popped
up
in
controller
runtime,
which
was
then
fixed,
we're
planning
to
bump,
like
at
least
like
another
version
of
control
runtime
before
we
release
zero,
four
zero.
B
That
should
happen
like
today
slash
tomorrow,
but
the
fix
is
like
pretty
minor
and
it
just
unblocks
us
to
use
121.2
for
m
test
to
run
our
integration
tests,
and
hopefully
we
can
actually
do
this
alongside
on
119
and
120
that
we're
doing
that
today
that
could
go
later,
though
it's
like
that's,
not
a
release,
blocker.
I
think
the
biggest
thing
is
to
just
make
make
sure
that
we
use
zero
nine
two
of
controller
runtime.
B
We
haven't
heard
feedback
or
like
regarding
bugs
for
zero.
Four,
like
so
far
some
kind
of
testing
that
I
personally
don't
like.
Actually
one
pretty
smoothly
and
our
grids
are
actually
green,
so
we
should
be
good
to
go
unless
anyone
has
any
objections.
C
Cecilia
yeah,
I
just
pasted
it
in
the
notes,
but
just
in
the
fyi
for
providers
there's
a
new
mock
version
as
part
of
this
update
and
it
causes
some
unit
tests
to
fail.
When
you
had
a
mock
function
that
was
expected,
but
not
being
called
so
some
of
your
unit
tests
might
start
failing.
You
don't
need
to
fix
those.
A
Thanks
any
other
questions
and
once
we'll
move
on
to
the
agenda,
all
right,
we've
got
one
from
joel.
Oh
just
check
the
release
blocking
issues.
Does
that
mind
sharing
the
agenda
because
it's
a
bit
difficult
on
linux.
A
Yeah,
so
we've
got
no
release
blocking
issues
so
we'll
move
on
to
first
one.
So
we've
got
one
from
joel
who's,
not
here
to
the
meeting,
which
is
what
to
do
with
dependable,
so
there's
lots
of
pr's
open
and
quite
a
lot
more
conflict
with
each
other,
and
how
do
we
as
reviewers
know,
which
ones
to
care
about
and
action?
A
I
will
just
briefly
respond
because
I
set
up
the
dependable
initially,
so
we
I've
set
this
up
on
cappy
and
kappa
and
cappy
yeah.
It
did
open
a
lot
of
pr's
that
immediately
failed.
A
Did
some
more
experimenting
on
the
aws
repo
and
have
got
it
such
that
when
dependable
does
prs,
it
will
run,
make
generate,
make
modules
recommit
the
update
and
then
that
can
be
merged.
So
it
should
be
better
going
forward
a
day
if
anyone
else
has
any.
A
There's
nothing
all
right.
Well,
we
don't
have
anything
else
on
the
agenda.
Do
anyone
want
to
do
any
last
minute
topics,
otherwise
we'll
call
it
going
once
going
twice
three
times
all
right?
That's
it!
Oh,
just
one
psa!
We
are
out
we're
doing
a
a
live
stream
on
friday
to
talk
about
bare
metal
with
cluster
api
tinkerbell
if
anyone's
interested
I'll,
throw
a
link
in
there
and
that's
with
jason
from
equinix,
so
if
anyone's
interested.
So
apart
from
that,
I
guess
that's
it.
Nice
short,
shot,
bye,.