►
From YouTube: 2023-06-29 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
We
have
a
bit
of
a
smaller
group
of
folks
today,
while
a
lot
of
people
are
on
vacation
and
I
have
some
conflicts
today,
but
we'll
get
everything
done
here
that
we
can
and
while
we
can
and
folks
can
catch
up
on
the
recording
later
on
as
well
so
I
will
drop
into
the
zoom
chat
right
now,
a
direct
link
to
the
agenda
doc,
so
folks
can
jump
in
there
and
they
can
get
into
the
dock
and
add
any
suggestions
that
they
may
want
for
topics
they
wanted
to
wanted
to
discuss.
A
We
don't
have
any
huge
topics
today,
so
I
think
that
there
will
be
a
time
if
folks
wanted
to
add
extra
things
so
feel
free
to
add
things
into
the
agenda
all
right,
so
we
don't
have
any
recent
Upstream
crosswind
releases
since
the
last
community
meeting
I
think
the
last
patch
result
patch
releases.
We
did
were
right
before
the
last
community
meeting,
so
nothing
to
mention
there,
but
we
are
getting
quite
close
now
to
the
next
release
of
of
Cross
Plains.
A
So
the
1.13
release,
so
we
have
I
think
it's
on
like
Late
July,
we
were
targeting
around
the
25th
or
so
so.
We've
got
about
four
weeks
left
and
that
means
about
two
weeks
are
left
until
we
get
into
our
feature
freeze
and
then
our
code
freeze.
So
let's
just
look
at
the
calendar,
real,
quick
together
to
make
sure
that
we've
got
all
that
there
right.
A
So
we
are
here
today
so
yeah,
so
we've
got
just
about
just
under
two
weeks
until
we
get
to
feature
freeze
and
then,
which
is
two
weeks
before
the
approximate
release
date,
and
then
we've
got
code
freeze
one
week
after
that,
where
we
would,
you
know,
stop
taking
bug
fixes
we
really
want
to
stabilize
and
then
the
release
is
the
last
week
of
July.
So
it's
yeah
we're
definitely
cruising
in
on
getting
near
there.
So
we
want
to
unblock
anybody
who
feels
blocked
on
things.
A
Maybe
we
could
take
care
of
that
some
of
that
in
this
meeting
here
today.
So
let's
take
a
look,
then
at
the
release
board
and
see
if
there's
anything
that
we
can
help
out
with
that.
I
took
a
little
bit
of
a
pass
through
some
things
that
you
know
were
not
did
not
have
traction
or
we're
not
going
to
be,
including
the
release
and
cleaned
it
up.
So
we've
mostly
gotta
clean
enough
release
board
here.
A
A
Philippe,
though,
there's
a
couple
important
things
that
you're
driving
here
in
1.13,
so
both
the
composition,
validation,
further
work.
Can
you
give
us
a
quick
update
on
what
would
be
included
in
1.13
and
then
we'll
talk
about
the
security
audit
as
well?
Yeah.
B
We
we
kind
of
agreed
not
to
promote
to
Beta,
because
it's
actually,
we
continued
evolving.
The
schema
validation
in
in
this.
In
the
meantime,
after
the
release
of
112-
and
there
is
still
stuff
features
that
were
not
back
parted
to
because
their
features
and
not
fixes
so
they
they
are
not
in
any
user
available
release.
So
we
decided
to
postpone
promoting
to
a
later
stages
so
that
we
can
have
at
least
in
113
all
the
features
widely
available.
B
Have
people
tested
find
bugs,
and
then
we
can
proceed
with
with
the
next
phase.
But.
A
So
is
there
any
outstanding
like
code
work,
then
that
would
be
left
for
1.13
or
we
could.
You
know,
move
this
along
to
it's.
C
B
Is
still
work
to
be
done,
but
it's
going
to
be
for
114
or
or
later
so,
nothing
at
the
moment,
so
it's
actually
kind
of
in
progress,
but
because
it's
a
wider
scope,
it's
not
specifically
for
114.
A
Right:
okay,
great
so
yeah,
let's,
let's
get
the
board
cleaned
up
on
that
then
after
the
after
the
this
meeting
here
and
then
let's
talk
about
the
security
audit
as
well,
because
that
is
winding
down
and
we're
working
on
a
number
of
fixes
for
issues
found
and
we're.
You
know
working
towards
getting
the
the
reports
Alice
and
stuff
like
that.
So
give
us
a
quick
update
on
where
you
are
with
that
and
what's
left
for
1.13
yeah.
B
So
other
logic
of
the
company
who
was
was
in
charge
of
his
security
audit
closed
the
audit
part,
so
they
they
shared
all
all
findings
which
were
nothing
to
worry.
To
worry
some.
Let's
say
we
are
still
trying
to
triage
a
few
issues
and
we
we
are
targeting
the
release
of
113,
to
publish
the
report
and,
if
any,
any
CDE
or
any
fix
for
forbacious
bound.
A
Perfect-
and
is
there
anything
else
that
you
need
right
now
to
like
get
yourself
unblocked
on
any
of
that,
or
are
you
largely
you
know
able
to
continue
executing.
B
Mainly
feedbacks
from
from
maintainers
on
a
few
a
few
issues
founded
to
have
a
feedback
with
a
little
bit
more
context
than
the
one
I
have
on
a
few
parts
of
the
code
base,
but
other
than
that
we
are
good
to
go
and
then
the
blog
post,
which
you
you
are
going
to
write.
Probably.
A
Yep
no
problem
with
that
at
all.
Okay,
that
is
good.
Then
that
sounds
good
to
me.
I
was
definitely
curious
about.
If
there
had
been
progress
on.
You
know
the
work
that
I
think
that
Hassan
had
had
an
outstanding
PR
on.
A
You
know
kind
of
a
step
towards
me
to
for
making
upgrade
process
for
packages
providers
configurations
whatever
across
different
versions,
to
be
a
little
bit
more
reliable
and
taking
the
resources
from
the
previous
version,
and
you
know,
transitioning
their
ownership
to
the
new
version,
making
that
more
smooth
but
I,
don't
know
I,
know
Hassan's
not
here
today,
but
I,
don't
know
if
anyone
has
a
latest
update
on
that.
That
I
might
not
have
already
heard
of.
A
Cool,
that's
fascinating
nice
good
to
see
that
so
I'll
follow
up
with
Hassan,
then
and
see
if,
if,
if
that
is
still
something
that's
in
scope
of
1.13,
because
then
no
progress
on
that
would
certainly
be
helpful.
A
Okay,
any
is
there
anything
that's
on
that's
not
on
the
board
here.
That
folks
wanted
to
make
sure
it
gets
tracked
or
gets
added
to
1.13
as
we're
winding
down.
B
A
So,
basically,
there's
still
kind
of
an
outstanding
decision
that
has
not
been
made
on
the
final
API
for
it
yeah
cool.
Do
you
who's
been
participating
in
that
that
you
that
you
need
a
okay.
B
I
think
Nick
gave
his
feedback
and
also
Azan
gave
his
feedback
about.
There
is
also
a
member
of
the
community
who
is
willing
to
to
work
on
that.
So
it's
I
was
helping
out
trying
to
steer
a
little
bit
the
conversation
on
the
design
and
but
yeah
a
member
of
the
community
will
be
willing
to
do
that.
A
Was
the
feedback
for
the
design
aligned
or
was
there
still
some
any
conflicts
to
resolve
to
resolve
in
that.
B
It
was
kind
of
yes
about
no,
so
yes,
but
we
should
find
a
broader
solution
to
the
whole
class
of
problems.
So.
A
B
Might
be,
but
I
would
lean
toward
the
saying
we
could
Implement
that
and
think
about
a
wider
solution
in
in
the
meantime.
But
it's
yeah
I
agree,
it's.
It
could
be
solved,
but
it's
actually
a
problem.
Many
operators
have
and
it's
it's
not
easy
to
solve
so
I,
don't
know
if
it's
worth
blocking
the
functionality.
A
Yeah
yeah
that
that's
fair,
so
yeah.
Let's
try
to
get
a
follow-up,
then,
with
Hassan
and
Nick,
to
make
a
decision
on
that
one,
and
then
you
know
if
there's
something
that
can
be
moved
forward
still
in
this
time
frame.
That
would
be
good,
but
yeah,
let's
see
if
we
can
get
a
final
ad
decision
on
that.
A
Okay,
so
let's
go
ahead
then,
and
look
back
at
the
roadmap,
then
so
in
terms
of
end
integration
testing,
you
know,
Nick
did
a
big
push
on
that
to
kind
of
get
the
the
framework
in
place,
the
the
the
you
know,
patterns
in
place
and
all
of
the
caperity
with
the
previous
integration
tests
there,
so
that
is
all
merged
in
available
in
main
branch.
Now
is
that
is
that
correct?
If
my
resource
me
correct?
A
Yes,
that's
correct,
cool
excellent.
So
then
is
there
any
other
instant
integration,
testing
stuff
that
needs
to
be
done
for
1.13
or
the
patterns
and
practices
and
examples
in
place?
Is
that
that's
that's
great,
and
then
we
have
some
backlog
to
start
implementing
scenarios
of
end-to-end
coverage
and
get
that
coverage,
but
like
otherwise,
though
everything's
in
place
for
having
into
tests
and
running-
and
you
know
giving
us
giving
us
some
Assurance
against
regressions
on
PRS
and
stuff.
B
Yeah
we
we're
discussing
some
change
to
the
pattern
we
are
adopting,
but
other
than
that
begin
to
end
tests
and
the
feedback
we
get
from
the
end-to-end
test
is
not
going
to
change
much
from
or
for
once,
I
think.
Okay,.
A
Good
and
then
the
other
thing
I
was
curious
about
is
I
know,
lovro
has
been
working
on.
You
know
the
granular
management
policies
and
adding
you
know,
essentially
the
ability
to
ignore
changes.
I
think
I
saw
a
PR
this
morning
that
was
opened.
A
You
know,
we've
got
some
of
the
patterns
in
place
now
for
the
types
and
everything
the
shape
of
the
the
apis
to
support
that
in
Cross
main
runtime,
and
then
the
pr
is
now
open,
I
think
on
like
code
generation
to
do
that
in
other
providers
as
well
is
that
is
that
corrective
of
what
other
folks
have
noticed
as
well
or
I,
didn't
look
too
deeply
into
it.
A
But
if
not
okay,
then
I
think
that's
at
least
what
I
saw.
So
that
looks
to
me
then,
because
then
deliver
has
been
focusing
on
it
and
got
a
lot
of
the
core
pieces
in
place
there.
So
at
least
to
me
I
think
that
that
is
on
track,
and
that
looks
like
that
would
be.
You
know,
included
in
1.13,
essentially
so
those
items,
then
in
the
like
the
high
level
roadmap
for
1.13,
look
good.
A
The
I
think
something
to
note
here
is
that
so
for
observing
resources.
You
know
promoting
this
to
Beta.
That's
something!
That's
you
know
with
the
more
granular
mandatory
policies.
You
know
the
ad
gives
new
abilities
of
how
to
do
observable
resources.
How
to
do
ignore
changes.
Things
like
that.
A
You
know
we're
essentially
evolving
the
API
for
observable
resources
that
was
introduced
in
1.12,
and
so
since
we're
continuing
to
evolve
that
API
to
cover
this
new
scenario
as
well,
then
we
do
want
to
have
another
release
of
bake
time
and
stabilization.
For
the
you
know,
management
policies,
API
that
enables
observable
resources
and
so
we'll
be
planning
on
bringing
that
to
Beta
more
in
the
1.14
time
frame
and
not
in
the
1.13
time
frame.
While
we
continue
to
evolve
the
API.
So
that's
important
to
note
here.
A
All
right
so
yeah,
so
you
know
once
again:
we've
only
got
you
know
a
couple
of
weeks
for
less
than
two
weeks
for
feature,
freeze
less
than
three
weeks
for
code
freeze
and
then
about
four
weeks
or
so
for
the
release.
A
All
right,
so,
let's
talk
about
recent
releases
for
providers
then
so
we
there's
two
releases
am
I
typing
in
that
accidentally.
Sorry,
if
I
am
there,
we
go
so
we've
got
two
releases
here
for
the
community
provider
AWS
here,
so
I,
don't
think
Max
is
on
the
call,
but
you
know
maybe
if
Christopher
or
manabu
or
somebody
wants
to
give
us
a
high
level
overview
of
any
of
the
important
changes
in
these.
These
two
releases.
A
D
First,
release
running
in
this
provider
so
but
in
general
I,
don't
know
if
there's
something
really
to
highlight
so
there's
one
new
option
for
a
web
identity:
token
file,
passport
environments,
which
is
inside
now
so
another
option
that
you
can
override
the
identity.
Token
file
pass
yeah
and
the
rest
is
what
what
was
from
the
community
as
pull
requests
open
and
we
worked
on
it
and
merge
it.
A
Awesome,
it
looks
like
a
few
new
contributors
for
this
release
as
well.
So
congratulations
to
all
those
folks
that
got
their
got
their
first
contribution
to
this
repo
was
included
in
the
release,
and
then
it
looks
like
a
fast
follow
with
a
patch
release
as
well
to
fix
a
bug
that
was
caught
in
the
with
the
IM
support.
A
D
A
Okay,
good
good
to
get
a
patch
out
for
that
quickly,
all
right
and
so
then
also
there's
a
few
new
releases
from
this
week
that
I
think
Jean
was
driving
those
those
releases
and
at
least
I
saw
his
name
pop
up
and
like
release,
notes
and
issues
closed
and
stuff
like
that,
so
I
think
Sean
was
driving
those
releases.
A
So
all
the
big
three
Cloud
providers
for
upon's
official
providers,
there
have
fresh
new
versions
to
check
out
as
well
and
then
Christopher
I
know
you
contributed
a
or
have
a
new
brand
new
provider
as
well
for
cast
AI
out
as
well.
Do
you
want
to
tell
us
something
about
that
scenario?
What
it's
covering
and
stuff
too.
D
Yeah,
it
was
with
cost
AI.
You
can
optimize
your
notes,
you're,
using,
for
example,
in
ecas
with
their
engine,
and
you
can
configure
connecting
your
clusters
in
the
read-only
mode
or
in
a
full
access
mode
and
then
cast
AI
will
cover
your
full,
auto
scaling
mechanism.
You
can
enable
a
few
roles
like
you
want
to
very
cost.
Efficiency
running
or
other
options
is
available
for
scheduling
the
pots
and
yeah
in
our
company.
D
We
tried
a
little
bit
with
it
and
we
switched
all
of
our
development
clusters
to
cast
Ai
and
it
looks
very
great
so
from
the
cost
perspective,
you
can
save
a
lot
of
money
if
you're,
using
this
autoscaler
I,
also
added
I,
guess
in
my
private
git
repository
platform,
reference
implementation
with
compositions
that
you
can
enable
it
completely.
A
Oh
nice
I
heard
about
that,
but
I
hadn't
seen
it
yet
Christopher.
Do
you
wanna?
Do
you
want
to
drop
a
link
to
that
here
in
the
agenda
document?
Also,
so
people
have
that
already
dude
nice
good
job,
awesome
man
all
right.
So
let's
go
ahead
and
move
to
the
community
topics
section
here.
A
Also,
so
a
couple
cool
pieces
of
content
that
are
available
now
so
last
night,
Nick
and
I
did
a
podcast
slash,
live
stream
recording
with
the
the
lovely
folks
over
at
floss
weekly
so
that
they
released
that
the
same
day.
So
you
can
go
here
and
check
out
that
it's
about
an
hour
conversation
with
me
and
Nick
and
The
Two
Hosts
there
Doc
and
Jonathan,
and
so
it's
definitely
we
covered
a
lot
of
ground
there.
A
You
know
it's
definitely
some
introductory
material
as
well,
but
so
a
lot
of
cool
opinions
that
were
shared
there
was
a
good
experience
and
there's
multiple
options
to
download
that
you
can.
You
know
watch
the
video
you
can
download
like
The,
you
know
podcast
to
your
podcast
player
or
Spotify
or
whatever
so
I
think
that
was
a
cool
conversation
and
I
would
I
would
recommend
checking
that
out.
A
We
also
have
a
I
guess
we'll
talk
about
this
a
little
bit
more,
but
there's
a
new
to
fact.
Frequently
asked
questions
blog
series
that
we
started
and
the
first
one
is
available
here
at
this
link.
A
A
It
also
there's
also
another
cool
article.
We
found
recently
about
somebody
making
a
assertion
about
only
needing
kubernetes
in
terms
of
you
know,
being
able
to
run,
deploys
your
software
and
your
infrastructure
Etc,
and
it
does
mention
Cross
Lane
being
a
component
of
that
at
the
end,
so
cool
couple,
cool
things
to
check
out
and
get
involved
with,
and
then
Pete
I
think.
Maybe
you
added
these
docs
updates
here.
As
well
for
new
content,
do
you
want
to
talk
about
these
too
yeah.
E
So
we're
working
through
a
pretty
comprehensive
rewrite
of
our
concept
section
to
really
get
dive
into
the
various
knobs
defaults
options,
configurations
and
also
kind
of
compartmentalize,
our
docs
a
little
bit
more.
Instead
of
having
more
kind
of
one
big
thing
describing
everything.
E
So
we've
got
the
first
three
done:
pods
providers
in
Mrs
I'm,
currently
in
the
process
of
taking
apart
the
composite
resources
page
and
that's
going
to
be
a
real
big
one,
because
I
think
it's
turning
into
protecting
that
one
page
and
turning
it
into
seven
I.
Think
in
total.
E
E
But
I
just
wanted
to
draw
some
attention
that
you
know
we're
restructuring.
Some
of
that
I
think
we're
moving
in
the
right
direction
on
on
quality,
and
hopefully
we
can
keep
going
yeah
and
as
Jared's
looking
at
that
PR
a
lot
of
the
other
ones
are
just
placeholders,
but
you
can
see
that
concept
section
is
going
to
grow
substantially
as
we
start
to
parcel
those
out
and
I.
Think
one
of
the
big
side
effects
of
this
is
I.
Think
search
is
going
to
get
a
lot
better.
E
It's
still
not
going
to
be
great,
but
it's
going
to
be
a
step
in
the
right
direction.
A
Very
cool
Pete
and
you
know
I.
Definitely
we
were
talking
about
this
just
last
night
together,
so
I
had
a
bit
of
a
cheat
there
in
terms
of
already
looking
at
those
but
yeah
I
think
that
the
further
Investments
that
we
make
in
you
know
having
useful
helpful
content
to
you
know,
answer
people's
questions
about
crossbling
or
get
help
to
get
them
unstuck,
Etc
and
then
finding
it,
making
it
more
discoverable.
A
So
people
can
access
and
find
the
information
they're
looking
for
as
well
is
is
definitely
a
step
in
the
right
direction.
So,
thanks
for
that,
the
effort
on
that
one-
and
so
are
you-
are
you
looking
for
like
for
broad
feedback
on
475
Pete
or
is
it
you
know
kind
of
like
what
we
talked
about
of
like
hey?
Look
at
the
structure
now,
there's
like
the
topics
and
high
level
Concepts
that
we're
surfacing
makes
sense,
or
is
it
more
more
than
that
that
you
want
now.
E
Mainly
that
I
would
just
say,
re
read
the
composition
stock.
Let
me
know
what
you
think.
You
know
looking
both
for
factual
errors,
but
also
does
it
make
sense?
Is
there
something
missing?
Do
you
have
you
know
if
you're
left
with
question,
then
that
probably
means
I
have
more
work
to
do.
A
Awesome
sounds
good
thanks
for
the
continued
effort
on
that
beat.
Let's
see
here.
So
you
know,
I'll
take
a
pass
to
that
as
well
to
make
sure
that
at
least
the
structure
is
looking
good
there
and
we
can
keep
working
on
that.
A
So
that's
all
the
content
stuff
that
we
had
if
anybody
else
has
any
blog
post
videos
Etc
about
Crossman
they've
seen
recently
or
made
recently
feel
free
to
drop
it
in
here
as
a
suggestion
and
we'll
make
sure
that
we
Make
Some
Noise
about
that
too.
I
think
we
talked
about
this
last
week,
but
I
just
wanted
to
have
one
more
reminder
about
the
special
interest
groups
that
we've
started
up
so
essentially
for
all
the
big
feature
areas
within
the
project.
We
have
started
up
special
interest
groups
for
each
of
them.
A
They
all
have
their
own
channels
that
you
can
subscribe
to
that
you
can
participate
in
the
conversation
and
they've
got
regular
meetings
as
well
to
make
progress
in
those
areas.
So
this
will
give
more
opportunities
for
folks
to
participate
and
contribute
and
collaborate
around
in
areas
of
interest
to
them,
especially
if
it's
a
feature
that
you're
highly
depending
on
and
you're
building
your
platform
around.
So
please
do
check
those
out
and
get
involved
with
those
if
you
want
to
be
participating
in
them.
F
Yeah
I
I
mean
this
special
interest.
Groups
are
kind
of
official
or
documented
or
listed
anywhere
upside
slack
and
the
stock.
C
They're
they're.
G
Just
in
the
community
calendar
at
the
moment,
I
they're,
pretty
lightweight.
We
we
effectively
wanted
to
create
a
forcing
function
to
review
our
designs
a
little
bit
more
so
I
are
you
still
there
Carlos.
It
looks
like
you've
frozen,
no.
G
Cool
camera
problems,
no
problem,
so
not
really.
Basically,
you
can
find
them
in
the
crossplay
community
meeting.
You
can
find
them
with
this
doc.
I
think
there's
there's!
Maybe
to
your
point.
There
is
more
to
do
to
make
them
discoverable,
but
we
didn't
want
to.
You
know,
go
all
the
way
towards
like
kubernetes
style.
Six
with
like
oh,
you
know,
they
have
pretty
heavy
weight,
sync
process
sort
of
thing.
We
just
wanted
to
sort
of
kick
off
some
feelings
to
get
started.
F
Yeah
my
my
two
cents
is
I
was
trying
to
like
parse
the
requests
on
this
bullet
like
you're,
asking
folks
to
to
join
or
make
them
aware,
or
will
be
good
to
have
more
people
in
them
or
there
are
like
ephemeral
things.
That's
that's
the
sentiment.
I
was
trying
to
get
to
and
and
again
I
agree
with
you.
They
don't
to
create
a
Sig
in
cross-playing
right
as
a
cncf
project.
F
You
have
the
autonomy
of
deciding
to
put
a
GitHub
page
with
a
table
and
say
like
these
are
very
lightweight,
like
you
said,
very
lightweight
they're
in
the
calendar
meeting
link
and
here's
the
lag.
It's
like
link
and
the
one
sentence
description,
and
that's
it
no
share
no
work
like
that
way.
You
have
a
link
to
give
to
someone
say:
hey
you're,
interested
in
cross-playing,
hey,
you
want
to
contribute.
F
G
Yeah,
well
let
me
let
me
try
and
walk
through
what
we're
doing
with
this
I
think
one
thing
was
we
had
identified
that
there
was
not
a
great
regular
Forum
to
talk
about
in
Flight
designs,
so,
as
you
can
kind
of
see
by
the
list
of
list
of
channels
there
most
of
these
correspond
to
like
a
big
feature
that
someone's
working
on
or
groups
of
people
are
working
at
the
moment.
G
So
we
have
this
meeting,
but
it's
really
hard
to
use
this
one
hour
to
get
any
like
depth
of
discussion
on
these
things.
Add
this.
You
know
we
might
get
really
deep
on.
Let's
say
you
know
easily
testing
it.
Maybe
70
of
the
people,
just
like
don't
care
or
I,
don't
have
too
much
to
add
there
right,
so
I
think
we're
still
learning.
Some
of
these
might
be
ephemeral
like
some
of
these
might
just
go
away
as
sex
after
the
design
gets
merged.
G
Some
of
them,
like
the
testing
and
things
like
that,
probably
will
stick
around
I
think
as
longer
term
things.
Today,
we've
put
them
in
the
calendar.
We
we
barely
have
agenda
docs
for
them.
We
we
don't
have
the
like:
let's
do
a
GitHub
Etc.
If
anyone
feels
motivated
to
help
with
that
I
would
I
would
very
much
value.
It
I
think
the
reality
is
a
lot
of
these
are
by
Hassan
and
I.
At
the
moment,
I
don't
think
we
have
like
the
bandwidth
to
go
with
the
you
know.
F
G
We
don't
even
necessarily
like
we
don't
even
just
like
we
don't
need
for
all
of
these.
Yet
we've
only
met
for
a
couple
of.
G
I
think
maybe
a
minimum
like
he's
he's
here's
some
things,
I'd
like
to
avoid
I,
don't
want
people
to
have
to
go
and
like
open
up
a
PR
and
go
through
a
process
to
create
a
new
Sig,
but
I
do
agree
that
they
should
be
discoverable.
So
I
think
with
the
base
that
we
could
discover
when
the
meetings
happen,
I
think
and
maybe
the
place
we
discovered
today
when
the
meetings
happen
is
the
Crossway
Community
card.
There
is
just
one
calendar,
a
group
calendar.
G
F
Don't
even
have
to
call
them
six
right,
that's
all
the
thing
we
can
name
it
something
else
like
here's
like
working
groups
that
get
together
and-
and
we
can
even
put
parentheses
like
terminal
or
like
whatever
you
want,
like
whatever
you
want
like
to
to
avoid
us.
That's:
okay,
but
I'm,
not
asking
for
a
formal
process.
That's
asking
for
PRS,
not
asking
for
a
formal,
so
yeah,
let's
table
that
I
think
we're
taking
a
lot
of
time
but
yeah.
That's
the
sentiment.
I
want
to
get.
C
A
Discoverability
aspect
makes
a
ton
of
sense
to
me
as
well
Carlos.
So
if
yeah,
if
you,
if
you
wanted
to
you,
know
open
up
a
PR
just
to
update
the
readme
here
to
kind
of
point
to,
you
know
mention
that
these
groups
exist,
and
you
know
mention
that
on
the
calendar
or
something
small
like
that
totally
reasonable
to
do.
F
A
Cool
that
sounds
good
yeah.
Thanks
for
that
feedback,
Carlos
I,
think
that
makes
a
lot
of
sense
to
help
you
know
make
it
more.
You
know
improving
the
discoverability
of
a
lot
of
things
in
the
community
is
always
always
a
bonus
to
help
people
know
what's
there
and
you
know,
what's
available
so
great,
that's
great
stuff.
A
A
problem
all
right
so
yeah
cool,
then
the
next
thing
on
here
is
that
we
have
a
new
maintainer
Encore
cross
plain
so
Bob.
You
know,
thank
you
very
much
for
all
your
contributions
that
you've
that
you've
made
you
know
all
the
input
on
designs
and
architecture
and
features
that
you've
taken
and
all
that
sort
of
stuff.
So
with
you
know
you
joining
the
maintainer
team
for
core
cross
plain
I
only
expect
to
see
more
of
that
I.
Don't
expect
to
see
that
good
town.
C
A
Thank
you,
fantastic
all
right.
So
next
topic
here
is
around
the
the
release,
dates
for
core
cross
play,
and
so
Nick
and
I
had
a
chat
about
this
and
in
practice
we
don't
really
intend
to
change
too
much
here.
You
know
we're
doing
quarterly
releases
they're
at
you
know
around
the
end
of
the
month,
each
time,
but
we
did
want
to.
We
were
very
hardcore
about
the
specific
date.
You
know
nine
months
into
the
future,
that
something
would
be
released
right
and
I.
A
Don't
think
that
that's
really
helps
the
project
significantly.
I
think
that
kind
of
you
know
it's.
We
don't
need
that
much
of
a
forested
function,
so
I
think
that
we
intend
to
release
its
same
Cadence,
pretty
pretty
much
the
exact
same
thing
actually,
but
not
having
hate
it's
going
to
be
on
the
25th
on
the
morning,
the
25th
exactly
and
that's
what
you
can
expect
I
think.
A
Let's
say
it's
going
to
be
that
last
week
of
the
month
there
and
we
have
a
little
bit
more
room
with
our
code
freeze
our
future
freeze,
and
so
the
variance
here
is
going
to
be
small,
but
I
did
want
to
call
out
that
you
know
it's
not
going
to
we're
not
going
to
say
the
exact
date
multiple
months
in
the
future,
but
in
practice
not
you
know.
The
Cadence
of
releases
here
is
not
really
going
to
change
much
foreign.
A
So
do
let
me
know
if
there's
any
questions
on
that,
but
yeah
I
don't
expect
too
much
too
much
actual
practical
changes.
A
The
next
thing
I
wanted
to
mention
to
folks
is
that
you
know
we
have
had
issues
over
the
last
few
months
with
the
invitation
page
we
use
for
inviting
and
inviting
people
or
having
a
self-service
experience
for
people
to
join
our
Crossway
in
Slack.
So
we
have
a
kind
of
a
stopgap
solution
in
place
there
that
essentially
kind
of
redirects
you
to
an
invite,
link
and
slack
what
whatever
their
reason
is.
They
do
not
allow
those
ex
there's
invitation
links
to
be
in
infinite
or
never
expire.
A
They
won't
expire
in
time,
but
they
will
expire
with
the
number
of
invitations.
So
every
400
people
that
join
the
slack,
the
invite
dies
and
the
link
is
broken,
and
you
know
blah
blah.
It's
not
a
great
experience
for
people
that
want
to
join.
So
you
spend
a
little
bit
of
time
recently
and
got
a
test
site
up.
That
is
essentially
a
replacement
for
it.
That's
kind
of
a
fully
automated
page
that
you
know
doesn't
expire
with
invite
links
and
does
some
interesting
stuff
using
the
slacking,
extended
project
so
I.
A
Just
this
is
an
ask
for
people
to
go
ahead
and
try
out
this
link
here,
the
slack
Dash
extended.crossmind.io.
Let
me
know
if
you
run
into
any
issues
with
it.
If
you
have
any
errors
or
anything
doesn't
work,
you
know
if
you
want
to
try
to
register,
to
join
the
slack
with
it
and
give
me
any
feedback
there.
A
If
we
don't
have
any
issues
with
this,
this
does
look
like
a
wonderful
long-term
solution
to
our
slack
invitation
problem
and
a
fairly
cost
efficient
in
terms
of
engineering
time,
because
it's
not
that
hard.
It
was
not
that
hard
to
put
together,
but
this
looks
like
a
great
solution,
so
I
would
then
you
know
if
it
looks
all
good,
then
I
would
do
some.
You
know
DS
up
DNS
updates,
so
that
slack.crossline.io
then
points
to
this
page
instead
and
the
registration
process
follows
this.
This
flow
instead.
A
G
Sure,
just
to
Carlos's
Point
that
he's
putting
in
the
slack
bar
at
the
moment,
I
think
I
linked
that
this
community
invite
I
think
that
kubernetes
used
I
don't
feel
strongly
if
the
thing
that
you've
really
done
Works
well,
we
should
we
should
use
that,
but
was
curious,
whether
you
looked
at
these
and
decided
not
to
use
them
or
just
weren't
coming
out
of
them.
A
Yeah,
the
the
not
deeply
no,
but
this
this
project
here
has
been
around
for
for
quite
a
while
as
well.
It's
just
kind
of
an
extension
to
the
one
we
were
using
for
five
years,
so
this
is
very
much
like
hey
it's
the
same
environment
variables
you
pass
to
it.
It's
the
same
configuration
file,
it's
like
the
lowest
lift
possible
to
get
something
up
and
running.
That
has
a
surface
area
that
we're
familiar
with
already
and
have
been
has
been
in
place
for
for
more
than
four
years,
maybe
almost
five
years.
A
So
that
was
really.
My
thinking
is
that
you
know
other
projects
use
it
as
well
like
Calico
or
the
in
The
Rook
project
as
well,
so
other
other
projects
are
using
it
within
the
ecosystem
as
well,
and
it's
the
very
similar
to
what
we
were
already
using.
So
it's
Lois,
lift
is,
is
what
was
guiding
here.
A
So
then,
I
wanted
to
make
a
call
out
here
that
I
I
believe
there
will
be
more
speaking
opportunities
in
the
near
future
for
folks
to
talk
about
cross-plane.
You
know,
especially
if
you
had
a
talk
that
you're
excited
about
for
kubecon,
if
it
doesn't
get
accepted,
Etc
I
think
that
we're
I
want
to
get
more
opportunities
for
folks
to
be
out
there
and
speaking
and
presenting
and
sharing
their
success
stories
sharing.
You
know
how
their
platform
works.
A
All
that
sort
of
stuff,
so
just
kind
of
nothing
to
show
here
right
now,
but
just
kind
of
wanted
to
start
greasing
the
wheels
a
little
bit
and
get
people
the
wheels
turning
in
people's
minds
around
you
know
what
you
might
want
to
talk
about
for
crosslane
and
if
you
want
to
brainstorm
or
chat
about
that,
I'm
happy
to
spend
time
on
that,
but
start
thinking
about
things
that
you
might
want
to
share
in
Cross
plain
and
we'll
try
to
find
Opportunities
together
for
that
in
the
future
too.
F
I'll
put
the
link
I'm
working
on
a
co-located
event
for
keepcon
called
up.
We
didn't
have
the
app
developer
con,
it's
the
first
time,
we're
doing
a
co-located
event:
developer,
Focus,
oh
cool.
F
So
if
people
I'm
brainstorming,
like
ideas
of
like
I
work
on
all
I
work
is
devops,
and
then
we
say
we
work
for
developers
to
give
them
a
good
experience
and
empathy,
and
all
that,
so
this
conference
is
more
focused
on
like
giving
the
point
of
view
of
the
developer
me
as
a
developer.
How
do
I
use
these
all
these
tools
like?
Why
do
I
care
about
cross-playing
or
whatever
care,
or
why?
Why
shouldn't
care?
But
they
get
you
they.
You
use
them
right
to
make
those
organizations.
F
F
They
can
be
improved
with
Cloud
native
yeah
ping
me
or
submit
a
talk
to
app
developer
on
and
I
want
to
get
good
content
there
and
it
could
be
from
using
programming
languages
to
drive,
cross,
brain
apis
or
or
be
on
top
of
cross-plane,
and
anything
is
valid
right
as
long
as
you
say,
developer
focused
type
of
individual,
not
devops,
kubernetes
expert.
That
makes
sense.
A
That
sounds
pretty
cool
Carlos.
Do
you
so
that's
in
the
process
now
is
that
is
that
gonna
be
the
kubecon
North
America
Chicago
yeah.
A
Sweet,
so
if
you
want
to
drop
a
link
to
the
cfp
there,
that
sounds
definitely
interesting
and
and
probably
could
have
some
cool
overlap.
We
have
with
what
folks
are
doing
in
this
community
in
space,
and
then
you
know
some
lessons
as
well.
We
could
all
learn
from
that
too.
So
that
sounds
pretty
cool.
A
Cool
all
right,
so
then,
I
wanted
to
call
attention,
as
I
mentioned
really
quickly
earlier,
that
we've
got
a
new
blog
series
that
is
out
or
just
started
about
frequently
asked
questions
that
we
have
in
Cross
plain,
and
so
a
goal
of
this
series
here
is
that
we
will
address.
You
know
common
questions
that
come
up
and
things
that
people
find
challenging
across
Spain
and
get
like
an
article
about
it
and
have
some
some.
A
You
know
some
content
there
that
helps
people
address
these
things,
but
then
also
to
take
that
content
and
put
it
back
into
the
docs
so
that
the
or
I
don't
know
or
bug
fixes
that
will
make
it
easier
whatever.
So
you
know,
get
ideas
from
people
write
about
them,
make
it
easier
to
approach
those
problems,
but
then
get
it
back
into
the
source
as
well
to
kind
of
continue
getting.
You
know,
iterates
in
progress
on
on
making
things
better
overall.
A
So
it's
kind
of
a
call
out
to
this
group
here
of
any
ideas
that
folks
have
about.
You
know
common
questions.
They
run
into
questions
they
hear
in
stock.
A
All
the
time
Etc
I
would
love
to
hear
about
them
so
that
we
can
get
those
on
the
schedule
for
things
that
for
for
the
content
series
here,
and
if
anybody
wants
to
be
an
author
on
that
blog
post
series
too
I'm
happy
to
collaborate
and
and
help
you
know,
help
facilitate
you
right
for
for
people
to
write
articles
to
be
part
of
the
series
as
well.
A
Yeah
and
then,
if
you
want
to
Carlos,
you
can
add
some
of
those
to
the
agenda
doc
here
or
like
on
the
I
think
we're
kind
of
collecting
crowdsourcing
ideas
in
the
documentation
channel
on
cross
on
the.
A
If
you
want
to
throw
ideas
in
there,
Carlos
please
do
and
then
we
can
figure
out.
You
know
hey,
which
ones
do
you
want
to
write
about?
Which
ones
can
you
know
I
write
about?
That
sounds
like
a
really
good
idea:
cool,
okay
and
then
we
had
a
PR
here
that
was
linked
in
the
backlog,
but
I
think
this
PR
has
since
been
merged.
Perhaps
so.
H
H
Yeah,
so
it's
actually
a
part
of
the
latest
proud
area
that
was
release
official.
So
what
is
special
about
this
PR
is
that,
like
viewer,
hesitating
to
implement
it
to
the
point
that
it
was
actually
closed,
the
first
iteration
of
it,
but
then
Community
requested
that
you
we
really
need
this
implementation
and
so
I
updated
it
and
get
to
the
well-tested
well-tested
scenario.
So
what
is
special
is
that
this
Route
53
is
on
Association.
H
It
is
like
a
kind
of
special
thing
that
touches
across
account
scenario,
so
Route
53
in
one
account
and
the
private
private
router
this
result
and
VPC
in
another
account.
So
this
Association
is
capable
to
to
create
this
this
connection,
and
there
is
like
additional
thing
that
is
called
I-
think
VPC
Zone
authorization
that
enables
this
cross
account
access
right
by
instantiating
this
Mr,
so
that's
kind
of
special
situation
and
additional
usefulness
out
of
this
VR,
apart
from
like
it
was
actually
requested
by
Community.
Is
that
like
we
can?
H
H
Here,
yep
and
if
you
can
yeah
thank
you,
you
can
see
like
there
is
a
like
a
private
conflict,
ref
tier.
So
there
is
okay
yeah.
So
that's
how
provider
AWS
tests
set
up
test
script
handles
it,
so
it
recreates.
Now
you
can
find
it
in
a
repository
if
interested
it
creates
a
two
provider
configs
that
are
actually
configured
to
different
AWS
accounts
right
and
pointing
to
this
default
and
a
special
peer.
You
can
create
an
actual
a
cross
account
end-to-end
test
cases
right.
H
So
that
was
very
useful
for
this
specific
scenario.
So
we
can
deterministically
prove
that
this
cross
account
Zone
Association
actually
works,
so
that
was
interesting
experience
and
special
to
Greece
for
validating
it
is
as
they
are
in
non-synthetic
environment,
but
they're
real,
real
cross
plane,
one
in
his
organization.
So
that's
it
yeah
and
again
it's
probably
it's
already
part
of
the
release.
So
it's
available
for
for
users.
A
Awesome
Yuri
yeah
thanks
for
sharing
that
update
there.
That's
you
know
about
and
giving
us
the
background
about.
You
know
what
this
solves,
why
it's
important
and
then
also
that
you
know
driving
it
to
get
it
included
and
merged
and
then
part
of
the
related
release
as
well.
So
that's
awesome
and
thanks
Carlos
and
Chris
as
well
for
validating.
A
A
All
right
sweet!
If
that
is
everything,
then
folks,
then
we
can
go
ahead
and
wrap
up
for
the
week,
and
you
know
great
to
see
everybody
here
today
and
once
again,
congratulations
to
to
Bob,
and
you
know,
looking
forward
to
everyone's
contributions
as
we're
working
towards
the
1.13
release
in
less
than
less
than
a
month,
foreign.