►
From YouTube: 20190325 - 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
All
right,
hello
and
welcome
to
the
Monday
March
25th
edition
of
the
cluster
API
provider
AWS
office
hours.
We
have
a
relatively
light
agenda
today.
So
if
you
have
any
topics,
please
go
ahead
and
add
them.
The
doc
is
linked
in
the
group
chat
if
you're
attending
live
so
looks
like.
Currently.
The
only
item
that
we
have
in
the
agenda
is
the
V
1
alpha
1
tracking.
Did
you
want
to
go
ahead
and
take
that
item
Andy.
B
A
B
B
All
right
so
I'm
gonna
go
from
the
bottom
up,
there's
one
more:
if
you
scroll
or
there
oh
I,
guess
you
have
them
sorted
somehow
all
right,
so
we
will
go
bottom
up,
then
umbrella
on
user
experience
and
getting
started.
Experience
improvements
this
one
I
haven't
looked
at
today,
but
it
hasn't
been
updated
since
January.
So
I
think
this
is
probably
something
that
we
can
just
defer
to
next
and
then
my
reference
is
against
umbrella
issues,
because
I
just
find
that
they're
hard
to
track.
B
Ok,
next
up
is
the
periodic
ete
testing
which
Harish
is.
He
did
a
session
with
Andrew
cuts
to
get
up
to
date
and
up
to
speed
on
what
this
involves
and
I
know.
Jason
you
have
taken
over
the
AWS
Bosco's
janitor
PR
from
Andrew
and
you're
gonna,
see
that
through
and
then
Harish
is
going
to
we're
gonna
close
out
the
bottom
open
tasks
in
that
list
and
Harish
is
going
to
open
up
a
replacement
PR
for
it.
So
I
would
expect
that
to
happen
this
week,
but
it's
not
going
to
gate
the
actual
release,
but.
B
The
goal
is
to
get
in
alright.
Next
up
is
document
what
you
get
in
a
cluster
I
think
this
is
kind
of
the
same
stance
on
documentation.
It
would
be
fantastic
if
we
get
this
in,
but
I
don't
believe
anyone
is
actively
working
on
it.
So
we
can
leave
it
in
the
milestone
for
right
now,
but
you
know
if
it
slopes
to
after
Friday.
That's
fine.
B
Tagging
failures
can
result
in
orphan
resources.
This
one
I
believe
you
all
said
there
was
an
update
from
nadir
and
yeah
there.
It
is
from
a
few
days
ago
and
that,
like
the
other
things,
we
probably
can
just
push
this
to
later.
Anyone
have
any
objection
to
taking
this
one
and
moving
it
to
the
next
milestone.
C
B
B
A
B
Right
I'll
make
a
note
for
to
follow
up
on
that
for
this
one
in
particular,
let's
I
think
we
probably
might
want
to
have
somebody
look
and
see
if,
if
this
is
actually
an
issue,
so
is:
does
anyone
have
some
spare
time
and
have
multi-factor
authentication
enabled
in
an
ADA
base
account
to
be
able
to
test
this?
So,
for
example,
my.
A
D
B
A
B
Yeah
I
mean
we
I,
don't
I'm
not
familiar
enough
with
the
build
process.
At
this
point,
around
go
version.
I
do
have
experience
in
other
projects,
where
we've
used
a
docker
image
and
container
that
pins
the
go
version
so
that
yeah,
you
can
run,
go
both
locally
with
whatever
version
of
go
you
have
installed,
but
in
terms
of
what
we
use
in
seei
and
what
we
use
to
produce
the
binaries
that
we
ship
like
that
all
goes
through
a
docker
workflow.
So
if
we're
not
doing
that,
it's
something
we
might
consider
yeah.