►
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
Cool
well
good
evening,
good
day,
welcome
to
the
cluster
api
provider
aws
office
hours
on
monday,
the
29th
of
november
2021
a
reminder
that
we
abide
by
the
cncf
code
of
conduct,
so
please
be
kind
to
each
other.
I've
just
shared
the
meeting
notes
by
the
window,
they're
also
on
the
on
the
meeting,
and
I
should
add
them
into
the
chat
window
as
well.
A
So
let
me
do
that
now
I'll,
do
it
in
a
minute.
So
if
you
want
to
talk,
please
use
the
raise
hand
feature,
and
if
this
is
your
first
meeting,
let's
have
a
look
at
the
list
of
attendees
feel
free
to
unmute
yourself
now
and
just
say
hello,
you
know:
what's
your
interest
in
cluster
api
provider
aws
give
you
a
few
minutes
to
do
that.
If
you
want
to.
A
A
Cool
okay,
we'll
carry
on
so
there
are
looking
at
the
agenda,
it's
quite
like
on
on
agenda
items
today.
So
it's
a
good
week
for
me
to
pick
to
do
so.
There's
no!
No
psas!
This
week,
although
we
say
oh,
there
is
sorry.
Okay,
I'm
ready
I'll
written
the
other
bit,
so
we
did
actually
release
v
1.1
and
the
0.72
about
a
week
and
a
half
ago
with
some
changes
and
some
bug
fixes.
A
In
there
we
delayed
the
the
zero
610
release
at
the
time,
because
there
is
a
bug,
pks
bug
with
add-ons
was.
I
was
struggling
to
get
merged
in
in
time.
So
so
those
are
the
two
releases.
There
will
be
another
one
coming
so
moving
on
to
the
action
items
today
from
well
from
last
week,
so
siddif,
I
see
you
put
a
across
against
building
flat
the
flat
car
images.
Do
you
want
to
say
anything
about
that.
B
A
Cool,
that's
good,
yeah
I'll
see
some
thumbs
up
there,
so
cool
and
as
with
you
again,
sid
f
on
the
the
next
action
item.
A
Yeah,
okay,
yeah
yeah-
I
guess
the
other
one
is.
The
action
item
is
on
the
still
the
v1
alpha
yeah,
but
yeah
later
on,
alpha
3..
So
the
next
one
is
with
me.
So
I
was
I
meant
to
do
some
updates
to
the
ipv6
stroke.
Dual
stack
document.
I
haven't
done
those
to
be
honest,
but
I
have
got
a
whole
bunch
of
other
notes.
I
need
to
add
so
we've
been
doing
a
bunch
of
work
in
this
in
this
area
as
well.
A
So
there's
a
lot
more
learnings
to
add
to
that
document.
So
I
will
I've
already
added
that
to
an
action
item
and
I
will
make
sure
that's
done
before
the
the
next
call
in
two
weeks
time
cool.
So
moving
on
to
the
actual
agenda
items
so
steph
did
you
want
to
take
that
one
on
zero,
six,
ten.
B
Sure
you
already
summarized
we
are
waiting
on
a
buck
fix
after
after
that
is
in.
We
are
gonna,
make
a
release
soon
and
the
next
one
is.
I
just
wanted
to
remind
everyone
that
we
are
collecting
some
features
to
create
a
roadmap
feel
free
to
add
the
features
that
you
want
to
see
in
the
upcoming
releases,
to
the
discussion,
topics,
yeah
and
and
the
third
one
is
a
keep
contact.
B
A
I
guess
on
that
topic
is:
are
there
any
talks
from
any
of
the
other
providers
or
just
a
general
cluster
api
talk
proposed
by
anyone?
Gonna
do.
C
I
suspect
maybe
they
bring
your
own
host,
I'm
not
sure.
Really,
I
don't
think
so.
I
ain't
mad
or
maybe
so
it
might
be
something
from
the
corner
cluster
class
stuff,
but
we
don't
have
anything
novel
to
show.
I
don't
think
something'd
be
a
struggle
to
get
get
a
talking
at
this
stage.
I
think.
A
Cool
fair
enough
and
then
just
on
that
so
def,
one
of
your
points
on
the
on
the
roadmap
for
the
discussion
points
I've
just
added
some
from
an
eks
point
of
view.
A
So
I
I
had
a
call
with
richard
chen
datadog
last
week
and
they're
going
to
be
adopting
capra
in
you
know,
potentially
in
a
big
way,
and
so
we
talked
about
priorities
and
stuff
like
that,
just
with
some
of
the
stuff
that
I
you
know,
I
guess
from
from
a
weaver's
point
of
view
as
well
and
there's
quite
a
lot
of
synergy
there.
So
I
started
to
correlate
that
into
this
or
or
group
those
into
this.
This
issue
that
steph
mentioned.
A
Cool
so
tillo
you're
up
next.
D
Yeah,
just
just
a
short
one
and
an
idea
was
so
nice
to
already
answer.
I
I
pinged
him
last
time
around
on
the
on
a
number
of
items
that
we've
addressed
in
the
pr
and
that
are
now
pending,
basically
feedback
from
from
upstairs.
And
that's
what
brought
me
here
today
again,
I
guess
you
folks
had
a
like
calm,
big,
yes
cornweek
last
week,
so
it's
understandable
that
there
hasn't
been
much
traction
just
wanted
to
make
sure
it
doesn't
get
lost.
A
Brilliant
thanks
to
luke,
so
next
is
siddeth.
On
the
the
question
of.
Do
we
have
time
for
some
backlog,
grooming.
Considering
this
this
call
has
only
taken
10
minutes.
I
guess
we
do
have
time
and
how
does
people
feel
about
doing
some
of
the
backlog
agreement
now.
A
Oh
go
for
it.
B
So
one
thing
we
can
do
is
to
go
over
the
newly
created
box
issues.
If,
if
you,
if
you
want
to
do
it,
because
we
are
good
in
the
1.2.0
milestone
as
we
did
in
the
privacy
or
we
can
do
regular
backlog,
milestone.
A
A
So
any
any
any
counter
offers.
A
Cool,
we
can
do
that
socially,
shall
I
stop
recording
from
a
office
hours
point
of
view
and
then
whoever's
interested
in
the
the
backlog
agreement
can
stay
on
the
call,
all
right
cool,
so
any
more
business
for
for
office
hours
only
last
minute
going
once
twice
three
times
all
right
cool.
Well,
thank
you.
Everyone
for
attended
and
see
you
again
in
two
weeks,
so.