►
From YouTube: 2023-03-23 Crossplane Community Meeting
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
recording
has
started,
and
this
is
the
March
23rd
2023.
A
lot
of
23
is
up
in
that
one
cross
plain
community
meeting,
so
I
will
drop
a
link
right
now
into
the
zoom
chat
to
help
you
all
directly
get
to
the
agenda
document
there.
It
is
in
the
zoom
chat.
A
Now
the
agenda
document
is
open
for
comments
and
suggestions,
so
feel
free
to
put
any
topic
that
you
want
to
most
likely
down
in
the
community
topics
and
questions
section,
and
we
will
get
to
it
today
for
sure
all
right.
So,
let's
jump
into
Milestone
checkup
stuff,
the
I
think.
On
the
day
of
the
last
community
meeting
on
March
9th,
we
had
a
slew
of
patch
releases
that
went
out
for
some
of
the
the
security
advisories
that
were
open
from
the
fuzz
testing
effort.
A
So
we
already
talked
about
those
ones
and
then
in
the
two
weeks
since
then,
there
has
not,
to
my
knowledge,
been
a
crosswind
runtime
or
a
crosswind
patch
release.
So
I,
don't
think,
there's
any
recent
releases
to
talk
about
there
and
we
could
go
ahead
on
to
the
1.12
Milestone
instead.
So
we
are
almost
exactly
a
month
away
from
1.12.
A
You
know
note
that
code
freeze
is
in
three
weeks
and
feature
freeze
is
in
two
weeks,
so
we
definitely
have
some
big
features
that
are
still
outstanding
and
have
not
landed
yet
so,
but
we
will
get
into
more
details
on
that.
Geno
walk
us
through
some
of
the
big
big
features
that
folks
are
working
on,
but
let's
go
ahead
and
take
a
look
at
the
board
right
now.
Then
I
should
scope
this
to
1.12.
A
all
right.
So
Nick
and
I
took
a
pass
through
this
board
just
yesterday,
so
we
believe
it
should
be
fairly
up
to
date
and
obviously
there's
a
lot
of
stuff.
That's
in
progress
right
now,
so
we
want
to
start
closing
some
of
these
outs
and
getting
them
over
to
the
done
column
as
we
are
getting
closer
and
closer
to
our
feature:
freeze
and
code
free
states,
so
Jean
you
have
a
whole
section
with
updates
below
for
the
major
features
that
your
team
is
reporting
delivering
on.
B
Yeah
no
problem
so
we're
pretty
much
on
observerly
resources.
We've
been
pausing
the
work
on
that
a
bit.
You
know
it's
functional,
end-to-end,
there's
a
whole
bunch
of
PR's
that
are
open.
B
That
has
received
some
reviews
and
we've
resolved
some
some
comments
on
them,
but
we
we
pulled
our
our
resources
more
into
focusing
on
external
secret
stores
and
getting
that
out
of
the
door,
and
you
know
that's
pretty
much
close
to
completion
now:
we've
We've
merged,
there's,
no
Secret
store,
API
and
client
implementation
this
week
and
the
Vault
store
now
exists
as
a
reference
implementation
for
external
secret
Stores.
B
So
there's
a
few
minor
things
that
we
need
to
to
wrap
up,
but
it's
pretty
much
there
and
you
know
we
should
move
back
on
to
observingly
resources
and
and
closing
that
off
next
week
and
then
on
composition,
validations
webhook,
so
lovro.
Do
you
actually
want
to
give
a
quick
update
on
that
since
you're
on
the
call.
C
Sure
sure
well
yeah,
so
we
are
progressing.
We
are.
We
have
already
have
some
POC
called
the
ready
and
as
written
here
we
have
some.
We
did
some
internal
review
and
we
decided
to
maybe
split
it
into
smaller
chunks,
which
would
be
easier
to
merge.
So,
basically
looking
good
and
hoping
that
soon
we'll
be
creating
the
concrete
PRS
for
that.
B
All
right
and
then
previously
we
we
thought
we
could
get
the
ignore
changes
work
in
as
well,
but
due
to
kind
of
like
a
lack
of
alignment
on
the
you
know
what
what
the
right
approach
might
be
to
take
on
the
design
proposal.
B
B
It
might
also
be
better
just
to
to
wait
for
observe
any
resources
to
land
and
and
see
how
that
might
help
the
situation
and
we'll
see
how
that
goes.
So
that's
pretty
much.
It
there's
a
couple
of
smaller
things
that
we're
that
we're
looking
at
as
well.
B
That's
on
the
board
that
I
didn't
put
updates
on
here,
they're,
mostly
3139,
which
I
think
lover
actually
just
I
added
a
comment
that
this
is
actually
working
in
in
the
latest
cross
plane,
but
not
in
110
and
one
nine
so
and
a
few
other
hassanists
looking
to
to
fix
the
last
of
the
the
back
off,
not
working
scenarios
as
well,
and
if
you
scroll
down
Jared
in
the
in
progress
column,
esky's
having
a
look
at
the
tag
deleted
from
claim,
spec
being
added
back
and
there's
one.
B
Definitely
the
fast
testing
work
is
now
being
completed
as
well,
and
that's
all
in
place
as
well
by
Philippe.
So
yeah.
A
All
right
so
there's
a
obviously
a
lot
going
on
and
a
lot
of
Investments
being
made
right
now
so
John
just
to
be
totally
clear.
You
expect,
with
your
with
your
team,
that
for
the
1.12
time
frame
still
that
observe
only
resources
validating
compositions
via
web
hook
and
the
plugable
external
secret
stores.
Those
three
major
features
are
all
still
on
track
for
1.12
time
frame.
Yes,
perfect,
that
sounds
great
to
me
and
I
know:
there's
a
yeah
there's
a
lot
of
other.
A
You
know
highly
demanded,
or
you
know,
impactful
bug
fixes
that
the
Jean
talked
about
as
well.
So
let
me
peruse
through
the
the
columns
here
and
see
if
there's
some
other
things.
Oh
yeah,
something
else
to
mention
for
1.12
time
frame.
A
Is
a
community
contributor
stepped
up
and
is
making
a
number
of
fixes
for
let's
work
towards
promoting
or
maturing
composition,
functions
to
Beta
so,
for
instance,
I
think
these
two
or
at
least
a
couple
of
them,
and
then
oh,
looks
like
this
one
might
have
been
merged
so
yeah,
so
like
at
least
three
issues
here
around
using
composition,
functions
have
been
got,
have
gotten
some
progress
and
should
be
in
for
the
1.12
time
frame.
A
So
this
one
here
I
think,
was
an
issue
with
the
version
of
sea
run
that
we
use
yeah
so
Andrew
is,
is
the
contributor's
name
I,
don't
know
if
they're
on
the
call
today,
but
definitely
want
to
give
them
a
shout
out
for
stepping
up
and
fixing
a
number
of
issues
with
with
the
alpha
implementation
of
composition
function.
So
Andrew.
Thank
you
for
that.
If
you
happen
to
watch
this
later,.
A
Adding
the
ability
to
essentially
publish
your
composition,
functions
to
a
private
repository
and
then
use
image,
pull
secrets
to
pull
the
container
image
with
your
composition,
function,
implementation.
A
Down
and
execute
it,
there
is
another
one
of
the
ones
in
progress,
so
some
good
progress
being
made
on
maturing
composition
functions
to
Beta.
Obviously
we
are
not
going
to
make
that
change
in
1.12,
declaring
them
beta.
They
that
there
there's
a
number
of
issues
that
are
still
being
worked
out
and
there
is
a
tracking
issue
for
that
where
I
think
it's,
probably
because
it's
not
in
1.12.
Let
me
see
if
I
can
find
a
yeah
here.
It
is
so
that's
the
issue
for
it
and
so
yeah.
A
A
number
of
these
are
in
progress
right
now
and
then
in
1.13
time
frame,
we'll
also
be
tackling
more
of
these,
as
more
feedback
comes
in
on
composition,
functions
do
feel
free
to
continue
adding
ideas,
and
you
know
things
that
you
would
like
to
see
progress
to
matured
to
this
issue
here
at
3751,
for
continuing
to
mature
composition,
functions
and
Jason.
Yes,
if
you,
you
know,
have
a
composition
function.
The
issue
that's
already
opened
and
it's
not
in
you
know,
captured
in
the
task
list
here.
A
I,
don't
know
if
you'd
be
able
to
edit
it,
but
just
feel
free
to.
You
know.
Add
a
comment
on
it
to
link
to
your
issue
and
then
or
ping
me
and
then
we'll
make
sure
that
it
gets
into
that
list.
A
All
right,
let's
see
what
else
is
in
the
board
here,
that's
worth
talking
about
Jesse.
Do
you
want
to
give
us
any
updates
on
package,
signature,
validation,
anything
you
need
to
share
there.
Yeah.
F
Absolutely
I
actually
was
putting
together
the
pull
request
on
my
latest
Branch
rebased
against
the
current
master
last
night,
and
there
is
a
couple
of
of
questions.
I
have
about
direction
that
I'm
I'm
not
prepared
to
to
show
right
now.
I
was
just
just
kind
of
running
to
get
to
my
office,
but
I
will
I
will
I
will
ping
folks
in
slack
the
the
long
and
the
short
of
it
is
everything
is
wired
up
behind
the
feature
flag.
F
Now
there
I
I,
because
of
my
my
relative
newbie
use
of
go.
F
There
was
some
some
issue
with
how
to
overload
some
of
the
existing
classes,
which
or
types
but
but
clearly
can't
do
that
with
go
so
I've
I've
gone
a
different
route
but
there,
but
because
of
that
I'm,
not
I'm,
not
liking.
The
way
the
code
is
is
looking.
There's
there's,
there's
some
two-way
dependency
kind
of
stuff.
That's
just
a
little
weird,
so
I
won't
I
want
to
get
some
other
eyes
on
it,
and
I
will
formulate
that.
F
But
long,
and
the
short
of
it
is,
is
that
that
it
passes
to
make
reviewable
I've
been
able
to
to
kind
of
get
it
up
and
running
and
and
see
that
the
intended
functionality
is
there?
It's
just
you
know
the
beautification
of
of
the
code
that
that
needs
to
be
done
now,
so
I'd
be
happy
to
have
some
input.
A
Beautification
I,
like
that
yeah
terminology,
there.
A
That's
a
great
way
to
capture
that
Jesse
awesome
man
thanks
for
sharing
that
update
and
then.
A
Your
continued
effort
on
on
that
feature
as
well
I
know
that
it
is
a
useful
and
impactful
feature
so
we'll
try
to
get
you.
You
know
some
of
the
feedback
and
to
help
out
with
that
direction
and
getting
that
closer,
great,
all
right,
okay,
so
I
think
then
that's!
We
basically
talked
about
everything.
That's
in
progress
that
does
not
also
have
a
later
agenda
topic
to
focus
on
it.
So
let's
is
Bob
on
the
call
today,
I,
don't
think
so.
A
A
So
then,
let's
go
ahead
and
open
it
up
for
any
other
questions
directly
related
to
1.12
I
know
we
got
a
question
in
the
chat
that
I
about
providers
that
I
added
to
digital
documents,
so
we'll
get
to
that
as
well,
but
anything
else
about
1.12
that
folks
wanted
to
bring
up
before
we
move
on.
G
A
You,
okay
awesome!
So
let's
move
on
down
to
provider
discussion
then,
in
terms
of
recent
releases,
I
believe
that
there's
there's
only
one
that
I
saw
an
announcement
about
since
last
community
meeting,
so
there's
a
link
to
that
in
the
marketplace
and
also
the
release,
notes
and
folks
can
dig
into
that
on
their
time.
So
Raul
asked
a
question
about.
If
we
know
there
are
any
active
developments
on
building
providers
for
resources
like
VMware
and
Akamai,
there
are
some
I'm
aware
of
Rahul.
A
There's
I,
don't
Sean!
Do
you
know
if
you
could
speak
to
like
the
the
latest
updates
on
any
of
those
type
of
Provider
efforts,
or
you
know
anything
more
up
to
date
than
the
general
status
that
I
have.
A
It
so
yeah,
so
there
there
had
been
some
Community
efforts
for
both
the
VMware
sort
of
thing.
I,
don't
think
I
don't
think
it
touched
NSX
though
I
was
more
like
a
vsphere
sort
of
focus
and
I.
Don't
know
a
lot
about
VMware
products.
Oh
I,
don't
know
how
related
those
are
I'm,
sorry
and
then
there
have
been
a
bit
of
a
start
on
an
act.
A
My
provider
as
well,
so
not
I,
guess
basically
the
the
main
takeaway
there
is
that
there's
not
a
big
push
that
I'm
aware
of
behind
them,
or
you
know,
like
the
T.
The
engineering
team
without
bound
doesn't
have
any
current
plans
of
making
official
writers
for
those
or
things
like
that.
So
that's
that's
what
I
could
say
about
that
now,
but
if
we
can
find
some
links
to
into
those
ongoing
efforts,
then
please,
let's
add
those
to
the
agenda
document
here.
A
So
for
a
little
bit
easier,
discoverability
for
Rahul
and
then
you
know
we
can
kind
of
follow
up
and-
and
you
know,
with
the
community
effort
on
those
providers,
but
there's
not
big
concerted
efforts
that
I
know.
If
this
is
the
real
answer
there.
A
All
right
so
John
I
will
definitely
let
you
take
this
one
about
the
latest
update
about
provider
performance.
B
Yeah
sure
thanks
Eric,
so
last
week
we
we
released
some
tested
images
for
folks
to
play
with
and
Matt
and
Adam,
and
the
community
really
gave
us
a
lot
of
good
feedback.
We
we
picked
up
on
specifically
an
issue
relating
to
authentication
that
we
weren't
catering
for
and
the
team
is
implementing
a
a
whole
bunch
of
you
know
work
around
that
more
more
specifically,
you
know
we're
delegating
some
of
the
authentication
work
down
to
to
the
terraform
layer.
B
Our
initial
tests
have
proven
to
be
successful,
we're
still
just
making
sure
we
cover
all
our
bases
internally
in
QA,
but
we,
you
know
everything
going
well.
We
should
provide
a
new
AWS
provider
tomorrow
for
for
testing
and
then,
if
that
one
goes
well
based
on
the
feedback,
we'll
we'll
do
a
round
of
update,
updated
releases
for
the
official
providers
next
week,
you
know
I
I'll
kind
of
like
a
link
to
some
of
the
latest
summaries
of
performance.
B
Improvement-
and
you
know
these
are-
are
obviously
specific
to
the
the
specific
configuration
we
tested.
You
know
and
they're
they're
very
specific
and
your
mileage
may
vary
based
on
your
specific
environment
and
and
configurations
Etc,
but
we've
seen
significant
Improvement
across
the
board,
and
we
have
various
ideas
that
we've
already
started.
Looking
into
and
Gathering
plans
for
how
we
can
further
improve
this.
You
know
like
when
we
make
the
next
release
with
with
improved
performance.
You
know,
that's
not
the
end
of
the
journey
for
us.
B
We've
got
a
whole
program
ahead
of
us
where
we're
looking
at
at
strengthening
the
quality
and
the
performance
aspects
of
the
providers.
Now
that
we've
got
on
the
coverage-
and
you
know
we'll
we'll
keep
releasing
improvements
going
forward,
so
yeah
look
out
the
the
main
place
where
we'll
announce
early
test
images
that
will
be
in
the
community
slack
Channel.
B
So
have
a
look
there.
If
you
want
to
be
an
early
tester
of
that,
give
us
feedback
and
we'll
communicate
widely,
once
we're
ready
for
folks
to
start
consuming
the
new
providers.
A
Awesome
John:
that
is
definitely
a
good
update
to
share
there
and
then
I
also
wanted
to.
You
know,
extend
a
appreciation
and
gratitude
for
all
the
folks
in
the
community
that
are
continuing
to
help
with
testing
and
you
know
providing
results
and
observations
and
data
from
their
environments
as
well.
That
has
been
very
helpful
to
continue
to
give
us
a
complete
view
of
of
an
invalidation
for
all
the
fixes
and
effort
that
we're
doing
so.
This
has
been
great
to
see
the
community
rallying
around
this
issue
together.
A
All
right
so
John,
you
talked
about
most
all
of
these
issues
here
for
what
the
outbound
Engineers
are
working
on
specifically
right
now,
I
did
want
to
call
out
this
as
well
that
Christopher
Harr
was
received
an
award
recently
for
from
up
on
for
a
care
for
our
communities
award.
So
it's
you
know
all
the
effort
that
Christopher
has
put
into
you
know
God,
like
basically
everything.
A
Your
name's
all
over
the
place,
you're
helping
people
out
on
slack,
constantly
you're.
You
know
obviously
an
important
part
of
the
premier
proprietary
AWS.
You
know
that
you're
everywhere
and
you're
really
having
an
impact
on
the
project
and
with
a
lot
of
people
man.
So
thank
you
very
much
for
all
your
effort
and
success
that
you've
had
in
helping
this
project
Christopher.
So
you're,
awesome
man
thanks.
A
Right
on
man
all
right,
so
then,
let's
move
on
down
to
the
community
topics
section
here,
there's
a
number
of
pieces
of
content
for
folks
to
peruse
and
read
on
their
time.
I
think
that
you
know
there's
an
in-person
Meetup
in
Seattle,
if
anybody's
in
the
Pacific
Northwest
area,
Nick
is
going
to
be
presenting
and
talking
about
cross-plane
there.
A
So
if
you
want
to
do
a
little
face-to-face
action
and
get
to
hang
out
with
Nick
a
little
bit,
you
can
definitely
join
the
this
Seattle
kubernetes,
meetup
group
and
I.
Think
it
is
the
let's
say:
what
day
is
this
March
28th
so
yep?
That
has
not
happened
yet
it's
in
five
days,
let
me
write
that
down
on
March
28th
and
then
also
there
is
a
kubernetes
communities
Day
in
Israel
the
Victor
is
presenting
at
and
I
think
that
was
actually
already
this
morning.
A
So
Victor
may
have
completed
this
task
in
the
past,
and
this
has
already
happened
today,
I
believe
cool
and
then
a
couple
other
blog
posts
and
stuff.
This
is
another
cool
blog
post,
I
assume
that's
in
German,
Christopher
feel
free
to
read
that,
and
let
me
know
if
it
isn't
saying
something.
Good
and
positive.
I
will
take
that
feedback
for
sure,
but
yeah
I,
don't
I,
don't
know
German.
A
All
right,
so,
let's
get
into
the
rest
of
the
updates
here
so
on
the
topic
of
crd
scaling
installing
for
your
crds
there's,
not
a
massive
update
and
a
decision
that
has
been
made
here.
So
the
the
update
here
is
that
Nick
cope
has
been
getting
pretty
deep
now
in
leading
an
investigation
into
all
the
various
proposed
solutions
that
folks
have
thought
of,
and
really
weighing
the
pros
and
cons
of
everything.
So
Nick
has
been
very
deep
in
that
recently.
There's
not
yet.
A
You
know
a
a
a
proposal
that
he
has
of.
This
is
the
direction
we
should
go,
but
when
he
gets
to
that
point,
he
will
make
that
public
and
you
know
folks,
can
weigh
in
on
it
and
provide
some
some
feedback
on
it
as
well.
But
I
just
wanted
to
really
give
the
update
here
that
you
know.
Nick
is
pretty
focused
on
this
and
making
making
progress,
and
this
is
you
know
what
I
what
we
believe
to
be
one
of
the
highest
priorities.
A
We
still
have
so
a
lot
of
progress
still
being
made
on
this
one
and
we'll
hope
to
have
another
update
for
a
you
know.
Proposal
out
sometime
soon.
A
I
wanted
to
also
mention
that
thankfully
stock.crosswind.io
is
back
online
again
so
I
know
a
number
of
people
ran
into
issues
over
I
think
it
was
about
six
or
so
days,
almost
a
full
week
where
slack.cross
plan.io,
the
landing
page
to
get
an
invitation
and
join
the
slack
Community
was
essentially
down.
A
So
the
I
need
to
do
one
final
update
on
this
issue
here
to
to
provide
more
information
about
the
resolution,
but
essentially
the
app
that
we
were
using
to
manage
invitations
for
slack
and
provide
a
self-service
experience
got
way
out
of
date.
It's
not
maintained
anymore
and
then
all
of
a
sudden
started
failing
with
some
certificate
issues
in
in
deprecated
apis
that
it
was
calling
in
slack
and
such
so.
We
spent
a
fair
amount
of
time,
diving
into
that
and
figuring
out
something
to
do
there.
A
When
we
arrived
at
what
looks
to
be
a
decent
experience
in
work
around
for
now
at
least
I,
don't
it
could?
This
could
end
up
being
long-term,
because
the
experience
is
actually
kind
of
good,
where
we
have
a
a
simple
website
that
just
so
you
could
go
to
slack.crosswind.io
with
very
simple.
You
know
nice
URL.
D
A
And
go
to
like
an
official
slack
landing
page
for
for
invitation.
There's
a
couple
of
doubts,
small
downsides
to
that.
But
the
main
point
here
is
that
people
can
self-service
join
the
community
again
to
join
the
slack
again,
and
this
has
been
resolved.
So
nice
updates
there
to
share
on
that.
One.
A
We
will
have
more
to
share
on
this,
because
there
there
will
be
a
big
blog
post
going
out
about
it
tomorrow,
both
on
the
cross,
plain
blog
and
the
cncf
blog,
but
these
Buzz
testing
effort
from
the
cncf
and
adalogics
is
completed,
and
if
you
want
a
preview
of
the
or
not
really
a
preview,
but
it
is
the
the
technical
details
as
much
as
they
you
know
you
can
get
into.
A
We
have
uploaded
Adam
from
analogics
uploaded
the
full
official
report
in
PDF
form
to
the
Cross
plain
repo.
So
if
you
want
to
get
into
all
the
technical
details
of
the
fuzz
testing
effort,
the
bugs
found
all
that
stuff,
it
is
available
on
that
PDF
and
we
will
have
a
more
high
level
summary
blog
post
that
goes
out,
it'll
be
published
tomorrow
morning,
both
on
Crossbay
blog
and
on
the
cncf
blog
as
well.
A
So
we'll
talk
more
about
that
I
think
next
week.
Once
it's
you
know,
all
the
announcements
have
been
made:
Etc,
okay!
So
then
I
we
had
a
topic
here
to
talk
about
promoting
an
environment
config
to
Beta
in
the
1.12
time
frame.
A
I,
don't
think
Max
is
on
the
call
here
today
correctly
if
I'm
wrong,
if
you're
here
Max,
but
there's
been
a
little
bit
of
discussion
with
Max
online
and
slack
about
what
would
need
to
be
done
to
promote
environment
config
to
Beta,
so
I
think
the
call
to
action,
or
the
ask
here
from
everybody
in
the
community
is
for
folks
that
are
using
environment
config.
A
We
would
love
to
hear
any
of
your
feedback
for
things
that
you
think
you
know
essentially
block
its
adoption
or
block
its
usage
or
behavior.
You
would
like
to
see
it
would
be
a
breaking
change
that
needs
to
be
done
before
we
mature
to
Beta.
Essentially
there's
a
couple
things
we've
captured
in
here
in
this
list,
the
the
the
the
bottom
two
of
those
are
not
for
sure
gonna
be
done.
A
There
are
more
ideas
and
I
need
to
sync
up
with
Max
about
you
know
what
we
want
to
implement
and-
and
you
know
what
what
exactly
we're
going
to
do,
but
any
feedback
that
we
get
on
either
hey
this
feature
is
working
great
for
me
or
B.
I
need
to
see
this
this
and
this
in
order
for
it
to
to
continue
maturing,
would
be
very,
very
useful,
so
we
could
take
that
all
into
account
and
continue.
A
You
know
promoting
and
moving
the
environment
config
along
the
maturity
scale.
Yuri
did
you
have
more
specifically
that
you
wanted
to
add
to
that,
while
we're
here.
H
Yeah,
so
there
are
a
couple
of
things,
so
the
the
stuff
works
right
so
basically
like
the
receiving
positive
feedback
from
community,
so
people
are
already
using
it
in
its
current
state.
We
definitely
like
documentation.
That's
about
one
thing.
There
is
also
like
Apache
ordering
some
surprises
when
you
try
to,
if
I
remember
correctly,
patch
from
us
to
a
status
from
environmental
config.
I
already
forget
the
details,
but
it's
documented
there
in
a
in
this
issue.
H
H
Think,
like
from
functionality
standpoint,
is
there
I
heard
the
request
to
enable
environment
config
to
like
we
have
a
patch
type
from
an
Environ
config,
which
is
obviously
like
consuming
environment
config,
and
we
also
have
a
patch
tab
to
environment
config
and
this
patch
type
currently
Works
only
for
in-memory
representation,
meaning
that
we
can
share
the
updates
only
like
kind
of
one
composition,
one
in
stage
the
single
like
instantiation
of
a
claim,
and
it
doesn't
work
for
multiple
claims
like
a
shared
storage
mechanism,
and
if
we
enable
it,
this
will
make
environment
configs
like
seriously
powerful
zobius
concern.
H
H
Yeah,
exactly
so
is
that
the
environment
field
pass
and
currently
patches
only
in
memory
representation.
It
doesn't
update
the
environment,
config
crd
right
in
a
kubernetes
CPA
server
site.
A
Yeah
and
that
one
I
don't
know
if
there's
opinions
from
other
folks
that
have
been,
you
know
utilizing
this
feature,
but
that
that
one's
a
bit
of
a
that
behavior
is
a
bit
of
a
surprise.
For
me
of
that's
not
the
way,
I
would
expect
the
feature
to
work
and
I
can
assume
that
other
folks
would
also
expect
the
same
thing
of
if
I
patch
to
this
environment
config.
Then
it
should
be
persistently
reflected,
and
if
I
did
like
access
it
from
another
composition,
then
it
would
have
that
value
reflected
Etc.
A
So
I
think
in
terms
of
a
principle,
be
surprised
this
that
that
you
would
people
in
general
would
expect
it
to
be
persistently
stored.
That
one
would
seems
like
that
would
be
if
that
were
to
be
done
after
material
debate.
That
feels
like
a
behavior
change,
where
you
know,
that's
that's
something
that
would
be
you
know,
once
it's
codified
or
into
a
matured
API.
That
would
be
feels
like
they're.
Definitely
behavioral
change,
so
I
I
would
say
that
makes
sense.
A
If
we're
going
to
do
that,
because
I
don't
have
the
full
context
on
why
it
was
implemented.
That
way
in
the
first
place,
but
if
we
do
want
to
make
that
change,
yeah
I
would
advocate
for
that
being
before
maturing
to
Beta
as
well.
A
H
So
realistically,
we
should
kind
of
make
a
sequence
so
implement
this
and
Alpha
level
like
patching
in
1.12
and
stabilization
in
some
next
next
release.
Is
that
correct
understanding.
A
Say
it
again:
Yuri
I'm,
sorry,
I
didn't
quite
catch.
The
specifics.
H
A
A
What
can
we
prioritize
and
if
we
do
make
some
changes
like
that,
then
that's
probably
the
time
frame
it
would
take
to
you
know,
keep
it
enough
of
another
release
and
then
mature
and
the
one
that
promote
it
in
the
1.13
time
frame.
But
we'll
we'll
see
the
timelines
on
implementation
there
or
you
know
what
Max's
opinion
is
on
doing
that
implementation
in
the
first
place
and
the
greater
context
here
around
around
the
design
choices.
A
All
right,
so
let
me
make
this
official
as
well,
so
that
it
goes
to
my
inbox
all
right,
but
yeah
the
other
opinions
and
experience
that
folks
have
to
share
about
environment
config.
Please
do
you
know
if
you
have
something
to
to
contribute
right
now
the
floor
is
open,
but
also
otherwise.
They'll.
Add
at
two
three
seven
is
three:
seven:
seven
zero
links
from
the
agenda
doc.
So
we
can
have
it
all
in
one
place.
A
All
right
there
was
I,
don't
know.
I
cannot
remember
at
least
where
this
agenda
item
came
from
I
I'm
sure
someone
suggested
this
that
there
was
a
discussion
that
started
on
slack
from
Blake
around
end
to
end
testing
for
crossbow
interface
providers.
Etc
I
am
not
up
to
date
on
what
like
what
was
included
in
that
discussion,
but
I
would
validate
that.
This
is
a
very
helpful.
You
know
step
forward
for
having
more
Assurance
about
regression.
You
know
avoiding
regressions.
The
quality
levels
kept
up
for
each
release
Etc.
A
E
A
Okay,
so
I
think
that
Blake
had
an
action
item
there
or
had
it
had
had
a
follow-up
to
open
up
some
discussion
with
some
of
his
thoughts
there
I
don't
think
that's
been
done
yet
still,
but
let
me
search
real
quick
to
see
if
there
was
a
discussion
that
got
links
one
seconds.
A
A
H
So
long
story
short,
so
the
question
was
about
end-to-end
testing
of
providers
initially
right
so
and
the
my
viewing
things
that
we
are
really
like,
invested
heavily
in
end-to-end
testicles
of
testing
Associated
pipelines,
but
Nick
proposed
some
more
a
test
cycle
with
that
touches
more
grounds
like
including
the
core
cross
plane
together.
Like
so
that's
some
proposals
that
apparently
resonated
Jason.
You
want
to
add.
D
Yeah
I
was
in
this
thread
as
well.
I
think
we
were
talking
I'm
happy
to
help
where
I
can
I
think
some
of
the
some
of
the
things
from
our
perspective
were
some
of
the
some
of
the
secondary
references
might
have
been
missing,
so
we
were
wondering
like
which
one
of
the
services
were
being
tested
or
used
in
that
they're
all
generated
and
I,
don't
know
which
ones
from
the
object
provider
version
which
ones
were
used
versus.
D
Not
so
we
could
make
sure
we
catch
all
of
those
usability
things
that
make
it
make
it
a
lot
more
usable,
I'm,
happy
to
help
test
help.
Do
whatever
I
can
to
help
move
this
along.
H
Well,
thank
you
so
much,
that's
actually
a
great
point.
So
in
current
state
of
things
we
have
a
test,
a
test
pipelines
and
examples
of
the
directory
right
so
and
the
current
examples
directory
is
mostly
generated,
so
we
tested
it
and
it's
generated
from
my
original
terraform
registry
example
documentation
so
and
we
tested
like
that's
a
source
of
like
it's
our
test,
Suite
as
that's
how
we
supported
the
development
official
provider,
so
it
obviously
doesn't
cover
all
permutations.
H
So
if
you
create
a
pull
request,
that
enable
adds
additional
examples
with
additional
reference
and
we
run
just
test
examples
for
it.
We
validate
that
our
test
is
green.
It
will
be
amazing
contribution
and
it
will
extend
this
regression
test
Suite.
So
thank
you.
I.
A
Yeah,
that's
a
good
point.
Yuri
and
Sean
I,
don't
know!
If
you
have
more
that
you
would
like
to
add
about
the
general
status
of
like
up
up
test.
You
know
integration
up,
test
coverage
for
all
the
the
provided
resources
and
the
beneficial
providers
beyond
what
Yuri
was
just
saying
like
if
there's
a
is
that,
like.
A
Resource
is,
is
tested
and
like
has
a
up
test
run
for
it
or
what's
the
full
coverage
there.
B
Yeah,
so
every
every
resource
that
has
an
example,
configured
and
part
of
part
of
our
kind
of
like
criteria
to
have
a
resource
at
V1
beta1
is
that
it
needs
to
have
an
example
and
it
needs
to
pass
the
intern
testing.
There
are
some
resources
that
we,
you
know
that,
for
various
reasons
like
you
know
whether
it's
elevated
permissions
or
requires
multiple
accounts
or
various
things
that
it's
not
possible
to
easily
at
the
moment
do
into
testing
on,
and
we
do.
B
We
do
have
a
manual
intervention
tag
on
those
where
we've
manually
verified
that
they
work,
but
every
time
there
is
like
we,
you
know
if
we
do
an
upgrade
on
on
the
Upstream
terraform
providers,
and
we
pick
up.
You
know
a
change
on
one
of
these
resources.
Those
all
of
those
resources
are
retested
either
end-to-end
or
manual.
B
We
even
have
some
ideas
with
you
know
our
friend
gbt4
to
to
maybe
help
us
generate
some
more
of
of
those
examples
to
broaden
our
test
Suite
day.
So
there's
various
it's
early
stages,
nothing
concrete!
Yet
you
know
our
immediate
focuses
on
the
performance
stuff,
but,
as
part
of
our
you
know,
strategic
direction
that
we're
looking
at
now
that
we've
got
to
a
coverage
point
that
we're
happy
with
is
is
around
quality
and
performance
and
we'll
we're
also
in
the
process
of
actually
defining
you.
B
What
does
quality
mean
for
the
official
providers
and
we'll
be
sharing
more
of
that
with
the
community
in
the
coming
weeks?.
A
Awesome
John
thank
you
for
sharing
that
definitely
appreciate
that
all
right
and
then
yeah.
So
if
Blake
wants
to
continue
that
conversation
as
well
there
with
the
discussion,
then
we
could
still
follow
up
on
it.
That
way
too,
I
wanted
to
make
a
quick
note
here
that
thank
you,
John
for
taking
the
old
meetings,
And
archiving
them
into
a
separate
documents.
I
think
we
had
had
meeting
notes
from
I,
don't
know
like
2018
or
so
so
this.
A
This
current
meeting
notes
document
was
getting
a
little
unwieldy
with
load
times
and
scrolling
and
stuff
like
that.
Yeah
I
went
all
the
way
back
to
2018
and
it
was
176
Pages.
A
So
John
asked
me
to
do
that
and
I
did
not
follow
up,
and
so
that
would
be
a
great
way
to
get
things
done
when
Jared
doesn't
follow
up,
is
do
it
yourself,
so
excellent
work
there
John
we're
going
ahead
and
creating
that
archive
document
for
all
the
old
meeting
notes
and
note
that
it
is
linked
from
the
bottom
here
as
well.
A
So
if
you
scroll
down
and
you
get
back
into
2022,
there's
a
direct
link
to
see
the
old
meeting
agenda
notes
from
there,
so
nothing's
lost,
but
we
are
below
20
Pages
now
as
opposed
to
107
something.
So
thank
you
for
doing
that.
John.
A
And
I've
lost
the
place
now
there
we
go
okay
and
then
next
agenda
item
here
looks
like
there
is
a
issue
that
has
been
opened
about
in
the
uks
managed
node
group
with
composition
functions.
Yes,
oh
bottle
rocket.
Oh
okay!
Yes
Jason!
You
have
a
context
here.
Yeah.
D
Just
just
really
quick-
and
you
know,
I'm
happy
if
I'm,
hopefully
it's
something
we're
doing
wrong,
but
we're
we're
working
through
this
and
we're
running,
manage
new
groups,
obviously
using
bottle
rocket
and
we
can
launch
containers.
We
can
launch
things
in
Cross
plane,
but
where
will
we
get
stuck
is
when
this
launches
and
here's?
This
is
just
the
error
genetically
some
of
our
team's
helping
with
this
and
what
what
happens
is
it
shows
up
and
it
says
no
space
left
on
device.
D
It's
it's
like
the
wrong
error,
but
it's
it's
having
a
problem,
allocating
the
for
the
the
the
second
container
to
come
down
on
bottle
rocket,
I'm
wondering
if
there's
a
if
there's
a
fix
or
a
way
around
it
or
if
it's
just
a
functional
limitation
of
bottle
rocket.
I,
don't
know
if
someone
in
AWS
I
think
manifold
is
on
the
call
or
follow
us
on
the
college.
But
you
know
any
more
detail
about
that.
It
just
feels
and
it's
very
specific
to
Amazon
but
again,
I
think
it's
also
kind
of
important
yeah
face.
E
The
same
issue
today
in
our
installation-
it's
not
possible
to
use
at
the
moment,
but
yeah
I
I,
will
have
more
look
tomorrow
if
I
have
more
time
what's
the
issue,
but
that's
exactly
the
same
that
you
have
foreign.
H
A
Yeah
so
I
think
this
at
least
warrants
Jason
at
least
warrants
in
a
deeper
investigation
into
you
know
the
the
machinery
and
the
mechanics
that
the
the
current
composition,
Runner
composition,
function,
Runner
does,
in
order
to
you,
know,
set
up
the
environment
to
execute
the
function,
and
you
know
the
capabilities
it
needs
to
do
that
Etc
and
then
the
constraints
that
you
know
a
more
locked
down
environment
like
bottle
rocket
might
have
is
at
least
more
into.
A
To
see
if
there's
you
know
a
way
to
make
the
functionality
work
in
this
type
of
environment
as
well,
I
know
that
at
least
in
the
initial
Alpha
implementation
you
know
that's
focused
on
getting
it
working
for
a
broad
range
of
environments,
but
you
know
this
is
definitely
a
classic
example
of
you
know,
like
of
of
you,
know
more
lockdown
environments
and
things,
your
capabilities
that
are
needed
or
assumed.
E
A
Be
present
not
being
there
in
those
environments,
so
I
don't
think
we
have
an
answer
for
this
right
now,
but
I'd.
D
A
Yep
and
then
Jason
you,
it
looks
like
you
did
also
added.
You
know
like
to
then
track
this
in
the
composition
functions
the
beta
issue
as
well,
then
right,
cool,
yep,
that's
a
great
place
to
put
that,
so
we
don't
lose
track
of
this
one
and
then
Christopher.
If
you
do
end
up
looking
into
this
more
and
add
and
find
more
observations
and
stuff
feel
free
to
to
add
that
as
well
and
then
also
any
of
the
Amazon
folks.
A
You
know
that
are
on
the
call
now
or
maybe
you
know,
have
an
opportunity
to
provide
Insight
on
this.
One
I
know
Malibu
and
Carlos
are
on.
If
you
guys
have
some
insight,
we're
always
welcome
that
as
well
too
yeah.
C
I'll
take
a
look
yeah
annoying
such
right
now,
but
yeah
good
to
catch
this
type
of
problems
in
constrained
environments.
A
Do
that
cool
all
right,
everybody
so
I
think
that's
the
full
set
of
things
that
were
in
the
agenda
documents.
I,
don't
see
anything
else
in
the
chat.
So
are
there
any
other
topics
that
folks
want
to
bring
up
before
we
adjourn
for
the
week.
G
G
We
came
across
a
it's
an
interesting
problem
where,
if
manage
node
group
of
one
cluster,
somehow
that
name
of
node
group
is
taken
to
some
other
cluster,
it
is
overriding.
The
cluster
contact
context
itself.
It
is
overriding
it
is
trying
to
recreate
the
node
group
or
delete
the
notebook
of
the
existing
cluster.
This
is
the
issue
which
I
faced
I,
think
I'll
I'll
create
a
issue
itself
when
GitHub
that
will
be
much
more
better
with
proper
context,
but
yeah.
G
A
Yeah
awesome
thanks
thanks
for
sharing
that
experience
there
did
you
did
you
say
arvind
that
there
was
already
an
issue
that
was
tracking,
that
that
was
open
or
there's
no
issue.
G
A
Awesome
yeah
that
sounds
perfect.
Then,
like
any
context-
and
you
know
observations
you
can
add
to
an
issue,
then
they
can
follow
up
with
it
there
but
yeah
thanks
for
for
sharing
that
and
then
thanks
for
you
know
being
able
to
join
today
as
well.
Thank.
G
A
Thank
you
all
right.
So
then,
if
that's
everything,
then
we
can
go
ahead
and
adjourn
for
the
day
and
while
I
hold
my
dog,
so
she
doesn't
bark
as
much
there's
there's
a
package
that
was
just
delivered
but
yeah
great
to
see
everybody
this
week
and
we'll
keep
following
up
on
everything
for
for
1.12
and
providers
and
all
that
stuff
too
cheers
thanks
thanks.