►
From YouTube: 20200923 - Cluster API Office Hours
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
All
right,
hello
and
welcome
to
the
wednesday
september
23rd
edition
of
the
cluster
api
office
hours.
Cluster
api
is
a
sub-project
of
both
sig
cluster
lifecycle
and
cluster
api
itself.
This
isn't
the
aws
one.
So
if
you
are
attending,
please
remember
to
use
the
raise
hand
feature
if
you
are
not.
A
B
Thanks
jason
yeah,
the
first
one
is
just
the
rc040310,
no
zero,
three
zero
that
has
been
released
and
yeah.
B
If
you
have
time
to
test
it
out
like
there's
a
lot
of
bug
fixes,
especially
for
the
memory
leak
that
we
discovered
like,
I
think
like
it
was
a
week
and
a
half
ago,
so
yeah,
it's
there's
no
release
notes
in
the
release,
but
there
is
definitely
the
artifacts
and
the
images
have
also
been
published
into
our
production
pocket
feel
free
to
test
it
out
and
open
and
file
any
bugs
if
there
are
any
we're
targeting
to
potentially
cut
the
final
release.
B
All
right
I'll
keep
going
on
the
for
alpha
4
like
I
wanted
to
propose
to
do
a
planning
session
during
this
meeting
next
week,
so
september,
30th
just
before
we
start
with
the
month
of
october.
One
ask
is
to
if
you
have
any
anything
that
you
would
like
to
work
on,
or
they
will
have
to
propose
either
open
issues
or
like
a
pr
to
the
roadmap.
B
We
like,
as
vmware,
will
work
internally
first
to
kind
of
like
see
what's
top
priority
for
us,
but
this
should
be
a
collaborative
effort
like
with
the
whole
community.
So
if
you
have
anything
that's
top
of
mind,
I
would
suggest
to
bring
it
up
to
the
next
meeting
and
then
we
can
kind
of
agree
on
high
level
items
first
and
then
use
the
month
of
october
to
start
like
filing
caps
or
rfes
and
re
reviewing
them
this.
B
Usually,
this
process
usually
takes
like
four
to
five
weeks
or
something
in
some
case,
like
a
little
bit
more
but
yeah
like
we're
gonna
use
the
month
of
october,
starting
october
1st.
We
also
start
doing
kind
of
like
the
chores
to
allow
for
alpha
4
to
happen.
For
example,
like
adding
the
new
types
revving,
the
api
version,
converting
the
conversion
web
books
and
removing
the
alpha
2
types
so
we'll
drop,
we
officially
drop
support
for
alpha
2..
B
The
tentative
date
like
I
actually
didn't
have
a
good
idea,
but
I
want
to
say,
like
start
of
march
2021,
we
for
zero
four
zero,
but
that's
just
like
kind
of
like
a
ballpark
like
so
it's
somewhere
in
q1
2021
next
year.
We're
kind
of
aiming
to.
A
A
C
Thanks,
I
just
had
to
find
the
button
there
yeah
vince,
I'm
just
curious,
if
maybe
about
the
time
frame
for
v1
alpha
4,
because
I'm
trying
I'm
trying
to
think
about
planning
for
some
of
the
scale
from
zero
work.
We
want
to
do,
and
you
know
we'd
like
to
make
a
proposal
to
change
the
crd
and
v1
alpha
4..
So
I'm
just
kind
of
curious.
What
what
are
we
looking
at
as
kind
of
the
bounding
box
for
when
that
work
should
be
completed
so
that
we
can
get
it
planned
properly?.
C
B
So
I
would
hope
for
the
month
of
october,
so
four
weeks
to
kind
of
like
either
write
and
review,
that's
really
tight,
usually
like
it
takes
much
more
than
that.
But
if
we
give
like
us
like,
maybe
a
couple
of
weeks
more
like
going
into
november,
we
can
start
working
on
some
parts
of
the
proposals
that
like
will
potentially
merge
first
and
keep
reviewing
other
ones
like
along
the
way.
So
that's
a
good
point
like
I
also
have
thought
like.
B
Maybe
we
can
just
say
like
by
november
15th
like
if
the
problems
have
not
merged
like
we
gonna
like
wait
for
those
like
into
the
next
version
or
like
potentially
make
them
in
a
patch
version
for
zero
four,
but
that's
something
we'll
have
to
decide
together
in
terms
of
code,
like
I
mean,
usually
it's
probably
like.
If
we're
doing
the
end
of
q1
like
I
want
to
say
two
weeks
or
three
weeks
before
march
1st,
I
think
or
march
1st.
I
don't
know
yeah
something
like
that.
A
All
right
going
back
to
the
discussion
topics,
it
looks
like
the
first
one
is,
you
might
for
the
auto
scaler
scale
from
zero.
C
Yeah,
this
should
be
a
really
quick
update.
I
wanted
to
thank
andy
and
mike
gugino
for
putting
a
lot
of
comments
into
that
pr.
I
I'm
still
trying
to
catch
up
technically
with
where
some
of
those
things
need
to
be,
and
I'd
like
to
update
that
proposal.
That's
probably
what
I'm
going
to
be
working
on.
I
just
wanted
to
let
everybody
know
that
you
know
I
I
haven't
stopped
looking
at
it,
I'm
just
trying
to
catch
up
technically
with
the
conversation
that
andy
and
mike
were
having.
A
All
right,
then,
moving
along
fabrizio
kcp
remediation
proposal.
D
This
work-
and
I
just
keep
resuming
the
work
and
put
in
in
in
shape
for
the
amending
the
proposal
and
also
to
the
death
that
that
are
helping
and
the
main
tfdr,
is
that
with
the
final
process
for
remediation,
the
remediation
with
follow-up,
failing
node
and
replaced
with
a
new
earthly
one,
because
deleting
a
node
is
the
suggested
approach
in
order
to
make
the
to
preserve
the
tcd
forum
or
not
to
create
more
risk
for
the
fcc
forum.
Everything
is
documented
in
the
proposal.
D
E
Hi,
so
thanks
to
everybody
that
reviewed
the
windows
proposal,
there's
a
flurry
of
updates
yesterday
I'll
be
addressing
them
all
today
and
I
also
opened
up
a
pr
for
the
vhd
and
image
builder.
I'm
not
sure
if
that's
actually
should
be
brought
up
at
this
meeting,
but
just
wanted
to
it's
kind
of
as
part
of
the
windows
proposal
started
some
of
that
work.
So
please
take
a
look
if
you're
interested
in
that
side
of
things
and
thanks
to
the
people
who
gave
some
reviews
yesterday.
A
All
right
that
actually
brings
us
to
the
end
of
our
current
agenda.
Does
anybody
else
have
any
questions,
comments
or
concerns.
A
All
right,
if
not
it
looks
like
it's
going
to
be
a
quick
meeting
today.
So
thank
you
all
very
much
and
we
will
see
you
next
week.