►
From YouTube: SIG Cluster Lifecycle - Cluster API 21-02-10
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
okay,
great
welcome
everybody
today
is
wednesday,
the
10th
of
february
2021-
and
this
is
the
cluster
api
project
meeting.
We
are
following
the
kubernetes
community
standards
for
this
meeting,
so
please
be
kind
to
your
fellows
and
treat
people
as
you
would
be
expected
if
you'd
like
to
speak,
please
use
the
raise
hand
functionality
and
with
that,
let's,
let's
get
things
rolling,
so
we
have
a
couple
of
psas
to
begin
with
vince.
Why
don't
you
take
it
away.
B
Thank
you
yeah.
The
first
one
is
to
try
to
find
some
free
states
for
the
proposals,
so
that,
like
will
come
in
and
they're
also
like,
are
in
flight,
so
for
a
tentative
release.
Days
like
where
we're
trying
to
propose
like
for
zero,
four
zero
to
be
april
15th.
B
This
gives
us
like
around
two
months
of
work
time
to
get
everything
that's
like
in
that.
We
need
to
do
it
like
in
terms
of
breaking
changes,
but
for
breaking
changes.
Proposals
like
we
were.
We
would
have
to
need
them
by
february
2
and
22nd,
and
this
would
give
enough
time
to
reviewers
to
kind
of
like
review
them
async
and,
at
the
same
time,
to
kind
of
have
like
at
least
like
a
month
of
work.
B
On
actual,
you
know,
implementation
wise
for
these
proposals
for
new
features
proposals
instead,
like
we're
trying
to
freeze
by
march
14th
and
all
of
the
proposals,
should
be
at
least
like,
maybe
just
like
open
fpr
with
the
proposal
that
they
don't
have
to
be
emerged.
I
would
say
by
them
at
least
that's
what
we
did
for
alpha
3.,
but
it's
more
to
get
an
idea
and
like
what
we
would
accept
in
zero
for
x
in
terms
of
new
features.
There
are
now
breaking
changes.
B
B
A
All
right,
cecile,
you
got
your
hand
raised.
C
Yeah
something
else
that
someone
had
mentioned
when
we
were
talking
about
the
since,
like
I
think
it
might
have
been
you
actually
michael,
was
or
maybe
it
was
worn
about,
defining
which
features
were
p0
or
which,
which,
which
things
we
had
in
the
milestone
right
now,
which
we
consider
p0
that
have
to
get
done
for
view
on
that
before
and
that
we
want
to
track.
So
we
should
define
what
that
is
exactly
and
yeah.
So
we
can
keep
track
of
like
if
we're
on
target
or,
if
we're
behind,
on
those.
A
All
right,
I
guess
any
other
questions
or
comments
around
this.
If
there's
enhancements
people
are
curious
about
or
features
you
know,
please
go
review
them
and
yeah.
I
guess
with
that
warren.
Do
you
want
to
take
the
next
one.
D
Yeah,
so
I
wanted
to
give
an
update
it's
more
of
a
broader
update,
though
I
want
to
sort
of
announce
to
the
community
that
this
is
actually
my
last
week
at
vmware
and
I'm
sort
of
moving
on
to
other
things,
and
with
that
said,
how
is
this
going
to
affect
the
community?
D
That's
basically,
the
fact
that
I
was
working
on
the
capi
operator
cap
and
at
the
moment
I
am
unable
to
lead
that
effort
and,
coincidentally
also
vmware's
priorities
have
changed
a
little
bit
and
hence
there's
not
going
to
be
any
sort
of
full
staff
member
to
be
working
on
this
proposal
moving
forward.
D
My
ask
has
sort
of
changed
a
little
bit
and
to
see
if
there's
anybody
who
would
want
to
sort
of
lead
the
and
shepherd
the
cappy
operator
cap
to
completion
and
if
there's
anybody
there
feel
free
to
reach
out
to
me
and
all
of
the
work
I've
done
so
far
is
been
in
the
open.
I
can
sort
of
add
more
context
to
that
and
because
I'll
add
more
color
to
make
that
transition
possible.
D
The
other
point
is,
of
course,
regarding
vince's
previous
point
about
the
tentative
release
dates
for
we
went
off
of
four
depending
on.
I
will
work,
obviously
with
the
maintainers,
but
depending
on
the
timeline,
if
you
can
get
this
with
in
v1,
alpha
4
that'd
be
great,
but
otherwise
I'll
be
sort
of
making
a
pr
to
remove
it
from
the
v1
alpha
4
roadmap.
If
we
see
that's
the
right
thing
to
do,
yep
and
yeah.
D
Another
point
is
it's
been
great
working
with
all
of
you.
I've
learned
a
lot
from
the
community
and
it's
my
first
sort
of
open
source
community
group
that
I
worked
with.
So
thank
you,
for
you
know,
being
kind
to
me
and
helping
me
along
the
way.
A
Well,
that's
that's
a
lot
to
take
in
warren,
but
I
guess
congratulations.
I
hope
your
new
adventure
is
exciting
and
and
yeah
you've
made
a
tremendous
impact
here.
I
know
like
personally,
you
know
you've
helped
me
out
a
number
of
times
so
yeah
thank
you
and
I
guess
to
everybody
listening.
If,
if
there
are
people
who
are
interested
in
this
cappy
operator,
work,
please
reach
out
to
warren
slack
or
email
or
whatever
works,
and
I
don't
know,
are
you
gonna
leave
a
comment
on
the
on
the
work?
D
Yes,
I'll
put
in
I'll
add
all
the
links
essentially
from
in
the
last
meetings
notes.
I
added
a
hack
d
sort
of
link
in
there,
where
I
sort
of
broken
the
work
up
into
stories
into
like
smaller
bite-sized
chunks
that
I've
sort
of
pulled
out
from
the
proposal.
D
But
again
that
is
just
my
thought
process.
Whoever
you
know
is
willing
to
take
this
work
on
moving
forward,
feel
free
to
you
know.
Do
it
your
way,
I'm
happy
to
give
context
on
the
proposal.
I
have
three
draft
prs,
a
pr
mode,
I'm
happy
good
old.
D
Otherwise,
you
know
just
gonna
close
the
odd
and
you
know
we're
going
to
leave
over.
A
Okay,
great,
you
know
thanks
and
yeah.
Thanks
for
all
your
contributions,
warren
it's
been.
It's
been
amazing,
all
right,
so
we'll
move
on
to
discussion
topics
unless
anyone
wanted
to
add
on
to
what
warren
was
talking
about.
Hopefully
my
dog
won't
bark
too
much
so
first
discussion
topic
is
from
me
and
this
is
just
kind
of
a
follow-up.
A
From
last
week
we
had
discussed
the
universal
or
the
universal
base,
image
for
red
hat
linux
as
a
possible
option
to
use
with
capd,
and
I
noticed
we,
we
merged
the
change
to
switch
it
to
debian,
but
you
know
I
hopefully
we
could
set
up.
A
Maybe,
like
a
you
know,
alternate
testing
as
well
or
I
don't
know,
but
I
did
follow
up
with
our
legal
and
as
far
as
as
the
user
end
user
agreement
goes,
it
should
be
no
different
than
any
other
linux
that
we
choose
to
use
so
debian
ubuntu
anything
along
those
lines.
The
ubi
image
follows
the
same.
You
know
language,
I
guess
for
its
end
user
agreement.
So
what
I've
been
told
is
the
only
thing
that
we
would
ever
run.
Afoul
of
sorry.
A
A
And
if
there's
no
questions
or
comments,
hand
it
off
to
fabrizio
for
the
next
topic.
E
Yeah,
thank
you
mike.
So
a
quick
topic
so
in
copy
recently
yesterday
or
today
merge
the
pr
which
is
basically
starting
to
use
search
manager,
v1.1.
A
Okay,
I
guess
any
questions
or
comments
for
fabrizio.
A
I'm
not
seeing
any
hands
we're
out
of
topics
at
this
point,
so
if
anybody
had
a
kind
of
last
minute
topic,
they
wanted
to
bring
up
or
some
sort
of
ad
hoc
statement
they'd
like
to
make
to
the
group
now
is
the.
A
C
Socio,
you
got
your
hand
raised
yeah,
just
a
quick
question
to
go
back
to
the
proposal.
Freeze.
Can
we
post
about
it
in
slack
to
give
a
chance
to
anyone
who
wasn't
in
this
meeting
to
react
and
potentially
object
and
maybe
give
it
like
a
one
week,
lazy
consensus
or
something
like
that?
Does
that
sound
good.
B
C
A
All
right,
I
guess
well,
if,
if
there's
nothing
else,
we
all
get
to
have
a
bunch
of
time
back
today,.