►
From YouTube: 2022-01-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
All
right
recording
has
started,
and
this
is
the
cross
plane
community
meeting
for
january
27th
2022
and
that's
a
special
date
that
has
nothing
to
do
with
the
community.
But
it's
my
birthday
so
I'll
make
that
as
the
first
announcement
that
has
nothing
to
do
with
the
project
or
where
anything's
going,
but
I'm
happy
so
I'll.
Take
it.
We
can
keep
on
filling
in
the
attendees
list
with
folks
from
the
participants.
A
A
We
have
not
had
a
community
meeting
for
about
a
month
now
because
we
took
a
holiday
break
and
then
we
had
a
conflict
at
the
last
regularly
scheduled
time
when
a
lot
of
folks
maintainers
were
at
a
separate
event.
So
we
are
getting
back
on
track
here
to
kick
off
2022
and
back
to
our
regular
cadence
of
every
two
weeks
for
the
community
meeting.
A
So
we'll
go
ahead
and
get
started,
then,
with
our
recent
releases
I
believe
so
1.6
the
that
minor
release
was
was
done
at
the
very
beginning
of
the
year
in
2022.
A
So
that
1.6
release
is
out-
and
we
have
done
also
two
patches
to
it
since
the
since
the
the
release
itself
came
out,
so
we
have
the
release
notes
available
here.
I
believe
nick
was
the
driver
on
that
on
that
release
there
nick
is
there
anything
you
know
kind
of
major
you
want
to
touch
on
for
that
release.
That
kind
of
summarizing
it
for
us.
Give
me
a
second
to
swap
it
back
in.
B
I
I
think
I'd
mostly
just
be
reading.
What's
on
here
I
mean
the
big
sort
of
warning
of
the
top.
Is
the
big
one
beta
1
apis,
a
bunch
of
them
were
removed.
We've
been
sort
of
tracking
those
for
deprecation
in
removal
in
1.6
for
a
while,
so
those
are
gone
as
you
can
see
there,
we're
also
going
to
get
rid
of
some
of
the
package
metadata
apis,
the
v1
alpha
one.
B
So
those
are
the
things
that
you
put
in
your
crossplane.yaml
in
your
packages,
not
actual
sort
of
api,
server-side,
api
types,
and
I
think
yeah,
the
the
the
sort
of
the
only
feature
as
it
were,
or
the
big
headline
feature
of
this
release
was
over
the
last
quarter
or
two.
B
We
did
a
bunch
of
scale
testing
to
sort
of
figure
out
ways
that
we
could
make
cross-play
a
little
bit
more
performant,
where,
in
this
case,
performance
means
being
able
to
reconcile
more
composite
resources,
more
managed
resources
at
once
and
also
sort
of
when
you
have
a
lot
of
managed
resources,
drive
them
to
completion
readiness
more
quickly.
B
So
we
did
a
bunch
of
behind
the
scenes.
Tutoring
that
just
will
have
will
be
there,
whether
you
are
doing
anything
or
not.
When
you
upgrade
to
1.6.
We
also
added
a
flag
max
reconcile
rate
that
you
can
see
on
these
release
docs
to
sort
of
tune
that
a
little
bit
further,
and
I
forget
what
I
put
there,
but,
as
you
can
see,
it's
sort
of
you
know
in
my
experiments,
sort
of
quasi
scientifically
against
cross
playing
about
two
to
five
times
faster.
B
B
Oh
sorry,
I
thought
victor
was
talking
to
me
two
times
faster
is
if
the
providers
that
you're
using
haven't
been
updated.
If
you
also
make
some
more
updates
to
the
providers,
then
that's
the
five
times
faster,
so
everything
I've
stopped
in
my
head.
A
Nick
yeah,
thanks
for
driving
that
release-
and
you
know
like
for
the
entire
team
for
getting
out
that
functionality
there.
So
then
we
had
a
couple
patches.
I
think
that
one
thing
that
I
wanted
a
little
bit
more
of
a
better
understanding
of-
and
this
is
to
dan
from
the
1.6.2
patch
that
came
out
recently.
I
know
there's
a
whole
bunch
of
effort
on
you-
know
getting
the
provider
credentials
stuff
working
and
with
proxies
and
all
that
stuff.
So
is
there?
A
C
All,
except
for
one,
which
is
not
a
regression
per
se,
so
all
situations
of
pulling
using
secrets
and
and
kind
of
like
just
your
normal
registry,
config
kind
of
stuff,
should
be
working,
just
fine
all
cloud
provider
credentials.
So
if
you're,
using
irsa
or
workload
identity
or
something
like
that,
should
also
be
working
fine.
With
the
exception
of
acr
azure's
container
registry,
there
is
still
a
bug,
that's
actually
been
addressed,
and
it
actually
was
addressed
right
before
this
release
went
out
and
it's
fairly
small.
C
The
reason
why
it
was
not
included
is
because
we'd
had
a
lot
of
community
members
chip
in
to
testing
this
specific
artifact
in
this
and
including
it
would
have
bumped
a
number
of
other
things.
We
also
didn't
currently
have
any
users
using
azure's
container
registry,
and
if
they
tried
it
would
have
been
broken
already.
So
we
definitely
want
to
improve
that
functionality,
but
we
made
the
trade
off
here
to
go
ahead
and
move
forward
with
an
artifact.
We
had
confidence
in
for
the
release
and
follow
up
with
that.
A
Yeah,
that
sounds
like
a
good,
a
good
approach
there
dana
thank
you
for
explaining
the
nuances
of
that
for
us
and
and
great
work
too
also,
you
know
collaborating
with
the
the
folks
on
the
you
know,
go
container
registry
project
to
get
some
fixes
in
there.
Also
so
yeah.
B
That
yeah,
that
project
is
coming.
A
Along
nicely,
I
really
I
really
like
what
they're
what
they're
doing
there
and
they
call
it
contributions
you've
made
to
it
as
well
all
right
so
upcoming
releases,
though
so
we
are
working
towards
a
1.7
release
kind
of
early
in
the
cycle
with
you
know
getting
the
1.6
out
earlier
this
month
and
then
kind
of
slowly
getting
things
going
for
2022,
and
you
know
planning
and
things
like
that,
so
a
little
bit
early
in
the
cycle
there,
but
I
think
something,
that's
really
exciting
or
first
actually,
first
note
is
that
you
see
on
the
screen
there
that
the
intended
release
date
there
is
towards
the
end
of
march,
so
typical
cadence
of
every
couple
months.
A
The
end
of
every
other
month
is
when
the
release
will
be
so
it's
scheduled
right
now
for
march
22nd.
So
that
is
so
something
very
exciting.
I
think,
though,
is
that
you
know
we'll
get
into
more
details
about
the
terror
jets
announcements
from
earlier
this
week,
but
with
that
big
milestone
for
terra
jets,
a
lot
of
the
crossblade
maintainers
will
now
be
having
a
little
bit
more
bandwidth
to
start
taking
on
core
cross
plane
functionality.
A
Again,
so
on
the
roadmap,
we
will
be
addressing
some
of
the
more
higher
demand
and
big
impact
features.
Now,
so
that's
it's
very
exciting
to
have.
You
know
solved
a
lot
of
the
the
concerns
around
provider
coverage
and
then
being
able
to
move
back
into
functionality
again.
So
we're
going
to
see
some
roadmap
improvements,
starting
here
in
q1
of
this
year
and
we'll
be
we'll,
be
investing
in
in
core
cross
plane.
A
Some
things
to
highlight
on
that
specifically
so
hassan
is
not
with
us
today,
but
he
had
already
completed
a
design
dock
on
the
plugable
secret
stores,
and
so
that
will
be
we'll
be
moving
to
an
implementation
phase
with
that
and
so
that
functionality
that
is
described
in
the
design
dock
there
will
be
something
that
will
be
expected
to
see
as
a
deliberate
feature
over
the
next
quarter
or
so
another
one.
A
I
think
that
is
of
of
quite
big
importance
is
that
nick
and
sergeant
will
be
driving
the
custom
compositions
feature
that
one
has
been
a
you
know
a
pretty.
I
think
that
one
has
a
lot
of
impact.
A
lot
of
value
of
you
know
being
able
to
take
compositions
and
the
functionality
there
to
you
know,
don't
know
it's
like
next
level.
It's
kind
of
like
really
opening
up
a
lot
of
functionality
there
that
it's
not
strictly
in
the
dsl
for
it.
A
So
that
would
be
something
that
nick
and
sergey
are
driving
and
putting
some
info
putting
some
of
their
efforts
into
nick.
Is
there
anything
that
you
want
to
add
about?
You
know,
timeline
or
sp,
not
necessarily
timeline,
but,
like
you,
know,
deliverables
or
milestones
or
feedback
that
you
want
from
the
community.
Anything
like
that
too.
B
I
just
added
this
to
the
1.7
roadmap
to
since
it's
the
end
of
march
to
have
an
alpha
implementation
when
asked
two
weeks
ago,
getting
this
to
alpha
implementation
by
the
end
of
q1
seemed
very
feasible.
Now
that
I'm
committing
to
a
date,
I'm
I'm
inclined
to
hedge
a
little
bit
say
that
it's
a
little
bit
of
a
stretch
to
get
1.7,
but
I
think
we
can
do
it.
B
I
would
just
ask
you
know
anyone,
that's
interested
or
anyone.
That's
had
limitations
with
with
compositions.
Please
please
click
through
to
that
custom,
compositions
issue
and
add
a
comment
on
it.
I
think
sort
of
some
of
the
most
valuable
feedback
style
that
you
could
give
us
is
is
effectively
just
like
walking
through
where
composition
hasn't
worked
for
you,
why?
You
think
you
would
want
this
feature,
like
specific
scenario,
isn't
as
much
detail
as
possible
advice.
A
Awesome
yeah,
I
think
that's
going
to
be
fantastic
to
move
the
project
forward
for
the
community,
so
I'm
really
glad
we're
getting
some
focus
time
on
that.
One
and
yeah
feedback
on
the
experience
as
nick
mentioned
would
always
be
useful,
the
and
then
another
one
I
can
think
of
as
well.
That
I
believe,
will
be
getting
some
some
effort
into.
Is
the
plugable
web
hooks
sort
of
framework
there?
A
You
know
that
enables
a
lot
of
things
like
being
able
to
do
validations
for
compositions
and
you
know
other
other
entities
in
the
crosswind
type
system.
So
you
know
having
a
bit
of
a
standardization
there
or
some
reasonability
to
be
able
to
more
easily
do
that
and
have
validation
and
web
hooks
etc
for
other
providers.
C
A
Be
quite
useful,
so
I
believe
we'll
be
spending
some
time
on
that.
Also
there's
already
been
some
design.
Thinking
on
that
one
and
you
know
being
able
to
move
a
lot
of
these
big
ideas
that
we've
been
pushing
for
designs
on
towards
implementation
is
going
to
be
really
nice
for
the
project
in
the
next
quarter
or
so
so
you'll.
You
can
expect
to
see
effort
on
all
those
you
know
during
the
1.7
time
frame.
You
know,
as
nick
mentioned
you
know,
maybe
some
early
alpha
implementations
will
be
delivered
in
there.
A
So
I
think
1.7
should
have
some
interesting
things
in
it.
As
we
have
you
know,
kind
of
a
2022
prioritization.
You
know
effort
ongoing
here.
Anybody
else
want
to
weight
in
on
road
map
items
or
upcoming,
milestone,
1.7
things
anything
on
people's
minds.
There.
A
All
right
cool
cool,
then
we
can
go
ahead
and
move
on
to
providers.
Then
after
our
conversation
there
about
some
deeper
investments,
we're
making
in
core
crossplane.
A
So
the
biggest
thing
here
for
providers
is
the
big
announcement
from
monday
on
the
ontario
jets
and
the
set
of
jet
providers
and
their
you
know
deep
coverage
of
all
of
resources
in
the
cloud
providers.
There
is
I'll
let
somebody
else
who
works
more
directly
on
it.
I
can
kind
of
dive
into
that
matthias
or
au
pair
anybody.
Do
you
want
to
kind
of
talk
about
the
high
level
big
announcement
there,
since
you
all
had
a
huge
part
in
it?.
D
Sure
I'll
start
and
then,
if
anyone
chime
can
want
to
chime
in
add
anything,
please
do
yeah.
We
had
our
announcement
with
a
little
bit
of
champagne
and
red
bull,
depending
on
the
title
of
where,
where
you
are
in
the
world,
I
had
red
bull,
yeah
and
yeah.
D
We
had
had
the
announcement,
it's
really
interesting,
to
see
because
obviously
from
a
community
perspective-
and
I
don't
recognize
all
folks
here-
you
know-
terra
jet
was
obviously
already
you
know
being
aware
of,
but
it's
it's
really
interesting
to
you
know
see
of
what
what's
kind
of
like
a
little
bit
of
promotion
can
do
so.
That's
like
one
of
my
key
takeaways
is
like
do
this
announcement
and
be
be
big
about
it.
D
I
guess
one
thing
that,
and
we
can
you
know,
start
on
this
on
a
personal
conversation
I'll
I'll
re-raise,
this
in
a
larger
later
call
what
we
would
be
interested
in-
and
just
you
know,
from
an
outside
upbound
perspective
is
like
how
this
was
perceived
and
how
like
the
community
was.
You
know
outside
of
upbound,
was
like
perceiving
this.
If
this,
if
there's
anything
that
we
could
have
done
better
but
yeah
from
our
perspective,
you
know
we're
we're
really
really
happy
about
this.
D
We
already
are
seeing
some
more
traction
on
it.
You
know
people
are,
are
starting
to
use
it.
There's
you
know
if
you,
if
you
head
over
to
terra
jet,
there
are
open
issues
but
yeah,
nothing
that
I'm
I'm
seeing
currently
blocking
for
for
creating
these,
but
yeah.
Just
you
know
just
another
pre,
please
give
us
feedback,
give
it
a
try
if
you
have
any
thoughts
on
improvement
or
for
the
further
ideas.
Let
us
know.
A
Yeah
awesome
and
we
have
a
bunch
of
links
further
down
in
the
agenda
doc
and
the
content
section
for
the
recording
of
that
live
stream
and
blog
posts
about
it
and
stuff.
So
people
can
get
into
the
nitty
gritty
details
with
all
of
those
links
there.
D
E
So
maybe
I
can
give
some
details
in
on
the
repo
level.
Like
you
know,
terrorist,
yet
0.3.2
was
released
during
this
period
in
preparation
for
the
announcement,
and
you
know
before
the
announcements
we
also
worked
on.
You
know
finalizing
the
api
groups
and
kind
configurations,
etc.
This
doesn't
mean
that
we
have
configured
each
and
every
resource,
because
there
are
hundreds
of
them,
of
course,
but
we
try
to
give
the
final
shape,
at
least
to
the
api
groups,
and
we
worked
on
adding
some
common
reference
fields.
E
You
know
to
make
the
resources
exam
compliant,
etc.
So
we
tried
to
close
some
open
gaps
before
the
announcement,
and
you
know
because
of
these
efforts.
We
had
releases
from
the
three
jet
based
providers,
namely
jet
azure
jet
aws
and
gcp
providers,
and
also
you
know
new
jet
based
providers
that
also
keep
coming
in.
A
D
No
there's
there's
a
link
from
hassan
that
basically
queries
github
of
of
what
the
what
the
previous
of
of
github
of
readme
that
contained
our
previous
string,
so
so
nothing,
nothing
official.
That
said,
I
have
a
personal
project
called
awesome
providers,
I'll
I'll
link
it
in
a
second,
but
it's
it's
just
just
for
me
to
to
to
keep
to
keep
up
to
date.
On
that
note,
we'll
definitely
looking
into
making
making
it
more
discoverable
of
of
looking
into
providers
and
finding
providers.
D
So
that's
definitely
something
on
our
list.
Nothing
concrete
there.
If
anyone
has
any
thoughts
ideas,
you
know
requirements
bring
them
along,
but
yeah
we
we,
we
will
make
them
more
discoverable
for
sure.
A
D
A
A
lot
of
pretty
interesting
things,
so
there's
a
couple
provider
releases
recently
as
well
so
provider
aws
had
a
0.23
release
since
the
last
time
we
met
christopher.
Do
you
want
to?
I
think
you
drove
that
one?
Do
you
want
to
give
us
a
quick,
high-level
update
of
what
was
included
in
that
or
things
to
note.
B
In
general,
a
thanks
for
for
aaron
to
testing
a
lot
of
the
merge
requests
from
my
site.
Otherwise
we
had
not
so
much
new
crds
available,
but
in
general,
elastic
load.
Balancer
is
available
now
in
the
provider
and
also
a
lot
of
more
resources
in
the
ec2
group.
B
I
think
we
see
that
fixing
the
problem
in
the
code
generator
for
easy
to
fix
or
helps
the
folks
a
lot
to
generate
more
and
more
ec2
resources
and
yeah.
The
rest
of
the
of
the
fixes,
and
so
on
are
related
to
used
resource
composition
that
references,
resolvers
and
external
annotations
working
as
expected.
A
A
That
sounds
good
thanks
for
writing.
That
update,
I
like
to
see
the
number
of
new
contributors
to
the
repo
as
well
in
that
release,
so
six
different
contributors
that
made
their
first
change.
First
contribution
to
provider
aws
in
a
release
is
pretty
decent,
so
that's
awesome
to
see
and
matias.
I
got
your
the
link
here
to
your
repo,
your
curated
providers
here
so
I'll
just
make
a.
A
In
here
perfect,
let's
click
that
link
there.
We
go
okay,
that
sounds
good
yeah
and
then
there
was
a
couple
of
other
releases
of
their
providers,
had
a
0.2
release
and
jan
and
his
team
have
been
working
on
that
pretty
pretty
heavily,
so
that's
good
to
see
that
functionality
and
then
there's
an
exoscale
provider
as
well.
I
think
there's
more
that
we'll
see
maybe
from
mathias's
curated
list
there,
but
we'll
continue
calling
them
out
in
this
community
meeting
as
the
more
than
one
of
them
are
making
progress.
A
I
think
we
kind
of
touched
on
a
lot
of
the
the
provider,
aws
and
and
other
native
providers
like
updates
for
that.
But
then
so
it
looks
like
we
had.
Do
you
have
a
quick
update
here
for
provider
azure
on
some
new,
mrs
managed
resources?
Albert,
do
you
want
to
add
a
little
bit
more
details
to
that?
One.
E
Yeah,
maybe
since
these
were
added
by
sargan,
he
might
want
to
talk
more
about
them.
What
what
do
you
think
sagan?
Would
you
like
to
sure
actually.
B
B
One
of
them
is
the
dns
one
and
the
another
one
is
the
dnsc
cord
set
managed
resources.
B
Other,
for
example,
firstly,
after
the
creation
is
on
you
can
add
some
record
sets
for
these
resources.
Yeah.
A
That's
are
those
are
those
at
a
like
a
v1
alpha
one
level
now,
since
they've
just
been
introduced.
A
All
right
so
yeah
lots
of
lots
of
updates.
You
know
the
community
is
growing.
Their
velocity
is
picking
up
we're
making
you
know
a
ton
of
strides
and
providers
and
then
now
you
know
focusing
again
on
core
cross
plan,
so
expect
to
see
a
whole
lot
going
on
in
2022.
I
think
there's
going
to
be
a
lot
of
progress
in
cross
plane
in
the
ecosystem.
In
general,
I
put
together
a
list
of
talks
and
blog
posts
and
such
over
the
last
period
since
the
last
community
meeting.
A
We
won't
touch
on
every
single
one
of
them
here,
but,
as
mentioned,
you
know
with
the
terror
jets
announcement.
This
is
the
collateral
here
that
is
directly
related
to
that
you
can
watch
the
the
live
stream
that
victor
and
moaf
and
matthias
did
on
tuesday
monday
morning,
tuesday
morning.
I
can't
remember,
but
earlier
this
week,
and
so
you
can
kind
of
relive
their
celebration
there
and
then
learn
a
lot
more
about
the
project
as
well.
There
was
a
lot
of
engagement
from
the
community
and
people
watching
that
live
stream.
A
So
a
lot
of
questions
folks
might
have
you
know
watching
this
as
a
resource
to
learn
more
and
get
some
of
the
potentially
common
questions
that
are
asked
and
answered
in.
There
might
be
a
good
good
experience
for
a
lot
of
people
that
want
to
learn
more.
We've
got
some
high-level
blog
posts
about
it
and
then
the
first
of
a
three-part
series,
blog
post
of
the
technical
dive
into
different
areas
of
the
terror
jets
project
and
then
the
providers
that
it
enables.
A
So
there
will
be
three
different
authors
in
those
series.
So
muafix's
is
done.
I
think
hassan
is
doing
part
two
and
then
alpera
is
doing
part.
Three
so
expect
to
see
some
more
technical,
deep
dives
to
kind
of
get
through
all
of
the
different
facets,
areas
and
components
of
the
project
there,
and
so
there
will
be
more
to
come.
A
Aaron
did
some
pretty
interesting
stuff,
I
think,
with
with
automated
testing.
You
know,
unit
testing
and
integration
testing,
I
guess
sort
of
but
testing
across
main
packages
using
some
tools
in
the
ecosystem
and
how
to
do
test
driven
development
for
crossbane
as
well.
So
aaron,
do
you
want
to
add
a
little
bit
more
details
on
that
one,
since
I
thought
those
are
pretty
interesting,
write-ups
and
something
that
I
don't
think
people
have
been
talking
about
before
you
did
that
right
up.
F
Yeah
the
this
I'm
pretty
excited
about
it.
This
is
kind
of
the
for
me.
The
real
big
win
as
an
sre
using
crossplane
and
using
composition.
Is
this
ability
to
finally
finally
say
hey.
I
got
my
managed
resources
in
the
state
that
I
know
I
want.
I've
got
my
template.
How
can
I
codify
that
so
that
I
don't
need
to
just?
I
launch
it
to
make
sure
that
I
didn't
break
my
composition,
so
this
is
basically
the
ability
to
write
a
test.
F
That
says
here
is
what
I
finally
want
deployed,
and
it
also,
I
think,
and
I'm
I
want
I
I
need
to
experiment
with
this,
but
I
also
believe
this
means
it
allows
you
to
start
editing
a
composition
so
that
it
better
suits
your
internal
processes
when
you're,
maybe
not
making
an
infrastructure
change
like
you,
you
need
to
repackage
something
you
need
to
make
something
part
of
a
different
composite
resource,
because
a
different
team
wants
to
own
it,
but
you
want
to
make
sure
the
final
product
comes
out.
The
same.
F
That's
another
nice
thing
you
get
if
you
start
kind
of
test
driven
development
processes
around
your
compositions
rather
than
kind
of
a.
I
want
to
sculpt
my
infrastructure
around
what
composite
owns
it.
Instead,
I'm
sculpting
my
composites
around
process
and
the
infrastructure
can
stay
the
same.
A
Yeah,
it's
an
interesting
new
perspective
that
was
at
least
new
to
me
aaron.
So
I
think
that
that's
really
cool
from
someone
who
is
a
platform
engineer-
and
you
know,
building
packages
and
using
compositions
to
solve
real
problems.
This
is
super
interesting
to
kind
of
build
out
some
of
the
capabilities
for
developing
and
testing
and
iterating.
So
this
is.
This
is
really
cool
that
you
drove
this
man.
A
So
there's
two
articles
on
that
one,
the
first
about
how
to
do
testing
and
then
how
to
do
test-driven
developments
as
well.
Nate
also
put
together
a
series
of
blog
posts
on
sort
of
the
basics
of
crossplaying
and
putting
them
together
to
start
becoming
effective,
as
well
as
he's
been
ramping
up
in
the
ecosystem.
So
there's
this
I
linked
one
from
directly
here,
but
that's
the
kind
of
the
summary
of
of
his
earlier
posts.
A
So
you
can
go
there
and
see
the
rest
of
the
post
for
kind
of
a
journey
through
some
of
the
basic
concepts
and
then
this
article
here
putting
them
all
together.
So
that's
really
helpful
for
people
new
to
the
community
to
kind
of
start
learning
more
about
some
of
the
concepts
and
start
their
journey
of
education
too.
A
Let's
see
what
else
what
else?
What
else
a
couple
different
talks
in
webinars
that
victor
has
been
doing
recently.
The
code
fresh
one
was
probably
particularly
interesting
to
folks
and
then
another
note
here
there
is
an
upcoming
webinar.
This
one
has
not
happened
yet
that
I
believe
grants
gregorimina
will
be
running,
and
so
you
can
kind
of
learn
more
about
some
of
the
things
that
we're
building
within
the
community
and
then
it
upbounds
specifically
as
well
and
there's
a
link
here
to
register.
A
If
anyone
is
interested
in
that,
so
there's
a
big
list
of
content
and
people.
Talking
writing
you
know
recording
things
about
crossplane.
I
think
I
pretty
much
got
most
of
the
things
that
I'm
aware
of
over
the
past
couple
weeks.
Some
things
could
have
slipped
through
the
cracks.
So
if
anybody
knows
of
any
other
interesting
contents
related
to
cosplay
and
feel
free
to
add
it
to
the
agenda
doc
and
we'll
we'll
get
it
merged
in
there
all
right.
A
So
we're
kind
of
near
the
end
of
nearing
the
end
of
the
agenda.
If
folks
had
you
know
specific
issues
or
pull
requests
or
things
that
they
wanted
to
bring
up
within
this
forum,
go
ahead
and
start
thinking
about
those
and
getting
them
added
to
the
agenda
document.
Now
those
thoughts
are
empty
right
now,
so
there
is
more
time
for
those
I
wanted
to.
I
brought
a
couple
of
these
guys
up
here.
A
Just
from
I
went
through
some
recent
slack
discussions
and
saw
things
that
were
maybe
interesting
to
share
here
within
this
group,
and
so
one
thing
I
saw
is
that
somebody
was
asking
about
running
in
a
windows
environment.
I
have
not
done
that
myself,
so
I
dan,
I
think
you
kind
of
answered
some
of
their
questions
there.
What
is
the
expectation
for
being
able
to
run
crossplane
in
a
windows
environment
right
now?
If
someone
has
a
windows
machine.
C
I'm
not
exactly
sure
what
this
one
specifically
was:
referencing.
We
definitely
publish
windows
binaries
for
our
for
our
cli
and
so
yeah,
most
of
the
most
time
you're
running
crossplane
in
a
containerized
process,
which
you
know
we're
not
doing
anything
with
windows
containers.
So
I
think
in
this
one,
the
installation
script
was
just
omitting,
a
specific
arch
that
was
being
sent
back
by
the
operating
system,
and
so
it
was
just
a
simple
update
where
the
we
had
a
binary
that
worked
for
them.
C
It
just
wasn't
being
installed
by
the
install
script.
So
I
don't
think
there's
anything
that
should
prohibit
windows
users,
though
we
do
obviously
test
much
less
on
windows,
because
most
of
the
developers
who
work
on
crossplane
do
not
have
windows
machines.
They
have
to
be
our
dedicated
qa
person
for.
A
A
No,
but
so
the
expectation
is
that,
like
from
a
client
perspective
of
you're
using
cube
control,
you
want
to
use
the
q
the
cross
plane.
You
know
cli,
you
want
to
use
the
the
q
control,
plug-in,
etc.
So
cube
control
cross
plane
from
a
windows
machine
should
be
able
to
work
now
once
you're
installed
right,
absolutely
awesome,
very
cool.
A
Then
server
side
like
if
you,
if
you
have
a
cluster
with
windows
nodes
in
it,
is
there
anything
special
that
I
really
don't
know
anything
about
kubernetes
on
windows,
I'm
so
sorry,
but
is
there
anything
like
special?
That
needs
to
be
done
to
enable
that
type
of
scenario?
Are
we
agnostic
to
that?
Do
we
not
work
in
that.
C
Scenario,
I
don't
think
we'll
work
in
that
scenario,
we
omit
I'm
just
double
checking
here.
We
omit
all
darwin
and
windows
builds
for.
Well,
that's
actually
just
for
images.
So
we
we
do
technically
have
a
cross
plane
binary,
I
believe,
for
for
windows,
but
we
don't
have
any
images,
not
an.
A
Image:
okay,
cool
so
like
on
a
windows
node.
If,
if
somebody
was
running
like
that,
you
know
that
there
wouldn't
be
necessarily
a
container
image
to
pull
down
and
run
on
that
node
correct,
got
it
okay,
that
makes
sense
that
makes
sense,
cool
and
then
somebody
else
had
brought
up
something
like
they're,
a
little
bit
of
confusion.
That
was
in
their
mind
around
crosstalk
packages
and
helm
charts,
and
so
I
just
wanted
to
kind
of
clarify
a
little
bit
more
for
that.
A
There
are
other
folks
who
had
some
confusion
on
it
around.
You
know
cross
playing
packages.
You
can
think
about
those,
as
installing
all
of
your
types,
they're,
like
your
crds,
your
ex
your
composite
resource
definitions.
You
know
your
type
system
and
the
capabilities
of
your
of
your
control
plane
get
installed
to
crosstalk
packages
and
then
it's
totally
reasonable
to
use
helm,
charts
to
to
create
instances
and
flow
templated
values
into
instances
of
those
types.
A
So
that
was
a
bit
of
confusion
there
about
trying
to
use
helm
to,
or
packages
to
you
know
instances
or
home
charts
to
do
types,
but
it
seems
like
a
nice
clear
delineation,
between
using
packages
to
get
the
type
system
in
place
and
using
helm
charts
to
create
instances
is
a
totally
reasonable
separation.
Dan
was
there
something
else
to
add
on
that.
From
that
conversation
that
you
had
with
the
slack
member.
A
Awesome
well,
cool,
okay!
So
anything
else!
That's
going
on
for
folks
in
the
ecosystem
community
things
of
interest
that
folks
want
to
bring
up
while
we're
still
together.
E
E
As
I
mentioned,
the
pull
a
pull
request
is
under
reveal
in
aws
controllers
for
kubernetes
code
gun
repository
and
if
it's
accepted,
as
we
suggested
it
will,
you
know,
introduce
a
backward
incompatible,
behavior
change
in
the
code
gang
that
we
are
employing
in
provider
aws
the
incompatible
behavior
changes.
You
know.
E
However,
you
would
like
to
introduce
you
know,
capability
of
configuring,
the
generated
version
for
the
custom
resource
definitions,
and
you
know
we
would
like
to
do
this
per
resource,
and
for
that
reason,
with
that
change,
if
it's
accepted
it's
already,
has
an
approval
but
not
merged.
Yet
we
will
be
moving
the
generator
config.yaml
files
to
the
api
root
directory.
Instead
of
the
version
directories
version
directories,
there's
a
draft
pr
open
in
provider,
aws.
E
Maybe
we
can
also
check
that
to
get
a
glimpse
of
what
will
happen.
B
E
A
And
is
is
that
okay,
so
that'll
affect
this
repo?
This
move
makes
all
those
movements
and
then
is
there,
like
documentation
of
you,
know
the
how
to
use
ack
to
generate
new
resources,
that
is,
that
updated
as
well,
so
that
folks,
following
that
guide,
will
end
up
with
things
in
the
right
place.
A
Awesome:
cool,
okay,
yeah.
Thanks
for
sharing
that,
then
I
appreciate
it.
A
All
right,
so
I
think
that's
everything
then,
for
the
agenda
here,
so
I
think
we
can
go
ahead
and
get
wrapped
up
here
and
adjourn
so
yeah
thanks
everybody
for
showing
up
today
here
and
a
whole
lot
of
exciting
things
to
keep
rolling
on
for
2022.
No
doubt
about
it
so
good
to
see
everybody
and
we'll
see
you
next
time.