►
From YouTube: 2023-08-10 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
August
10th
2023
crosswind
community
meeting
right
now,
I
will
go
to
the
chat
and
I
will
drop
a
link
directly
to
the
agenda
document.
So
if
you
have
any
topics-
or
you
want
to
add
yourself
as
an
attendee
here,
then
you
are
more
than
welcome
to
do
so
and
we'll
get
to
everything
on
the
agenda
today.
A
So,
let's
start
with
recent
releases,
so
I
think
on
the
day
of
the
last
community
meeting
we
put
out
the
we
released
the
1.13
Milestone,
so
that
was
on
the
day
of
the
last
community
meeting
since
then,
we've
done
two
patches
to
it,
so
I
did
want
to
call
those
out
because
they,
both
of
them,
had
a
common
theme
and
something
a
little
bit
of
a
lesson
that
we
learned.
So
when
we
put
out
1.13.0,
we
got
a
notice
for
for
folks
that
were
trying
to
upgrade.
B
A
They
some
of
them
are
running
into
issues
with
the
init
container
of
the
Crossland
pod
not
being
able
to
get
all
of
the
crds
installed
and
running
Etc,
and
so
we
noticed
that
there
there's
an
issue
with
the
composition,
revisions,
API
and
removing
an
old,
an
old
version
of
it
and
being
able
to
handle
the
migration
or
upgrade
in
place
process
there.
A
So
we
learned
a
little
bit
of
a
lesson
from
that
and
we
got
a
fix
out
in
1.13.1
that
will
just
automatically
take
care
of
that
for
you.
So
we
have
a
pattern
in
place
now,
that's
if
a
very
old
version
of
a
crd
is
removed,
that
we
just
upgraded
in
place
and
it's
you
know
not
it's.
It
tended
to
be
completely
non-impactable
to
the
cluster
and
keep
the
cross
plane
running.
A
So
we
got
that
in
place
and
then
also
then,
after
unblocking
that
then
we
learned
as
well
that
the
same
thing
was
true
for
the
old
locks.
Api
I
think
this
one
was
much
less
of
a
scope
of
affected
folks,
but
it
was
still
important
to
go
ahead
and
fix
that
one
as
well,
but
with
the
pattern
already
in
place
from
the
with
reusable
code
from
1.13.1.
A
That
was
actually
quite
easy
to
do,
and
so
you
know
the
special
thanks
to
chiffon
and
Philippe
and
folks
that
were
investigating
into
that
and
getting
a
fixed
out
for
that.
But
so
that's
where
we
have
landed
now
is
1.13.2
is
the
obviously
the
recommended
version
to
be
running
from
the
1.13
Branch.
So
that
is
the
latest,
and
that
is
the
one
that
you
know,
especially
if
you
are
upgrading
from
previous
versions
of
cross
plane
that
you
go
ahead
and
just
go
straight
to
1.13.2
as
opposed
to
trying
1.13.0
or
1.
A
there's
a
bit
of
additional
functionality
added
in
those
patch
releases
as
well
or
fixes.
That
is
but
the
the
migration
thing
was
by
far
the
most
important
thing
to
call
out
I
believe
we
also
did
a
couple.
Recent
releases
of
the
Cross
plane
run
time
as
well.
They
do
not
off
the
top
of
my
head.
Remember
the
importance
of
those
okay,
yeah,
there's,
essentially
a
simple
fix
that
was
put
into
that
that,
as
cube
is
driving,
so
those
are
available
as
well,
both
for
the
dot
20
and
the
dot
19.
A
minor
releases.
So
yes
for
cross-spinning
core
in
the
runtime,
those
are
all
the
recent
releases
we've
had
since
the
last.
A
Meeting
so
then
we
can
jump
on
into
the
current
Milestone
that
we
are
making
progress
on
and
we're
very
early
in
the
cycle,
but
we
are
ready
to.
We
have
started
working
on
1.14,
so
let's
do
a
quick
recap
for
everybody
here
on
the
roadmap
that
we
have
for
1.14.
So
I
will
follow
up
to
go
ahead
and
close
out
or
remove
from
this
view,
1.13,
because
that's
shipped
everything
is
done,
that's
all
well
and
good,
and
so
1.14.
A
We
are
starting
on
in
Earnest
here
and
making
a
lot
of
progress
early
in
the
Milestone
here.
So
let
me
check
to
see
who
is
on
the
call,
because
I
did
want
a
couple
updates
since
we're
getting
kicked
off
in
the
Milestone
here
and
we're
actually
making
progress
so
I
see
both
that
Hassan
is
on
and
Nick
is
on
as
well.
So
I
wanted
to
check
in
with
folks
just
to
kind
of
get
a
bit
of
an
update
on.
You
know
the
as
we're
starting
the
1.14
Milestone
here.
A
I
want
to
get
a
bit
of
an
update
on
the
high
level
Direction
and
what
we're
hoping
to
accomplish
in
this
milestone.
For
each
for
some
of
these
important
features
here
so
Nick,
if
you
are
available
to
kind
of
just
give
a
quick
overview
of
what
we're
going
to
accomplish
or
what
we
want
to
focus
on
for
composition,
functions
in
1.14.
That
would
be
very
helpful.
D
Yeah
there
was
a
design
sort
of
great
context,
I'm
just
getting
back
for
vacation,
so
I've
been
out
for
a
couple
of
weeks,
but
just
before
I
left
about
three
weeks
ago,
we
merged
a
design
for
an
iteration
of
composition
functions.
So
we
expect
to
basically
change
the
way
it
works.
A
little
bit
still
kind
of
solve
the
same
problems
probably
do
the
same
thing,
but
it
will
change
a
bit
in
1.14,
so
broadly
the
major
goal.
D
The
first
major
goal
is
to
implement
that
and
we'll
go
into
details
now,
but
basically
functions
will
be
long.
Running
and
most
functions
will
run
as
pods
I'll.
Add
a
link
to
the
Community
agenda,
doc
design
for
anyone
who
wants
the.
D
So
there's
going
to
be
a
reasonable
amount
of
work
to
to
get
that
built,
then,
on
top
of
that,
we
also
want
to
have
at
least
one
kind
of
generic
composition
function
available.
We
think
that's
probably
going
to
be
a
structure
that
lets
you
use
gojap,
leading
to
to
specify
to
configure
composition
in
crossblade.
We
also
want
to
have
one
language
SDK
to
build
your
own
functions.
D
A
All
right,
sweet
and
then
Nick,
you,
you
and
phillipineski-
are
kind
of
the
the
team
focusing
on
the
composition.
Functions
in
1.14
is
that
right.
D
I
think
so,
I
I
don't
know
exactly
I
have
seen
Philly
but
Esky
work
on
it,
I'm
pretty
sure
John
would
be
the
authority
one
for
that.
I'm
pretty
sure.
That's
right,
though,.
A
Cool
awesome
and
welcome
back
by
the
way
as
well.
You
you
were
missed
by
everybody.
Thanks,
awesome,
okay
and
then
Hassan
I
wanted
to
check
in
with
you
as
well,
because
I
know
you
had
started
implementation
on
order,
deletion
and
usage
tracking
and
stuff
like
that.
So
I
definitely
wanted
to
check
in
with
you
on
where
that
is,
you
know
any
sort
of
blockers
or
what
you
expect
in
1.14.
E
Yeah
sure
so
basically
there
is,
there
is
an
open
PR
for
that
which
is
ready
for
review.
There
were
just
like
couple
of
tools
that
I
am
like
taking
care
of
in
parallel,
but,
as
I
said,
like
the
pr
is
ready
for
you
and
I'm.
I
have
been
mostly
working
on
the
end-to-end
testing
Etc,
which
should
not
block
the
review
process.
E
So
far,
there
is
no
blocker.
There
was
one
issue
that
we
couldn't
find
a
perfect
solution
yet,
which
is
the
the
garbage
collectors
reaching
to
like
like
long
long
too
long
back
of
times
we
we
have
been
collaborating
on
that
together
with
Bob.
We
just
had
the
like
special
interest
group
meeting
just
before
this
one
and
we
are
trying
to
like
different
approaches.
E
We
couldn't
find
it
like
perfect
solution,
yet
as
I
said,
but
we
agreed
that,
like
this
shouldn't,
be
a
Blocker
on
the
feature
itself.
Like
the
teacher
this,
this
will
most
probably
be
more
like
a
ux
problem
for
for
certain
scenarios,
especially
when
nested
compositions
are
used
and
nested
Composites
are
used
and
combined
with
a
foreground
deletion
policy.
So
so
far
there
is
no
brokerage.
Once
the
PR
is
approved,
review
then
approach.
We
can
get
this
feature
in
and
hopefully
make
it
available
for
testing.
E
Actually,
there
is
already
a
test
image
that
I
have
included
in
the
description
of
the
pr
so
for
anyone
interested
in
they
can
just
follow
those
steps
there
and
I
would
appreciate
any
feedback
on
on
like
how
this
solves
the
the
problem
of
deletion.
Ordering.
A
Amazing,
Hassan
and
I
definitely
appreciate
I.
Think
this
maybe
just
to
call
this
out
like
this
is
a
really
good
example
of
a
pull
request
that
you
know
kind
of
gives
a
high
level
like
you
know
what
this
photograph
is
all
about,
but
then
also
gives
an
example
of
you
know
what
the
user
experience
is
or
what
the
API
types
look
like,
and
then
also
you
know
information
about
how
people
can
consume
it
and
test
it
and
get
feedback
as
well.
A
So
all
this
extra
information
in
here
I
think
makes
this
you
know,
adds
the
quality
of
this
PR
and
then
the
accessibility
of
people
to
engage
with
it.
Also.
A
You
can
consider
it,
you
know
I'm,
not
sure
if
it
makes
sense
yet,
but
one
idea
is
that
for
the
next
community
meeting
we
could
consider
like
demoing
this
or
showing
it
off
and
kind
of
you
know
doing
a
little
section
to
dive
into
the
experience
as
well,
depending
on
where
we
are
with
it.
A
Cool
all
right:
let's
go
back
to
the
roadmap
here,
so
so
promote
observable
resources
to
Beta.
With
that
one
I
don't
expect.
There
is
a
lot
of
work
to
be
doing
here.
A
You
know
we
got
we
Advanced
the
observe,
only
a
feature:
the
management
policies,
API
Etc
in
1.13,
with
being
able
to
have
granular
management
policies
and
ignore
changes,
and
you
know
avoid
or
disable
late,
initialization
stuff
like
that.
So
now
that
that
is,
you
know
in
place
and
the
1.13
Milestone.
We
hope
to
bake
this
in
1.14
and
not
make
drastic
changes
to
it.
Not
make
your
breaking
changes.
Not
do
anything
like
that.
So.
A
This
will
bake
in
1.14
and
make
it
we
will
mature
it
to
Beta
by
the
end
of
the
release
or
by
the
at
least
time
and
I.
Don't
at
this
point
at
least
I
don't
see
any
major
obstacles
with
that
cool.
So
that's
the
high
level
1.14
roadmap
features
that
we're
working
on.
A
It's
all.
You
know,
as
I
mentioned
last
time
as
well,
we're
going
to
be
putting
some
investment
into
developer
experience
improvements.
You
know,
making
it
easier
to
build
and
run
cross-plane.
There's
not.
You
know,
like
that's,
not
gonna,
be
done
in
1.14
and
we're
kind
of
still
trying
to
figure
out.
You
know
what
exactly
to
focus
on
and
deliver
in
the
1.14
time
frame.
So
if
anybody
is
interested
in
that,
you
know
feel
free
to
reach
out
to
me
and
we
can
have
a
little
chat
and
kind
of
figure
out.
A
You
know
we
want
to
listen
to
people's
feedback
and
you
know
what
they
want
to
see
and
stuff
like
that.
So
we
can
at
least.
A
Together
with
that
I'm
happy
to
chat
with
anybody
on
that,
one.
A
Cool
so
then,
let's
I
don't
know
if
this,
if
this
is
up
to
date,
but
let's
take
a
look,
yeah
I
think
we're
probably
gonna
have
to
clean
up
the
1.14
Milestone
a
bit
and
get
things
accurately
tracked.
But
let
me
see
if
there's
anything
that
we
wanted
to
call
out
or
explore
here
and
also
while
I'm
doing
that
the
floor
is
open.
If
anybody
wanted
to
check
in
on
anything,
that's
on
their
mind
for
1.14.
A
Well,
one
thing
I
had
is
that
Hassan,
maybe
this
might
be
for
you
buddy,
since
you
responded
on
the
issue,
but
I
was
wondering
if
there
was
I
added
this
this
issue
here
into
the
1.14
project
board,
just
because
it
if
it
we
don't
know
the
scope
of
it
yet
and
it
could
be
concerning
so
I.
Don't
I.
Think
where
we
are
is
that
we
don't
necessarily
understand
why
this
is
but
did.
A
E
Yeah,
to
be
honest,
I
I
missed
the
response
here.
So
I
need
to
check
before
I
can
make
a
comment,
but
I
will
I
will
add
it
to
mine
to
the
list.
Yeah.
A
That
yeah,
that's
I,
added
it
to
the
1.14
board
to
because
this
this
I
we
haven't
had
widespread
reports
of
this,
but
the
behavior
as
described
is
concerning
enough
to
at
least
try
to
get
the
scope
and
try
to
understand.
What's
going
on
yeah
cool,
okay,
then.
A
C
A
Well,
let's
hop
on
into
provider
releases
then
as
well,
so
I
gathered
all
of
at
least
things
that
were
posted
to
the
announcements
channel
in
the
slack
workspace.
They
gathered
all
those
here
for
this
list
here.
Since
the
last
community
meeting,
there's
been
a
number
of
Provider
releases,
the
community
AWS
provider
got
a
0.42
and
we've
got
links
to
the
release,
notes
right
there,
so
you
can
read
all
about
that
openstack,
the
provider
openstack
is
the
CI
is
set
up
for
that.
A
It's
been
donated
to
the
crosswind
contrib
organization,
but
there
there
is
one
issue
still
remaining
with
getting
it
published
publicly
with
I
think
the
tags
got
a
little
bit
confused
with
with
you
know,
the
release
branches
and
the
release
tags,
and
everything
like
that.
So
we
need
to
clean
that
up
and
then
that
should
be
publishing
and
available
publicly
soon
and
then
there's
this
a
suite
of
outbound
official
provider
releases
as
well.
A
That
are
all
linked
here
to
the
release,
notes
and
everything
like
that
as
well
on
providers
Jean
or
Alper
anybody
that
may
be
here
focusing
on
providers.
We
obviously
have
a
direct
agenda
topic
later
on
about
some
of
the
community
providers,
but
anything
else
in
terms
of
Provider
releases
or
provider.
Progress
that
you
all
would
like
to
share.
F
Yeah,
so
the
the
main
kind
of
like
feature
that
landed
in
the
in
the
latest
providers
was
the
granular
management
policies.
That's
part
of
the
observerly
feature,
and
there
it's
now
available
in
all
of
the
providers-
and
you
know,
along
with
the
the
usual
kind
of
like
enhancements,
new
resources
and
and
Bug
fixes.
F
We
are,
we
were
hoping
to
be
able
to
release.
Do
a
patch
release
on
these
providers
this
week
with
some
performance
gains.
We
we
we
picked
up
in
some
tasting
scenarios,
but
unfortunately,
we've
also
detected
a
a
memory
regression
on
the
terraform
side
on
the
latest
styrofoam
binary,
and
so
we're
still
investigating
why
that
is
and
trying
to
see.
If
we
can,
you
know,
find
a
solution
for
that.
F
So
you
know
don't
hold
me
to
it,
but
hopefully
in
the
next
week
or
two,
we
can
do
another
release
with
further
enhancements
on
on
some
of
the
optimizations
we've
been
able
to
identify
so
far.
A
Fantastic
yeah,
thanks
for
that,
more
thorough
update,
John
I
appreciate
that
that
further
context.
A
Okay,
so
if
folks
have
other
providers
that
they
are
using
and
or
have
published,
new
releases
or
anything
like
that,
feel
free
to
add
those
to
the
agenda
document
here,
we'll
get
that
into
this
list
as
well,
so
yeah
moving
on
to
the
community
topics
section.
So
you
know.
Typically,
we
have
this
section
here
for
Content
within
the
ecosystem,
blog
post,
videos.
A
Cross
plain
I
I've
been
collecting
those
in
the
backlog
throughout
the
last
two
weeks
since
the
last
community
meeting
and
I
forgot
to
decorate
them
with
little
descriptions
and
stuff,
so
they're
just
raw
URLs
right
now.
So
it's
not
super
helpful
to
everybody,
but
one
thing
I
did
want
to
call
out
specifically
and
if
Pete
is
on
the
call,
you
know
I'd
love
to
have
you
talk
through
it,
but
I
don't
see
Pete.
A
So
that
might
not
be
the
case,
but
I
did
want
to
make
specific
mention
of
of
the
docs
improvements
that
we
had
done
recently.
So
those
did
kind
of
get
included
into
the
1.13
timeline,
but
we
also
have
this
blog
post
about
it
as
well.
That
kind
of
goes
into
some
of
the
details.
Etc,
so
I
wanted
to
just
call
out.
That's
you
know
we
made
a
big
investment
into
deeper
content
and
more
useful
content
and
the
organization
of
that
content
Etc
on
the
main
docs
site.
A
So
you
know
Pete
spent
a
lot
of
Cycles
on
this
and
we're
not
13,
and
you
know
added
a
6
000
new
lines
of
content,
so
things
that
had
not
been
previously
covered
that
folks
asked
out
about
a
lot
are
now
included
in
the
docs.
So
this
is
the
start
of
more
to
come.
P
you
know
is,
is
working
it's
a
full-time
on
Crossland
docs.
It's
been
focusing
on
that.
A
So
there'll
be
more
to
come
here
and
you
know
happy
to
hear
from
folks
more
about
what
they
want
to
see
in
the
docs.
What's
missing
from
being
documented
and
all
that
sort
of
stuff,
but
I
really
am
impressed
with
this
investment
that
and
this
progress
that
Pete
made
and
we're
not
13
and
really
happy
to
see
it.
Some
pizza
should
also
be
noted
that
Pete's
meme
game
is
on
point
as
well.
A
A
You
sneaky
guy
all
right.
Well
then,
you
just
listened
to
me
ramble
about
your
work,
anything
that
you
would
love
to
add
in
addition
to
that,
Pete.
C
No
I
think
you
covered
it
pretty
well,
you
know,
like
I
said,
like
you
said,
we're
really
trying
to
focus
on
making
things
a
little
bit
more
clear,
a
little
bit
more
digestible
and
I
like
to
call
this
project.
You
know
the
breaking
up
of
our
docs
monolith
into
you
know:
docs
microservices,
as
we
break
up
those
components,
the
next
big
thing,
not
as
big,
but
the
next
big
thing
is
working
on
kind
of
fleshing
out
some
of
the
provider,
authentication
methods,
that's
one
of
the
another
thing.
C
We've
heard
a
lot
of
people
struggle
with
you
know
what
are
the
various
options
and
how
do
they
work
and
give
me
some
working
examples?
But
if
there's
anything
else,
you
all
are
hearing
or
struggling
with
on
a
regular
basis
that
you
think
we
need
to
add
in
I'm.
A
And
one
great
format
to
do
that
is
opening
issues
on
the
cross
plan
docs
repo-
that
is
that's
the
where
the
backlog
is
that's
where
everything's
captured.
You
can
also
throw
suggestions
on
the
documentation
channel
in
cross-plane
stock
yeah
we're
definitely
listening
to
those
and
incorporating
as
much
as
we
can
to
keep
moving
the
moving
the
ball
forward
here.
A
All
right
and
that's
a
listen
people
can
dive
into
some
of
these
other
links
and
news
articles
and
stuff
about
crossband
in
the
last
couple
weeks.
A
Cool
so
I
wanted
to
make
a
mention
here
that
so
the
Community
Day
event
that
we
are
putting
on
I
think
it's
September
19th.
If
memory
serves
me
correctly,
the
call
for
proposals
closed
at
the
end
of
last
week,
so
it
is
now
closed
and
I
wanted
to.
You
know,
give
a
thank
you
to
everybody
who
submitted
things.
We
got
a
lot
of
quite
high
quality
content
there
and
you
know
there
are
limited
slots.
A
So
it's
it's
a
challenge
to
to
figure
out
the
final
schedule
here,
because
there
is
such
really
such
good
topics
there.
A
So
I
just
wanted
to
give
an
update
that
the
program
selection
committee
is
it
or
has
reviewed,
essentially
everything,
and
then
we
are
meeting
to
to
finalize
all
our
decisions
together
and
we
expect
to
be
announcing
the
schedule
we'll
be
notifying
the
accepted
proposals
pretty
pretty
soon.
But
then
we
expect
to
announce
the
schedule
publicly,
probably
by
the
end
of
next
week.
A
Another
note
here
to
make
is
that
we
did
have
a
community
survey
for
folks
to
provide
feedback
on.
You
know
what
you
like,
what
you
don't
like
what
you
want
to
see.
What's
you
know
everything
there,
it's
kind
of
influenced
where
we're
going
with
cross
plain.
There
is
a
direct
link
here
to
the
Google
form
that
has
all
that
information.
A
A
lot
of
the
questions
are
optional,
so
you
know
if
you
just
want
to
provide
a
little
bit
of
feedback
and
don't
want
to
get
bogged
down
in
a
lengthy
survey,
which
is
not
that
lengthy
to
begin
with,
but
you
can
skip
a
lot
of
questions
if
you
want
to
as
well,
then
we
still
appreciate
any
feedback
you
do
have,
and
so
this
closes
at
the
end
of
this
week.
A
So
tomorrow
will
be
the
last
day
for
this
survey
here
and
thanks
to
everybody
who
has
already
provided
their
feedback,
but
they
have
one
more
day
to
get
a
response
in.
A
If
you
are
able
to
do
so-
and
we
do
appreciate
it
all
right
next
topic
here,
I
believe
this
came
from
Stefan
who
I
don't
know,
I,
guess
I'm,
not
very
good
at
looking
at
the
participants
list,
so
maybe
is
on
the
call,
maybe
is
not,
but
I
don't
see
him
directly
here
and
I
think
he
might
actually
be
on
PTO
anyways
but
anywho,
so
chiffon,
Dr
Stefan,
here
a
wonderful
person
started
a
thread
that
he
wanted
to
get
a
little
bit
of
feedback
from
people,
and
so
he
had
been
looking
at
metrics
and
a
reservability
etc,
especially
in
production
scenarios.
A
And
so
it
was
kind
of
posting
for
folks
kind
of
crowdsourcing
a
little
bit
that
if
there
was
one
metric
that
that
you
could
add-
or
you
would
want
to
add
to
crossband
to
be
able
to
observe
it
better
in
production,
then
there's
a
thread
to
add
those
to
I.
Don't
know
if
it's
gotten
much
traction
yet.
So
any
responses
there
would
be
quite
useful
as
chiffon
is.
A
You
know,
thinking
through
some
of
you
know
more
things
about
monitoring
and
observability
etc
for
cross
plain,
so
that
would
can
only
help
the
entire
community
at
large,
with
any
ideas
that
you
all
folks
might
have
so
there's
a
direct
link
to
that
thread
here
in
the
agenda
doc
so
feel
free
to
click
through
and
go
on
over
there
and
contribute
to
that
thread.
A
Okay
and
then
the
last
topic
here
more,
the
main
event
of
the
discussion
today,
I
wanted
to
you,
know,
turn
the
floor
over
to
Jean
since
you've
been
kind
of
running
or
kind
of
messaging
there.
So
like
yeah
John.
If
you
want
to
get
kicked
off
in
the
discussion
here
about
maintainership
of
community
providers,.
F
Yeah,
so
the
the
removal,
the
well
let's
say,
the
formal
removal
of
of
the
outbound
Engineers
as
as
maintainers,
is
mostly
actually
just
a
more
accurate
reflection
of
what
has
been
happening
over
the
last
few
months.
F
We
you
know,
since,
since
we
released
the
upans
official
providers
for
for
AWS,
Azure
and
gcp,
you
know
all
of
our
energy
has
has
been
going
into
that
initially
to
to
get
resource
coverage
and
and
now
we're
we're
very
much
focused
on
performance
and
and
improving
the
efficiency,
and
so
we're
we're
not
able
to
to
Really
dedicate
any
of
our
time
to
maintaining
these
Community
providers.
And
you
know
from
time
to
time,
Engineers
would
get
pinged
about
people.
You
know
asking
you
know,
can
you
merge
as
PR
or
to
so
on?
F
And
you
know
it's
not
as
trivial
as
just
clicking
a
button
to
merge
it,
and
you
know
if
you
you've
got
to
take
the
responsibility
to
think
through
it.
Make
sure
that
it's,
you
know
doing
the
right
things
and
you
know,
is
it
actually
adding
value
and
so
it
became
you
know
like,
and
it's
also
not.
You
know
something.
That's
easy
for.
F
Engineers,
you
know
to
feel
like
they
have
an
expectation,
because
their
name
is
publicly
listed
as
a
maintainer,
but
the
reality
is
they're
tied
up
with
with
other
work
and
expectations,
and
so
we've
made
the
decision
to
to
just
basically
more
accurately
reflect
the
reality
of
the
that
we
can't
actually
commit
time
to
to
these
providers
because
of
our
own
providers
that
we're
focusing
on
the
the
I
guess.
You
know
the
main
call
to
action
here
is
really
also
about
specifically
provider,
Azure
and
provider
gcp.
F
Now
that
the
the
apparent
Engineers
aren't
on
there
as
maintainers
they,
you
know
it
does
look
like
there's,
potentially
a
lack
of
active
maintainers
day.
You
know
one
of
the
maintainers
left
is
Dan,
who
you
know
recently
moved
to
an
emeritus
maintainer
of
crossblane.
F
F
You
know,
and
and
are
willing
to
to
kind
of
like
commit
the
time
and
and
effort
to
to
become
maintainers
that
they,
you
know
basically
step
up
and
and
indicates.
As
such,
you
know
the
last
thing
we
want,
for
you
know,
repositories
of
providers
to
to
be
there
that
basically
becomes
stale,
and
you
know
people
might
go
and
use
them.
F
But
then
you
know
later
on,
like
see
like
you
know,
you'll
see
these
issues
pop
up
like
is
this
dead,
as
you
often
see
in
these
open
source
projects
when,
when
maintainers
kind
of
like
move
on-
and
so
you
know,
the
hope
is
that
you
know
there's
some
folks
in
the
community
that
will
step
up
over
the
next
week
or
two.
F
Otherwise,
you
know
we
might
need
to
make
a
recommendation
to
the
steering
committee
to
consider
whether
we
need
to
archive
or
more
formally
indicate
that
those
providers
aren't
being
maintained.
Currently
I
believe
the
the
situation
is
slightly
different
for
provider
AWS.
F
You
know
we
do
have
two
maintainers
on
there
that
are
that
are
active
and
I
believe
I've
at
least
given
an
indication
that
they're
willing
to
to
stay
on
and
and
look
at
bug,
fixes
and
PR's
coming
in
you
know,
and
but
I
guess,
the
request
is
is
exactly
the
same.
You
know
like.
Are
they
some
people
in
the
community
who
are
willing
to
step
up
and
and
help
out
on
on
these
providers?
F
F
S
kept
asking
you
know,
like
you
know,
what's
the
difference
even
between
up
and
and
you
know,
Community
providers
and
that
that's
been
a
common
question,
that's
come
up
a
lot.
I've
tried
to
give
like
as
unbiased
on
opinions.
F
I
could
in
in
slack
day,
just
to
give
a
little
bit
of
a
summary
of
of
the
outbound
providers,
and
you
know
I
I
believe
you
know,
Jared
is
is
kind
of
like
considering
also
you
know
whether
we
should
be
doing
a
blog
post
about
the
various
providers
and
that's
available
to
community.
F
H
I
was
wondering
if
I
could
interject
something
on
this
topic.
That's
okay,
yeah!
Please
do
Dan,
okay
yeah.
So
at
least
you
know
from
my
team
at
sap,
I
can
say
that
there
definitely
has
been
and
I
think
continues
to
be
confusion
about
the
you
know,
particularly
the
licensing
differences
or
lack
thereof
between
community
and
official.
In
fact,
I
think
in
the
last
three
days,
I've
had
to
explain
it
to
the
same
set
of
people
twice
after
I
got
whatever
information.
H
You
know
from
you
guys
in
slack,
you
know,
and
it
was
just
somehow
wasn't
sticking
it's
like
no
look
same
licensing
so
yeah.
Anything
that
could
you
know
make
that
really
clear
would
be
great,
I'd
love
it.
If
I
could
point
to
a
doc
or
something
or
blog
post.
That
says
you
know,
hey
look
same
license.
H
And
my
team
has
been
using:
there
are
other
teams
using
cross-plane,
starting
to
use
cross-plane
within
sap,
I'm
not
really
plugged
into
them,
but
from
my
team
I
can
say:
we've
been
using
it
for
two
plus
years
and
we
certainly
are
using
all
three
of
these.
These
providers
and.
H
H
What's
the
way
forward
for
us,
you
know:
do
we
become
maintainers
or
do
we
do
just
become
maintainers
and
stick
with
Community
contrib
providers
or
do
we
you
know
not
become
maintainers
and
work
as
much
as
we
can
to
switch
to
the
official
providers,
or
do
we
see
some
sort
of
mix
where
well,
we
sign
up
for
being
maintainers,
for
you
know,
six
months
whatever,
while
we
sort
out
the
transition
to
official,
so
we're
trying
to
figure
that
out
what
we're
doing
and
one
of
the
things
we
well
one
of
the
things
we
need
in
order
to
figure
that
out
is
some
sort
of
understanding
of
what
would
be
involved
in
transitioning.
H
You
know
to
the
official
providers,
thus
far
I.
Think
just
all
that's
happened.
Is
you
know,
some
months
ago
one
of
our
developers
briefly
looked
at
the
official
prize
and
just
noticed.
Oh,
you
know
what
hey
like
the
property
names
aren't
the
same
on.
You
know
the
objects
we're
using
like
elastic
cache,
so
we
have
to
do
something.
It's
not
just
a
simple,
you
know:
hey
change
the
provider,
we're
referencing
and
that's
the
that's
the
end
of
it.
H
There's
there's
more
work
to
be
done
here,
so,
unfortunately
that
guy
who's
one
of
our
most
Hands-On.
You
know
folks,
with
cross-plane
stuff
he's
on
vacation
for
a
bit.
So
where
we
are
is
you
know,
like
I,
said
we're
trying
to
sort
out
what
to
do,
and
you
know
there's
a
data
point
at
the
moment
that
we're
missing
and
if
anything
that
crossbling
could
do
to
help
us.
H
You
know
fill
in
that
data
point
would
be
great
like
okay,
whether
it's
just
something
anecdotal
like
hey
someone
did
migration
and
it
looked
like
this
or
you
know,
whatever
anything
on
that
font
would
be
appreciated.
A
Yeah
and
then
there's
a
I'm
gonna
drop
a
link
here,
just
so
that
it's
accessible
is
that
there
is
a
documentation
on
on
what
the
migration
process
looks
like
and
the
availability
of
tooling
and
all
that
sort
of
stuff
so
making
that
accessible
and
seeing
that
is
at
least
the
first
first
step
like
John
was
probably
gonna.
Make
another
comment,
maybe
a
little
bit
deeper,
but
at
least
that's
the
first
step
here
that
I'll
I'll
drop
right
now
into
the
agenda
doc.
Thanks.
H
F
You
know
they
are
API
changes
and
we
we
have
some
guides
around
how
to
manually
migrate,
and
you
know,
like
the
the
effort
related
to
that,
will
obviously
quite
vary
based
on
you
know
the
how
how
complex
your
your
and
extensive
your
usage
of
the
the
resources
are
and
then
we're
currently
working
on
on
a
migration
tool
that
will
not
make
the
process
totally
seamless
and
painless,
but
will
help
a
lot.
F
So,
for
instance,
you
know
there
will
be
a
two
migration
tool
kind
of
like
template
and
there
will
be
shared
converters
that
will
basically
could
take
care
of
most
of
your
managed
resource
conversion
to
the
official
providers
and
then
there's
there's
a
you
know,
a
framework
that
allows
you
to
to
write
your
own
custom
converters
for
some
of
your
compositions
and
so
on,
and
so
a
bounce
team
is
currently
you
know
using
this
tooling
to
help
some
of
our
customers
migrate
over
and
we're
learning
a
lot
from
the
feedback
and
so
on.
F
The
tooling
will
probably
become
publicly
available
towards
kind
of
like
the
end
of
of
August,
when,
when
we've
ironed
out
quite
a
lot
of
issues
and
we'll
keep
updating
that
migration
page
with
the
latest
information
and
available
tooling.
H
Great
thanks
much
so
probably
what
will
happen
on
my
team's
side
is
I'll.
Take
this
to
my
manager
and
then
we'll
figure
out
yeah.
What
what's
like
I
said?
What's
our
way
forward
like?
Should
we
sign
up
and
provide
as
maintainers
or
you
know,
focus
our
energy
on?
H
You
know
migration,
like
obviously
we
don't
want
to.
We
wouldn't
want
to
jump
on
as
maintainers,
and
then
you
know
like
two
weeks
later
say:
oh
no,
sorry
we
didn't
mean
it.
You
know.
If
we're
going
to
commit,
we
want
to
be
sure
that
we're
going
to
be
committing.
You
know
for
many
months
at
least
before
you
know
pulling
out
if
we
do
pull
out
so
yeah,
we'll
on
our
side,
we'll
have
a
chat
and
sort
out.
A
Yeah
and
Dan
one
thing
to
think
about
too
there
is
that
you
know
I,
you
don't
have
to
make
that
decision
in
isolation.
If
you
want
to
chat
or
get
some
ideas
or
you
know
brainstorm
or
whatever,
like
you
know,
we
can.
We
can
share
some
time
together
and
kind
of
talk
through
some
things.
If
that
helps
too
man,
yeah.
H
H
We
have
been
trying
to
it
will
coordinate
with
them
like,
for
example,
you
know
we're
all
interested
in
sap
we're
all
interested
in
Alibaba
support,
for
example.
So
we
were,
we've
been
powwowing
about.
Okay,
do
we
go
with
the
community
contribute
existing
one
or
the
generated?
You
know
upbound
tool
generated
thing
like
what
are
we
going
to
do
here?
We're
trying
to
to
sync
up?
H
A
The
stars
have
aligned
that's
awesome
and
then
something
something
else
here.
So
Carl
is
also
on
the
call
here-
and
you
know,
is
one
of
the
current
maintainers
of
provider
at
the
community
provider
AWS,
so
Carl,
if
you
had
more
to
you,
know,
share
for
your
opinion
or
your
thoughts
or
anything
then
you're
more
than
welcome
to.
But
you
know,
is
this
not
a
requirement.
G
Yeah
I
think
yeah
I'll
summarized
it
very
well
and
that
we're
kind
of
in
the
same
situation
as
Dan,
except
for
it's
more
like
we're
too
busy
to
migrate
at
this
time,
and
we
also
look
forward
to
any
tooling
to
help
migrating
but
will
stay
on
us
maintainers
at
least
for
as
long
as
we
use
it
when
we're
not
using
it,
then,
of
course
that's
a
much
more
difficult
task
to
maintain
something
that
you
don't
use
so
yeah,
but
bug
fixes
and
such
will
work
on.
H
Just
I
want
to
mention
something
that
came
up
in
a
chat
with
Carl
between
Carl
and
I
yesterday
before
was
I
think
Carl
mentioned,
you
know
the
topic
of
things
being
in
production,
so
we
have
some
stuff
in
production
that
yo
we
wouldn't
want
to
lose
in
the
process
of
transitioning.
H
So
that's
one
area
of
concern.
I
think
it
will
sounds
like
there's
multiple
consumers
of
providers
today
that
that's
a
concern
like
how
do
we?
How
can
we
or
can
we
migrate
from
Community
to
official,
leaving
things
in
place.
A
Yeah
I
totally
agree
with
that
car
Dan
and
that
that's
yeah,
that's
that's
what
we've
been
doing
with
you
know
some
of
our
about
customers
that
we've,
you
know
gone
through
the
migration
process
with
and
you
know,
keep
things
running,
and
you
know
the
tooling
that
we're
developing
and
the
guides
that
we
have
and
all
that
sort
of
stuff.
So
that's
absolutely
a
focus
of
and
a
goal
of,
the
migration
effort
that
we've
had
as
well.
G
Yeah
I'm
thinking
also,
maybe
the
new
observe
only
resources,
would
allow
you
to
do
a
dry
run
migration
and
check.
If
what
what
are
there
any
differences
in
the
do
the
new
Pride?
We
want
to
make
any
changes,
or
is
it
happy?
So
if
you
create
all
the
managed
resources
for
the
the
new
provider,
the
official
provider,
but
with
observe
on
the
mode
that
would
give
a
confidence
that
we're
not
going
to
lose
any
data
I
think
so,
if
that's
possible,
that
would
be
very
cool.
A
Cool
but
yeah
so
definitely
appreciate
folks
weighing
in
on
this
and
Sean.
Thank
you,
for
you,
know,
kind
of
driving
and,
and
you
know,
driving
the
process
here
being
thoughtful
about
the
messaging
and
you
know
kind
of
communicating
with
the
rest
of
the
community
Etc.
So
that's
definitely
appreciated
as
well,
and
you
know,
as
I
mentioned,
to
Dan
as
well
right
like
that,
you
know
I'm
always
happy
to
chat
with
folks.
B
A
Find
time
to
talk
and
try
to
try
to
navigate
things,
I'd
say
but
yes,
and
then,
if
folks
are
interested
in
becoming
a
maintainer,
a
provider
of
any
of
these
providers
do
feel
free
to
reach
out.
And
we
can.
We
can
figure
that
out,
and
you
know,
work
with
the
current
maintainer
teams
and
and
all
that
sort
of
stuff
to.
A
H
Isn't
it
from
the
doctor?
Is
there
something
I
just
posted
to
the
chat
and
I
mean
if
we
don't
discuss
it
here,
that's
totally
fine!
It's
just
something.
I
would
like
to
get
people
thinking
a
little
bit
about
is,
after
this
recent
problem,
with
the
upgrading
with
the
lock
storage
type
which,
by
the
way
we've
had.
My
team
has
had
like
three
upgrade
problems,
kind
of
like
this.
In
the
last
year
and
a
bit
there
was
another
one,
nothing
related
to
the
Cross
plane
where
it
was.
H
It
was
particularly
nasty.
We
actually
had
to
tear
down
a
couple
of
Landscapes
or
clusters
as
a
result,
so
we're
looking
at
in
ways
that
we
can
somehow
you
know,
do
some
sort
of
upgrade
validation
and
or
mitigation
of
this
kind
of
problem.
So
I
posted
in
the
chat
something
about
this
or
just
a
link
to
this
was
it
here,
whatever
Cube
Storage
version
migrator.
H
So
that's
something
we're
just
starting
to
consider,
but
obviously
we
can't
you
know,
adopt
it
if
it's
going
to
interfere
with
the
cross,
plane,
init
process,
so
it'd
be
great.
If
some
cross-plane
folks
could
just
take
a
quick,
you
know
look
at
it
and
maybe
let
us
know
you
know
if
it
would
be
safe
for
us
to
even
consider
or
if
it's
like.
No,
no
don't
do
that.
A
Yeah
and
that's
a
really
good
question
Dan,
because
I
know
that
that
had
come
up
when
I
say
something
to
investigate
when
we
were
looking
for
an
initial
solution
to
you
know
migrating
the
crds
and
their
versions
Etc
before
we
got
the
patch
releases
out,
so
I
didn't
look
into
it
through
too
thoroughly.
Myself,
though,
but
I'm
also
super
curious
to.
If
there's
any
interaction
there
or
you
know,
think
that
we
want
to
be
aware
of
I
think
another,
so
I
could
ping.
A
Maybe
chiffon
probably
already
has
an
opinion
on
this
like
in
his
sleep,
so
maybe
we
can
ping
him
and
see
if
he's
got
an
idea
on
it
as
well.
But
then
the
other
thing
to
note
as
well
here
is
that,
let's
see
if
I
can
drop
a
link
to
it
here,
so
we
also
recently
added
a
new
Epic
on
the
roadmap
that
is
focusing
on
reliable,
safe
installs
upgrades
Etc.
A
So
that's
something
you
know
kind
of
that
a
theme
Here,
an
epic
that
would
be
kind
of
in
the
same
in
the
same
vein.
Here
of
you
know,
making
sure
that
the
all
those
processes
and
rollbacks
Etc
are,
you
know,
invested
in
and
you
know,
obstacles
are
removed
and
things
like
that.
So
that's
that's
something
that
could
also
be
of
help
here
as
well.
B
Just
I
can
I
can
add
something.
So
we
we,
when
we
fix
when
we
fix
this
problem
for
the
releases.
Recently
we
checked
first,
the
cube
storage
version
migrator
and
we
implemented
in
cross-plane
a
CID
migrator,
based
on
what
the
guys
are
doing
in
the
cube
storage
version.
Migrator.
B
If
you
want,
you
can
run
it
before
the
in
the
processes
from
cross-plane,
there's
no
interference
in
it.
It
will
only
check
if
the
storage
version
can
be
migrated.
If
there
is
not
old
version
set
it
in,
then
nothing
will
happen
when
it
process
from
Crossland.
B
You
can
run
this
before
it's
not
a
problem,
because
we're
checking
only
if
their
old
version
is
set
it
in
the
xcd
and
if,
if
yes,
we
doing
the
migration,
if
other
processes
during
the
migration
before
it's
also
fine.
B
A
Awesome:
dude,
okay,
so
yeah
yeah,
thanks
for
Dan,
bring
that
up
and
I
missed
that
in
the
chat
there
as
well.
So
just
doing
a
quick
scan
and
I
don't
see,
I,
don't
see
other
big
questions
that
came
up
or
anything
but
yeah.
A
couple
couple
new
folks,
though,
that
joined
the
call
here
and
are
new
to
the
community
as
well
so
Santosh
in
Jared
other
Jared
Jared.
Two.
A
Let's
call
him
joined
on
here
and
definitely
happy
to
see
you
all
today
and
I'm
looking
forward
to
any
you
know,
involvement
and
engagement
that
you
all
want
to
get
into
with
the
project
tune
in.
G
It
thanks
Jordan
nice
to
meet
you.