►
From YouTube: 2023-07-13 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
July
13th
2023
cross
plain
community
meeting
lots
of
stuff
to
talk
about
today.
You
know
as
we're
kind
of
moving
on
into
the
final
days
of
the
1.13
release.
I,
don't
think,
there's
a
big
surprises
or
anything
majorly
contentious
left
there.
So
I
don't
expect
the
agenda
to
take
super
long
today,
but
I
definitely
want
to
make
space
as
we're
at
an
important
phase
of
the
Milestone
here,
getting
close
to
a
release
all
right.
So
let's
just
jump
on.
A
Actually
let
me
do
something
real
quick.
Let
me
share
into
the
chat
a
direct
link
to
the
agenda
doc
so
that
if
anybody
wants
to
add
topics
to
the
agenda
that
they
that
are
not
currently
included,
that
they
can
do
that
now,
all
right,
so
1.13
coming
up
hot.
So
we
started
the
feature
freeze
window
this
week.
The
current
plans
or
the
plans
as
if
as
they
have
always
been,
is
to
do
the
release
the
last
week
of
July
so
we're
targeting
around
the
25th
or
so
so.
A
Two
weeks
before
the
release
we
go
into
feature
freeze
and
then
one
week
before
the
release,
we
go
into
code
freeze,
so
we're
in
the
future.
Freeze.
Now
there
may
be
a
couple
things
that
are
still
in
Flight
that
we'll
definitely
want
to
talk
about,
but
we're
kind
of
starting
to
to
to
get
to
the
baking
time
and
we're
converging
on
the
final
release
Here.
A
So
let's
first
talk
real
quick
at
the
highest
level
about
the
things
that
are
part
of
the
1.13
roadmap
and
so
I
think
that
there's
a
couple
things
that
are
already
completed
here
and
then
there's
a
couple
things
that
I
would
love
to
get
the
latest
update
on
one
of
the
ones
that
is
top
of
mind
for
me
is
going
to
be
the
security
audit
stuff
and
then
also
the
ignore
changes
or
the
evolving.
The
management
policies
API
part
of
observe,
only
resources
to
enable
you
to
ignore
changes
as
well.
A
So,
let's
see
who
is
on
the
call
here
today?
Okay,
it's
both
Philippe
and
lovo-
are
so,
let's
just
start
top
to
bottom
here
Philippe.
Can
you
give
us
a
quick
update
on
where
we
are
with
all
the
findings
from
the
security
Audits
and
the
fixes
for
vulnerabilities
that
we
want
to
get
included
in
the
1.13
release.
B
A
So
awesome
Philippe
that
sounds
good
and
it
sounds
like
there's.
Maybe
two
major
Avenues
here
one
is
like
for
the
vulnerabilities.
You
know
making
sure
that
we
make
final
decisions
on
severity
or
if
we
want
to
do
a
CBE
and
all
that
sort
of
stuff
do
do
you
want
to
just
or
do
you
feel
like.
We
need
to
just
get
together
and
sync
and
make
final
decisions
on
those,
or
are
we
mostly
wrapped
up
on
that.
B
We
could
probably
schedule
a
meeting.
Maybe
it
will
be
better
to
have
a
sink,
a
synchronous
meeting
so
yeah.
If
we
manage
to
do
that
tomorrow,
maybe
because
I
know
Nick
is
going
to
not
to
be
here
next
week,
I
think.
Otherwise.
We
can
schedule
it
early
next
week
and
and
discuss
it
with
we'll
still
still
here.
A
And
so
I
think
that
kind
of
gets
to
the
second
part
of
deciding
the
what
the
technical
fixes
are,
and
so,
in
my
opinion
and
Nick
correct
me
if
I'm
wrong
but
I
feel,
like
you
know,
maybe
you
or
Hassan's
opinions
are
going
to
be
most
important
for
the
technical
decision
of
how
we
patch
some
of
these
things,
and
you
know
what
we
do
in
the
code
base.
We
probably
want
your
opinions
for
that,
but
in
terms
of
figuring
out
severity
and
cbes
and
stuff
like
that,
I.
B
A
Like
Philippe,
you
and
I
can
make
those
decisions
together
and
we
don't
that's
not
critical
for
Nick.
C
Make
sense
definitely
yes,
yeah
I,
don't
think
any
of
this
needs
to
from
what
I've
seen
play
on
so
far
I
haven't
recently,
but
I,
don't
think
any
of
it
needs
to
block
on
me.
I'll
try
and
help.
But
you
know
if
we.
A
That's
fine
and
then
you
and
Hassan
can
work
to
work
together
during
you
know:
EU
daytime
hours
to
get
the
patches
in
approved
and
the
technical
decisions
done.
B
A
All
right
sounds
good
man
sounds
good.
Thank
you
for
continuing
to
drive
this
and
then
just
to
confirm
as
well.
I
will
be
doing
it's
on
my
agenda
to
do
the
blog
post
for.
D
A
Care
of
that
man
all
right,
so
that's
big
stuff.
There,
security,
audit,
I
really
like
where
we're
going
with
this
and
the
you
know
the
continuing
to
progress,
our
security
posture
and
continuing
to
mature
the
the
project.
I
really
like,
what's
coming
out
of
this,
so
really
happy
to
have
that
in
1.13.
all
right
now,
let's
talk
about
the
granular
management
policies.
Lofro.
Can
you
give
us
an
update
on
what's
still
left
to
land
in
there
and
any
impact
that
has
on
1.13?
A
And
you
know
the
the
releases
and
stuff.
E
Yeah
yeah
sure,
so
the
ground
management
policy,
like
basic
function,
is
mostly
still
in
reviews.
E
The
good
thing
is
that
it's
connected
with
the
providers
not
with
crossbone
itself,
so
we
are
planning
to
release
this
with
the
providers
well
with
the
official
providers
anyway
by
the
end
of
July
as
well,
so
it
doesn't
directly
impact
cross
plane.
There
may
be
like
a
mismatch
in
what
cross-plane
which
which
crossban
runtime
crossband
is
using
and
which
Crossman
runtime
the
providers
will
be
using,
but
I
hope
that
won't
happen
and,
and
anyway,
it's
already
is
mismatch
they're,
not
using
the
same
version
but
yeah.
E
So
the
basic
basic
functionality
is
ready
just
sitting
in
reviews
we
are
hoping
we
can
get
approved
and
merged
soon,
and
init
provider
is
still
in
progress.
A
A
Cool
and
is
there
anybody?
Okay,
any
specific
reviewers
that
you're
waiting
on
to
make
progress
on
any
of
the
unmerged
stuff
in
runtime.
E
Well,
Hassan
is
back
from
vacation,
so
now
I
think
we'll
it'll
it'll
go
faster.
C
C
The
pr
right
now
and
Hassan
and
I
have
both
approved
it
so
I
think,
theoretically
we're
good
to
go.
Yeah.
E
Yeah,
that's
a
very
great
just
Hassan,
just
press
the
merge
button.
A
A
This
could
be
so
far
the
most
productive,
15
minutes
of
a
community
meeting
ever
then
great,
all
right,
cool
cool
all
right.
So
thanks
for
those
updates,
then
I
do
want
to
focus
mostly
on
1.13
today.
So
when
we
next
community
meeting
I
think
we,
if
everything
goes
according
to
schedule,
we
should
be
have
with
that
13
out
the
door,
and
then
we
can
start
doing
some
more
early.
You
know
roadmap,
1.14,
1.15
type
of
talking
again
I.
Think
the
big
Focus
today
is
is
converging
on
getting
1.13
outs.
A
Let
me
check
just
real
quick.
The
the
pro
the
1.13
scoped
project
board,
I
think
there
most
certainly
is
some
things
that
need
to
be
cleaned
up
from
here,
but
the
ask
that
I
would
have
for
folks.
Is
there
anything
on
this
board,
specifically
that
you
want
to
call
attention
to,
or
you
want
to
raise
your
hand
that
you
know
needs
some
help
in
order
to
kind
of
wrap
them
up
for
the
1.13
time
frame.
C
I
may
have
one
Jared
I
wrote
on
the
issue
yesterday.
Yes,
that
dry
run
apply
one
I,
unfortunately,
pretty
sure
it's
not
going
to
make
1.13.
C
my.
It
ended
up
being
quite
a
lot
to
refactor
that
I
have
somewhat
hesitant
to
land
at
the
last
minute
and
while
I
would
prefer
to
get
it
into
1.113
to
sort
of
unblock
people,
a
topic
that
I've
got
later
Rodney
is.
We
have
designer
that
makes
pretty
large
changes
to
functions
anyway.
So,
basically,
if,
if
that
desire
goes
as
planned,
functions,
everyone's
just
going
to
have
to
rewrite
their
functions
for
one
by
114,
because
they'll
work
differently.
D
So
so
I.
C
I
think
that,
basically,
that
would
be
diminishing
returns
to
making
the
way
that
functions
work
today,
work
better
in
1.13.
If
we're
just
going
to
ask
people
to
change
how
they
work
for
42
anyway,.
C
I
added
the
design
onto
the
interesting
PRS
towards
the
end,
just
as
a
heads
up
but
I
wanted
to
give
a
heads
up
that
I
I,
don't
think
I'll,
I
I
think
if
I
pulled
out
all
the
stops,
I
could
get
this
PR
done
in
time
for
1.13.
But
again
it
would
be
a
pretty
big
change
and
it
feels
a
little
risky
with
limited
benefit
to
sort
of
try
and
get
this
through
at
the
last
minute
to
me
at
the
moment,
but
unless
I
think
we'll
have
to
make
a
strong
case.
C
The
work
that
I
was
doing
fixes
is
that
when
we
do
what's
called
a
dry
run
apply,
which
does
two
things
it.
It's
a
it's
a
kind
of
a
weird
hacky
way
to
generate
a
name
automatically
for
your
composed
resources
during
composition,
and
it
also
does
some
validation
to
kind
of
make
sure
the
resources
are
valid,
and
a
couple
of
folks
pointed
out
correctly
that
we
should
have
done
that
after
the
Patch
and
transform
stuff
has
around
it
and
after
the
function
pipeline
has
run.
C
B
C
Do
functions,
the
symptom
is
that
your
functions
might
get
names
given
to
them
automatically
and
if
you
were
trying
to,
if
you
try
to
make
like
a
patch
and
transform
set
of
resources
that
are
like
half
valid
and
then
run
a
bunch
of
functions
that
makes
them
valid,
like
let's
say
the
let's
say
the
functions.
Add
a
field,
that's
required
that
won't
work
at
the
moment
because
they
have
to
be
valid
when
they're
dry
rub
runs.
C
So
so
it
is
a
real
problem
that
needs
fixing
I'm,
not
sure
how
impactful
it
is,
but
it
ended
up
being
a
lot
of
chopping
and
changing
to
to
actually
fix
it
more
than
I
expected
so
I
say
my
inclination
is
to
just
leave
that,
given
that
we're
going
to
have
to
do
that
shopping
and
changing
for
the
for
the
new
function,
implementation.
Presumably
we
proceed
with
that.
It
seems
likely.
A
Yeah
that
that
does
seem
reasonable,
nick
in
terms
of
the
call
you're
making
there
yeah
and
I,
see
now
that
we've
we've
got
more
stuff.
That
was
added
to.
A
From
the
since
last
time
we
we
talked,
we
looked
at
it
so
yeah,
let's
let's
kind
of
keep
moving
then
through
any
other
outstanding
1.13
stuff.
Thanks
for
raising
your
hand
on
that
one,
Nick
and
and
you're
that
that
does
make
sense
anything
else,
then,
for
1.13
before
we
keep
moving
through
the
agenda.
A
All
right,
okay,
so
on
provider
releases
and
such
I
did
not
see
like
we
had
a
couple
of
writer
releases
just
around
the
last
community
meeting,
but
I
didn't
see
any
new
ones.
There
so
folks
want
to
add
a
particular
provider,
releases
and
versions
and
stuff
that
have
happened
in
the
last
two
weeks.
Then
please
do
add
them
here
as
a
suggestion
and
we'll
merge
them
in
there.
But
I
didn't
remember
any
off
the
top
of
my
head
or
didn't
see
anything
in
the
announcements.
Channel.
A
Cool,
so
let's
keep
moving
to
the
topics
here,
a
few
interesting
resources
that
we
found
around
the
community
for
people
writing
and
blogging
and
making
videos
Etc
about
Crossway.
So
a
couple
things
to
check
out
there.
So
click
through
these
links,
if
you're
interested
in
those
and
definitely
you
know-
let
us
know,
if
there's
anything
else,
that
you
want
to
add
to
that
as
as
for
other
contents,
that
people
have
been
writing
and
Publishing
quick
announcement
for
folks
that
Philippe
is
now
the
newest
maintainer
on
cora
Cross
Plains.
A
So
congratulations
Philippe
and
thank
you
very
much
for
all
of
the
tireless
efforts
you've
been
putting
into
the
project
to
continue
moving
it
Forward
there
and
growing
with
your
influence
as
well.
Last
community
meeting,
we
announced
that
Bob
adelton
was
the
latest
the
latest
new
maintainer
on
Cross
plain
and
which
is
no
longer
true,
because
now
Philippe
is
the
newest
maintainer,
so
Bob's
still
has
influence
and
still
is
I
mean
Danner
just
no
longer
the
most
recent.
A
So
speaking
of
maintainers
was
kind
of
kicking
around
an
idea
with
a
few
folks
about
doing
some
like
Community
feedback
sessions
with
members
of
the
community
and
adopters
of
cross-plane
and
kind
of
meeting
with
some
maintainers
and
having
some
chats
and
getting
some
direct
feedback.
A
One-On-One
like
that,
I'm
super
interested
in
doing
this
doing
these
some
of
these
myself
of
you
know,
meeting
with
folks
and
listening,
and
you
know
just
kind
of
making
sure
we're
getting
a
good
pulse
of
what
people
are
experiencing
and
what
people
want
to
see
with
the
project.
So
I
wanted
to
kind
of
throw
this
out
to
the
group
here
today
that
you
know
we
want
to
do
some
of
these
feedback
sessions.
A
You
know
and
have
some
meetings
here.
So
if
anybody
is
interested
in
doing
that
feel
free
to
DM
me
or
you
know,
connect
with
us
some.
You
know.
However,
you
want
to
express
your
interest
in
it,
because
I
would
love
to
sit
down
with
you
all,
for
you
know
any
numbers
of
you
all
for
you
know
30
minutes
or
whatever
and
just
listen
and
share
some
ideas
together.
I
think
it
would
be
really
really
valuable.
So
please,
please
do
reach
out
to
me
if
you
have
any
interest
in
that
foreign.
A
Is
not
attending
the
meeting
today
looks
like
he's
got
some
bumpy
Wi-Fi
I
like
that
adjective,
but
we
did
want
to
call
out
that
Stefan
worked
on
a
new
section
in
the
contributing
guide
for
observability
this
week
and
it
was
generated
a
lot
of
discussion.
I
think
there
were
like
60
something
comments
on
it
in
the
first
like
Day.
A
So
you
know
I
think
that
this
will
be
a
bit
of
an
ongoing
thing
as
well
of
you
know.
Now,
we've
got
this
guidance,
we've
all
kind
of
aligned
upon
it.
So
we
you
know
for
for
the
code
that
we're
writing.
You
know
we
could
be
following
these
conventions
to
have
good
errors,
but
there
may
be
someone's
lingering
within
the
project
and
the
ecosystem
as
well
of
you
know,
providers
and
stuff
that
can
benefit
from
taking
a
pass
through
this
guidance
here
and
incorporating
it
into
the
code
base.
A
A
All
right,
Jean,
this
next
agenda
item
is
yours
and
I,
don't
think
you're
on
bumpy
Wi-Fi,
so
I'll,
let
you
take
it
I.
F
Think
so,
so
one
of
the
things
we're
currently
looking
at
is
just
the
the
overall
efficiency
characteristics
of
different
railroad
scenarios,
as
people
try
and
scale
up,
you
know
to
hundreds
and
thousands
of
amrs
with
with
the
official
providers.
F
You
know
we
have
a
few
scenarios
that
we
are
evaluating
and
and
going
deep
to
understand.
You
know
the
different
kind
of
like
metrics
involved
from
a
performance
and
a
utilization
point
of
view,
and
this
is
more
a
call
out
to
anybody
if
you
have
any
kind
of
like
good
compositions
out
there,
that
have
has
a
couple
of
apis
in
them
already,
and
you
know
something
that
you've
been
maybe
trying
to
see
how
far
you
can
scale
it.
You
know
if
you're
willing
to
share
it
with
us.
F
We
really
appreciate
it
as
it
gives
us
some
more
different
kind
of
like
combinations
to
have
a
look
at
and
help
us
understand.
You
know
where
we
can
make
some
further
improvements,
and
you
know
just
I
mentioned
this
a
few
months
ago,
but
we're
still
fully
focused
on
a
you
know:
improving
the
kind
of
like
efficiency
of
the
providers
to
help
you
know
reach
a
higher
level
of
scale
going
forward.
A
And
John
is
there?
Is
there
a
good
means
to
which
to
provide
that
feedback?
Is
there
a
specific
like
slack
Channel
or
something
that
you
want.
A
F
Just
realized
I
didn't
add
that,
but
I
will
add
it
to
the
agenda
now
afterwards,
as
well
and
I
will
add
it
to
the
announcement
channel
in
slack
as
well
perfect.
A
All
right
cool,
so
then
it
looks
like
we
are
at
the
the
agenda
item
here
where
we
want
Andre
to
go
ahead
and
show
off
some
of
the
interesting
work
that
he's
announced
in
the
community.
Just
I
think
it
was
maybe
last
week
with
the
Como
play
in
these
buildings,
so
I'll
stop
sharing
my
screen
and
Andre.
You
can
go
ahead
and
introduce
the
project
and
walk
us
through
a
little
bit.
A
There
I
think
we
probably
probably
have
at
least
15
minutes
to
do
that
Andre,
so
you
don't
have
to
be
too
rushed
to
get
through
it.
G
Still
I
will
respect
your
time
and
will
not
make
it
too
long.
Let
me
share
my
screen
first
and
make
sure
that
you
are
able
to
see
that
are.
G
Yeah,
you
can
see
the
the
GitHub
repo
yep
amazing,
so
I
work
for
a
company
called
Commodore
and
my
role
is
to
be
open
source
everything
open
source
related
guy
and
in
my
past
I
we
already
did
a
nice
tool
for
developers
called
Helm
dashboard,
which
was
visualizing
the
helm.
So
this
is
my
usual
thing
and
then
I
came
across
with
cross
plane
and
I,
really
like
the
concept
because
I'm
thinking
about
where
do
you
do?
G
We
all
go
with
these
Cloud
Technologies
and
Cloud
providers
I
to
be
fair,
I,
never
liked
the
cloud
providers
in
because
it's
a
bit
too
much
of
things
to
manage,
and
it
doesn't
look
like
developer
experience
to
me
and
now,
when
I
see
cross-plane
as
a
concept
of
utilizing
kubernetes
concepts
for
managing
those
big
and
hairy
objects
in
the
cloud
I
really
like
it.
But
when
I
started
to
play
with
cross
plane,
I
I
was
really.
G
It
was
not
so
easy
to
start
because
it's
pretty
complex
and
it
is
hard
to
navigate
through
all
of
the
objects
and
understand
their
relations.
So
I
understood
that
it's
actually
a
really
good
thing
to
feel
really
good
Gap
to
feel
by
creating
something
that
will
be
visualizing
for
the
the
guys,
like
me,
visualizing
what
cross-plane
consists
of-
and
this
is
how
I
came
up
with
this
common
plane
project,
which
is
basically
visualization
of
cross
plane,
resources
to
to
speed
up
troubleshooting,
to
understand
the
status
quicker
and
sorry
for
that.
G
G
And
I
build
the
tool
and
now
I'm
looking
to
share
it
with
the
community
to
hear
the
feedback
and
understand
if
we
should
go
forward
with
this
concept,
does
it
solve
the
problem?
It's
called
comma
plane,
I'll
walk
through
the
beginning
of
using
it,
so
it's
possible
to
install
it
as
a
Helm
chart
into
your
cluster,
or
you
can
try
it
without
installing
by
downloading
the
binary
release,
which
I
will
do
we
I
can
go
to
releases.
Yesterday,
I
made
a
fresh
release.
G
It
starts
the
web
server
which
I
can
now
open
in
my
browser-
and
this
is
the
cross
plane
now,
the
common
plane
cross
plane
gets
visualized
I
have
some
areas
with
all
the
main
objects
of
cross
plane.
Let's
start
with
claims,
I
have
some
test
bed
in
my
computer,
I
prefer
isolated
environments,
so
I'm
experimenting
basically
with
Helm
as
main
provider,
so
I
have
created
a
claim
which
I
can
now
look.
It's
unhealthy,
there's
something
wrong
going
going
on
with
that
claim,
let's
dive
deeper.
So
this
is
the
presentation
of
claim.
G
I
can
see
that
there's.
No
recent
events
in
the
claim
itself
and
the
biggest
point
of
value
is
the
ability
to
navigate
to
the
root
cause
of
the
problem
and
the
cross
plane.
I
can
see
that
my
claim
is
not
ready.
It
was
reconciled
with
success,
but
it's
not
ready
and
I
can
see
that
it's
actually
because
of
the
composite
resource
being
not
ready,
and
that
in
turn
is
because
of
the
managed
resource
is
not
synchronized.
I
can
navigate
to
most
of
these
objects.
G
For
example,
if
I
go
to
composite
resource,
I
would
see
that
my
composite
resource-
yes,
it's
not
healthy,
and
we
see
that
it
happens
because
of
these
managed
resource.
I
can
see
my
victim
who
is
suffering
from
me
being
unhealthy,
and
this
is
my
claim
is
suffering
being
unhealthy
and
I
can
see
also
some
attributes
over
the
object
like
the
status
of
it.
The
events
that
were
happening
all
good
I
can
review
the
yaml
of
my
composite
resource.
Then
I
can
go
to
the
managed
resource.
Let's
go
first
to
the
healthy
one.
G
I
can
see
that
it
depends
on
some
provider.
Config
and
I
can
see
who
suffers
if
there's
problems
with
these
specific
managed
resource,
the
composite
resource,
my
managed
resource
is
fine.
The
composite
resource
is
unhealthy.
I
can
navigate
back
to
it
and
go
and
look
at
the
problematic
one,
and
you
can
see
this
is
intentionally
broken
situation.
I
can
see
that
my
provider,
config,
is
not
found.
It's
unhealthy.
I
can
see
the
events.
G
The
error
message
is
perfectly
explanatory.
It
says
that
there's
not
the
provider
cannot
work
with
this
provider.
Config
I
can
review
that
in
my
provider
config.
Indeed,
the
reference
is
bad
and
some
events
status
all
the
options.
G
Basically,
the
idea
was
to
minimize
the
time
I'm
spending
by
navigating
through
K9s
or
cube
CDL,
to
get
this
information
get
to
the
root
cause,
there's
no
intent
to
replace
completely
Coop
CTL,
because
you
would
be
fixing
the
problem
with
your
Cube
CDL
or
whatever
process
detox
process
that
you
are
utilizing
but
to
actually
get
to
the
root
cause.
You
would
go
through
the
visual
process
of
figuring
it
out,
and
here
you
go,
you
can
navigate
through
various
lists.
Like
you
can
go
to
the
composite
resources.
You
can
see
that
there
is
a
composite
resource.
G
That
is
fine.
This
one
is
directly
created
through
the
yaml
and
it's
it
looks
alright,
I,
don't
know
how
is
this
possible,
but
it
looks
all
right,
but
it
points
to
the
managed
resource
that
is
not
since,
although
it's
ready
so
it's
kind
of
okay
I'm,
not
an
expert
in
Frost,
plane,
I'm
learning
it
as
I
go
so
I'm
I'm.
Seeing
these
situations
make
me
curious,
I'm,
starting
to
learn
other
aspects
of
what
is
possible
in
Cross
plane.
G
We
can
see
all
of
the
managed
resources,
for
example,
to
understand
what
do
we
consume
from
the
providers?
We
can
see
the
providers
themselves
I
I
have
couple.
Helm
providers
is
in
perfect
shape.
Kubernetes
provider
doesn't
say
that
it
has
any
troubles
either.
G
My
compositions
I
can
review
what
I
have
declared
as
compositions
and
composite
resource
definitions.
So
to
me,
as
a
newbie,
it's
really
a
tool
to
learn,
learn.
G
I
I
can
assume
that
there
is
certain
depth
that
I'm
missing
the
third
dimension
of
cross
plane
that
I'm
still
missing,
like
I
heard
of
composition,
revisions
as
important
aspect-
maybe
some
other
things
in
Crossman
that
I
could
expose
here,
but
at
this
stage
I'm
trying
to
be
agile
and
I'm
trying
to
see
if
the
community
would
tell
me
that
this
is
the
right
thing
to
do,
or
this
is
the
wrong
thing
to
do,
and
maybe
Point
me
where
what
is
more
important
to
dive
deeper
and
what
is
less
interesting.
G
So,
let's
keep
it
simplistic
in
these
cross-plane
project.
If
you
are
interested
check
it
out
I'm
at
this
stage,
mostly
looking
for
a
feedback,
as
I
said,
you
can
find
me
in
Cross
plain
slag
just
tag
me
directly,
but
please,
let's
keep
these
discussions
in
somewhere
open.
Please
not
one-to-one
messages,
but
in
the
wider
form.
So
people
can
actually
see
that
the
discussion
is
happening
and
put
their
opinions.
B
G
A
I
can
answer
because
this
is
sweet
Andre
thanks
for
taking
the
time
to
well
to
show
it
today,
but
I
guess
also
to
write
it
before
that's,
maybe
even
more
important
than
showing
it
today.
So
this
is
super
cool
man.
What
one
quick
question
I
had
was
like
I
love,
the
you
know,
visualizing
the
relationships
in
you
know
in
the
references
between
the
resources
that
really
helps
people
kind
of
see.
What's
going
on
under
the
covers.
A
What
are
the
like?
The
example.
You
showed
that
I
think
it
was
the
at
the
helm
resource
that
it
was
like
they
had
a
not
found
provider
config.
How
did
you
know?
How
did
you,
how
was
this
tool
able
to
determine
that?
It's
not
found.
Is
that,
like
a
specific
condition
on
this,
like
a
status,
condition
that
it
looks
at
or
how
did
it
know
that.
G
The
most
straightforward
way,
I'm
getting
the
object,
then
I'm,
seeing
the
references,
the
important
reference
that
it
points
to,
for
example,
provided
provider.
Config
is
one
of
the
most
important
references
from
the
objects
and
then
I'm
going
to
kubernetes
and
I'm
checking
if
the
resource
exists
or
not,
and
if
it
not
exists,
then
I'm
bringing
that
up
as
the
problem,
because
in
my
experiments,
I
figured
that
in
many
cases,
I'm
screwing
up
with
my
names
here
and
there.
G
If
my
structure
of
resources
gets
complex,
I'm
half
of
my
time,
I
was
suffering
just
because
the
name
I
forgot
the
name
or
did
a
misprint.
And
then
my
question
is
why
my
claim
feeling
bad,
although
there's
that
whole
chain
of
a
problem
down
to
the
managed
resource
suffering
from
missing
provider
Conte,
so
I'm
implemented
some
I
I've
implemented
something
that
was
surfacing.
Those
problems.
G
Can
kind
of
do
validation,
yes
and
sometimes
I
have
to
the
Cross
Lane
is
so
Universal
that
it
in
its
code
base
it
doesn't
force
dependencies
and
structures
in
many
places
it
allows
for
free
form
structures,
so
in
some
places
I
have
to
rely
on
de
facto
standards.
Just
every
provider
has
provider
configs
or
yes,
provider,
configs
to
it
so
I'm,
relying
on
that
as
a
de
facto
standard
and
not
something
that
is
forced
by
cross-plane
core.
G
That's
the
life
of
open
source
project
around
cross
plane.
A
Cool
any
other
questions
from
folks
about
the
about
this
demo
here
and
the
tool.
A
All
right,
well,
yeah!
A
So
that's
you
know,
there's
a
link
to
the
repo
here
in
the
agenda
doc,
so
folks
can
go
ahead
and
check
it
out
there,
and
then
you
know,
as
Andre
is
mentioning
one
of
the
things
he's
most
interested
in
right
now
is
getting
feedback
from
folks,
and
you
know
kind
of
getting
some
experience
and
kind
of
continuing
to
shape
it,
so
that
can
that
can
definitely
go
on
with
you
know,
issues
in
the
in
the
repo
here
and
thanks
again
Andre
for
for
for
showing
this
to
us
today.
A
A
B
Yes,
yeah
I
just
wanted
to
point
out
that
we
merged
and
that
in
113
we
will
get
a
change.
A
minor
breaking
change
to
the
alpha
environment,
conflicts
Behavior
regarding
label
selection,
so
long
story
short
before
this
using
label
selection
to
to
pick
an
environment
config
resulted
in
in
case
of
multiple
matches,
resulted
in
a
random
choice.
Now
we
are
with
we
discussed
it
in
in
a
few
of
the
last
six
environment
meetings
and
with
a
few
folks
interested
in
the
topic,
and
we
agreed
it
in
the
default.
B
Behavior
should
have
been
erroring
out
in
case
multiple
matches
were
found,
but
we
introduced
the
two
modes
single
and
multiple,
so
in
single
mode,
which
is
the
default,
we
have
an
error
in
case
multiple
matches
are
found
because
you
are
expecting
a
single
environment
config
to
match
the
labels,
while
if
you
specify
a
multiple
mode
with
Max
matches,
so
our
maximum
number
of
matches
to
be
picked,
you
can
get
back
the
old
Behavior,
but
it's
not
going
to
be
randomically,
choosing
the
environment
conflict
to
to
select
but
and
it's
going
to
sort
them
either
by
name
or
by
a
specified
field.
B
A
Possibly
thanks
for
making
that
well
known
and
then
yeah
like
definitely
anything.
We
could
do
to
kind
of
broadcast
that
and
make
that
well-known,
like
yeah
in
the
release,
notes
or
if
it
needs
something
needs
to
be
added
to
the
docs
about
the
behavior.
Then
that's
that's
reasonable,
as
well.
A
All
right,
cool
and
glad
to
see
that
get
merged
in
also
to
kind
of
continue
advancing
the
functionality
there
in
1.13
also
all
right.
So
let's
go
ahead
and
take
a
look
at
a
couple
of
PRS
that
folks
have
been
calling
out.
So
let's
click
on
this
first
one
here
and
see
it's
Christopher
Harve.
Is
this
one
that
you
brought
up
or
are
you
on
the
meeting?
A
Let's
see
okay
so
cross
Council,
Association
and
cross-account
testing
with
a
test
real
world
example,
Central
DNS,
resolver,
Network
accounts
and
all
the
Route
53
zones
and
other
accounts
and
vpcs.
So
it
looks
like
this
has
been
merged.
So
it's
available
at
least
the
recent
merge.
A
And
it's
possible
that
this
is
this
from.
Maybe
maybe
this
is
a
stale
agenda
item
from
oh
yeah.
It
is
that's
my
fault
I!
Take
your
accountability!
For
that
sorry,
folks
I
was
wondering
how
Christopher
had
added
something
here
to
the
intention
and
he's
not
here.
That's
my
bad
all
right
and
then
Nick.
Let's
go
ahead
to
yours,
then,
like
I
think
we
already
talked
about
just
a
little
bit
of
this,
but
this
is
a
pretty
important
topic,
I
think
so
I'll.
C
A
Bring
up
the
like
the
the
design
dock
as
well.
It's.
C
Not
sure
yeah,
I,
I,
maybe
or
I,
don't
think
it
really
bad
is
we
could
just
you
know,
just
talk
about
it,
real,
quick,
hopefully,
everyone's
aware
of
composition
functions,
it's
something.
We've
been
working
on
for
a
long
time.
C
The
quick
version
of
this
is:
we
have
a
design
open
that
is
approved
as
of
today
to
change
somewhat
significantly
how
functions
work
in
cross-play
before
we
make
the
beta
layer
Alpha
at
the
moment,
they're
off
by
default
as
a
reminder
for
Alpha
features
and
cross-plane
there's
effectively
no
contract,
we
we
reserve
the
right
to
break
them
or
change
how
they
work
at
any
time,
and
that
allows
us
to
basically
get
feedback
on
these
features
and
make
them
better,
which
is
I,
think
what
we're
doing
in
this
case,
so
targeting
cross-playing
1.14
targeting
not
guaranteed,
but
targeting
crossbow
1.14
in
October
we're
hoping
to
get
composition
functions
data.
C
The
big
difference
is
that,
while
we
still
feel
that
the
developer
experience
will
be
the
same
or
actually
better
because
we're
investing
a
lot
more
in
developer
experience
in
this
iteration,
we
still
feel
like
people
are
going
to
be
academically.
They're
going
to
be
writing
a
function,
you
will
feel
like
you're
writing
a
function
to
build
one
of
these
we're
thinking
we're
going
to
deploy
them
as
long
run.
C
Processes,
rather
than
oci
images,
that
sort
of
start
stop
do
so
start.
Do
something
then
stop?
C
C
If
you
are
interested
in
this
and
I
would
encourage
you
if
you're
using
functions
or
if
you
feel
passionate
about
functions,
to
go,
read
this
document
and
be
aware
if
you
have
any
dire
concerns,
you
should
probably
let
me
know
today
or
tomorrow,
because
we're
likely
to
to
merge
this
so
that
folks
can
start
working
on
it.
C
The
other
thing
that
is
somewhat
related
is
a
a
shorter,
smaller
design
document.
One
pager
that
I
currently
call
it
package
one
time
config.
This
one
has
not
had
much
review
yet
I
only
opened
it
late
last
night.
The
general
idea
is
this:
replace
control
or
config
I
know
that
everyone
uses
controller
config
I,
know
that
us
sort
of
deprecating
it
without
having
a
obvious
replacement
for
it
concerns
of
people.
C
So
now
we
have
an
obvious
replacement
for
it.
Well
proposed
one
at
least
it's
pretty
similar
to
controller
config.
It
really.
The
the
reasons
we
got
rid
of
control
are
config
were
two-fold
one.
There
was
a
a
long
running
proposal
from
Dan
Mangum
that
we
basically
make
how
cross-plate
runs
provide
is
pluggable
I.E.
Instead
of
going
and
deploying
a
deployment
in
your
kubernetes
cluster,
maybe
they
I
don't
know
if
we
had
any
super
concrete
ideas.
I'll
say
something
wacky
like
deployed
as
a
Lambda
function,
or
something
like
that
right.
C
So
we
were
like
control.
The
config
is
kind
of
turn
into
a
template
for
kubernetes
deployment,
but
maybe
these
won't
always
be
kubernetes
deployments.
So
we
don't
know
if
we
like
that,
what
I
propose
in
this
design
is
is
pretty
quick
to
capture
I
propose
we
had
a
flag
to
cross-blade
that
lets.
You
turn
off
the
default
package
manager,
behavior
of
making
a
deployment
to
when
you
install
the
provider.
C
C
As
far
as
I
know,
only
a
bound
has
this
need
so
I
think
it's
kind
of
reasonable,
given
that
it's
a
very,
very
edge
case
thing
to
instead
of
adding
a
lot
of
complexity
and
abstractions
across
planes,
so
the
cross
play
goes
and
could
deploy
providers
in
10
different
ways.
We
should
just
keep
what
progress
light
does
today,
but
let
you
opt
out
of
that
and
write
your
own
code
if
you
want
to
and
so
they're
that
simplifies
what
cross-plane
understands
to
be
like:
okay,
I'm
always
going
to.
C
Basically,
if
you,
if
you've
ever
looked
to
control
a
config
and
thought
oh
I
wish
this
had
volume
supporter,
which
has
had
label
selector,
support
or
I
wish.
C
That
that
should
all
just
be
there
by
default
onto
this
design,
that's
it
yeah.
Please
feel
free
to
reach
out
to
me
I'm
going
on
vacation
on
Tuesday.
So
if
anyone
has
any
thoughts
about
this,
I
would
encourage
you
to.
Let
me
know
correctly
soon.
A
Awesome
Nick
yeah,
thanks
for
taking
the
time
to
walk
us
through
that
and
kind
of
understand
the
objectives
for
your
proposals
and
the
impact
of
them
as
well.
That's
that's
really
really
helpful
and.
B
A
Know
a
lot
of
folks
do
use
controller
config
right
now,
and
so
it
would
be.
It
would
be
helpful
for
folks
that
are
using
it
to
make
sure
that
this
kind
of
you
know
addresses
the
the
needs
that
they
have
so
feedback
would
be
appreciated.
A
All
right
and
then
the
last
thing
we've
got
on
the
agenda
here-
is
Roberto
for
migrating
large
infrastructure
from
terraform
and
then
AWS
rate
limiting
I
guess
that
comes
along
with
that.
Perhaps
indeed.
H
Yeah
we're
we're
starting
to
discuss
internally
in
the
company
that
I
work
on
it's
Wildlife
Studios
we're
trying
to
we've
been
using
Crosslink
for
a
while
for
the
for
the
internal
apis
that
we're
doing,
and
we
still
have
a
bunch
of
infrastructure
in
terraform.
But
we
were
starting
to
think
like
oh,
is.
Is
it
okay
to
actually
migrate
that
infrastructure
as
well
into
Crosslink
resources,
and
one
thing
that
we've
noticed
while
trying
to
do
some
of
that
stuff?
H
Is
that
AWS
has
a
pretty
aggressive
range
limiting
approach,
especially
for
like
Route,
53
and
stuff,
so
having
a
constant
reconciliation
Loop
trying
to
apply
those
changes
is
not
really
the
best
for
for
the
cloud
provider
itself.
Right
I
would
like
to
know
if,
like
if
you
guys,
seeing
in
any
other
companies,
doing
things
that,
at
a
bigger
like
at
a
larger
scale,
to
have
some
issues
or
something
like
that
or
something
that
we
should
be
aware
of.
A
H
Yeah,
we
we
are
able
to
decide
it
to
like
only
reconcile
which
resource
every
like
cow
hour
or
so
so
that
that
would
reduce
the
amount
of
calls
significantly.
But
the
idea
behind
having
the
the
constant
reconciliation
Loop
is
basically
whenever
something
changes
you
can
have
a
faster
like.
If
someone
changes
something
manually
on
the
cloud
you
can
have
it
be
reconciled
back
to
the
to
the
original
state
as
fast
as
possible.
So
I
don't
know
if
that's
a
good
way
to
solve
it.
I'm
not
sure
I
would
like
to
discuss
that.
A
Yeah
and
I
think
there's,
because
someone
could
keep
me
honest
here,
but
I
think
you
know
there's
a
couple
different
parameters
that
you
can
specify.
A
You
know
one
is
like
the
the
sync
rate
or
I
can't
remember
the
names,
but
you
know
it
kind
of
influences
like
the
periodic
rate
of
time
that,
like
a
resource,
will
be
checked
again,
for
you
know
a
Delta
between
the
actual
State
and
the
desired
State
and
there's
also
kind
of
like
more
like
a
a
global
rate
limiter,
which
kind
of
you
know
for
all
the
controllers
limits
the
number
of
reconciliations
or,
and
you
know
that
they
could
be
doing
in
parallel
or
or
you
know,
like
the
the
number
like
the
frequency
at
which
they
could
be
trying
to
execute
within
their
two
separate
parameters.
A
So
I
don't
and
maybe
you've
already
looked
at
both
and
seen
that
that
doesn't
resolve
the
situation,
but
I
know
there's
more
than
one
parameter
that
affects
the
behavior
of
syncing.
Here
that
could
be
at
play.
That
could
be
interesting,
yeah.
H
I
think
I,
mostly
played
around
with
the
max
reconcile
rates.
Yeah
I
can
I'll
take
a
look
at
this.
This
other
parameter
for
the
global
rate.
Limiting
there.
A
Yeah
did
somebody
know
it
off
the
top
of
their
head,
because
it's
just
kind
of
a
little
hazy
from
recollection
here,
but
you
know
like
the
of
the
or
do
we
have
documentation.
That's
easy
to
point
at
for
the
different.
You
know
couple
different
ways
there
is
to
influence
the
the
reconciliation.
You
know
throughput.
D
A
C
I
I
believe
the
key
one
is
just
max
reconcile
rate,
and
that
does
in
and
of
itself
like
chew,
and
a
couple
of
other
things
like
if
you
give
a
bigger
Max
reconcile
rate,
will
allow
multiple
client,
if
you're
going
to
be
able
to
server
and
a
couple
of
other
things
that
we
think
are
necessary
to
achieve
the
max
Arkansas
rate
off
the
top
of
my
head.
I'm,
not
sure
if
or
where
there
is
documentation
of
that.
There
should
be.
D
I
was
gonna,
say
one
thing:
I,
don't
know
if
it
would
kind
of
be
outside
a
cross
plane,
but
if
you
could
trigger
something
through
cloudtrail,
whenever,
like
a
non-service
account
edits
something
causing
a
manual
reconciliation
of
the
cross-plane
resource.
That
way,
you
can
still
have
a
high
reconciliation
or
you
can.
You
know,
make
sure
your
reconciliation
is
like
an
hour
but
have
changes
that
are
done
manually,
be
done
through
cross
plane
at
the
time
that
they
happen
through
cloudtrail,
or
something
like
that.
Maybe
something
of
interest
to
look
into.
H
H
To
the
Adam's
saving
guide.
A
Chat,
climate,
yeah,
yeah,
cool
yeah,
of
course,
and
Blake
thanks
for
sharing
that
idea
as
well
about
cloudtrail.
That's
that's,
definitely
interesting
and
like
a
a
nice
creative
way
to
think
about
it
too,
sweets,
yeah,
so
Roberto.
Let
us
let
us
know
if,
like
for
the
documentation,
I,
would
take
a
quick
look
after
this
as
well
to
see
if
there's
further
documentation
I
was
thinking
of
and
if
there's
not.
A
This
very
much
could
be
a
nice
candidate
for
another
like
upcoming,
like
blog
post
or
something
to
you,
know
kind
of
share
this
this
topic,
but
then
also
make
sure
that
that
gets
into
the
documentation.
If
it's
not
there
too,
so
we'll,
we.
H
H
But
you
haven't
seen
any
any
other
companies
doing
this
and
having
issues
or
something
related
right.
A
Yeah
I
mean
like
the
the
migration
stuff
or
the
importing
stuff
that
I've
seen
tends
to
have
I,
haven't
seen
like
a
big
scale.
Throughput
of
that
I've
seen,
you
know
folks
doing
migrations,
but
like
kind
of
more
like
a
project
by
project
basis
and
kind
of
going
a
little
bit
more
slowly
with
it.
So
I
don't
think
that
this
exact
scenario-
I,
don't
know
I
I
can't
remember
having
myself
talk
to
somebody
about
it.
A
Yeah
thanks
a
lot
for
that.
Roberts
I
definitely
appreciate
it
cool
all
right,
so
that
was
the
last
of
the
agenda
items
here.
So,
if
folks
have
more
things
they
want
to
bring
up
the
floor
is
open
for
that,
and
while
you
were
thinking
about
that,
you
know
the
keep
in
mind
here
that
the
major
Focus
for
the
next
two
weeks
or
so
is
going
to
be
getting
on
1.13
and
getting
that
out
the
door.
A
We
would
expect
around
July
25th
if
anybody's
blocked
on
anything
while
we're
in
this
critical
phase
for
for
converging
on
the
release
and
feature
freeze
code.
Freeze
do
let
us
know
so
we
can
make
sure
we're
getting
attention
on
things
so
that
everything
can
get
out
the
door
and
we
can
have
a
successful
quality
release
again.
A
All
right!
Well,
then,
if
that's
everything
we'll
keep
working
on
1.13
and
hopefully
by
the
time
we
meet
next
time,
we
will
have
that
release
out,
we'll
be
able
to
celebrate
a
little
bit
all
right
good
to
see
everybody
thanks
for
stopping
by
today
and
thanks
again
Andre
for
the
Demo
Man.