►
From YouTube: 20200601 - 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).
B
A
A
A
C
So
if
you
wanted
to
consume
that
programmatically
base
also
going
to
drop
the
alpha
prefixes
and
move
to
using
a
configuration
file,
the
idea
is
to
give
customization
around
what
roles
are
called
being
able
to
add
extra
policies,
correct
setting
up
trust
policies
if
you're
doing
it
in
a
assume
role,
manner,
which
will
be
important
to
people
using
multi-tenancy
use
case
C
you'll
be
able
to
either
generate
CloudFormation
template
or
spits
the
spit
out.
The
I
M
policy
documents
and
consume
that
in
terraform
or
whatever.
D
A
Yeah
I
know
that
we
had
some
that
were
III
have
to
look
at
the
actual
PRS
to
refill
your
eyes
myself,
but
I
know
that
we
have
like
one
PR
that
was
out
there.
That
would
just
limit
the
subnets
that
were
returned
so,
instead
of
having
all
discovered
subnets
returned
when
we,
the
ones
that
were
specified,
be
challenged
with
altering
that
behavior
will
be
ensuring
that
we
don't
break
any
existing
clusters.
That
may
be
relying
on
the
default
behavior
that
we
have
today.
A
A
But
I
definitely
anybody
who
has
time
to
review
and
provide
feedback
on
those
PRS.
Please
go
ahead
and
do
so
because
I
know
that
there
are
various
use
cases
that
we
have
that
we
aren't
meeting
today
that
we
would
like
to.
But
we
also
want
to
make
sure
that
we're
not
breaking
existing
use
cases
that
people
are
relying
on
as
well.
So
we
may
need
to
make
it
potentially
opt-in,
behavior
for
the
new
behavior,
at
least
on
the
subnet
lookups.
A
Potentially,
we
need
to
weigh
those
three
PRS
that
were
linked
in
the
in
the
notes
and
try
to
you
know
figure
out
which
you
know
is
there
an
ordering
that
we're
looking
at
to
Landy's
as
far
as
priority,
and
you
know
how
we
want
to
take
that
so
I
know
your
feedback
would
be
great
Robert
but
I
know
also
others
that
have
been
involved
will
have
will
want
to
make
sure
to
get
feedback
as
well
such
as
Seth
and
Andrew.
The
New,
Relic,
folks
and
I.
Think
m'dear
probably
has
some
feedback
on
it
as
well.
A
E
C
Not
right
now,
I
will
need
to
read
in
terms
of
sorting
I.
Just
lexicographical
from
probably
is
fine,
I
suppose
yeah
everything
you
need.
One
thing
we
should
note.
We
should
add
that
to
our
documents
on
managing
AWS
resources
that
whenever
you
do
it
describe
order,
is
always
fandom
and
when
we
get
stuff
back
so
don't
ever
make
decisions
based
on
that.