►
From YouTube: 2023-05-18 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
May
18th
2023
cross,
Blaine
community
meeting.
So
the
agenda
Doc
is
open
for
everybody
to
add
any
topics
that
they
want
to
I'm,
going
to
go
ahead
and
drop
a
link
to
the
agenda
doc
within
the
zoom
chat
here,
so
that
folks
can
directly
access
the
doc
and
start
adding
any
suggestions
for
what
they
want
to
be
talking
about
today
and
adding
today.
A
I,
don't
think
we
have
a
super
heavy
agenda
to
go
through
today,
so
there's
definitely
some
room
for
folks
that
want
to
add
anything
that
they
that
they
want
to
and
Dan
we
should
get
you
edit
permissions
on
the
doc
again
looks
like
you're
only
adding
suggestions,
so
we
should
definitely
get
you
some
edit
permissions
again,
my
friends
as
a
maintainer
of
the
project,
all
right
cool.
So
the
last
meeting
we
had
was
on
May
4th
in
my
absence,
Jean
drove
the
meeting
and
the
agenda
for
me.
A
So
thank
you
for
taking
care
of
that.
John
I.
Do
appreciate
that,
since
that
meeting
there
have
been
no
releases
like
patch
releases
or
minor
releases
of
the
crossbank
project
or
crossfang
runtime,
so
I
think
we
could
skip
over
that
and
move
into
discussion
for
for
1.3.
So
I
think
we're
about
one
third
of
the
way
through
the
life
cycle
for
the
1.13
Milestone.
A
We
are
about
one
month
in
from
from
the
1.12
release
and
then
at
the
end
of
July
is
when
we
were
scheduled
to
do
1.13
so
we're
about
one
month
in
out
of
three
months
so
still
still
somewhat
early,
but
starting
to
pick
up.
Some
momentum
I
think
that
there
are
a
number
of
things
that
are
in
flight
or
going
to
be
focused
on
I.
A
Myself
have
been
out
of
the
office
for
at
least
two
weeks
now,
maybe
more
than
that
including
Amsterdam
coupons,
so
I'm
a
little
bit
out
of
touch
so
I'll
be
leaning
on
folks
a
little
more
heavily
today
than
normal
I
think.
But
let's
go
ahead
and
for
the
1.13
Milestone
here.
Let's
take
a
look
at
the
at
the
1.13
board.
Actually,
Let's
do
let's
look
at
the
high
level
road
map.
It
looks
like
the
Scott's
chopped.
Somehow
we
can
maybe
deal
with
that
later.
A
Okay.
So
let's
look
at
the
road
map
first
and
so,
let's
look
at
the
1.13
problem
and
so
I
think
there's
a
number
of
things
that
are
have
been
moved
into,
one
of
that
13
or
B
areas
of
focus.
Well,
not
13.,
I
think
it
is
still
yet
to
be
seen
exactly
what
will
be
delivered
by
finished
within
this
Milestone.
Some
of
these
things
will
be
starting
with
designs
or
starting
with
some
initial
foundational
efforts
for
it.
A
So
I
think
that's
one
thing
that
I
would
like
to
improve
about
the
roadmap
and
I've
heard
this
feedback
before
as
well
of
making
it
more
clear
when
you
look
at
the
variable
what
will
be
delivered-
and
you
know-
finalized
within
the
given
Milestones
here,
but
we
have
a
number
of
things
that
are
all
that
are
already
part
of
we're,
not
13
or
any
efforts
are
going
on
there.
A
So
I
think
we'll
talk
completely
about
the
full
effort
for
installing,
through
our
crds
and
no
longer
equipping
the
API
server
when
providers
are
installed
in
Cross
plain
that
will
have
a
special
section
on
that
entirely.
So,
let's
skip
over
that
note-
and
we
have
talked
in
the
past
about
continuing
to
mature
and
advanced
composition,
functions
and
environment
configs.
So,
let's
see,
if
there's
things
that
have
not
been
talked
about
before
that
should
maybe
be
mentioned
here
so
and
John
you.
A
You
know
what
was
talked
about
last
time,
so
maybe
internet
integration
testing
is
that
something
new
to
mention
and
kind
of
give
a
little
bit
talking
about
the
what
the
status
is
or
what
we're
doing
with
that.
B
No,
we
talked
about
all
of
these
things
last
time
as
a
as
a
quick
reminder,
you
know:
end-to-end
integration,
testing,
We've
busy
working
on
a
proposal
for
that,
so
lavro
and
predrack
is
evaluating
a
whole
bunch
of
different
Frameworks
and
tooling
to
just
and
probably
about
a
week
or
so
away
from
putting
a
proposal
out
there
we're
continuing
to
to
expand
on
the
schema
where
composition,
validation
and
Philippe
continues
to
add
more
more
coverage.
B
There
we're
pretty
much
close
to
to
that
and
then
with
the
proposal
for
the
ignore
changes,
functionality
is
getting
close
to
completion
lover,
I,
don't
know
if
you
went
I
know,
there's
been
some
last
a
few
conversations
over
the
last
few
days.
I
don't
know
if
you
want
to
give
a
quick
summary
of
what
the
outstanding
kind
of
like
decision
points
are
on
that
proposal.
C
Yeah
so
I
already
thought
that
we
are
wrapping
it
up
and
we
have
it
ready,
but
there's
still
some
concerns
about
how
the
management
policies
will
interact
with
the
deletion
policies,
especially
the
observe
only
one
which
makes
you
know,
have
you
observony
and
then
having
a
deletion
policy
delete,
seems
kind
of
counterintuitive.
So
we
have
some
discussion
going
on
around
this
still.
So
if
anybody
has
some
feedback
for
sure
Nick,
you
can
check
it
and
yeah
I
I
hope
soon,
we'll
be
able
to
come
to
some
conclusion
and
pick.
E
C
Yeah
there's
some,
like
you
know,
points
that
Hassan
made
that
could
cause
some.
You
know
like
like
having
a
I
mean
I
won't
go
into
details,
but
yeah
there's
still
some.
If
you
could
take
it,
it
would
be
great
and
as
you
comment
there,
your
thoughts,
maybe
maybe
we
are
overthinking
events
are
too
cautious.
Maybe
it's
also
that.
A
So
something
then
that
I
wanted
to
call
out
specifically
as
well,
is
that
you
know
with
the
effort
to
mature
composition,
functions
and
environment
configs.
If
you
look
at
both
of
these
issues
here,
they're,
you
know
more,
like
epics,
with
a
task
list
of
known
things
that
we
want
to
at
least
look
into
when
considering
how
to
mature
these.
A
These
currently
Alpha
level
features
something
that
is
helpful
is
well
two
things
actually
one
is
that
getting
an
understanding
for
people
if
you
have
strong
opinions
or
or
desires
for
particular
issues
of
of
this
lift
here
that
are
very
important
than
other
ones.
A
Do
let
us
know
so
we
get
that
feedback
and
understand,
what's
the
most
important
things
to
do
to
successfully
mature
these
features
and
make
sure
that
they're
usable
for
folks
and
then
I
know
at
least
like
I
said,
with
both
of
them,
both
composition,
functions
and
environment
configs.
We
have
been
getting
good
participation
and
support
from
contributors
within
the
community.
A
So,
if
folks
want
to
tackle
some
of
these
sub
tasks-
and
you
know
Implement
them,
then
that's
something
that
you
know
folks
are
already
doing
and
will
certainly
continue
to
encourage
for
being
a
community
effort
to
continue
maturing.
These
features
too.
A
Let's
do
a
quick
look
thin
at
the
1.3
sorry
1.13
board
as
a
whole.
A
I
think
this
may
be
a
little
bit
out
of
date,
so
I
would
ask
contributors
to
the
project
if
there's
things
that
you're
working
on
or
pull
requests
that
are
open,
if
you
can
make
sure
that
they're
updated
on
this
board
as
well,
and
if
you
have
any
access
permissions
or
issues
with
that
do.
Let
me
know
also:
is
there
anything
on
this
within
1.13
scope
that
folks
want
to
bring
up?
D
Yeah
I
was
just
about
to
move
the
well
I,
don't
know
if
it's
technically
in
design,
since
the
pr
is
not
open
yet,
but
for
the
PRI
last
week
for
folks
who
weren't
here
or
two
weeks
ago
for
folks
who
weren't
there,
we
there's
a
PR
open
to
expand
the
controller,
config
and
I
kind
of
push
back
a
little
bit
on
doing
that
since
it's
deprecated
right
now.
D
D
One
was
a
and
you
know,
on
my
part,
getting
a
design
doc
up
for
provider,
runtime
interface,
which
I
currently
have
in
progress
and
hope
to
have
open
next
week
and
then
some
work
from
folks
around
mutating
web
folks
or
using
something
like
iverno
to
mitigate
the
intermediate
use
cases
that
folks
have
so
that's
kind
of
top
of
Mind
Focus.
For
me,
right
now,
I
think
Hassan
has
kind
of
taken
the
lead
on
some
of
that
revision,
resource
ownership,
stuff.
D
So
I'm
kind
of
just
reviewing
his
work
on
that.
At
this
point,.
A
Awesome,
let
me
do
that
on
my
other
screen,
because
this
is
a
should
be
at
least
a
GitHub
that
I'm
not
signed
into
and
specifically
on
purpose.
So
let
me
try
to
do
it
other
screen
and
that's
the
yeah
approved
resource
transition
ownership.
That's
in
probably
in
progress
then
Hassan
yeah.
A
Well,
let's
see
if
they
refresh
the
board,
because
I
just
moved
here
we
go
so
it
sounds
like
Dan
that
the
provider
runtime
interface,
that's
something
that
InDesign
now
you're
kind
of
like
working
on
the
design
doc
there
it's
not
necessarily
available
for
review,
but
that's
something
you're
thinking
through
sketching
things
out,
trying
to
come
up
with
proposal
there
and
then
Hassan
is
working
on
some
practical
implementation
stuff
around
improving
the
research
resource,
ownership,
transition,
stuff,
yeah.
A
Well,
yeah
that'd
be
probably
good
if
his
son's
working
on
that
to
have
have
them
there
too.
Okay,
that's
great,
because
those
are
I
know.
3742
has
come
up
in
a
couple
different
Avenues
or
channels
recently,
and
it
would
be
great
to
have
continued
investment
there
to
make
that
more
robust
and
improve
their
increased.
You
know
already
decent
reliability.
A
It
does
have
but
making
it
even
harder,
especially
as
you
know,
providers
pop
up
too
so
I,
like
the
the
effort
that
we're
doing
okay,
other
things
that
are
on
the
board
for
1.13
anything
anything
else
that
anybody
on
the
call
here
wants
to
add
as
a
as
something
in
progress
or
questions
on
1.13.
A
Okay
cool,
so
then
we
can
go
ahead
and
move
on
then
now
that
we're
done
talking
about
1.13
and
let's
move
on
down
into
providers
as
well,
then
so
Jean.
Do
you
want
to
kind
of
take
this
section
here,
for
you
know
giving
us
an
update
on
the
providers.
I
think
maybe
folks
can,
on
their
own
time,
click
through
the
different
versions
there
and
release
notes
Etc,
but
getting
on.
B
Yeah,
so
the
just
on
the
the
abound
providers
for
AWS,
gcp,
Azure
and
Azure
ID,
one
of
the
biggest
changes
was
just
we
bumped
them
up
to
the
latest.
Terraform
providers
so
they'd
be
there
will
be
new
resources
that
can
be
added
new
fields
and
Bug
fixes
Etc,
and
then
there
was
some.
You
know
smaller
bug
fixes
Etc
in
them
in
terms
of
the
the
kind
of
like
what
we're
referring
to
as
provider
families.
B
So
we've
now
released
made
available
for
testing
some
release
candidate
images
to
help
specifically
with
the
problem
of
crd
scaling.
So
right
now,
for
instance,
if
you
install
the
Azure
or
AWS
provider,
it
installs
over
900
crds
and
can
be
pretty
crippling.
So
with
the
the
new
approach,
you
can
dramatically
trim
that
on
and
we've
seen
some
some
positive
feedback
from
from
some
of
our
customers
who
are
trying
this
out.
You
know
one
person
reported
I,
think
it
was
Cube
control.
You
know
calling
a
get
managed.
B
You
know
where
it
would
take
two
minutes
previously
returning
in
something
like
20
seconds
now,
so
that's
some
positive
feedback
that
we've
received
so
far.
B
We're
currently
focused
on
you
know
further
testing
and
validation,
but
then
also,
specifically,
you
know
evaluating
you
know
the
migration
process
from
the
monolith
to
the
to
the
smaller
providers,
and
you
know,
if
anybody's
interested
in
in
trying
it
out
there's
a
document
with
some
details
on
on.
You
know
what
they
are,
how
it
works
and
what
you
should
be
doing,
and
then
there's
also
some
instructions
on
how
you
can,
if
you're,
already
kind
of
like
running
the
the
monolith
provider
in
an
environment.
A
And
John,
if
I
correctly,
if
I'm
wrong
but
I,
believe
this
dock
here
was
shared
within,
like
the
announcements
channel
on
the
slack
workspace.
Also
right.
So
that's
already
gotten
a
bit.
A
Distribution
than
just
being
announced
in
this
community
meeting
right,
correct,
awesome,
good,
yeah
and
I
think
this
is
especially
helpful
to
help
folks
understand.
You
know
what
it
is
like
what's
being
changed
here,
how
to
use
it
the
benefits
of
it,
immigration
to
be
able
to
consume
it
all
that
sort
of
stuff-
and
this
is
a
great
time
now
in
terms
of
a
practical
perspective
of
trying
it
out
getting
feedback.
You
know
making
sure
that
your
experiences
is
heard,
and
things
like
that.
A
So
you
know
this
is
a
pretty
big
effort.
That's
you
know
took
a
lot
of
consensus,
so
it
took
a
lot
of
discussion
Etc
and
is
coming
together
now
and
and
providing
very
soon,
very
tangible
benefits.
So
I
think
a
lot
of
folks
worked
very
hard
on
this
and
I'm
really
happy
to
see
where
it
is
so
far.
B
No
I
mean
we'd,
appreciate
anybody,
trying
them
out
and
sharing
any
feedback
you
have
specifically,
if
you
run
into
Pro
problems,
but
also
positive
feedback,
is,
is
helpful
to
hear
if
everything
goes
well.
We've
got
a
provisional
Target
date
of
the
13th
of
June
to
go
ga
with
them
and
at
that
point
will
also
be
introducing
changes
to
the
marketplace.
Ui
to
accommodate
the
new
provider,
family
structure.
A
Sweet
all
right
did
you
want
to
take
it
to
the
next
section,
as
well
as
usual,
yeah.
A
Sounds
good,
okay,
so
then,
let's
move
on
into
the
community
topics
section
here
then
so,
as
usual,
we
put
together
a
set
of
recent
content
from
the
prospain
project.
You
know
podcasts
and
blogs
and
all
sorts
of
stuff.
So
a
couple
cool
things
to
read
here.
Our
watch
as
it
may
be
so
feel
free
to
click
into
all
of
these
links
here
and
check
out
anything
that
may
be
of
interest
to
you
and
if
you
have
anything
that
you've
written
or
you
know
published
or
anything
about
cross
plain
feel
free
to.
A
Let
us
know
about
that
as
well,
and
we
can
add
it
to
this
list
and
always
happy
to
you
know,
share
things
from
the
community
that
you're
writing
and
Publishing
Etc
on
the
various
channels
and
Twitter
and
slack,
and
all
that
stuff
too,
so
just
always
reach
out.
If
you
have
something
that
you've
produced
that
you
want
us
to
share
Pete
I,
believe
this
was
you
my
friend
about
a
proposal
of
dropping
versions.
A
It
was
in
the
backlog,
but
it
didn't
have
a
name
so
I,
but
I
think
that
was
new.
Is
that
correct?
My
friend?
That
is
thank
you
all.
F
So
today
we
maintain
the
current
supported
versions
in
documentation,
so
everything
gets
duplicated
into
a
folder.
It
has
its
own
unique
subdomain,
there's
a
little
version
drop
down
on
the
dots.
If
you
want
to
go
to
the
docs
really
quick
chair
just
to
make
sure
everyone
knows
what
we're
talking
about,
go
ahead
and
click
on
user
docs
on
the
left
and
so
we're
on
V
1.12
and
there's
this
pretty
little
drop
down.
We
change
this
with
every
release,
as
we
EOL
you
know
is
1.13
comes
out
we'll
EOL
1.10.
F
We
remove
that
old
version
of
the
docs
so
effectively.
What
I'm
proposing
is
flattening
this
and
so,
instead
of
having
versions
here,
we
just
have
the
docs,
which
we
see
in
a
lot
of
other
products.
F
The
big
things
that
we
would
have
to
be
extremely
mindful
of
is
one
introducing
a
changelog
which
will
happen
independent
of
this
proposal
so
that
we
can
see
what
things
are
happening.
What's
new,
what's
changed
between
releases
and
that
will
be
not
only
cross-plane
releases,
so
it
will
mirror
some
of
the
cross-plane
release
notes,
but
also
just
updates
and
changes
to
the
docs
as
well,
and
then
two
within
a
given
page
making
sure
that
of
we
clearly
indicate
when
a
feature
was
introduced,
deprecated
or
removed.
F
I
don't
know
if
anybody
has
any
initial
thoughts.
You
know
looking
for
feedback
in
The
Proposal
on
the
issue
itself,.
A
Yeah
Pete,
I
I
think
there's
probably
very
oh
yeah.
This
looks
like
Nick
has
weighed
in
with
some
some
opinions
on
it
I.
You
know
I'm
kind
of
catching
up
on
a
lot
of
things,
and
so
I
have
not
read
through
this
in
this
entirety.
But
you
know
my
initial
instincts
around
it.
Maybe
maybe
are
the
same
of
what
I
would
guess.
Nick
might
say,
is
you
know
as
it's
hesitancy
or
concerns
about
hey?
A
You
know
when
things
change
or
you
know,
there's
a
new
feature
here
or
this
thing
was
different
in
a
different
version.
So
having
the
docs,
you
know
live
alongside
the
version
so
that
they're
always
exactly
matching.
You
know
the
the
truth
at
that
point
in
time
is
typically
a
good
thing,
but
I
do
see
that
you've,
you
know
kind
of
at
least
had
some.
You
got
some
headers
here
around
addressing
addressing
that,
and
you
know
thinking
through
that.
F
And
I'm
not
looking
for
a
resolution
on
call
today,
but
just
wanted
to
bring
it
to
you.
All's
attention,
you
know
have
have
folks
bring
their
their
thoughts
or
concerns
around
around
here
as
well.
A
Nick
was
there
some
of
your
feedback?
That
would
be
at
least
where
you're
thinking
about
it.
Now
that
would
be
useful
to
summarize
right
here
in
this
discussion.
E
No
I
same
as
you,
my
intuition
is,
but
this
is
not
how
I
would
do
it,
but
my
comment
on
this
was
more
than
a
week
ago
and
I'm
just
rereading
it.
A
load
of
the
state
now
so
I
think
I
could
have
a
productive
conversation
of.
C
A
All
for
me
thanks
here
and
Pete.
What's,
if
you
can
you
kind
of
talk
through
some
of
the
the
your
thought
process
around
this?
If
you
like,
do
you
have
like
a
top
number
one
reason
for,
for
you
know,
the
proposal
here
is
like
what's
the
biggest
problem
that
you
want
to
solve.
Is
that
is
this
an
order
of
priority
here
or.
F
What
kind
of
I
I
think
it's
number
one
is
searching:
bookmarks,
not
just
Dal
Golia
on
Page
search
but
Google
search,
especially
when
new
versions
comes
out.
It
takes
it
takes
those
search
indexes
like
you
know,
one
two,
three
weeks
to
catch
up,
so
you
always
end
up
getting
Google
search
results
for
older
versions
or
possibly
even
removed
versions,
and
also
because
the
version
is
part
of
the
URL.
F
Your
bookmark
will
eventually
break
when
we
EOL
that
that
version
of
The
Talk,
those
those
are
the
two
big
things
and
I
think
the
other
one
is.
It
allows
us
to
flatten
a
lot
of
the
content
that
is
split
between
the
knowledge
base,
which
is
kind
of
version,
independent,
stuff
and
call
like
the
user
docs
or
the
configuration
guides,
which
are
more
version
dependent.
A
I
see
I,
see
you're
talking
about
that
yeah,
at
least
with
the
URLs
and
search
results
and
stuff.
I.
Think
that
so
with
the
search
results
within
the
docs
I
noticed
when
I
was
using
the
docs
recently
that
you
did
make
an
improvement
there
to
only
show
like
latest
version,
essentially
right
in
the
search
results,
and
that
already
did
seem
like
a
tangible
step
forward.
In
terms
of.
D
A
Experience
around
search
results
within
the
docs,
so
kudos
to
that
and
I
think
that
that
did
solve
at
least
some
of
this
yeah
some
percentage
of
these
problems
right.
So
that
was
really
yeah
and.
F
I
agree
with
that
and
I've
done
some
work
to
try
to
work,
to
try
to
improve
the
indexing
with
surgeons
as
well,
but
really
a
lot
of
that's
coming
at
the
expense
of
ignoring
the
older
stuff.
So
just
not
indexing
the
non-latest
version.
A
Oh
got
it
and
you
know,
and
so
that
kind
of
leads
me
to
also
make
a
specific
mention
as
well.
Is
that
with
each
release,
one
of
the
tangible
steps
that
we
do
is
in
the
release
process
is
to
add
a
what
is
it
a
Content
removal
request
to
Google
for,
like
the
version
that
we
just
sunset
or
just
just
went
out
of
of
you
know
our
maintenance
window.
A
So,
for
instance,
like
a
glass
release,
we
I,
you
know
I
added
a
request
to
Google
within
the
Google
search
console
to
remove
1.9
and
do
not
show
that
anymore.
One
thing
we
could
consider
is,
you
know,
have
Google
only
show
the
latest
so
like
we
would
say,
nope,
don't
do
1.10
or
1.11,
either
just
true
1.12
right
now
in
terms
of
Google
search
results,
so
that
could
be
a
further
Improvement
to
make
that
better
for,
like
Google
search
results
and.
F
That's
one
of
the
things
we've
done
so
we
actually
had
a
hidden,
slash
latest
set
of
the
docs
and
only
slash
latest
gets
indexed.
A
If
it's
working,
okay,
it'll
be
interesting
to
see,
then
like,
if
you
have
good
results
from
that,
okay,
cool,
okay,
cool!
Yes!
Well,
thanks
for
bringing
that
up,
Pete
and
if
folks
have
further
opinions
on
it,
then
it
looks
like
there
already
is
a
discussion
going
on
here.
So
we
can
continue
continue
along
with
the
discussion
here
as
well:
cool
all
right,
okay
and
then
a
there
were
no
other
specific
agenda
items
that
were
at
or
PR's
that
need
attention.
A
A
Okay,
well,
if
there
weren't
other
things
that
folks
wanted
to
add
to
the
agenda
then
looks
like
we
could
adjourn
a
little
bit
early
here
and
get
folks
back
some
time.
A
All
right
well
good
to
see
everybody,
and
maybe
next
time,
Dan
we'll
see
you
with
with
the
buzzed
hair.
Maybe
not,
though,
we'll
see
how
you
resolve
that
situation.