►
From YouTube: 20200420 - 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
April
20th
edition
of
the
cluster
API
provider
PWS
office
hours,
a
sub-project
of
both
cluster
API
and
C
cluster
lifecycle,
just
a
reminder
that
this
meeting
is
recorded
and
will
be
posted
up
to
YouTube
later,
and
it
also
adheres
to
the
kubernetes
community
guidelines.
So
in
general,
please
be
excellent
to
one
another.
If
you
have
any
issues
that
you
would
like
to
bring
up,
please
go
ahead
and
add
them
to
the
agenda
dot
now
and
go
ahead
and
add
yourself
to
the
attending
list
on
the
meeting
notes.
A
A
The
big
difference
is:
it
is
I'm
trying
to
align
a
little
bit
better
with
the
changes
that
were
made
to
upstream
cluster
API,
where
they're
delaying
the
release
of
v1
alpha
4
and
instead
trying
to
focus
on
adding
features
on
top
of
v1
alpha
3
right
now.
So
I
was
trying
to
align
for
the
same
timelines
and
the
same
type
of
process
for
us
if
at
all
possible,
I.
A
Don't
think
we
have
any
demos
today
so
that
can
bring
us
into
the
group
topics.
I
was
looking
earlier
today
and
I
noticed.
We
have
a
couple
of
Doc's
PRS
that
are
in
New
York
native
review.
Scott
Lowe
had
submitted
a
couple
of
great
documentation,
updates
on
using
existing
infrastructure
and
I
can't
remember
exactly
what
the
second
but
the
other
one
was
C
updating
the
docs
for
accessing
instances.
So
if
we
can
get
some
reviews
on
those
would
be
great.
A
I
also
wanted
to
bring
up
that
the
work
that
I've
been
doing
to
put
the
conformance
tests
for
the
upstream
kubernetes
CI
artifacts.
Previously
we've
been
doing
that
against
B
1
alpha
2,
with
the
PR
that
I
have
linked
in
the
dock.
It
updates
it
to
run
against
v1,
alpha
3
and
everything's
working
I've
done.
A
A
couple
of
tests
would
conformance
the
only
thing
we're
hitting
right
now
is
a
timeout
on
that
PR
and
even
though
customer
has
already
been
updated
to
a
three-hour
time
out,
because
this
PR
was
existing,
it
so
using
a
two
hour
timeout,
but
as
far
as
I
can
tell
everything
else
is
function
along
there.
So
if
that
looks
good
like
to
see
if
we
can
go
ahead
and
get
that
merge,
and
then
we
can
update
the
periodic
job
so
that
they'll
be
running
against
people
in
alpha
3
and
say
we
went
out
for
two.
B
A
A
A
A
All
right
take
a
look
at
the
outstanding
pull
request.
That's
one
of
the
ones
that
I
linked
for
Dobbs
updates.
That's
the
testing
related
lon,
totally
balanced
the
roadmap
that
ones
the
testing
related
one
there's
an
added
Bastion
check
here.
I
think
this
is
waiting
on
addressing
a
comment
right
now.