►
From YouTube: 2023-07-27 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
There
we
go
all
right,
recording
has
started,
and
this
is
the
July
27th
2023
cross
plain
community
meeting
by
far
the
most
important
news
of
the
day
is,
as
of
an
hour
ago,
we
shipped
the
1.13
release.
So
this
is
a
a
nice
Milestone
here
with
a
bunch
of
really
cool
stuff
and
it's
and
it's
very,
very
fresh
and
hot
off
the
press
this
year.
So
just
within
the
last
hour,
the
as
Esky
and
Philippe
finished,
you
know
going
through
the
release
process
and
Publishing
everything.
C
A
Oh
okay,
yeah,
it's
okay,
cool,
ESG
or
Philippe.
If
you
could
update
the
link
in
the
release,
notes
to
the
blog
post,
yeah.
A
Thank
you
yes,
so
there's
a
whole
blog
post
to
read
about
everything,
just
kind
of
the
high
level
big
news
items
here,
though,
is,
as
we've
talked
about
on
this
community
meeting.
You
know
we
do
have
two
new
maintainers
within
this
Milestone
Bob
and
Philippe,
and
you
know
they've
already
started
contributing
heavily
and
you
know
I'm
super
happy
to
have
them
on
the
team.
A
Really
big
news,
too,
is
that
we
finished
our
security
audits.
That
is
a
big
part
of
the
you
know
maturing
process
to
get
to
full
graduation
with
the
cncf,
and
so
the
the
folks
on
the
edelogics
team
worked
with
us
for
the
last
couple
months
and
and
with
Philippe.
Specifically
Philippe
was
the
the
largest
part
by
far
from
the
cross-plane
community
and
team
working
on
it.
A
But
you
know
we
went
through
a
full
audit
there
you
know
found
16
issues
in
total
and
then
got
all
got
everything
there
fixed
and
merged,
and
part
of
the
patch
releases
for
all
the
currently
supported
releases
of
Cosplay
and
included
in
the
1.13
Milestone
as
well.
So
that
was
really
big
news
and
there's
a
specific
blog
post
for
that
one
as
well.
A
If
you
want
to
read
more
about
it
and
let's
hope
this
link
works,
it
does
so
all
the
details
about
the
security
audit
can
be
read
about
on
the
blog
as
well
a
like
another,
a
big
feature
that
was
put
in
was
you
know
it
was
the
ignore
changes
ability
it's.
You
can
think
of
that
as
an
extension
of
the
observe,
only
resources
API,
where
you
know
you
can
say
hey
for
these,
the
use,
the
management
policies
that
would
enable
you
to
do
observe
only
resources.
A
You
can
also
use
those
to
enable
you
to
ignore
certain
changes,
such
as
like
a
cluster
Auto
scaler
wants
to
change
your
node
counts
in
your
cluster.
You
can
tell
crossplaying
to
just
ignore
that,
so
that
will
be
available
that
gets
released
as
part
of
the
providers.
The
core
functionality
in
Prospect
runtime
is
already
there
and
it's
published
and
all
that
stuff,
but
the
you
know
the
user
facing
ability
to
consume
this
functionality
is
going
to
be
an
official
I'm.
A
Sorry
in
providers
that
were
going
to
be
released
fairly
soon,
we
also
into
testing
framework,
which
is
running
on
every
epr
now,
and
every
commits
Master
with
a
series
of
tests
that
will
are
continuing
to
be
invested
in
over
time.
So
everybody
like
that
for
the
perspective
of
other
people,
are
maintaining
our
Quality
Bar
and
making
sure
that
we
don't
have
regressions
and
all
that.
A
So
it's
really
nice
to
be
testing
at
a
higher
level
at
the
integration
level
there,
as
opposed
to
just
our
unit
tests
and
make
sure
that
coverage
continues
to
expand
as
well
composition.
Functions
are
continuing
to
be
invested
in
I.
Think
folks
have
seen
the
proposal
for
approving
the
developer
experience
on
that
as
well.
So
a
lot
of
progress
is
made
on
this
Milestone
and
we're
expecting
to
mature
it's
a
beta
in
the
1.14
time
frame,
and
then
also
you
know.
A
If
we
all
recall
here
early
in
the
1.13
Milestone,
we
went
through
a
process
of
updating
how
we
package
and
build
providers
so
kind
of
break
them
apart
into
smaller
service
scoped
ones.
So
that
was
part
of
the
1.13
time
frame
as
well
and
I
know.
There's
been
a
lot
of
relief
on
people
for
in
clusters
for
people
that
have
adopted
that
so
a
lot
of
exciting
things
on
1.13
and
I'll.
Just
keep
accepting
these
ones
here.
A
Do.
Is
there
anything
else
that
folks
wanted
to
call
out
in
1.13?
You
know,
especially
folks
that
were
heavily
involved
in
it,
the
that
I
didn't
touch
on
yet.
A
All
right
well
either
way,
though
you
know
we
could
be
definitely
proud
of
that
release
and
it's
really
nice
to
get
that
out
the
door
here,
and
so
you
know
it
kind
of
be
be
happy
with
what
we've
accomplished
today
and
I
know
that
the
community
and
the
ecosystem
as
a
whole
will
be
benefiting
from
it.
So
great
work,
everybody
on
getting
that
release
out
and
I
know.
A
It
was
a
lot
of
efforts
and
thanks
for
everybody's
efforts
that
we
put
into
it
so
the
let's
look:
real
quick
at
the
1.13
release
board
just
to
see
what's
still
lingering
there
so
Philippe
what
is
left
for
us
to
go
ahead
and
close
out
the
audience
issue.
Is
there
anything
big
like.
A
Sweet
awesome
so
yeah.
Let
me
close
that
out
the
1.13
release
issue.
So
there's
just
a
couple
lingering
things
at
the
very
end
here:
right,
Esky,
nothing
else,
you
know
of
that.
It
still
needs
to
be
done.
A
Sweets
all
right,
so
that's
almost
almost
done
as
well
and
then
I
guess
slow
fro.
Do
you
do
you
want
to
we'll
wait
to
close
this
until
we
actually
have
a
provider
released
with
this.
D
Yeah,
the
provider
research
should
go
out
on
Monday
I
mean
the
changes
for
in
it
provider.
This
is
the
last
thing
left.
It.
D
A
Awesome,
so
that
is
not
very
far
away
at
all:
that's
just
a
few
days
away.
So
then
that
puts
us
in
really
good
position
for
everything
here.
This
you
know
kind
of
within
the
realm
of
the
1.13
Milestone
will
be
closed
out
and
we
will
be
in
great
shape
there.
A
So
then,
that
kind
of
sets
this
up
for
1.14
and
going
into
into
that
I
think
that
you
know,
we've
had
a
fairly
well
defined
road
map
for
a
for
a
little
bit
now
so
I
think
that's
like
what
is
planned
in
the
1.14
time
frame
is,
you
know,
probably
no
real
surprises
there
if
you've
been
following
along
with
the
roadmap
or
following
along
with
the
roadmap
over
the
past
month
or
so
so,
I
think.
Maybe
the
only
thing
really
to
mention
here
and
I.
A
Think
next
community
meeting
once
we've
officially
started
the
1.14
Milestone
and
you
know
timeline
for
that.
Then
we
can
dive
more
into
this,
but
I
think
we'll
also
see
some
advancements
on
a
couple
of
other
things
that
are
scheduled
for
you're
kind
of
like
wrapping
up
or
release
in
1.15,
we'll
be
making
some
progress
along
those
as
well.
A
You
know,
but,
like
notably
you
know,
project
is,
is
making
progress
on
the
design
for
cross-resource
references.
They
I
think
that's
in
the
agenda
for
later
on
today
and
then,
like
developer
experience,
stuff
I
think
is
going
to
be
a
big
Focus
for
us
as
well,
not
sure
exactly
what's
going
to
ship
there,
but
making
progress
in
1.14.
A
In
addition
to
all
of
these
other,
fairly
fairly
highly
demanded
and
important
and
impactful
features,
we'll
all
be
kind
of
included
in
the
1.14,
so
I
think
that's
shaping
up
to
be
a
pretty
impactful,
pretty
big
release
as
well,
which
we
will
be
diving
more
into
as
we
get
into
the
the
cycle.
For
that,
you
know
reminder
that
our
releases
are
quarterly,
so
that
will
be
late.
Late.
October
is
when
we're
scheduled
to
do
this
release.
So
we've.
C
A
All
right,
then,
we
can
keep
on
moving
on
here
in
terms
of
Provider
releases.
I
didn't
get
a
chance
to
look
through
to
see.
If
there
are
recent
provider
releases,
but
as
lovro
was
just
mentioning,
there
will
I
think
there
is
expected
to
be
a
swath
of
Provider
releases
on
Monday.
Is
that
right,
Lebron
Sean.
D
Yeah
yeah:
this
is
the
Band-Aids
John
correct
me.
If
I'm
wrong.
A
And
is
there,
is
there
other
things
to
note
in
those
those
provided
releases?
Besides,
you
know
the
ignore
changes,
abilities.
B
Yeah,
there's
there's
actually
quite
a
few
updates
to
object,
that's
being
made
right
now,
I'll
press
not
on
the
call,
otherwise
it
could
have
given
us
a
big
update.
But
you
know
this
is
in
line
before
our
big
Focus
around
performance.
B
A
Awesome
so
I'm
gonna
take
a
note
of
that
big
release.
A
Was
that
the
31st
is
that
right.
A
All
right
and
I
also
wanted
to
call
out
that,
because
I
think
this
was
since
the
last
community
meeting
I
honestly
can't
remember,
but
some
lovely
folks
contributed
the
openstack
provider.
That
has
some
traction.
You
know
in
their
in
their
own
fork
and
their
own
GitHub
organization.
A
So
so
Jacob
was
driving
that
and
so
that
is
now
available
in
the
as
a
you
know
in
the
Crossway
and
contribute
org
as
a
neutral
place
for
everyone
to
from
the
community
to
be
to
be
collaborating
upon
that
together
and
we
are
taking
the
steps
right
now.
So
it
should
be
pretty
darn
soon
to
get
that
published
to
the
marketplace
as
well.
So
that'll
be
an
easy
place
to
to
find
and
explore
and
discover
and
download
install
that
that
provider.
A
Contributing
that
and
getting
that
as
part
of
the
community
set
of
providers.
A
All
right
cool,
let's
move
on
down
then
to
the
community
topics,
then
so
in
terms
of
content.
Here,
a
lot
there's
a
whole
bunch
of
pieces.
Recently,
we've
looked
at
briefly.
The
blog
post
for
1.13
that
goes
over
goes
over
everything
that
was
included
in
that
Milestone.
So
do
feel
free
to
check
that
out.
We
talked
about
the
security
audits,
blog
post
as
well.
A
That
goes
into
all
the
details
about
what
we
found
in
the
security
audits,
what
we
fixed
and
all
that
sort
of
stuff
the
cncf
picked
up,
that
blog
post
and
reposted
it
onto
their
blog
as
well.
So
that's
cool
to
see
the
cncf
kind
of
making
a
little
bit
of
noise
about
that
accomplishment
as
well.
A
A
A
So
these
are
all
the
interesting
you
know
pieces
of
content
and
things
that
are
going
on
that
you
know
folks
writing
about
the
project
if
anybody
has
other
links
or
feel
free
to
add
them
here,
as
a
suggestion,
I'll
make
sure
to
to
get
that
to
get
that
accepted
into
the
agenda
doc.
Also.
A
So,
as
I
was
just
mentioning,
but
I
want
to
go
into
a
little
bit
more
detail
about
it,
though,
is
that
you
know
we
are
planning
an
event
for
I
think
it
was.
Is
it
August,
sorry,
September,
19th
I
think
it
is
yeah
September
19th,
and
so
we
have
an
open
call
for
speakers
right
now
about
for
anybody
who
wants
to
share
their
experiences
CrossFit
and
share
their
story
share
their
practical
knowledge,
whatever
it
may
be.
We
are
super
open
for
interesting
ideas
for
talks.
A
One
thing
that
had
been
causing
a
bit
of
confusion
for
everybody
I've
heard
is
that
we
forgot
to
mention
how
long
the
talks
will
be
so
when
you're,
if
you
are
submitting
an
idea
here,
you
should
plan
for
your
talk
being
about
15
minutes
long.
Those
will
be
the
session
links
that
we
have
so
do
plan
accordingly
in
terms
of
what
contents
that
you
you'll
be
able
to
to
go
over
in
that
time,
and
then
the
CFB
closes
on
August,
2nd,
so
I
think
it's
six
days
from
now.
A
So
it's
the
Wednesday
of
next
week
and
then
within
two
weeks
from
there
we
will
send
out
notifications
for
all
the
talks
that
were
accepted.
I
know,
there's
been
some
really
cool
talks
that
have
been
submitted
already,
but
there's
certainly
room
for
more
and
if
anybody
has
any
questions
or
wants
some
feedback
on
your
proposal
or
anything
like
that.
A
Just
reach
out
to
me
directly
and
I'm
happy
to
provide
any
sort
of
guidance
or
feedback
about
that
happy
to
spend
time
on
that
cool
and
then
the
last
agenda
item
we
had
in
the
community
section
here
was
that
we
are
haven't
made
a
lot
of
noise
about
this.
Yet,
but
we'll
we'll
be
talking
about
it
a
little
a
little
bit
more
but
I
kind
of
wanted
to
get
it
out
to
this
audience
of
folks
here
at
the
community
meeting.
A
A
But
if
you
want
to
right
now,
you're
more
than
welcome
to
click
this
link
here
and
share
your
feedback
in
that
Community
survey
thing
there's
a
forum
there
and
then
what
I'm
thinking
to
do
here
also
is
that
folks
that
want
I
think
it'll
be
really
useful
to
have
some
high
bandwidth
discussions
here
as
well.
A
So
folks
that
you
know
kind
of
get
some
information
and
feedback
submitted
in
that
survey
here,
if
you're
open
to
chatting
with
me
or
other
members
of
the
maintainer
team,
or
steering
whatever
to
kind
of,
have
a
discussion
and
learn
more
and
really
kind
of
listen
to
everybody.
I'm
certainly
excited
to
do
that.
So
this
is
one
way
to
get
that
process
started
is
you
know,
do
the
survey
and
we
can
hopefully
meets
and
talk
more
and
then
you
know,
get
more
good.
Ideas
coming
to
the
project,
make
sure
everyone's
heard
cool.
A
So
that's
everything
I
had
for
the
community
topics
here.
I
think
the
you
know
the
drastically.
The
big
thing
today
is
1.13..
So
still
super
happy
about
that.
C
A
Let's
go
ahead
on
to
project
for
the
cross
resource
references
proposal
that
you've
got
going
on.
Do
you
want
to
share
your
screen,
protect
to
kind
of
talk
through
it
a
little
bit
or.
C
Well,
I
mean
I,
didn't
plan,
I
mean
I
was
just
wanting
to
to
to
share
with
people
that
this
PR
is
open
and
since,
since
a
week
ago-
and
we
had-
we
have
already
started
discussion
there-
so
I
just
think
well,
I
did
the
Community
member
to
to
visit
the
pr
and
if
they
have
any
any
concerns
or
anything
that
they
would
like
to
share
or
share
with
other,
really
helpful
yeah.
That's
all
what
I
wanted
to
to
announce.
Okay,.
A
Cool
yeah,
yeah
and
I
want
to
see
it.
Just
look
real
quick
I'll
put
on
the
screen
here,
just
to
see
the
what
the
proposal
looks
like
so
people
can
get
kind
of
a
quick
visual
of
of
what
this
Merit
looks
like.
C
Yeah
I
mean
we
are
basically
proposing
a
a
way
to
reference
fields
in
in
an
arbitrary
kubernetes
resource.
This
is
helpful
in
some
cases
where,
where
the
current
established
convention,
where
we
have
like
reference
field
and
the
reference
field
is
basically
embedded
with
the
kind
of
of
the
big
certain
resource
and
and
the
path
where
the
the
value
is
found,
so
we
can
relax
that
and
then
configure
it
around
time
in
the
deployment
time.
C
So
basically,
that's
that
the
the
the
idea
and
the
proposal
so
we're
still
not
clear
if,
if
the
approach
we
described
currently
in
the
rules
will
be
the
final
one,
but
it's
a
really
good
good
basis
for
the
for
discussion.
A
Nice
Frederick
I
really
do
like
and
I
appreciate
here,
that
this
design
is
is
being
done
fairly
early
in
the
Milestone.
Also,
so
we'll
have
time
to
think
about
it
to
kind
of
make
sure
that
we're
getting
everybody
aligned
there
and
that
the
API
is
looking
good
and
then
before
we
do
implementation
in
the
1.15
time
right.
C
A
All
right
so
I
think
that's
everything
we
actually
had
on
the
agenda
for
today.
It
was
a
little
bit
of
a
light
agenda,
since
it
was,
you
know,
a
big
scramble
to
get
you
know
the
1.13
in
security
Audits
and
everything
done
there.
A
So
all
that
is
done
and
out,
and
so
there's
not
a
lot
more
to
talk
about
for
in
terms
of
like.
What's
left,
what
do
we
have
to
do
all
this
sort
of
stuff,
so
I
think
next,
you
know
next
time
we'll
talk
more
deeply
through
the
1.14
Milestone
and
what
we're
planning
there.
A
But
the
floor
is
open
here.
If
anybody
has
something
to
add
to
the
agenda
that
did
not
get
put
into
the
dock
yet.
A
All
right,
then,
if
that
is
everything
that
folks
wanted
to
chat
about,
then
we
can
go
ahead
and
adjourn
and
get
some
time
back
early
today.
But
once
again
you
know,
congratulations
and
thank
you
very
much
to
everybody
for
a
successful
1.13
release
and
successful
security
audit,
and
you
know
all
that
stuff-
a
lot
to
be
celebrating
today,
so
great
work,
everybody
and
thank
you
thanks,
cheers
see.