►
From YouTube: 20190617 - 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
A
So
the
first
item
obviously
we're
on
a
temporary
zoom
today,
due
to
a
conflict
with
the
mini
cube
office
hours,
I've
already
talked
to
Tim
st.
Clair
and
he's
going
to
work
on
trying
to
resolve
that
scheduling
conflict
for
us.
So
hopefully
we
will
be
back
on
the
normal
zoom
next
or
two
weeks
from
now.
All
right
next
item
we
already
have
zeroed
out
3.0
release
out
there.
There
are
some
issues
that
people
have
been
having
related
to.
The
I
am
permissions
that
are
set
up
with
the
cluster
AWS
ADM.
A
So
we
are
in
need
of
a
0.3
dot,
1
release
so
that
new
users
have
a
working
release
to
download
and
run.
There
are
two
outstanding
PRS
that
I
think
are
in
a
good
spot
for
us
to
go
ahead
and
try
to
get
merged
before
the
0
to
3.
Double
and
release
has
cut,
but
I
wanted
to
see
if
anybody
else
had
any
input
on
any
issues
that
are
in
need
of
addressing
or
any
PRS
that
we
need
to
try
to
fast-track
into
that
release
is.
A
A
D
A
A
E
Absolutely
yeah
yeah,
so
basically
an
account
had
to
be
created
while
using
while
starting
up
a
cluster
with
a
I
am
I.
I
am
and
and
like
that
is
a
different
story,
so
yeah
so
I
already
have
an
account
like.
Why
do
I
need
another
one,
and
so
the
gist
is,
if
my
account-
or
it
does
have
pretty
much
brought
permissions
to
use
ec2.
Why
do
I
need
even
broader
missions
so.
E
C
E
D
Go
ahead,
I
think
I
completely
answer
that
one
say:
I
think
the
permission
should
rather
the
permissions
in
the
policies
for
that
user
should
be
the
minimal
ones
required
for
Kappa
apart
form.
Maybe
we
could
do
some
more
stuff
tightening
up
on
tags,
but
yes,
you're
right.
We
don't
actually
need
to
create
the
user.
It
was
there
for
convenience
early
on
that
you
could
use
it
instead
of
your
root
account,
but
it's
so
I
think
we
shouldn't
I
think
from
the
slack
conversation
last
week.
We
should
definitely
make
that
optional.
D
That's
totally
reasonable
to
do.
If
we
have
not
tightened
some
of
the
permissions
as
much
as
possible,
then
we
should
wait,
write
notes
as
well,
but
we
do
need
some
things
which
are
not
an
easy
to
like
ELB
one
ELB
permissions
and
some
weird
I
am
one
steam
that
grant
lb
sufficient
permissions.
The
ECT
that
makes
sense
yeah.
E
E
E
B
So
I
think
what
nadir
we're
saying
is
we've
attempted
to
do
that
and
if
you
look
at
the
policies,
they
are
not
wild
carded
to
everything.
So
I'll
paste
the
link
in
slack
here
or
in
in
zoom.
So
if
there
is
something
that
you
don't
think
needs
to
be
there,
then
we
can
look
at
getting
rid
of
it,
but
I'm
pretty
sure
the
team
has
made
every
attempt
so
far
to
scope
this
down
as
small
as
possible.
Thank
you.
D
I
would
add
that
one
that
is
loads,
loads
of
pens
is
actually
the
AWS
cloud
provider,
not
Kathy
itself.
So
we
we
assume
that
people
want
to
use
the
AWS
cloud
provider.
So
that's
granted
and
I've
opened
the
issue
on
their
repo,
saying,
hey.
We
should
probably
try
and
minimize
this
so
there's
I
think
that's
the
majority
of
work
that,
in
terms
of
tightening
there
are
some
like
clever
stuff.
We
can
do
with
tags
potentially
as
well,
but
try
it
as
much
as
possible
not
to
wildcard
just
blindly
wildcard
stuff.