►
From YouTube: 2022-10-06 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
October
6th
2022
cross
plain
community
meeting
I
made
the
agenda
outline
last
night
since
I
was
going
to
be
busy
or
not
at
a
computer
all
this
morning,
so
I'm
just
kind
of
rolling
in
here
and
didn't
flesh
out
any
agenda
from
this
morning.
So
anything
that
folks
want
to
add
is
more
than
welcome
and
especially
contributing
to
to
that
agenda.
A
So
let's
get
go
ahead
and
get
started.
I
checked
before
last
night
before
before
this
meeting
here
of
any
recent
cross-plane
patch
releases
Etc,
we
have
not
had
any
that
I
saw
since
the
last
community
meeting.
So
nothing,
nothing
there
to
call
out.
But
the
big
thing
I
think
coming
up
here
is
the
the
V
1.10
release,
so
the
scheduled
release
that
we've
been
working
to
this
whole
time
is
for
October
18th.
A
So,
looking
at
the
the
schedule
here,
we've
entered
into
feature
freeze
now
next
week
will
be
a
code
freeze,
and
you
know
continue
that
sort
of
escalation
there
of
pausing
taking
big
features,
pausing
to
take
only
things
for
like
critical
bug,
fixes
docs
changes
Etc
as
we
work
our
way
towards
October,
18th,
so
kind
of
winding
down
this
release
here.
So
I
wanted
to
check
in
with
folks
and
see
you
know
how
things
are
going
if
there's
things
that
we
wanted
to
get
some
attention
on.
A
If
there
are
things
that
we
needed
some
support
with,
while
we're
trying
to
wind
down
this
Milestone,
maybe
Bob,
it
might
be
a
good
place
to
start
might
be.
You
know
some
of
like
the
garbage
collection.
You
know,
deletion
type
of
work,
you've
been
doing
I,
don't
think
we
were
necessarily.
You
know,
planning
on
that
being
in
1.10,
since
there's
a
lot
of
hairy
scary
things
to
figure
out
there.
A
B
Yeah,
so
I've
kind
of
split
it
out
into
two
pieces
have
been
talking
with
Nick
extensively,
and
so
the
foreground,
cascading
deletion,
I,
think,
is
going
to
be
kind
of
separate
by
itself,
I'm
hoping
to
maybe
get
that
into
1.10,
but
I'm,
not
sure
whether
we
will
or
not.
It's
really
you
know
it
doesn't.
B
It
doesn't
affect
anything
unless
you
specifically
ask
for
foreground
cascading
deletion.
So
you
know
in
terms
of
impact
it,
it
shouldn't
be
a
huge
impact,
the
the
basic
question
there
is:
what
do
we
do
about
claims
because,
because
there's
no
owner
reference
between
the
claim
and
the
composite,
you
cannot
run
foreground.
Cascading
deletion
from
the
cube
control
delete
command
line
on
a
claim.
It's
just
never
going
to
work.
B
So
we
talked
about
adding
a
adding
an
attribute
to
the
composite.
That
basically
says
tells
the
claim-
or
maybe
it
was
to
the
claim-
I-
don't
remember
anyway,
adding
an
attribute
that
basically
tells
the
claim
reconciler
whether
to
use
foreground
cascading
deletion
when
it
calls
delete
on
the
composite.
So
that's
kind
of
the
one
thing
that's
up
in
the
air
right
now,
the
other
half
of
that.
B
The
kind
of
the
resource
dependency
cleanup,
you
know,
issues
we've
kind
of
broken
out
of
that
I
and
I've
been
doing
some
work
on
a
POC
with
some
ideas
that
Nick
had
with
using
web
web
admission,
web
Hooks
and
dependency
resources
to
try
to
block
block
deletion
of
certain
objects
while
they
have
dependencies.
B
The
initial
results
were
promising
I'm
running
into
some
problems.
Now
that
I
think
are
maybe
less
promising
than
we
had
hoped.
So
I
need
to
have
a
discussion
with
Nick
and
see
where
he
wants
to
go
with
that,
but
yeah
I
mean
that's
kind
of
where
things
are
not
as
far
along
as
I
had
hoped.
But
you
know
it's
it,
like
you
said
it's
a
big
hairy
mess
and
it
just
didn't.
We
need
to
come
up
with
the
right
solution
to
it.
So.
A
Yeah,
absolutely
there's,
there's
no
question
about
the
you
know,
complications
or
complexity
of
that
problem.
So
yeah,
that's
that's
a
good
update,
though
Bobs
thanks
for
sharing
that
and
then
you
know,
we'll
continue
making
effort
on
that
and
thanks
they're
making
progress
on
that.
And
so
thanks
for
your
efforts
on
it,
and
then
you
know
that's
something
that
we
can
probably
have
more
confidence
of
fitting
in
to
the
you
know:
1.11
time
frame,
yep,
sweet!
Okay,
that's
great!
A
Let's
see
if
there's
other
things
that
are
kind
of
outstanding,
so
I
know
Nick
and
Max
had
been
working
on.
You
know:
support
patching
from
common
data
sources.
The
interfaces
and
you
know
the
API-
went
into
cross
plane
runtime,
but
the
implementation
within
core
cross
plain
is
still
outstanding.
A
So
I
was
hoping
to
get
that
in
for
the
1.10
released
as
well,
but
it's
still
open
right
now
and
we
are
now
into
feature
freeze,
so
I,
you
know
I,
don't
think
that's
a
great
fit
for
you
know
trying
to
squeeze
in
at
once.
We're
in
feature
freeze.
So
you
know,
if
Nick
or
Max
and
folks
involved
in
reviewing
that
have
a
different
opinion.
You
know
they're
more
than
welcome
to
share
that
and
we
can
take
that
out.
A
Asynchronously
on
that
pull
request,
but
I
would
not
be
counting
on
that
in
the
1.10
release,
since
it's
you
know,
hasn't
quite
landed
yet
Dan
is
there
anything
that
you
wanted
to
call
attention
to
401.10
or
as.
C
C
The
I
linked
it
later
on
in
the
PRS
that
need
attention,
although
I.
C
Really
need
attention
for
folks
here,
but
I
did
want
to
mention
the
signature,
verification
for
packages,
there's
a
open
PR
for
that
and
I
left
some
feedback
on
it
and
I.
Think
it's
going
to
be
easier
for
kind
of
like
a
zoom
conversation
about
it.
So
Jesse
and
I
are
going
to
sync
on
that
tomorrow.
Obviously,
as
usual,
anyone
else's
welcome
to
join
for
that
it
is
not
I,
think
I,
think
Jesse
and
some
other
folks
might
demo
it
at
kubecon.
C
A
And
is
there
a
way
that
did
the
folks
reach
out
to
you
or
be
included
in
that
synchronous?
Conversation.
A
And
then
so,
Dan
the
feature
3048
or
sorry
issue
3048,
which
I
believe
is,
is
you
know
tracking
the
feature
for
an
enabling
package
package?
Signature
validation
that
looks
like
that.
Wasn't
on
the
the
project
board,
so
I'm
gonna
put
that
on
right
now
and
then
that's
kind
of
like
just
in
progress
now
right.
A
Right
all
right
sweet,
so
that
should
be
on
the
board.
Now
then
there
it
is
sweets
and
then
I
think
it'd
be
good
to
assign
Jesse
to
that
as
well.
I
don't
know
if
he
is.
C
A
A
Good
all
right,
so,
let's
skip
back
into
releases
upcoming
release,
stuff,
so
yeah
I
think
that's
most
of
the
stuff.
That's
going
on
for
1.10
are
still
you
know,
things
that
are
maybe
moving
to
1.11.
anything
else
that
folks
want
to
bring
up
in
the
context
of
1.10.
C
Yeah,
so
the
there's
this
issue,
kind
of
describing
it
providers,
are
not
in
scope
for
the
cross-plane
charter
in
terms
of
like
making
sure
that,
like
every
provider
is
part
of
the
cncf
cross-playing
project,
we
do
have
crosswind
contrib,
which
is
a
nice
place
for
folks
to
you,
know,
be
able
to
get
community
support
if
they
want
to
develop
a
provider
and
that's
where
a
lot
of
providers
live
today,
there's
also
a
fair
amount
of
providers
that
live
in
other
GitHub
orgs
and
that
sort
of
thing.
C
But
basically
we
wanted
to
make
it
very
clear
like
where
to
find
providers
and
kind
of
what
their
Association
was
and
that
sort
of
thing
so
we're
updating
to
push
to
cross-plane
contrib,
all
one
word
on
Docker
Hub,
because
they
don't
allow
dashes
or
underscores
or
anything
and
crosswind
dash.
Can
trip
on
the
outbound
Marketplace
about
Marketplace
is
just
an
oci
registry,
with
a
with
a
fancier
name
and
most
of
the
providers
are
now
updated
to
push
there
as
well.
C
And
if,
if
you
have
a
provider,
that's
not
feel
free
to.
Let
me
know
and
I'm
happy
to
assist.
We
have
some
example,
PRS
or
I'm
actually
happy
to
do
the
literal
work
as
well,
and
one
of
the
reasons
why
we
like
pushing
it.
C
There
is
some
more
flexibility
around
like
rate
limits
and
that
sort
of
thing,
as
well
as
you
get
documentation
and
examples
shown
for
for
all
of
your
releases
there
automatically
and
searchability
across
them,
so
definitely
want
to
kind
of
give
that
experience
that
folks
have
kind
of
gotten
with
doctorate
series.dev
before,
but
basically
way
more
with
the
examples
and
search,
and
that
sort
of
thing
want
to
make
that
kind
of
a
more
robust
experience.
C
So
yeah,
all
that's
going
on.
If
you
have
any
questions,
you're
also
welcome
to
reach
out
to
me
on
Slack.
A
And
so
Dan
is
there?
Is
there
like
a
checklist
of
providers
that
are
going
to
be
updated?
Like
I
see
a
few
of
them
have
been?
You
know
kind
of
linked
back
to
this
tracking
issue,
but
is
there
you
know
a
set
that
are
still
outstanding
or
you
know
you
know
that
we
need
to
have
done
or
you're.
You
know
asking
for
help
for
or
anything
like
that.
C
C
So
it
is
a
bit
Dynamic,
we're
looking
to
have
all
of
them,
pushing
to
the
marketplace
and
pushing
to
the
right,
Docker,
Hub,
repo
and
everything
like
that
by
the
end
of
this
week.
So
we
are
pretty
close
and
a
number
of
folks
have
contributed
to
that.
So,
thanks
to
everyone
who
has
once
we
have
full
coverage
and
we're
trying
to
link
back
here,
but
obviously
there's
been
more
than
four
that
have
gotten
updated
and
it's
been
by
different
folks.
C
So
we
need
to
update
our
tracking
a
bit,
but
once
they're
all
updated
all
of
the
ones
that
we
currently
have
right.
Now
that
aren't
archived
or
unmaintained
or
something
like
that,
then
we'll
go
ahead
and
close
out
this
issue
and
that
will
signify
that
everything
is
done.
C
Yeah,
sorry
also,
if
anyone
has
a
provider
and
you're
like
hey
I,
don't
know
what's
happening
and
I
need
help
to
be
able
to
do
this.
Commenting
on
this
issue
is
also
a
great
option
as
well,
and
that
makes
it
quite
visible
to
us
and
we
obviously
won't
close
it
if
there's
a
someone
who's
asking
for
for
help.
There.
A
In
the
Dan,
did
you
also
comment
on
like
kind
of
a
transition
there
of
you
know,
will
release
is
still
like
upcoming
releases?
They
will
no
longer
be
published
to
the
Cross
plain
doctor,
Hub
organization.
Would
that
be
like
an
immediate
thing,
we'll
leave
up
some
of
those
like
the
older
releases?
There,
though
for
posterity
or
what
was
the
the
plan
there.
C
Yeah
there
was
an
announcement
in
slack,
but
I
probably
should
copy
it
over
to
this
issue,
to
make
it
more
visible.
Okay,
the
we
are
going
to
do
a
a
hard
cut
over,
which
is,
you
know,
potentially
breaking
in
some
respect
for
folks
now,
we'll
have
all
the
documentation
updated
to
point
to
the
right
location.
So
as
long
as
you're
consuming
stuff
from
there
consuming
stuff
from
docs
installing
from
there,
you
should
always
have
the
pointing
to
the
right
place
for
the
right
versions.
C
We
are
going
to
keep
all
of
the
history
of
older
images
around
if
necessary,
we
may
switch
over
to
sync
those
to
crosswind
contrib
as
well.
However,
that's
usually
less
of
a
problem
for
folks,
because
if
they're,
installing
fresh
they're
going
to
be
going
with
a
newer
version
and
if
they
have
an
old
version
right,
they're
already
pull
in
from
the
cross
plan
one.
So
what
we
really
don't
want
to
do.
C
The
the
primary
use
case,
we're
trying
to
avoid
happen
is
where
someone
is
currently
pulling
an
image
from
the
the
current
org
on
Docker
Hub
and
that
stops
working.
We
definitely
don't
want
that
to
be
the
case.
So
that's
what
we're
prioritizing
preserving
the
behavior
of.
A
Got
it
cool
dad
thanks
for
explaining
that
Dan
and
yeah,
and
that
that
would
be
very
helpful
to
copy
over
your
announcements
channel
message
into
the
this
issue
as
as
a
comment,
so
it's
in
a
single
place
here
with
the
history,
so
thanks
for
doing
that,
Dan
all
right
so
yeah!
So
that's
a
big
thing
affecting
providers
here
and
then
Dan
is
more
than
happy.
As
you
said,
to
answer
questions.
A
What,
like
anything
else
that
folks
wanted
to
bring
up
for
providers
I
feel
like
there
was
a
another
there's:
a
provider
AWS
release
as
well.
That
I
did
not
write
down
here.
So
let
me
do
that
on
another
screen:
real
quick,
but
any
other
provider
topics
that
folks
want
to
bring
up.
A
C
I
transferred
the
repo
I
haven't
done
any
of
those
okay,
so
yeah
there's
some
some
awesome
folks
working
on
that
and
that
that's
one
that's
just
about
switched
over
and
pushing
as
well,
but
that's
a
new
one
also.
It
seemed
like
a
lot.
We
announced
it
on
Twitter.
It
seemed
like
a
lot
of
folks
were
pretty
excited
about
that.
So
really,
nice
addition.
There.
A
Yeah
very
cool
awesome
glad
to
see
that
I'm
glad
to
see
the
the
provider
ecosystem
continuing
to
grow,
very
cool,
very
cool,
all
right.
Well,
let's
keep
on
moving
through
the
agenda
so,
as
usual
I
want
to
talk
about
some
of
the
recent.
You
know
air
pieces
of
content,
videos
and
blog
posts
Etc,
so
Victor
did
a
video
recently.
That
was
kind
of
interesting
of
you
know.
As
we
are
working
on.
You
know
a
pretty
highly
demanded
and
fairly
powerful
feature
of
composition,
functions.
A
There's
you
know,
Victor
has
a
couple
of
interesting
ideas
about
how
to
Wrangle
some
complexity
within
your
compositions
in
the
intermediate
term,
before
some
of
the
longer
bigger
roadmap
features
and
functionality
are
implemented.
So
you
check
out
this
video
from
Victor
that
goes
into
some
of
that
stuff.
Pure
keeps
continues
to
be.
Writing
really
really
high
quality,
interesting,
thought-provoking
blogs.
So
there's
a
you
know
a
link
there
for
his
as
well
and
then
a
little
plug
for
Matthias
will
be.
If
you
will
happen
to
be.
A
Oh
I
didn't
write
where
that
was
sorry
about
that.
So
in
Germany,
if
you
were
in
Germany
and
then
I
think
it's
in
cologne,
specifically
Matthias
will
be
doing
a
in-person
presentation
to
the
AWS
User
Group
there.
So
I'll
just
write
that
in
there.
A
So
yeah
we'd
love
to
meet
you
if
you're
close
by
and
want
to
stop
by
and
check
that
out.
It's
a
couple
weeks,
two
weeks
from
today,
then
so
yep
that's
interesting
opportunity
kubecon
is
I,
think
like
less
than
two
weeks
away
now
sorry
less
than
three
weeks
away,
so
I
think
it's
like
two
and
a
half
weeks.
So
it's
coming
up
soon
and
hopefully
we'll
get
to
see
a
lot
of
you
folks
in
Detroit.
A
I
know
a
fair
good
chunk
of
you.
Folks
will
be
there,
so
we're
definitely
looking
forward
to
that.
You
know
specific.
You
know.
A
We've
had
this
link
in
here
for
a
while,
but
all
of
the
talks
that
that
mention
cross-plane
are
about
cross-plane
are
available
here,
so
feel
free
to
sign
up
for
those
and
include
those
on
your
schedule
and
then,
in
addition,
you
know
we
do
have
a
booth,
that's
part
of
the
cncf's
project,
Pavilion
area,
so
we'll
be
there
the
entire
time,
all
the
entire
time
that
the
you
know,
Pavilion
is
open.
We'll
have
somebody
there
to.
You
know,
meet
chat
and
listen
to
your
ideas,
feedback
all
that
sort
of
stuff.
A
So
it's
a
really
good
opportunity
to
meet
with
the
project.
Maintainers
and
you
know,
have
some
good
discussions
there.
So
the
and
a
note
on
that
too,
is
that
it's
not
something
that
like
needs
to
be
stacked
specifically,
and
only
by
you
know,
official
people
with
the
cncf
anyone
from
the
community
more
you're,
more
than
welcome
to
come
hang
out
chat
with
other
people
answer
their
questions.
You
know,
if
you
know,
if
you're
more
advanced
on
your
you
know,
user
journey
within
crossplay
feel
free
to
answer
other
people's
questions
as
well.
A
So
it's
definitely
going
to
be
a
little
place
to
hang
out
and
and
see
us
and
and
have
discussions
with
the
community.
A
Okay,
let's
see,
let's
see
what's
next.
What's
next
so
I
I
I
was
hoping
to
catch
up
with
Alberta
today
about
the
buzz
testing,
stuff
and
I,
don't
know
if
he
had
followed
up
to
get
some
more
details
about
the
root
causes
there.
So
we'll
follow
up
with
him
again
asynchronously
on
that
is
Pete
on
the
call
today
does
not
look
like
Pete
is
there,
but
so
Pete
is
undergoing
a.
A
He
talked
about
this
last
community
meeting,
he's
undergoing
a
big
migration
of
our
crossplane.io
website
in
this
and
all
the
documentation
as
well
from
the
Jekyll
framework
to
using
Hugo
instead.
So
all
that
is
on
PR
151
here,
and
so
you
can
follow
along
with
that.
I
believe
that
Dan
has
taken
a
full
pass
through
that
and
people
might
want
to
squash
it
as
well.
A
That's
a
long
commit
list,
but
yeah
I
think
Dan
has
taken
a
full
pass
to
that
and
maybe
given
a
lot
of
feedback
Dan
one
thing
I
wanted
to
bring
up
here,
though,
since
I
know
you
had
looked
at
it
is
that
I
think
there
was
mention
of
maybe
some
documentation
authoring
experience,
changes
that
were
maybe
temporary
or
you
know
a
short-term
sort
of
thing.
Do
you
have
more
insight
that
you
can
share
with
us
on
that
yeah.
C
So
you
know
for
kind
of
a
a
long
time.
We've
we've
been
very
maintainer
engineer,
driven
on
our
docs
and
Pete's.
Bringing
a
lot
of
Doc
specific
expertise.
Has
a
few
changes
being
made
here,
although
it's
it's
not
the
commit
history
here
is
got
some
rebased
stuff
in
it,
but
it's
it's
not
too
big
of
a
diff,
but
there's
a
couple
things
around
like
changing
with
links
and
things
like
that
that
will
lead
to
Links
not
rendering
properly
in
GitHub.
C
It's
a
trade-off
right.
It
would
be
really
nice
for
those
links
to
render
properly.
However,
it
does
mean
that
we
in
Hugo,
the
links
will
actually
like
it'll,
refuse
to
build
if
a
link
is
incorrect
or
doesn't
isn't
linked
correctly
and
so
there's
kind
of
like
we're
getting
more
like
build
time
guarantees
as
a
trade-off
to
to
some
of
like
the
experience
of
maybe
authoring
them.
C
Pete
has
added
a
whole
dock
here
about
authoring
docs,
which
is
going
to
be
really
helpful,
I
think
for
contributors
and
things
like
that,
but
overall
we're
kind
of
taking
approaches,
saying
hey!
This
is
a
a
much
better
path
forward,
especially
since
we're
moving
to
Hugo,
which
is
in
go
and
I'm
sure
Pete
talked
about
that
last
week,
but
it's
overall
better
a
better
place
to
be,
but
we
may
do
some
iteration
here.
C
So
you
know
folks
may
have
to
be
patient
with
some
of
the
updates
as
we
go,
but
we're
going
to
try
and
make
this
transition
then
iterate
on
it
quickly.
Also
this
is
happening
on
Friday,
and
so
it's
possible.
Yes,
yes,
it's
possible
that
there
could
be.
You
know
some
issues
we
have
to
work
through.
We
don't
anticipate
the
site
being
down
or
anything
like
that.
C
But
just
be
aware,
you
know
if,
if
you're
giving
a
demo
that
depends
on
cross-playing
docs,
let
us
know
we'll
try
to
do
it
in
a
window.
That
is,
you
know
closer
to
the
weekend
for
folks,
but
just
a
heads
up
on
that.
A
And
so
Dan,
if
I
understood
correctly,
you
know
it
seems
like
the
documentation
operating
experience.
Changes
are
mostly
around
like
how
we
do
like
links
like
the
format
for
links
and
and
then,
and
so
they
won't,
they
might
not
render.
If
you
look
at
the
docs
the
markdown
on
GitHub,
but
you
said
that
there
is
some
build
time
for,
like
validation,
linting,
perhaps
something
like
that.
That
will
like
confirm
that
links
are
are
good
before
you.
Even
you
know,
push
and
get
it
get.
It
live.
C
Yeah,
so
right
now,
when
they
get
synced
to
the
docs,
repo
or
the
site,
repo
we'll
get
that
that
warning,
so
that
will
fail
when
it
tries
to
deploy
there.
What
we're
going
to
try
to
do
is
also
bring
some
tooling
into
the
crossline
repo
that
says,
like
hey
the
pr
won't
even
pass.
If
you
have
a
link,
that's
not
properly,
you
know
doesn't
have
a
proper
linking
to
the
whatever
the
actual
content
is
and
so
yeah
there.
C
A
Got
it
got
it
got
it
very
cool
though
yeah
I,
like
the
lot
of
the
improvements
in
progress
that
Pete
has
been
making
on
the
crossman.io
website,
is
all
in
pretty
pretty
good
good
service.
I
think
so.
That's
fantastic
I
see
that
Jesse
joined
and
so
Dan.
You
are
here
for
the
first
half
and
then
Jesse
is
here
for
the
second
half,
but
it
looks
like
you
all
might
have
a
few
minutes
of
overlap.
A
C
Jesse
you're
welcome
to
to
add
anything.
I've
only
mentioned
that
we're
gonna
sync
up
tomorrow
and
other
folks
are
welcome
to
attend
that
and
that
it's
coming
in
pretty
hot
for
1.10,
so
we
might
not
be
in
there,
but
but
it's
making
great
progress
so
yeah.
D
Yeah,
you
know,
but
no
problem
at
all
I
I
I
appreciate
the
eyes,
so
I
would
just
say
that
if
anyone
has
the
time
to
actually
review
what's
going
on
there,
it's
it's
a
it's
a
fairly
simple
PR
at
this
point,
but
there
are
some.
D
You
know,
I
think
that
Daniel
wrote
raised
some
some
interesting
design
decisions
that
that
we
will
go
over
tomorrow
in
regards
to
the
storage
of
keys
and
and
so
on
and
so
forth,
and
you
know,
I
think
that
the
the
goal
of
of
having
packages
be
able
to
be
validated
is
already
achievable
with
this
PR,
so
you
know
we
can
kind
of
choose
how
far
we
want
to
progress
before
we
target
a
release.
I,
don't
think
that
there's
any
problem
with
it
missing.
D
You
know
the
dot
10
release,
so
we
can
can
we
can.
You
know,
go
into
our
kubecon
talk,
which
is
part
of
what
this
is
building
up
to
with
this
being,
you
know,
simply
a
PR
at
that
point.
A
Awesome:
okay,
that
sounds
good
and
I.
Definitely
like
the
progress
on
this
so
far,
just
you!
So
thanks
for
digging
in
and
getting
this
type
of
functionality
available
for
the
community
to
you
know
be
able
to
take
advantage
of
as
well.
So
that's
this
is
really
good
stuff
and
then
Dan
mentioned
then
Jesse
that
if
other
folks
in
the
community
wanted
to
join
the
conversation
tomorrow,
they
could
just
ping
him,
and
then
you
know
they
can.
They
can
join
in
and
listen
in
or
maybe
contribute
some
ideas.
A
Awesome
all
right,
good,
stuff,
great
stuff,
great
stuff,
okay,
so
the
only
I
think
then,
since
we
skipped
ahead
to
this,
the
only
other
agenda
item
I,
think
that
was
on
the
agenda
right
now.
Obviously
there
will
be
time
for
other
folks
to
bring
up
things
that
did
not
make
it
to
the
paper
doc
agenda,
because
I
did
want
to
call
out
to
folks
that
there's
a
cross-plane
runtime
feature
that
was
added
recently.
A
That
is
essentially
a
an
annotation
that
you
can
add
to
manage
resources
to
pause
reconciliation
of
them.
The
main
point
for
this
is
to
help
out
with
potentially
with
migration
scenarios.
So
if
you
have,
you
know,
maybe
some
breaking
changes
in
in
whatever
provider,
You're
Building
or
you
know
using
either
side,
and
you
need
to
do
a
little
bit
of
migrate
manual
migration
effort.
It
can
be
very
useful
to
use
this
annotation
on
the
resources,
so
the
crosswind
will
stop
reconciling
them.
A
Stop
you
know
making
changes
the
the
resources
in
the
cloud
or
wherever
they
may
live
and
kind
of,
let
you
do
some
of
the
migration
efforts
and
then
unpause
it
when
you're
done
so.
This
is
something
that
folks
have
been
asking
for
for
a
little
bit
in
terms
of
making
some
of
the
migration
process
easier.
A
There's
a
number
of
things
that
make
migrations
easier
now,
with
especially
the
web
hook
framework
support
that
mafik
had
added
earlier
this
year,
but
a
couple
of
these
things
together
will
continue,
making
upgrades
migrations,
Etc
more
easy
for
for
the
community,
so
I
just
wanted
to
call
attention
to
that
and
I
believe
that
now
so
this
was
in
crosswind,
runtime
and
so
then
I
believe
I
haven't
kept
up
with
it
too
much,
but
that
there's
a
series
of
PRS
that
is
then
incorporating
this
functionality
into
various
providers
to
start
taking
advantage
of
it
as
well.
A
Foreign,
okay,
so
I
think
that
was
everything
that
was
on
the
written
agenda.
Any
topics
that
folks
want
to
bring
up
now
or
new
folks
that
are
on
the
call
for
the
first
time.
If
you
want
to
introduce
yourself,
the
floor
is
open
for
anything
that
folks
want
to
bring
up.
E
So
there
are
some
I
mean
what
you're
doing
in
Cross
plane
I
saw
the
presentation
from
Victor
your
colleague,
of
what
you're
trying
to
achieve
with
crossplaying
across
multiple
apis
of
multiple
multi
or
Cloud
vendors
actually
and
multiple
control
planes,
because
if,
if
well,
not
many
have
insights
into
5G
and
not
many
interested
into.
But
there
is
actually
an
involvement
of
several
service
enabled
Frameworks
and
there
is
something
related
to
the
edge
with
Edge
application
server.
And
now
they
have
defined
clear
apis
between
the
edge
application
server
and
the
cloud
application
server.
B
E
The
application
functions,
context
from
the
application
functions,
business
logic
and
you
store
them
separately
as
a
structure,
an
unstructured
data,
and
you
can
have
a
function
that
actually
can
act
as
a
consumer
or
a
producer,
and
you
can
group
them.
So
there
are
certain
capabilities.
I
mean
these
functions
as
a
function.
They
have
a
meaning,
but
it's
a
value.
E
They
mean
zero
as
far
as
they
are
not
related
to
end
user
services,
and
not
many
actually
have
these
insights
onto
end-to-end
solution
when
it
comes
to
even
4G
and
5G,
because
in
the
last
10
years
not
many
have
been
involved
into
Supply
and
commissioning
of
a
complete
server
Network.
You
have
many
people
who
are,
you
know
working
on
bits
and
bytes,
but
hardly
anybody
is
looking
for
men
to
end
as
a
result
of
this,
you
cannot.
E
So
sorry
that
you
know
I've
been
dragging
this,
but
what
I'm
trying
to
to
look
is
if,
when
you
are
trying
to
look
into
interoperability
or
common
API
common
control
plane,
so
that
you
can
manage
and
orchestrate
different
Cloud
vendors
suppliers,
you
do
you
because
I
mean
they
have
been
running
very
much
on
the
cell
network
and
for
free
I
mean
if
you
look
anybody
of
the
hyper
Cloud
providers
actually
over
the
top.
They
have
been
using
this.
E
But
do
you
have
any
insights
or
do
you
actually
comply
to
the
5G
Network
to
the
Telecom,
because
5G
is
very
different
from
2G,
3G
and
4G.
E
So,
that's
that's
why
you
know
I
joined
your
meeting
just
to
see
because
I've
been
participating
also
at
the
cncf
Telecom
music
group,
and
there
is
you
know,
I
wouldn't
criticize
it
I
mean
that's
what
people
have
chose
to
do
to
have
chosen
to
do.
They
have
focused
very
much
on
kubernetes
and
I
would
personally
say
that
they
have
hardly
have
any
insights
into
Telecom.
E
So
I
was
just
you
know,
curious,
based
on
what
you're
doing
to
see.
Do
you
have
anything
related
to
the
other
side
of
the
coin
when
it
comes
to
Telecom
and
Telecom,
actually
work
on
the
apis
and
service
based
interfaces
and
service
based
architecture
and
actually
their
focus
on
using
context
and
data
characteristics.
A
Yeah,
you
get
a
good
good
question
Mike,
you
know
so
there's
in
terms
of
the
core
cross-plane
functionality
that
that's
that
those
type
of
environments
or
those
apis
have
not
been
a
large
Focus.
So
far,
I
have
started
hearing
and
seeing
more
folks
from
from
Taco
companies.
A
You
know
and
and
like
in
these
type
of
environments,
starting
to
show
up
more
in
their
discussions,
but
has
it
not
been
a
core
like
a
focus
of
the
the
core
project?
So
I
wonder
you
know
if
there's
some
folks
to
connect
to
on,
like
within
the
crossband
slack
community
of
you
know
other
folks,
working
at
Telco
companies.
A
E
E
But
recently,
when
I
looked
at
the
Publications,
maybe
since
one
or
two
years
ago,
I
have
not
seen
actually
previously,
they
had
been
very
open
to
publish
all
the
references
they
had
been
using
for
all
the
specifications
in
the
last,
maybe
12
to
14
months,
I've
seen
that
they
have
not
been
so
open,
I
don't
know,
maybe
they
perceive
they
see
some
competition.
E
There
is
also
a
shift.
Maybe
you
have
seen
from
Red
Hat
reports
from
2021
and
2022
about
the
open
software,
the
state
of
the
Enterprise
open
software
and
how
it's
been
used
and
the
shift
actually
and
the
difference
in
the
business
models
between
devops
software
as
a
service
and
telcos
business
model.
Software
is
a
product
and,
as
you
already
detect
it
and
you're
trying
to
resolve
a
major
problem
previously
Telco
has
been
very
much
criticizing
criticized
about
being
silos.
E
But
now,
interestingly,
your
project
is
actually
directly
focusing
on
I
mean
Victor
has
been
referring
in
his
presentation
to
this
as
a
fragmentation,
but
there
is
also
a
project
with
an
lfm
called
anokept
I
mean
right
right
now,
I
mean
you
have
some
companies
that
had
dominance,
and
they
are,
you
know,
leading
like
Amazon
and
in
Google
or
Usher
and
Google
is
trying
to
get
in.
E
But
there
is
you
know,
fragmentation.
If
I
would
code,
you
know
Victor,
but
they
also
silos,
because
many
very
much
on
the
management
and
orchestration.
We
have
different
tools
or
plugins
that
they
have.
You
know,
particularly
targeting
specific,
you
know,
feature
or
capability
when
it
comes
to
management
and
orchestration
and
I'm
a
little
bit,
I
wouldn't
say
concerned,
but
Warrior,
because
the
cloud
Community
lacks
major
insight
into
a
Telco.
This
particularly
specifications
for
5G
Advanced,
and
they
are
you
know
there
is
a
major
difference.
E
What
5G
is
about
from
2G,
3G
and
4G?
It
enables
such
capabilities
and
provides
you
know:
end-to-end
quality
of
service
and
enablement
of
services
focused
on
data,
so
I
I'm.
You
know
Frank
a
little
bit
to
see,
hopefully
that
these
two
worlds
will
merge
at
some
point
but,
as
it
looks
like
now,
they
are
not
very
much
Crossing
or
they're
Crossing
on
particular
points
of
particular
cases.
E
I,
don't
see
too
much
Synergy,
as
I
indicated
to
you.
There
is
a
specification
with
clearly
defined
interfaces
between
the
edge
application
server
and
the
cloud
application.
Server
and
I
was
just
sorry
to
repeat.
War
I
mean
in
wondering
if,
if
you
you
were
also
including
this
as
a
part
of
the
scope
of
your
project,.
A
Yeah
I
think
I
think
that
you
know
the
the
main
thing
that
I
could
say
about.
That
is
that
you
know
with
with
the
architecture
of
cross
plain.
You
know
it
has
like
core
generalized
functionality
for
orchestration
provisioning,
managing
Etc
of
resources
in
general
and
not
really
any
specific
opinionated.
You
know
aspect
of
what
those
resources
are
and
then
at
the
provider
layer
you
know,
there's
that's
a
kind
of
an
extension
point
to
orchestrate
manage
Etc
lots
of
different
types
of
resources.
A
So
you
know
there's
a
main
focus
of
that
has
been
on
Cloud
public
cloud
provider,
hyperscaler
type
of
resources,
but
then
there's
all
sorts
of
other
types
of
providers
for
anything
with
an
API
can
be
managed
and
orchestrated.
So
there
may
be
some
Synergy
there,
but
I
certainly
do
not
have
you
know
domain
expertise
to
understand
exactly
how
those
things
start
fitting
together
with
you
know,
in
the
Telco
domain.
A
So
maybe
there
is
some
cases
there,
for
you
know
the
provider
layer
for,
for
you
know,
the
extensions
to
cross
planes
be
able
to
have
integration
resources
there,
but
I
don't
have
a
strong
or
well-informed
opinion.
At
this
point
myself,
that
is
right.
E
B
Using
your
example,
you
know
if
there
is
a
you
know.
If
there
is
a
this,
what
do
you
call
it?
A
specification
for
the
API
for
Edge
access
or
Edge
application?
I.
Don't
remember
the
exact
term
that
you
that
you
that
you
said,
but
it
sounds
like
you
know.
If
there's
an
API
specification
for
that,
then
someone
could
very
easily
write
a
cross-plane
provider
that
implements
that
API
interface
into
you
know:
either
a
generic
open
source,
implementation
of
the
provider
of
the
API
or
a
company
specific
implementation
of
the
API.
B
B
However,
I
would
not
expect
cross
plane
itself
to
care
one
way
or
another
about
what
the
actual
application
is.
Right,
Cross
Plains
job
is
to
facilitate
the
communication
to
facilitate
the
modeling
and
the
API.
B
You
know
the
to
me
to
me:
it's
the
modeling
is
the
big
thing
right
and
the
being
able
to
combine
different
resources
from
different
providers
and
Abstract
away.
All
of
that
complexity
into
a
single
composite.
That's
the
value
and
then
the
fact
that
I
can
plug
in
these
different
providers
to
different
apis
as
I
need
them.
So
I
mean
certainly
I
mean
I.
Can
I
I
personally
have
experience
in
the
5G
arena
with
crossplane
and
I
will
tell
you
that
there
is
a
lot
of
work
going
on
in
5G.
B
For
that,
that's
about
the
extent
of
what
I
can
tell
you.
I
can't
give
you
any
details,
but
yeah
I
mean
the
the
benefit
to
me
of
crossblain
is
being
able
to
have
these
providers
that
Implement
these
apis
to
equinix
as
an
example
as
an
edge
cloud
provider,
or
you
know
AWS
or
anybody
else,
and
then
again
if
there
are
higher
level
application
apis
that
can
be
modeled
as
well.
Then
that's
great!
That's
just
one
more
thing
to
put
into
the
API
provider
bucket.
E
Right,
no
first
of
all,
I
do
apologize
in
case
that
I
use
some
terms,
so
I
expressed
myself
and
I
misled
you
because
I
mean
these
specifications
by
3gpp,
they're,
open
and
accessible
by
anybody,
and
anybody
who
implements
that
by
default
should
be
able
to
be
interoperate
with
anybody
else
who
also
implemented
this
yeah.
Unfortunately,.
B
E
Well,
I
mean,
as
I
mentioned
to
you,
I
mean
that's
a
little
bit
what's
the
purpose
of
the
5G
is
I,
mean
they're,
trying
with
five
Jewel
through
the
5G
to
resolve
all
the
problems
and
all
the
issues
that
they
have
experienced
with
the
two
and
three
and
four
G
so
and
I'm,
seeing
that,
okay,
maybe
on
the
implementation,
part
I,
definitely
can
agree
with
you.
E
But
from
the
specification
point
of
view,
this
is
what
they're
targeting
and
there
is
a
lot
of
Legacy
out
there,
which
is
not
very
easy
to
replace
and
to
change.
There
is
a
lot
of
investment
so
but
I
mean
personally,
as
I
indicated,
what
you're
trying
to
do
is
something
which
is
great
and
it
will
provide
if
you
succeed.
A
Opinion
yeah,
that's
a
good
point.
I
can
and
that's
that
kind
of
gets
back
to
like
the
charter
of
the
Crossfade
project,
and
you
know
the
core
functionality
that
is,
you
know
in
like
as
a
framework
to
enable
people
to
build
control
planes,
and
so
you
know
I
could
see
like
at
the
provider
layer,
the
community
you
know
taking
on
and
and
rallying
around
some
of
these
type
of
use
cases
and
support
for
them
to
kind
of
plug
into
the
greater
ecosystem
of
other
providers
built
on
top
of
the
core
crosswind
functionality.
A
So
it'll
be
interesting
to
see
how
that
how
that
plays
out
like
the
interest
and
how
the
community
may
want
to
Rally
around
that.
But
you
know
within
the
core
the
cross,
plane,
project
itself
and
and
its
Charter.
You
know
the
that
core
functionality
will
be
its
main
focus
for,
for
as
through
the
Project's
life
cycle,.
E
E
That
has
puzzled
means
that
I
mean
there
is
a
lot
of
great
applications
and
features
and
functionalities,
and
maybe
it's
also
a
little
bit,
but
the
background
that
I
have
and
I'm
probably
biased,
and
when
I
try
to
look
okay,
how
how
these
features
or
these
features
and
functionalities
and
applications
for
which
and
user
services
or
what
kind
of
you
know
latency
or
throughput
they
contribute
I
mean
which
use
cases
they're
connected
to
then
usually,
people
have
a
big
question
mark
because
I'm
also
coming
from
technology
background
and
in
some
I
mean
also
I,
have
a
training
on
this.
E
When
people
you
know
the
trainers
are
going
around
and
asking
you
to
write
the
value
statement
and
then,
of
course,
you
write
about
feature
or
functionalities,
and
you
don't
see
that
in
the
head
they
had
a
stamp.
You
know
hit
written.
So
what
because
I'm
also
very
much
you
know,
speaking
about
different
features
and
functionalities,
and
sometimes
not
very
often,
but
sometimes
I.
Also,
can
miss
a
little
bit
to
connect
them,
how
they
contribute
to
resolve
the
issues
in
order
to
provide
or
commission
you
know,
end
user
services.
E
A
Yeah
definitely
yeah
thanks
for
bringing
that
kind
of
stuff
up,
and
then
you
know,
I
think
following
up
on
slack
is,
is
a
potentially
a
good
possibility
as
well
for
connecting
you
know,
there's
thousands
of
users
on
on
the
slack
and
then
you
know
a
much
smaller
number
here
at
the
at
the
in-person
synchronous
meeting
so
yeah.
A
If
you
want
to
drop
a
note
on
the
Cross
Lane
slack
to
see
you
know
what
other
Telco
involved
or
you
know
where
people
are
out
there
and
if
there's
any
sort
of
you
know
momentum,
maybe
they
can
be
drawn
towards
providers
that
are
focusing
on
this
area.
That
would
be
probably
a
good
Next,
Step
Maybe
sure.
Thank
you.
Thank
you.
Jack
awesome,
yeah
nice
to
meet
you
Eric.
F
Very
well
who's
doing
our
Channel
introduce
myself
yeah
I'm
Don
Mayo
I
work
for
Oracle
on
their
managed
kubernetes,
offering
use
terraform
for
years
loved
it,
but
I'm
very
excited
by
Solutions,
like
cross
plain
yeah,
because
you
know
people
can
push
more
infrastructure
into
kubernetes
where
it's
easier
to
maintain
and
continuously
reconciled.
That's
awesome,
so
I'm
really
here
to
just
get
the
full
experience
using
it
because
I'm
pretty
new
to
the
cross-plane
project
and
really
just
looking
for
any
opportunity
that
I
could
contribute
where
I
can.
F
Don
this
is
Ram
here
we
had
reached
out
to
you.
You
know
a
couple
of
weeks
back
just
you
know:
I
worked
with
Don
and
a
few
others
from
Oracle,
also
giant
I.
Think
I
sent
an
email
a
couple
of
weeks
back
about.
Like
you
know,
we
are
very
positively
increased
by
what
you
guys
are
doing
with
cross
plain.
F
We
see
it's
a
huge
opportunity
and
so
apparently
we're
working
very
closely
with
Rob
Clark
from
abound
on
some
of
the
you
know,
possibilities
on
on
the
providers
and
go
to
market
aspects.
But
specifically,
you
know
we
are
sort
of
treating
these
two,
as
as
independent
paths
like
one
is.
F
We
want
to
contribute
to
the
vision
of
cross
plane
and
that's
where
Don
and
and
a
bunch
of
other
Engineers
from
Oracle
would
like
to
you
know,
join
this
team
and
and
contribute
to
the
open
source
movement
here
for
cross
plain
parallely.
F
You
know
we're
obviously
working
with
a
bound
as
a
company
as
well,
because
we
see
that
as
an
opportunity,
and
so
you
know
as
as
we
move
forward,
we
look
forward
to
joining
these
calls,
as
Don
mentioned,
and
you
know,
listen
and
learn
and
obviously
contribute
in
the
coming
weeks.
F
A
That's
fantastic
yeah.
Thank
you
very
much
for
that
introduction
to
the
community
here.
Definitely
appreciate
that
and
I
appreciate.
You
know
the
sentiment
as
well,
so
you
know
I
think
there
will
be
lots
of
opportunities,
for
you
know
at
various
levels
of
the
project,
too,
you
know
feedback
and
in
bugs
and
issues
ETC
documentation.
A
You
know
like
helping
steer
the
road
map
in
terms
of
like
you
know
what
functionality
is
important
to
your
use
cases
and
how
you're
adopting
it
and
then
you
know
contributions
and
code
and
features
and
stuff
like
that.
We've
had
some
fantastic
contributors
coming
in
as
consumers
of
the
project
and
using
the
project
and
then
wanting
new
functionality,
and
you
know
Bob
is
immediately
coming
to
mind
on
that
of
driving
some
bigger
features
and
stuff
too.
G
Well,
I'm
I'm
Roberto
Montessori
at
Wildlife,
Studios,
it's
a
mobile
gaming
company
and
we're
building
like
a
platform
now
to
to
provision
like
infrastructure
and
all
that
that's
necessary
for
a
new
application
to
show
up
in
the
company
and
we're
using
Crosspoint
to
to
create
all
of
that
and
the
raw
infrastructure.
G
We've
had
a
previous
project
that
did
that
with
terraform,
but
we've
found
that
managing
terraform
files
in
repositories
wasn't
really
very
easy
to
do,
or
or
even
good,
so
we
decided
to
to
go
with
crossplaying
we've
been
using
it
for
a
couple
of
months
now
and
we
found
some
scalability
issues
with
Terror
jet
that
I
posted
an
issue
about
it.
I
think.
Maybe
at
some
point
we
can
take
a
look
at
that.
But
I
don't
know
if
that's
the
moment
right
now,
but
yeah
eventually
we'll
probably
contribute
as
well.
G
Some
other
providers,
for
example,
we're
working
right
now
on
a
on
a
vault
provider
for
for
crossplaying
to
be
able
to
manage
like
policies,
roles
and
and
other
about
things,
I'd
like
to
know
as
well.
How,
once
we
have
it
working
a
little
bit
as
well?
How
can
we
move
that
to
the
crossbling
country
Oregon?
A
Awesome
Roberto.
That
sounds
really
good.
Yeah,
there's
there's!
Definitely
you
know.
We've
done
that
many
times
before,
where
you
know
folks
have
started
the
independent
efforts
on
particular
providers
and
then
you
know
they
want
to
be
able
to
have
a
neutral
place
with
you
know
a
defined
governance
to
collaborate
with
other
people,
and
so
lots
of
different
providers
have
been
contributed
to
the
to
the
Crossman
contrib
and
it's
an
easy
process
as
well.
A
Just
a
couple
different
options
for
it
to
either
do
a
transfer
or
to
you
know
we
can
create
a
repository
for
you
and
you
essentially
can
create
a
PR
with
the
content
to
seed
that
repository.
So
you
can
just
reach
out
to
me
anytime
and
I'm
happy
to
help
guide
that
there
and
then
you
know
I'd
also
love
to
follow
up
on
some
of
the
scalability
things
you've
been
running
into
as
well,
because
there
has
been
a
ton
of
work.
A
You
know,
Nick
I
think
was
I
was
leading
some
of
that
effort
on
scalability,
and
you
know
we
put
a
couple
of
fixes
into
Upstream
kubernetes
as
well.
So
there's
a
bit
of
a
lot
of
progress,
or
you
know
focused
on
that
over
the
past
few
months,
so
it'd
be
good
to
see
what
maybe
you
could
still
be
lingering
there.
G
Yeah
I've
been
seeing
a
lot
of
issues
pop
up
here
and
there
about
how
to
make
cross-playing
more
scalable
right,
because
it's
one
thing
like
kubernetes
can
handle
a
whole
lot
of
custom
Resources
by
them
themselves
like
if
they
don't
communicate
with
external
resources.
But
once
we
add
that
extra
latency
of
having
to
communicate
with
external
resources,
everything
starts
to
break
down
a
little
bit.
A
Yeah
and
are
you
do,
are
you
like
you
know
we
can
follow
up
offline
to
Roberto,
but
are
you
all
working
with
like
a
like?
A
large
scale
of
you
know
instances
of
recent
resources,
or
is
it
more
like
the
the
large
number
of
you
know,
crds
of
customer
resource
definitions
of
types,
that's
causing
problems
for
you
all.
No.
G
G
A
G
A
A
All
right,
okay,
so
we're
about
running
out
of
time
now,
but
thanks
folks
for
introducing
yourselves
for
bringing
lots
of
lively
discussion
here
together,
definitely
enjoyed
it
and
then
yeah
I
think
before
so
before
we
meet
next
time.
We
will
have
the
1.10
release
out
as
long
as
it
sticks
to
schedule
which
I
don't
see
any
reason
for
it,
not
to
so
yeah
lots
of
things
to
follow
up
on
here
and
thanks
for
everybody
for
coming
and
contributing
today
and
it's
great
to
see
everybody
foreign.