►
From YouTube: 20200406 - 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
If
you
are
attending
blog,
please
go
ahead
and
add
yourself
to
the
attending
list
on
the
agenda
and
notes
document
and
if
you
have
anything
to
add,
please
go
ahead
and
add
it
to
the
agenda
as
well.
To
start
with,
I
did
want
to
let
everybody
know
that
we
have,
since
our
last
meeting
version,
0.5
2
was
released,
mostly
bug
fixes.
So
if
you
are
having
any
issues
with
0.51
or
before
update
2-0
5.2
and
hopefully
it'll
solve
your
issues
and
we
I
don't
see
any
demos
for
today.
B
So
it's
basically
when
they've
changed
that
so
and
you
may
open
up
a
PRT.
Add
I
am
role
field
to
the
cluster.
We
from
VMware
side
we
want
to.
We
basically
want
to
initially
put
that
into
a
secret
because
of
our
some
of
the
concerns
that
came
from
our
security
organization
and
also
open
up
the
possibility
to
support
different
types
of
credentials.
B
So
basically
the
idea
around
this
is
we
would
have
a
secret
reference
and
there
would
be
different
types
of
Secrets
which
correspond
to
the
different
ways
you
can
wire
up
the
credential
in
for
AWS,
so
it
could
be
static
credentials.
It
could
be
an
IM
wild
assumption.
It
could
even
be
using
oh,
I
DC
so
from
communities
116.
B
You
can
use
projected
account.
Service
volume
to
projected
service,
account
token
volumes
and
you
can
exchange
that
shot
directly
with
AWS
in
return,
some
AWS
credentials.
So
that's
the
feature
that
is
available
in
eks,
for
example,
apart
from
the
side
they're
not
on
116,
yet
so
yes,
so
it's
about
giving
the
flexibility
being
able
to
support
caching,
so
you
don't
want
if
you're
managing
lots
of
clusters,
you
don't
want
the
STS
to
see
more
being
called
constantly.
So
we
did
some
stuff
and
we
went
out
for
two
to
do
that.
B
B
A
A
A
We've
seen
it
more
around
the
move,
workflow
so
I'm
wondering
if
it
might
be
related
to
some
of
the
issues
like
some
of
the
intermittent
issues
we've
seen
with
sed
latency
and
but
I.
Don't
know
it's
been
difficult
to
try
to
get
a.
You
know
reproducer
for
it
where
we
actually
have
enough
logging
data
to
really
tell
anything.
I
know.
A
A
B
A
A
A
Clear
that
out
see
if
anything
hasn't
been
labeled
properly
all
right,
everything's
labeled,
one
of
the
things
that
I
probably
should
also
bring
up,
is
that
for
the
core
cluster
API
project,
they're,
looking
at
potentially
trying
to
make
the
next
release
a
non
MPI,
breaking
change
release
and
try
to
do
I
try
to
have
at
least
a
period
where
we're
adding
features
without
introducing
breaking
changes
to
the
to
the
API,
at
least
for
a
short
while
and
will
probably
follow
suit
as
well.
So
I'll
try
to
do
a
little
bit
of
milestone.
A
Cleanup
like
right
now
we
have
a
0.60
milestone.
I
may
try
to
introduce
something
in
the
way
of
a
different
milestone
in
there.
They
track
some.
You
know
feature
improvements
that
we'd
like
to
land
that
are
non
API
breaking
changes
as
well,
and
if
anybody
wants
to
take
a
look
and
suggest
anything
for
any
of
those
milestones,
please
feel
free
to
raise
those
and
do
that
as
well.
I.