►
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:
everyone
welcome
to
the
cluster
API
provider
AWS
office
hours
on
Monday,
the
20th
of
February,
just
a
reminder
that
we're
by
the
cncf
code
of
conduct,
so
that
basically
means
just
just
be
nice
and
respectful
to
each
other,
we'll
follow
the
usual
meeting
etiquette,
which
basically
means
if
you'd
like
to
speak.
Please
use
the
raise
hand,
feature
and
zoom
I've
shared
the
meeting
notes
in
the
chat
window.
So
these
are
the
2023
our
calendar.
A
Invite
is
still
not
up
to
date,
so
yeah
make
sure
you
add
your
name
to
the
2023
meeting
notes
and
any
agenda
items.
A
Let
me
just
grab
a
few
windows
up.
Just
so,
I
can
see
people
cool.
If
this
is
your
first
meeting,
we
normally
give
a
few
minutes
at
the
start
of
the
meeting
just
for
you
to
unmute.
If
you
want
to
and
say
hello,
you
know,
while
you're
here
and
so.
B
A
B
Sure
I'll
go
ahead
first,
just
so,
you
know,
I
can
get
over
the
introvert
part,
but
hi
I'm,
Rudy
I,
basically
handle
infrastructure
engineering
for
a
company
called
Porto,
where
we
essentially
help
people
get
off
Heroku
and
have
like
the
same
open
source
workflow,
but
using
services
like
eks
on
top
of
their
own
clouds
and
cluster
API
is
not
something
we're
really
kind
of
betting
huge
on
more
so
because
we've
been
using
terraform
for
the
longest
time,
and
you
know
that
that
comes
with
its
own
setbacks,
plus,
as
we
see
the
world
moving
towards
Cappy,
we
think
we
should
ideally
not
get
left
behind.
B
So
yeah
I've
been
working
with
Cappy.
A
lot
been
working
on
integration
points
also
trying
to
understand
how
things
are
designed,
like
from
a
philosophical
perspective,
probably
also
made
a
fool
of
myself
on
GitHub
issues
for
the
API
provider
for
AWS,
but
we'll
see.
C
Was
there
anyone
else?
Would
that
would
like
to
unmute
and
say
hello.
D
Oh
yeah,
hello.
This
is
there
that,
because
of
the
unsteady
connection,
I
won't
be
able
to
show
my
placement
currently
so
yeah
hello,
I'm
I'm
I'm
here
because
of
the
current
LFX
mentorship
program
and
I
am
interested
in
this
whole
project.
So
yeah
I
just
wanted
to
come
here
and
say
hello
to
everyone
and
just
in
just
whatever
I
can
with
this
meeting
so
yeah
hello,.
A
Cool,
oh
yeah,
well
good
to
meet.
You
then
yeah
welcome.
We
will,
after
the
testing,
probably
talk
about
the
nfx
mentorship
as
well,
so
yeah.
It
was
good
that
you
joined.
C
Cool
anyone
else
would
like
to
say
hello,
if
not.
E
Mentioned
sure
I
can
say
hello
I've
been
here
a
few
times,
but
I'm
still
sort
of
new
to
this
I'm
Cameron
McAvoy,
a
software
engineer
and
indeed's
platform
team,
and
we
use
the
cluster
API
to
run
all
of
indeed.com.
So
it's
a
little
scary
to
say
that.
A
Yeah,
it's
good
to
say,
hello,
brilliant,
so
I
will
just
I
need
to
just
check
on
the
excellent
items.
We
didn't
take
any
action
items
from
the
last
meeting,
so
we'll
move
on
to
the
agenda.
So
there
are
no
PSAs
this
week.
So
we
can.
Then
we
normally
talk
about
any
action
items
from
the
previous
meeting,
which
was
two
weeks
ago,
but
they
were
no
action
items
again,
nice
short
and
sweet.
So
we
can
then
move
on
to
the
agenda
proper
and
go
go.
A
You
have
the
first
agenda
item
on
testing.
F
F
F
We
are
safe
from
this
problem,
but
then
we
got
the
second
issue,
which
now
seems
to
be
like
consistently
bad.
Is
that
no
node
is
joining
the
control,
plane
and
I
looked
at
the
events,
the
logs,
the
artifacts,
the
I,
don't
know
so
so
many
Yama
files.
So
many
young
advice
like
to
dispute
the
cluster
information
like
cluster
elements
in
clustered
API
objects,
and
it
looks
like
it's
waiting
on
bootstrap
data.
F
G
So
is
the
even
Bridge
air
has
gone
now.
G
F
Okay,
yeah
thanks
that
that's
fixed,
I
I,
don't
particularly
see
any
like
like
definitive
errors.
That
would
explain
why
it's
why
it's
hanging
on
waiting
for
bootstrap
data
like
there
is
and
that's
and
that's
why
I'm
stuck
like
I'm
I,
have
no
idea
what
to
do
now,
because
there
is,
there
is
no
definitive
error.
F
I
sorry,
I
grabbed
the
cluster
definition
that
it
that
it
dumps
and
and
launched
that
locally
with
the
namespace
and
everything
and
the
the
authenticator
and
everything
that
it
sets
up
like
a
static
credential
and
everything
I,
reproduced
the
whole
environment
locally
and
drain
it
like
five
six
times
works.
Every
time
works.
Sorry
like
it
would
have
been
so
nice
if
it
failed,
then
at
least
I
could
have
debugged
it,
but
no
it
just
works
like
what
am
I
supposed
to
do
now.
A
A
So
does
that
that's
obviously
that
indicates
it's
environmental,
because
if
we're
using
the
same
e2e
test
config,
does
that
mean
that
we
are
then
potentially
swallowing
or
masking
an
error
somewhere.
F
I
don't
know
I
was
thinking
so
right
now,
if,
if
there
is,
if
it's
waiting
for
a
bootstrap
data,
if
if
that
is
the
last
status,
then
it
doesn't
return
any
kind
of
error
or
doesn't
require
the
object.
It
just
says
it
sets.
It
sets
that
status
to
false
and
then
and
then
like
stops,
reconciling
the
object.
F
A
It
should
do
because
we
should
be
so
we
should
be
watching
on
the
obviously
the
cluster,
so
the
Cappy
cluster,
so
the
bootstrap
data
in
our
instances
is
it.
This
is
free
I'm
assuming
the
eks.
Isn't
it.
D
A
F
A
Well,
I,
guess:
that's
one
thing
to
try,
isn't
it
so
we
could
I,
guess
check
out
the
same
tag
for
Cappy
itself,
because
that's
that's
the
thing.
Isn't
it
this
obviously
indicating
bootstrap
data
is
ready.
F
A
A
F
Because,
because
locally,
when
I'm
doing
built
up
I'm,
obviously
using
master
the
main
at
that
point
on
on
the
cluster
API
side,
so
yeah
that's
a
possibility
that
it's
using
the
tag
that
that
has
some
kind
of
problem.
A
I
wonder
if
you
also,
let
me
also
bump
the
version.
Sorry,
the
velocity
level
of
the
Cappy
looks
within
our
end-to-end
test,
so
we
get
more
more
data
into
our
logs.
F
A
But
now
we
we
have
a,
we
have
an
environment
variable,
we
don't
know
we
can
set
the.
F
Yeah,
so
what
what
was
I
I
haven't
followed
that
thing
too
closely
too
much
work,
but
what
was
the
the
diacon
migration?
What
happened
there.
A
So
I
think
I
think
it
just
comes
down
to
that.
They've
migrated
the
accounts
from
somewhere
like
Google
or
or
VMware,
paying
directly
to
to
the
cncf
controlled
AWS
accounts
for
Community
controls.
Basically,.
F
So
it's
just
it's
just
a
matter
of
switching
hands.
A
A
F
A
Like
the
the
service
quotas
in
the
the
automatic
you
know
up
in
the
services
number
of
vpcs,
we
added
that
originally
because
we
didn't
have
access.
We
needed
a
larger
number
of
vpcs
and
stuff
like
that,
so
yeah
you're
right.
It
could
be
something
that
just
so
happened
to
be
in
that
in
those
accounts,
it's
no
longer
there
because
they're
completely
new.
A
A
A
F
D
F
F
Like
a
tag
or
or
something
like
that,
yeah
I,
don't
suppose
they
have
something
like
that,
but
but
it
doesn't
hurt
to
ask
Maybe.
F
A
F
F
A
I
guess
to
work
with
that
out:
we'd
have
to
again
ask
in
the
test
infra.
A
Channel
but
hopefully
hippie
hacker
will
be
able
to
take
a
look
at
it.
We
might
need
to
just
ping
on
the
thread
again.
This.
F
A
But
it's
not
I
guess:
there's
been
a
lot
of
improvements
to
the
intern
test
as
a
result
of
these
failures.
So
isn't
there
so
like
all
that
dodgy
code
around
creating
a
stack
and
then
deleting
and
all
sorts
of
other
places
that
you've
done
so
it
has
sort
of
been.
The
pain
has
been
beneficial
in
a
way.
F
A
A
Yeah,
oh
yeah,
I
think
that's
a
good
idea
create
a
completely
fresh
account
because
we
should
see
all
the
areas
that
we've
seen
like.
Oh,
if
we
haven't
got
enough
of
bbcs
and
then
you
run
it
again
and
the
service
request
should
have
been
actioned,
and
so
we
should
be
recreating
everything
that
you've
seen
along
the
way.
B
F
Right
I
think
that's
all
I
had
on
that
topic.
A
Cool
alrighty,
so
the
the
next
topic
is
sort
of
related
to
what
we've
just
partially
been
related
to.
What
we're
talking
about,
which
is
the
LFX
mentorship
program,
so
literally
I
think
tomorrow
is
the
last
day
to
get
applications
in
so
that
I
think
they
actually
shut
at
the
end
of
the
21st
and
then
there's
a
period
of
I.
A
Think
of
two
weeks
why
the
applications
are
reviewed,
but
a
lot
of
the
pain
that
we're
having
substrate
some
of
the
pain
that
we're
having
with
the
cloud
formation
stack
side
of
things
and
a
lot
of
pain
that
our
users
have
that
cloud
formation
stack
provisioning
of
the
I
am
stuff
will
be
solved
by
the
mentorship
program.
So.
A
Just
to
give
yeah
for
anyone
that
doesn't
know
so,
we've
tagged
this
issue,
the
rethink,
how
we
managed
prerequisites
in
cluster
AWS
ADM.
So
the
moment
where
we
do
the
create
stack
and
that
basically
just
runs
cloud
formation
to
create
all
the
IAM
related
stuff
as
part
of
the
mentorship
program.
We
want
to
rethink
that
because
we
have
the
situation
where
people
run
or
create
the
cloudformation
stack
in
different
regions.
A
Even
though
IAM
is
global
and
then
we
end
up
and
our
users
end
up
in
an
inconsistent
state
where
they're
trying
to
delete
it
for
the
wrong
region
and
it
just
causes
a
whole
world
of
pain,
so
hopefully,
as
part
of
the
LFX
program,
we're
going
to
rethink
how
we
do
the
prerequisites
to
how
we
create
all
this,
our
IAM
stuff
within
cluster
AWS,
ADM,
so
I
guess
for
anyone
that
is
interested
in
doing
this
yeah.
The
applications
will
close
tomorrow.
So
yeah.
A
If
you
know
anyone
that
would
be
interested
in
this
feel
free
to
encourage
them
to
apply.
Let's
have
a
link
yeah
in
the
project
here,
I'll
have
the
business
Foundation.
You
have
to
have
to
apply
there.
My
kids
I
will
speak
to
Nate
to
get
you
listed
as
well
as
a
mentor,
so
it'll
be
me
and
and
kitchen
doing
the
mentorship
or
the
mentoring.
That's
a
great
way.
A
Of
course,
you
know
cluster
API
and
Cappy
Kappa
and
then
move
on
to
design
and
implementation,
so
sort
of.
C
A
D
D
Is
currently
facing
this
issue
and
why
are
are
not
the
others
facing
the
same.
A
To
ask
a
question
so
so:
every
every
Cappy
provider
so
Kappa
Capri
capsi,
they
have
I,
guess
their
own
requirements
around
prerequisites,
that's
very
specific
to
the
cloud
environment
that
the
provider
is
targeting
so
for
for
Kappa
we
target
AWS.
So
most
of
our
prerequisites
are
around.
A
So
none
of
the
other
providers
run
into
this
problem
that
we
have
necessarily
they're
running
to
their
own
problems,
which
might
be
different
potentially,
but
we
run
into
this
problems
specifically
because
how
IAM
works
and
how
cloud
formation
works
and
the
the
I
guess
the
interaction
of
the
two
and
the
I
guess
the
misalignment
or
the
I,
don't
know
how
you
go,
go
or
and
guitar
you
would
describe
it.
A
But
you
know
people
assume
that
you
can
run
it
multiple
times
and
it
will
be
fine,
but
then
they
run
it
in
different
regions
and
it
does
it's
not
fine,
so
yeah,
I,
guess,
there's,
there's
mismatching
understanding.
D
D
A
That
as
well
so
I
feel
like
for
cap
G
for
LFX.
You
you
get
given
access
to
a
gcp
account
for
the
period
of
the
mentorship,
so
we
are
trying
to
sort
out
the
same
thing
for
Kappa.
So
you
you
know
you're
not
expected
to
have
your
own
AWS
account
so
yeah
we
need
to.
We
will
be
following
up
on
that.
A
There
we
go
cool,
so
that's
the
end
of
our
normal
agenda
items
so
normally
at
this
point
we
pause,
recording
or
stop
recording
and
then,
if
there's
anything-
and
we
have
this
section
called
after
hours,
so
if
anyone
has
what's
any
informal
help
with
issues
or
PR's,
they
can
ask
questions
so
I
will
okay
go
for
it.
A
Cool
so
yeah
I
will
pause,
recording
and
stay
on.
If
you
want
to
talk
about
issues
and
stuff
like
that,
if
not
we'll
see
you
again
in
a
couple
of
weeks.