►
From YouTube: Kubernetes SIG Cluster Lifecycle 20180502 - Cluster API
Description
Meeting Notes: https://docs.google.com/document/d/16ils69KImmE94RlmzjWDrkmFZysgB2J4lGnYMRN89WM/edit#heading=h.pwt481usyw83
This was a short meeting due to many folks attending KubeCon EU this week.
Topics:
- Cascading deletes of machines
- Status of MachineDeployment controller
- ProviderStatus on machines
- Status of migration to the cluster-api repository
A
C
A
Well,
can
other
people
give
like
a
thumbs-up
thumbs-down
whether
they
can
hear
Devon?
Okay,
so
be
interesting
to
see
if
the
recording
can
hear
you.
B
Are
we're
starting
to
get
a
position
where
we
can
start
using
this
API
a
bunch
more?
We
had
kind
of
our
API
and
we're
trying
to
pivot
to
the
API
working
on
here.
I
think
we're
getting
closer
to
that.
So
we're
starting
to
have
a
lot
of
questions,
and
hopefully
we
can
help
out
a
little
bit.
What
a
couple
of
things
that
we
wanted
to
ask
initially,
were
we.
B
We
noticed
that
it
seems
that
deleting
a
machine
set
today,
the
machines
that
belong
to
that
machine
set
remain,
and
we
were
wondering
if
that
is
intentional.
It
was
kind
of
contrary
to
what
we
would
have
expected.
We
would
have
thought
if
you
delete
your
machine
set,
the
the
machines
would
get
cleaned
up
and
it
seems
like
that
might
come
into
play
when
we
start
dealing
with
machine
deployments.
So
we
were
wondering
if
that
would
be
a
reasonable
change
to
put
in.
E
Also
expect
that
didn't
she
deployment
sets
with
deleted
machines
when
there's
deleted.
Unless,
like
explicitly
stated,
it
should
be
an
option
on
the
machine
set
like
just
like.
We
have
it
on
Damon
sets
and
deployments
or,
like
you,
don't
delete
your
children.
I
would
assume
that
you
would
have
some
option
like
that,
and
machine
deployments
actually
does
rely
on
machine
said,
deleting
the
machines
under
underneath.
So
the
machine
deployment
controllers
is
work
in
progress
and
we
hope
to
send
it
out
review
this
week.
B
E
D
D
F
E
B
This
ok,
so
what
one
will
do?
Maybe
we'll
try
and
poke
around
that
on
our
side.
If
anybody
does
have
anything
in
progress,
just
let
us
know
on
slack
and
and
we'll
stop,
but
if
not
we'll
see
if
we
can
maybe
get
that
added.
Do
you
mind
opening
go
would
get
her
by
shape
so
that
we
can
track
sure.
Absolutely
that's
it.
Yeah
yeah.
D
C
C
The
other
question
I
had
related
to
that
is
that,
right
now,
the
provider
specific
status
own
clusters
is
just
a
strainer,
be
it
things
like
following
the
pattern
the
provider
can
take.
It
should
be
a
long
extension
or
or
structured.
That
includes
a
long
extension
so
that
we
can
restore
proper
struct
there.
Any
thoughts
on
that.
F
F
C
D
Okay,
I
think
the
next
one
on
the
item
on
the
agenda
is,
is
around
just
logistics
on
the
repo,
so
Chris
Nova
sent
sent
out
a
PR
just
a
couple
of
days
back
then,
which
will
remove
the
code
from
Q
to
play
and,
and
everything
has
been
migrated
and
I
was
successfully
to
cluster
API
I.
Think
there's
nothing
missing
earth,
so
I,
don't
know
if
or
crease
others
don't
have
any
any
any
updates
but
other
otherwise.
You
know
that
should
be
the
new
repo
dunno
point
forward.
So,
oh
she
would
they
playing
more.