►
From YouTube: 20200224 - Cluster API Provider AWS 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
Hello
and
welcome
to
the
February
24th
edition
of
the
cluster
API
provider,
AWS
office
hours,
a
sub-project
volts,
a
cluster
lifecycle
and
cluster
api.
Please
remember
that
this
meeting
is
recorded
and
is
subject
to
the
kubernetes
community
guidelines.
So
in
general,
please
be
excellent
to
one
another.
If
you
are
attending
live,
please
go
ahead
and
add
yourself
to
the
attending
list
in
the
dot
and
I
can
link
that
in
the
zoom.
And
if
you
have
any
topics
that
you
would
like
to
bring
up,
please
go
ahead
and
add
them
to
the
agenda
as
well.
A
A
So
part
of
that
is,
as
I
created
a
RC,
0,
milestone
and
github,
and
when
we
get
to
the
issue,
triage
and
grooming
later
we're
going
to
try
to
make
sure
that
that's
populated
correctly
and
everything
that
we
need
that
we
want
to
try
to
get
in
before
a
release,
preferably
later
this
week
is
in
that
milestone
all
right
than
that.
A
reminder
that
if
you
haven't
been
to
the
main
class
or
API
meeting
or
seeing
the
mailing
list,
we
are
having
a
meeting
greet
breakfast
for
cluster
API
and
cube
Connie.
A
You
there's
an
RSVP
link
in
the
dock.
So
if
you
would
like
to
attend,
please
fill
that
out
so
that
we
can
send
you
the
location
once
we
have
that
tied
down
and
make
sure
that
we
have
room
for
you
and
if
you
haven't
already
received
a
cluster
API
t-shirt,
there's
a
link
to
a
forum
through
request,
one
in
the
dock
as
well.
I.
B
A
A
C
D
Don't
think
that
we
necessarily
should
require
or
default
to
requiring
an
AWS
config
file,
because
if
you
just
have
credentials
they
can
go
into
the
AWS
credentials.
File
and
configure
is
optional,
so
I
think.
Maybe
we
need
some
documentation
around
this,
but
I.
Don't
know
that
we're
necessarily
gonna
want
this
to
be
the
way
that
we
have
everybody
doing
it
like
out
of
the
box.
Yeah.
C
C
A
A
C
A
A
D
A
A
Set
early
identified
the
date
at
which
we
fix
the
issue
and
publish
newer
images,
so
it's
basically
just
doing
a
query
against
AWS
against
the
account
that
holds
them
for
images
that
are
older
than
a
certain
date.
So
it's
it's
actually
not
that
bad,
but
I
just
haven't
had
the
time
to
kind
of
spin
up
new
images
yet
and.