►
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
Cool
welcome
to
the
cluster
api
provider
aws
office
hours
on
monday,
the
9th
of
august
2021
a
reminder
that
we
abide
by
the
cncf
code
of
conduct,
so
please
be
kind
to
each
other.
I
will
share
the
meeting
notes
now,
if
you
could
add
yourselves
to
the
attendee
lists.
A
So
if
there's
not
many
people
attending
today,
but
if
this
is
your
first
meeting,
so
I
don't
know
austin
if
it's
your
first
meeting,
if
you
fancy
I'm
muting
and
saying
hello
feel
free
to,
but
you
don't
have
to.
B
Hello
yeah,
I'm
austin,
I'm
from
databricks,
I'm
just
listening
in
right
now.
I'm
gonna
be
working
through
just
a
quick
prototype
with
eks
and
cluster
api,
but
I
just
wanted
to
to
listen
in
and
see
how
these
meetings
go.
A
Cool
well
welcome,
yeah
if
anyone's
got
any
topics,
there's
not
many
topics
on
the
agenda
today,
but
if
you
have
any
topics
or
not
there
can
you
add
them
now,
with
your
name.
A
Cool,
so
one
psa,
basically
there's
a
work
in
progress.
Pr
for
the
eks
graduation.
There's
a
couple
of
things
to
note:
if
you're
interested
in
the
eks
side
of
things
there's
no
longer
a
separate
bootstrap
control,
plane,
provider
and
essentially
means
you
can
just
do
cluster
cuttle
in
it
and
the
aws
infrastructure
provider,
the
eks
is
enabled
by
default
as
it's
graduated.
So
there
is
a
new
environment.
A
Variable
kappa,
underscore
eks,
where
you
can
disable
the
eks
controllers,
if
you
want
to,
but
they
will
be
enabled
by
default,
I've
removed
the
aws
managed
cluster
actually
from
the
code.
Although
we
removed
references
to
this
quite
a
few
releases
ago,
so
I
not
entirely
sure
the
best
way
to
handle
the
scenario
where
people
are
actually
still
using
this
they
shouldn't
be,
but
if,
if
they
are
because
the
we'd
have
to
change
the
reference
on
the
cappy
cluster
on
the
cluster
reference,
is
it
cluster
infrastructure
reference?
A
Whatever
it's
called
on
the
capital
cluster,
so
yeah?
I
wasn't
sure
the
best
way
to
achieve
that
in
an
automated
way,
because
I
guess,
as
soon
as
you
apply
it,
cappy's
gonna
start
reconciling
it.
So
we
could-
maybe
I
think,
the
dear
you
recommended
another
controller
that
we
could
could
write,
but
yeah
it
didn't
seem
particularly
I
don't
know
it
just
seems
a
bit
yeah.
So
I'm
not
sure
about
that
one.
A
A
So
as
a
result
of
that,
I've
introduced
a
new
feature
flag
for
people
to
enable
that
by
default,
just
didn't
seem
right
to
to
graduate
that
as
well,
and
so
it's
basically
all
done
except
the
entire
tests
are
failing.
Obviously,
so
I'm
currently
going
through
the
the
painful
process
of
trying
to
get
them
working,
but
all
the
other
tests
are
passed
into
the
unit
test
departing.
It's
just
the
the
antwen
tests
that
are
failing
at
the
moment.
C
Yeah
this
one
last
week
I
did
create
an
issue
out.
It
was
gonna
explore,
replacing
all
their
annoying
m4
stuff
in
the
mate
file
with
major
I've
started
testing.
Some
of
that
there's.
It's
still
interesting
around
how
you
get
like
options.
We
have
a
lot
of
sort
of
configuration
options
and
make,
and
the
mage
file
doesn't
make
it
super
easy
to
have
that,
like
don't
support,
positional
arguments
which
are
mandatory
so
we'd
have
to
inject
some
of
our
own
stuff.
A
Yeah
cool
yeah
I'd
be
interested
in
that
one.
Actually,
the
the
next
two
agenda
items
are
yours.
C
As
well
yeah
yeah,
so
kubernetes
122
came
out
last
week,
so
we
really
need
to
cut
the
we
run
out
for
four
release.
So.
C
There's
a
bunch
of
so
we
had
produced
the
scope
to
just
the
breaking
api
changes,
but
given
we
really
really
need
the
122
support.
Now,
maybe
there's
a
case
we
made
that
we
see
where
we
are
in
our
milestone
and
see
if
we
just
pump
stuff
up
to.
We
went
out
for
five
and
how
are
you
feeling
around
the
eks
graduation
like
do
you
think?
Are
we
we?
We
need
to
release
asap,
otherwise,
people
can't
deploy
cluster
api
to
kubernetes
122
clusters.
A
Yeah
yeah,
so
it's
literally
just
end-to-end
tests
so
locally
with
kind.
It's
working,
I'm
not
seeing
any
issues,
so
I
will
I'll
focus
on
tomorrow
and
I'll
get
the
end-to-end
test
fix
tomorrow.
So
that's
then
it
should
be
good
to
go.
C
Yeah,
so
maybe
we
should
run
down
the
milestone
after
so
just
won
the
next
one,
and
then
we
can
go
through
the
milestone
completely.
So
we've
it's
been
speaking
to
shivani
and
ankita,
who
both
sort
of
volunteered
to
step
up
to
start
helping
out
with
reviews.
So
pretty
much.
If
I'm
going
to
open
the
pr
if
anyone's
got
any
objections
to
add
ankita
and
shivani
as
reviewers,
but
I
think
we
also
need
to
move
some
people
to
emeritus.
C
I
will
I'm
happy
to
chat
with
those
folks
individually
and
mostly
that's
going
to
be
michael
buman
and
andrew
rudoy,
mostly
because
I
don't
dare
I
don't
think
either
of
them
are
still
active
in
cluster
api
at
the
moment,
so
see
if
they're
so
what
they
want
to
do,
because
they
probably
don't
want
to
get
pinged
continually
on
github
yeah.
A
A
A
A
Cool,
so
then
did
you
want
to
look
at
the
the
milestone
for
zero
seven
zero,
so
aws
resource
references
on
unimplemented
logic.
C
C
I
think
that
one
and
the
cleanup
aws
templates
and
naming
taipei
changes
like
if,
let's
just
try
and
get
them
done
at
an
asap
and
if
they
don't
it's
like
it's,
not
the
end
of
the
world,
if
they
don't
make
it
in,
I
think
yeah,
they're,
they're,
sort
of
quality
of
life
improvements,
definitely.
A
Good
to
have,
I
think,
probably
the
awesome
machine
balls
stuff
as
well.
That's
that's
not
going
to
be
done
in
time.
Is
it
so
we
could
push
that
back
to
the
the
next
one.
So
then
that
just
leaves
the
I
guess
the
eks
out
of
graduating
that
which
hopefully
I
can
get
done
tomorrow
and
then
maybe
that
frees
us
up
to
do
a
release
wednesday.
I
guess
that
would
be
when
it
or
yeah
yeah,
potentially
yeah
cool.
A
Did
you
want
me
to
push
these
change?
The
milestones
on
these,
these
other
ones,
to
seven
zero,
seven
x.
C
A
A
C
Did
you
go
for
it
yeah?
Sorry?
I
just
I
will
put
a
link
into
this,
but
a
couple
of
us
have
started
discussions
around
a
load,
balancer
proposal
proposal,
for
we
won
alpha
5
for
plus
cluster
api
there's
going
to
be
impacts
for
the
aws
provider.
There
is
a
thread
so
if
anyone's
interested
in
that
and
like
the
main
requirements
were
going
to
be
to
replace
the
default
elb
behavior
with
nlb
support
and
ability
to
use
nlb
defront
vmc
on
aws.
C
So
that's
the
vmware
on
aws
solution
and
it
would
also
act
as
a
sort
of
generic
machine
type
load,
balance
thing
and
support
our
multi-tenancy
constructs,
etc.
We're
looking
at
using
gateway
api
if
we
can
but
and
red
hat,
also
interested
in
splitting
out
internal
load
paths
as
well
as
external
load
balancer.
So
the
load
balancer
that
worker
nodes
talk
to
will
be
completely
vpc
internal
and
then
you
might
still
have
an
external
load
balancer
that
external
cube
cattle
one
other
class
14.,
so
that
will
cut
down
on
your
costs,
especially
if
you're.
C
If
that's
the
thing
that
has
been
of
concern
to
you,
then
that
that
should
be
solved
but
yeah
this
is
this
is
next
fleece
or
so
I
think
we
were
now
for
five
is
ended
the
year.
I
think
I'm
not
sure
that's
where
we
are
and
the
class
api
roadmap
will
be
discussed
on
wednesday.
People
interested
in
that.
A
Cool,
well,
I
think
that's
probably
it
then
so
we
can
call
it
a
close
speak
to
you
all
in
a
couple
of
weeks.
Take
care.
Take
care.