►
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
All
right,
thank
you
for
joining
the
Wednesday
February
13th
edition
of
the
cluster
API
provider.
Implementers
meeting
amia
just
a
reminder
that
this
is
a
kubernetes
meeting
and
we
are
governed
by
the
CN
CF
code
of
conduct,
we'll
go
ahead
and
get
today's
meeting
started
with
an
agenda
item
from
Pablo
I
believe
regarding
the
permission
issues
when
deploying
the
sample
provider
from
cluster
API.
B
B
Yes,
basically,
the
question
is
that
I
was
just
following
the
intrusion
of
the
boot
of
the
processor
API
book
and
how
to
create
provider
from
your
platform
and
I
felt
two
issues.
The
first
one
I
saw
as
a
boat
that
I
reporter,
but
they
could
solve
myself,
which
is
related
to
I.
Think
a
change
in
the
way
gotta
build
a
builder
generic
scaffolding
code
that
now
the
the
DD
operator
needs
to
handle
additional
in
parameters.
B
It's
something
that
is
home,
but
then,
when
I
could
finally
make
it
run,
I
get
a
lot
of
errors
because
of
the
permissions
basically
is
happening
is
that
is,
there
is
no
or
only
permission
for
accepting
the
closer
API
objects.
Okay,
an
actor
is
very
clear.
The
said
the
access
to
four
grocer
for
resources
are.
B
Role
that
is
created
by
the
Builder,
which
makes
sense
to
add
they
require
permission,
but
I,
don't
know
which
permission
are
those
so
I,
don't
know
where
to
start
looking
at,
because
I
can
try
to
make
it
by
trial
and
error.
That's
probably
my
Bambi,
but
I
would
like
to
know
whether,
if
any
working
implementation
of
this
API,
the
problem
is
that
the
other
providers
don't
necessarily
follow
in
this
pattern,
because
my
understanding
is
some
of
these
older
provider,
like
the
AWS
provider,
worked
way
like
before
the
API
was
consolidated.
A
That
being
said,
there
is
some
issues
with
coop
builder
in
creating
our
back
where
you
currently
I'm,
not
sure
I
haven't
looked
at
the
1.0.8
release
of
COO
builder,
but
as
of
1.0.7,
you
weren't,
arbitrarily
thesaurus
or
e,
able
to
arbitrarily
create
rules
that
allowed
you
to
access
some
components
that
were
being
generated
outside
of
the
specific
coop
builder
code.
So
I
would
suggest.
A
A
They
were
far
too
limited
in
scope
for
us
to
be
able
to
handle
all
of
the
things
that
needed
to
be
done.
Ie
accessing
secrets
now
accessing
some
things
that
were
in
different
namespaces,
etc,
and
the
generated
manifests
then
needed
to
be
hand
created.
Shall
we
say
to
the
effective
permissions
to
allow
the
the
controller
to
operate?
Ok,.
B
Iq
builder
stop,
and
they
said
you
said
mother
we
modified
here
or
about
the
role
and
adding
and
I'm
now
I'm,
seeing
stuff
that
I
recognize
that
are
failing
in
my
case
or
who,
probably
just
at
whatever
they
do
here
except
okay,
they
are,
they
are
the
old
resources
and
then
okay,
yes,
they
they
they
had
the
show
you
just
wait
for
the
record.
What
is
this
implementation?
B
So,
yes,
I
will
try
with
this
one
I
mean
about
him
to
my
king,
but
I
think
that
they
already
included
what
I
need,
which
is
all
decoder,
API
resources,
machine
machine,
state,
machine
deployments,
but
she
said
everything
all
these
were
failing.
You
make
a
so
I
would
try
with
this
now
I'm
pretty
sure
yeah
yeah,
what
I?
What
there
was
to
go
I
would
play
some
star
because
you
know
he
said
at
least
I
try
to
do
it
myself.
B
I
will
end
up
with
probably
something
which
is
not
really
a
good
example,
but
it
starting
with
it
picks
up.
I
can
look
forward.
I
will
try
that
today
and
they
say
go.
What
is
something
that
you
mentioned,
that
you
said
something
RQ
builder
now
it's
it
allows
you
to
generate
additional
permissions.
It
does.
A
Not
currently,
so
that's
where
the
problem
is,
is
that
we
aren't
able
to
provide
directives
to
ku
builder,
to
say,
hey,
allow
all
of
these
things
and
generate
our
back
for
it
now,
so
it
is
somewhat
limited
in
what
it
can
create
currently
and
there's.
Certainly
some
upstream
issues
with
ku
builder
and
its
associated
tooling
repositories
to
enable
you
to
generate
that
from
code.
But
those
are
not
again
as
of
1.0.7.
Those
were
not
in
place
and
I,
don't
know
about
1.0.8.
B
A
B
What
I
would
do
is
that
I
will
try
to
make
it
like
a
patch
for
me,
so
that
I
could
want
to
do.
We
have
any
support,
for
the
revealer
itself
is
probably
the
best
way
to
proceed
is
to
create
at
us
and
the
same
way
they
patch
it
is
the
customization
step,
create
a
custom
set
of
rules
that
you
can
be
applied
to
the
default,
because
I'm
thinking
not
only
solving
my
problem,
but
also
trying
to
fix
the
documentation
and
add
an
additional
step
percent.
B
Do
these
add
these
additional
rules
that
can
be
applied
to
the
default
of
the
Y's
not
going
to
work,
because
any
anyone
who's
come
after
me
will
face
the
same
problem,
because
it's
more
or
less
okay,
you
make
it
one,
and
then
you
see
the
the
problem
with
any
question
in
which
one,
because
it's
a
long
list
of
stuff
so
I
will
try
to
solve
it.
That
way,
I
mean
an
order
way,
so
that
can
be
reproducible
for
others.
B
I
say
apply
this
patch
to
the
default,
because
what
I've
seen
from
the
WS
is,
besides
all
resources,
the
racist
should
be
quite
standard
because
it's
the
core,
a
roster
API
object,
so
that
made
a
lot
of
sense
and
the
rest
is
what
is
already
and
taking
a
look
yeah.
The
rest
is
exactly
what
is
already
in
my
role:
I
only
missing
the
costume,
API
stop
and
I
will
add.
Adam
will
try.
Okay,
that
one
sounds
great.
Okay,
I
will.