►
From YouTube: 2023-05-04 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
A
Well,
good
morning,
good
day,
good
evening,
everybody
I
am
standing
in
for
Jared
today,
who
is
having
a
ball
of
a
Time
surfing
in
the
south
of
France.
A
So
we
we're
thinking
about
you
Jared
and
yeah,
we'll
we're
this
is
our
first
Craftsman
community
meeting
since
the
1.12
release
and
the
last
the
previous
meeting
was
canceled
due
to
conflicting
with
kubecon,
and
so
we've
got
quite
a
few
things
to
go
through
and,
as
usual,
please
add
any
items
to
the
to
the
agenda
that
you
would
like
discussion
and
we
can
get
to
to
those
we'll
start
off
by
just.
Let
me
show
you
my
screen
here.
A
So
we'll
just
recap:
there
was
obviously,
as
I
mentioned,
we've
we've
seen
the
1.12
being
released.
There
was
also
a
patch
release
followed
up
shortly
after,
and
that
was
based
on
findings
that
we
needed
to
fix
things
to
the
Arabic
manager
relating
to
permissions
to
allow
for
the
access
to
to
service
code
providers
for
provider
configs,
and
there
was
also
some
utilization
issues
that
was
picked
up,
so
that
was
really
starting.
A
That
actually
is
a
very
welcome
fix
because
it
opens
up
the
the
path
to
installing
less
crds
in
in
Cross
plane
and
we'll
more
and
more
on
that
a
little
bit
later.
So
as
we're
into
the
the
new
release
cycle
today,
we'll
be
going
over
kind
of
like.
A
What's
on
the
roadmap
for
for
1.13,
we
will
have
a
look
at
the
what's
currently
on
the
board
and
I'll
start
off
by
opening
the
roadmap,
and
it's
kind
of
like
I've
added
a
few
things
based
on
commitments
that
we've
had
from
people
who
can
work
on
certain
things
in
this
time
frame.
A
First
up,
you
know
installing
vrcrds
the
design
proposal
has
been
merged
and
and
the
the
proposed
solution
to
to
break
up
large
providers
in
in
servoscope
packages
has
been
accepted,
and
will
that
is
now
going
forward?
It's
not
gonna.
You
know
from
a
cross-plane
point
of
view,
there's
nothing
that
needs
to
be
done
in
113
to
to
accommodate
this
and
I'll
share
more
about
that.
A
little
bit
later
on
then
we're
also
looking
to
to
promote
composition,
functions
to
Beta
we're,
not
certain.
A
This
work
will
actually
get
to
Beta
in
the
1.13
release.
There's
quite
a
bit
of
things
that
need
to
be
looked
at,
but
I
know.
Nick
has
mentioned
that
he'll
be
putting
some
time
in
on
this
over
the
next
few
weeks
and
we'll
see
where,
where
we
land
with
with
composition,
functions
towards
the
end
of
1.13.,
at
least
we
will
should
be
able
to
address
quite
a
few
of
these
issues
and
then
we'll
be
working
on
promoting
environment
conflicts
to
to
vivon
Beta.
A
There's
a
feature,
that's
been
getting
a
lot
of
usage
in
the
community
and
folks
have
expressed
the
interest
in
in
moving
this
forward.
A
So,
if
the,
if
any
of
you
are
using
this
and
and
have
some
thoughts
on
things
you'd
like
to
see
in
there
make
sure
to
get
it
in
there
before
the
work
wraps
up
on
that,
and
then
we're
we're
looking
at
investing
in
improving
the
end-to-end
integration
testing
for
cross-plane.
So
right
now,
you
know
most
of
the
testing
is,
is
unit
testing
and
there's
not
a
lot
of
end-to-end
testing,
which
makes
it
difficult
for
the
maintainers
to
to
ex.
A
You
know
just
have
confidence
in
merging
new
changes,
especially
things
that
touch
areas
of
the
code
base
that
might
not
have
been
looked
at
in
a
while,
and
we
believe
that
as
cross-plane
matures
as
a
project,
it's
definitely
time
to
invest
in
expanding
on
the
end-to-end
testing.
A
So
we've
got
lavro
and
predrak
who
Joy
recently
joined
the
app
on
team
will
be
investing
some
time
into
looking
into
this
they're
fairly
early
on
they're
kind
of
like
investigation
on
this
they're
evaluating
the
different
approaches
and
we'll
put
a
proposal
together
soon
for
for
how
they
propose.
We
we
tackle
this
and
then
Felipe
is
continuing
with
the
the
work
he
started
on.
A
The
composition,
validation,
so
he's
already
been
implementing
quite
a
few
of
the
phase,
two
improvements
to
extend
the
schema,
aware,
validation
and
we'll
continue
pushing
that
forward
in
the
1.13
time
frame
and
there
I
go
and
close
the
wrong
thing
again
and
then,
lastly,
we're
getting
close
to
what
seems
to
be
alignment
on
the
proposal
for
the
ability
to
ignore
changes
on
specific
fields,
and
lover
also
mentioned
that
he'll
be
looking
to
polish
up
the
proposal
over
the
next
few
days
and
we
should
be
able
to
get
that
merge
soon
as
well,
and
implementation
might
make
it
in
1.13
as
well.
A
So
this
is
currently
worked
at
people
have
kind
of
like
committed
to
to
looking
at
over
the
next
three
months.
If
there
is
anything
on
you
that
or
something
you're
not
seeing
on
here
that
you
really
feel
passionate
about.
You
have
an
opportunity
now
to
to
verbalize
that,
and
also
you
know
in
the
Crosman
slack
you
can
reach
out
in
the
crosswind
owners
channel
for
that
as
well.
A
Anybody
have
any
questions
or
feedback
on
the
current
roadmap
commitment.
B
Hi
I
have
one
question:
is
Christopher
yeah
if
we're
promoting
the
composition
function
and
the
environment
configs
to
V1
beta1?
Is
it
also
possible
then,
to
downgrade
cross
plane?
B
So
if,
if
we're
bumping
this
in
in
13's
version-
and
we
don't
write,
then
cross
plan
to
the
12th
version,
because
there
is
one
issue
in
the
community
between
version
11
and
10-
it's
not
possible
to
downgrade
cross
plan
after
you
did
the
first
upgrade,
because
then
in
the
crd
there
are
two
versions
available
and
the
old
version
of
cross
plan
is
not
aware
of
it.
So
it
would
be
helpful
if
dog
riding
is
possible
if
you're
bumping
this
year,
at
least
there.
C
Chris,
could
you
Christopher?
Could
you
raise
a
if
there
isn't
one
already?
It
would
be
helpful
to
have
a
issue
on
Cross
Lane
about
this
General
problem,
not
just
1.11
to
1.10.
C
Yeah
I
I'm,
guessing
from
from
the
brief
sound
of
this
all
right
yeah,
it
would
be
I
haven't
seen
this
issue,
yet
this
is
the
first
time
seeing
it
just
looking
at
it.
The
title
says:
I
can't
go
back
to
1.11
to
1.10.
It
sounds
like
the
actual
underlying
problem
is:
where
did
you
see?
Id
is
added.
B
A
All
right,
we'll
open
the
the
board
and
just
have
a
look
at
the
work
that
is
currently
being
earmarked
for
113.
Overall.
A
As
a
reminder,
you
know,
roadmap
items
are
mostly
kind
of
like
larger
features
that
push
the
the
project
you
know
strategically
forward,
but
that's
only
a
a
small
part
of
all
the
effort
that
goes
into
overall.
A
If
we
look
at
things
that
are
in
review
package,
signature,
validation,
I,
don't
know,
I
don't
see
Jesse
on
the
call
today,
so
we'll
see
if
we
get
an
update
from
Jesse
on
that
I
know
this
one
I
believe
Jared
has
already
looked
at
yeah
and
that
should
be
closed
soon
as
well,
and
here
I
do
that
again.
A
And
can't
use
composition
function
to
update
XR,
let's
see
here
it's
in
review.
Currently,
what
is
our
pull
requests.
A
Nick
I
see
you're
reviewing
this
one,
so
that's
great,
although
I
see
Bradley
hasn't
responded
in
a
while
Bradley's
on
the
call.
So
maybe
we
can
ping
him
on
that
again
all
right
and
then
let
me
just
back
here.
A
Implementing
image
pool
secrets
for
composition
functions.
You
know
this
one
has
been
been
around
for
a
while
as
well.
A
C
Know
someone
someone
has
a
pull
request
open
that
implements
this
to
be
fair,
Andrew
I,
don't
see
upon
this
call.
I
did
a
pretty
thorough
review
yesterday
and
unfortunately,
it's
a
fair
bit
of
work
so
slow
down
like
that,
but
it's
happening
yeah,
just
what
I,
just
while
I'm
while
I'm
talking
it's
an
amazing
way
to
misrepresent
how
much
I'm
going
to
be
working
on
composition,
functions.
I
definitely
would
like
money
today
this
week
to
do
a
PR
or
two.
A
Yeah
no
I
I
definitely
didn't
want
to
create
the
expectation
that
nickel
will
be
focusing
on
it
for
a
lot
and
then
add
credential
helpers,
support
for
composition,
functions,
I,
assume
that
will
be
part
of
the
composition,
functions,
work
and
then
I
know
Hassan.
You
you
mentioned
that
you
had
a
look
at
this
one
specifically
around
a
server-side
solution
for
this,
which
isn't
trivial
and
it'll
probably
need
a
little
bit
more
time
before
we
get.
We
get
to
a
fix
for
that.
D
E
A
E
A
Right
in
progress
as
as
we've
talked
about
earlier,
Philippe
is
on
the
composition,
validation
and
ignore
changes.
Proposal
is
getting
close
to
being
finalized
all
right.
A
Moving
on,
we've
talked
about
the
cross-plane
Milestones.
Nobody
raised
any
other
priorities
for
today.
Let's
move
on
to
provider
releases
Investments,
so
there's
been
a
recent
release
as
a
little
last.
What's
now
been
four
weeks
instead
of
two
weeks
since
we
skipped
the
previous
meeting
so
provider,
AWS
0.390
was
released
provider
ansible,
zero,
five
zero
was
released
last
week,
I
believe,
and
it
was
a
round
of
releases
of
advanced
providers
as
well
and
then
update
on
implementing
smaller
service
code
providers.
So
now,
with
the
design
doc
merged.
A
A
Finally,
they've
they've
kind
of
like
done
an
initial
validation
to
prove
that
it
works
at
a
technical
level
and
now
just
finishing
up
all
the
build
pipelines
and
optimizing
the
images
and
the
build
process
to
make
sure
this
works
and
doing
some
testing,
and
we
should
have
release
candidate
packages
ready
for
people
to
test
and
play
around
with,
and
if
you're
interested
in
in
testing
these
out
and
able
to
provide
feedback.
A
Please
join
the
the
Sig
channel
in
the
community
slack,
so
we
can
keep
you
up
to
date
on
on
progress
there
on
the
Vayner
update
side.
So,
as
I
mentioned
already,
you
know
we're
busy
working
on
promoting
schema
where
composition
validation,
as
well
as
the
improved
end-to-end
integration,
testing
and
right
Community
topics
and
questions.
So
on
the
content
side,
there's
been
quite
a
bit
of
content.
Obviously,
thanks
to
kubecon
I've
listed
all
the
the
talks
that
I
could
find
that
mentioned.
A
Cross-Plane
and
and
most
of
them
have
videos
uploaded
to
YouTube
now
already,
there's
also
monitoring
as
code
with
crosswind,
a
blog
post
at
Matthias,
wrote
earlier
this
month
last
month
and
build
a
modern
platform
with
cross-plane
and
thousand
Argo
CD,
and
then
also
Community
member
salaboy
published
a
kind
of
like
a
cloud
native
snapshot
publication
that
he's
doing
right
now
that
also
covers
cross-plane
and
outbound
in
there
it
is
behind
a
paywall,
so
I'll
just
mention
that
manibu
just
added
a
article
here,
stuff.
A
Well,
thank
you
very
much
and
then
all
right
I
do
want
to
encourage
folks.
If
you
see
articles
mentioning
Crosman
or
talking
about
it,
you
know
do
post
it
in
an
announcements
channel
in
in
slack
it's
a
great
way
to
to
bring
some
get
some
eyeballs
on
these
articles.
A
This
is
just
a
reminder
from
Jared.
He
also
posted
this
in
in
the
slack
Community
slack
earlier,
where
we're
we're
looking
at.
A
A
You
know
to
put
a
little
thumbs
up
on
something
and
so
on,
but
it
does
actually
give
signal
and
it
helps
you
know
in
in
helping
understand
what
is
important
to
the
community
and
prioritizing
the
work
like
that,
so
encouraging
folks
to
to
start
engaging
with
issues
that
they
feel
are
important
to
them
or
have
and
interesting
and
add
a
thumbs
up
there
and
then
I
also
called
out
Nick's
message
in
in
slack
earlier
this
week
around
or
yesterday.
A
Actually
Nick,
do
you
want
to
verbalize
it
around
the
rack
manager
moving
to
to
basic,
rather
than
advanced.
C
Yep,
it's
pretty
much
what
it
says
there.
So
please
respond
on
that
issue
and
let
me
know
if
you
do
use
the
back
rolls.
The
cropland
creates
an
H
namespace
or
let
me
know
if
you're
doing,
if
you
don't
know
what
I'm
talking
about.
Please
open
up
that
issue
and
just
be
like
I,
don't
know
what
this
functionality
is.
That
will
help
us
decide
whether
we
can
turn
it
off
or
not.
A
All
right,
thanks
Carlos
for
adding
more
content
there
and
then
on
to
PR's
to
discuss
or
that
needs
attention.
So
Stephen
you
you're
on
the
call.
A
Today
you
opened
a
PR
recently
to
add
the
volume
and
volume
man
support
to
control
the
config,
and
you
know
this
is
one
that
is,
you
know
interesting
one,
because
obviously
the
controller
config
API
has
been
deprecated,
there's
a
desire
to
move
to
PRI
in
the
future,
and
we
don't,
but
we
don't
actually
have
a
commitment
from
somebody
to
work
on
that
at
the
moment.
E
Yeah,
what
happens
here
in
the
use
case
is
that
if
you're
running
a
provider
pod-
and
you
have
something
like
a
proxy
in
between
it
and
the
cloud
provider
which
a
lot
of
large
Enterprises
have
it's
not
easy
right
now
to
be
able
to
inject
custom
CA
certificates
into
a
provider.
E
And
if
you
try
to
modify
the
deployment,
the
the
cross
plane
controller
will
go
in
and
rewrite
the
deployment
over.
You
so
I'm,
not
sure.
If
anybody
in
the
community
has
any
workarounds
I
saw
some
like
coverino
Pro
policies
but
yeah.
So
this
is
just
basically
kind
of
mapping
the
same
data
structures
that
are
in
a
deployment
and
adding
that
to
the
controller
config.
A
And
you,
you
had
a
sorry
Dan,
it's
good
to
see
your
face
here.
You
had
a
you
added,
a
comment
actually
that
you,
you
were
not
in
favor
of
expanding
the
deprecated
API.
You
want
to
add
something
here.
F
Yeah
it's
it's
kind
of
a
mix
of
like
both
practical,
because
it's
already
a
really
big
API
and
also
just
from
like
a
messaging
perspective
that
we
don't
want
to
be
encouraging
like
further
use
of
this.
But
it's
a
very
valid
statement
or
concern
right
that
we
haven't
made
progress
on
the
PRI
thus
far.
F
So
if
we
are
going
to
as
I
kind
of
like
recommended
their
prohibit
expanding,
this
API
I
think
that
we
should
start
some
active
work
on
defining
what
the
roadmap
is
for
the
pra,
because
it's
not
really
fair
to
leave
users
kind
of
like
in
between
there
I
do
think
I.
Think
I
just
saw
it
in
the
chat
I'm.
Unfortunately,
on
my
phone
today,
but
I
looked
like
someone
mentioned
a
mutation
web
hook,
which
I
also
believe
would
work
in
this
case.
F
F
I
think
I
put
up
my
hand
to
have
a
discussion
with
some
folks
about
the
driving
it
Forward
I
want
to
make
sure
that
you
know
folks
are
all
represented
there.
So
I
won't
necessarily
commit
to
saying,
like
Hey,
we're
going
to
drive
this
forward,
but
I
will
commit
to
getting
folks
together
to
start
talking
about
what
the
the
course
of
action
is.
There.
C
So
I
want
to
be
careful
on
this
one.
My
understanding
is
that
for
us
and
about
we
have
like
multiple
customers
who
are
blocked
by
this
at
the
moment,
and
it's
like
a
it's
like
a
line,
change
or
something
like
that
being
so,
while
I
understand
the
sort
of
you
know,
I'm,
usually
very
much
on
the
side
of
let's
not
do
the
wrong
thing
api-wise.
C
If
we're
talking
a
quarter
or
more
like
we
don't
have
PRI
on
our
roadmap
at
all
at
the
moment,
so
I
don't
think
we
can
go
back
to
our
customers
and
just
say
sorry
folks
copy
that
for
a
long
time,
maybe
maybe
that
means
we
book
a
setup
out
to
get
through
or
something
like
that
or
maybe
the
keyboard
I
think
works
out,
but
it
I
I
I
get
I
get
that
we
don't
want
to
send
a
message
that
we're
adding
more
stuff
but
there's
already
a
whole
bucket
of
stuff
in
there
we've
already
said
yet
we
know
this
is
not
the
plan.
C
F
I
feel
like
this
is
a
a
pretty
good
use
case
for
a
downstream
distro,
like
a
pretty
good
example
of
being
able
to
get
in
quickly,
because
even
if
we
do
add
it
right
now,
it
you
know,
in
theory,
isn't
going
to
be
an
upstream
release
for
a
bit
anyway,
since
we
just
had
a
recent
release,
so
I
would
obviously
I
I,
don't
have
an
essay
on
how
this
works
anymore,
but
I
would
advocate
for
the
downstream
implementation.
If
that
works.
For
folks.
C
Yeah,
my
gut
feeling
is
we're
being
a
little
bit
overly
philosophical,
relevant,
pragmatic,
yet
but
I'll
sort
of
defer
to
I'll
chat
to
the
books
about
and
see
how
urgent
this
is
and
what
the
options
are.
C
B
C
This
was
like
a
big
bunch
of
functionality
going
into
control
config.
It
was
like
really
complicated
and
adding
a
bunch
more
stuff,
I'd
be
like
whoa
yeah,
let's
pop
the
brakes,
but
the
controller
configure
already
has
like
what
you
know
in
out
of
the
X
fields
on
deployment
and
it's
adding
like
one
more
I
I,
don't
know.
A
Anybody
else
in
the
community
have
some
thoughts
on
this
topic.
F
I
think
that
current
story
is
there
isn't
a
road
map
in
place
for
it.
So
if
we're
going
to
be
denying
changes
like
this,
then
I
think
that's
at
the
very
least
yeah
something
that
needs
to
be
put
out
and
shared
with
the
community,
because
it's
not
really
fair
to
say,
like
Hey,
we're
not
going
to
unblock
this
use
case,
and
we
don't
have
a
plan
for
how
we're
gonna
do
it.
Yeah.
D
C
C
Be
all
right,
but
it,
but
it
is.
It
is
just
like
an
issue
at
the
moment.
It's
not
even
like
a
one-pager,
it's
kind
of
a
it's
kind
of
a
very
broad
future
direction.
To
look
into
so
like
my,
my
hunch
is
that
it's
probably
going
to
be
a
while
unless
someone
steps
up-
and
it's
like
I-
really
feel
passionate
about
this-
that
I'm
gonna
drive.
It.
F
Yeah
I
mean
I,
think
that's
I
think
we
should
have
that
conversation
basically
before
we
make
a
decision
here,
because
if
we
do
have
that.
D
F
Right
exactly
like
we
should,
we
should
have
a
conversation
about
whether
we're
going
to
commit
to
committing
this
thing.
Basically,
before
we
make
a
decision
here
and
I
think
we
can
do
that
pretty
eminently
so
I'm
happy
to
be
getting
that
set
up.
F
D
F
D
Are
suffering
and
they
don't
they're
like
we
also
have
to
be
fair
right.
Not
everyone
knows
when
we
throw
like
terms
or
like
Solutions,
assume
that
everybody
knows
what
we're
talking
about.
But
if
somebody
wants
it
wants
to
explain
like
what.
What
would
what
a
small
Mission
web
hook
will
look
like
with
a
snippet
of
code
or
an
example
using
Governor
like
to
to
folks
that,
like
are
happy
with
that
solution,
is
that
they
just
don't
know
right
enough
kubernetes
to
figure
like
oh
there's.
D
This
thing
called,
like
you
know,
extensions
that
you
can
add
two
parts
and
to
add
things
to
parts
that
certain
amount
of
the
community
are
like
that's
easy
like
we
do
it
every
day
and
the
other
community
like
I,
don't
know,
I
have
no
idea
what
you're
talking
about
about
what
is
imitation
Web
book
or
what
it?
What
is,
how
do
you
spell
governor
or
like
Apollo
sitting
mutating
thing.
C
Yeah,
the
other
thing
to
keep
in
mind
here
is
that,
like
we've
got
this
type
called
controller
config
and
it
basically
has
a
template
for
deployment
in
it,
and
it's
got
you
know,
I,
don't
know
what
the
actual
numbers
are,
but
they've
got
50.
The
53
of
the
deployment
has
in
it.
So
while
we're
in
this
interview
period,
if
we're
taking
a
photo
or
it
goes
somewhere
else,
then
we
need
to
communicate
to
people.
This
is
a
deprecated
API
Fields.
If
it's
not
one
of
those
fields,
then
you'd
better
go.
C
Do
this
other
thing
as
well,
so
a
lot
of
folks
are
going
to
end
up
being
like
okay.
I've
got
my
controller
config
to
specify
these
10
fields
and
I've
got
my
mutating
and
Mission
Control
web
hook
to
specify
this
other
video.
That
I
could
put
people
in
a
pretty
sort
of
Gross
Middle
Ground,
while
we're,
while
we're
waiting.
D
Yeah,
and
and
also
specifying
the
version
right
with
this
type
of
things
like
the
imitation
where
who
may
not
work
in
the
next
version.
If
changes
are
made
or
or
something
right,
so
they
always
have
to
double
check
that
what
they're,
mutating
or
or
the
way
they're
mutating.
That
was
too
much
to
send
sorry.
A
It
sounds
like
the
crosswind
maintainers
will
discuss
the
right
path
forward
and
communicate
on
the
pr
as
necessary.
A
All
right
any
last
minute
discussions
anybody
would
like
to
bring
forward.
A
Feels
like
a
sufficiently
awkward
long
pause
there
and
with
that
we'll
wrap
up
today's
meeting.
Thank
you
for
joining
everybody.