►
From YouTube: 2021-12-02 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
So
first
thing
is
about
the
crosstown
releases,
so
we're
expecting
the
1.6
release
to
be
cut
in
december
21.
But
it's
feature
freeze
is
on
december
7
next
week.
So
we
gotta,
like
you,
know,
merge
all
the
pr's
that
introduce
new
feature
by
december
7
so
that
they
they
they
are
included
in
the
release.
And
after
that
point
we
will
accept
patchfix
patches
for
like
bugs
until
I
believe,
like
you
know,
december,
like
three
or
four
days
before
december
21
the
day
we
cut
the
release,
daniel
might
can
correct.
B
A
A
A
C
C
A
So
yeah,
that's
that's
about
the
release,
dates
and
we've
got
the
roadmap
board
about,
like
you
know,
what's
going
to
be
implemented
in
the
next,
like
you
know,
in
the
next
couple
of
months
at
least,
and
here
under
releases,
we
we
close
these,
like
you,
know,
intelligent
related
ones,
because
I
mean
I'll
I'll
get
to
that
entire
section.
But
we've
had
like
you
know
a
number
of
releases
intelligent
land
and
what
is
in
progress
is
testing
cross
planet
scale.
A
There
was
a
pr
from
nate
like
resulted
from
these
scale
tests
that
makes
like
you
know,
I
believe,
limit
the
reconciliation
rates.
Like
you
know,
reasonable
amount.
A
So
yeah
the
the
fruits
of
that,
like
you,
know,
work
will
it
was
that,
like
you
know
that
and
other
few
pr's,
and
now
we're
gonna
update
all
providers
with
this
new
functionality
from
first
time
around
time
and
the
ack
stuff
this
these
are
still
on
hold.
Since
we
are
focusing
on
other
generation
efforts
like
turret
right
now
and
remove
or
highlight
older
cross-conversion
documentation,
do
we
have
an
update
on
this
any
libel?
You
were
looking
into
this,
like
you
know,
by
removing
it
from
google
or
something.
C
Yeah,
so
basically,
we
have
a
a
couple
of
ways:
we're
addressing
this
right
now
number
one.
When
a
release
goes
out
of
support
which
muaffik
was
describing
at
the
beginning
of
the
meeting,
we
remove
its
documentation
from
the
website,
which
can
be
you
know,
kind
of
an
issue
if
you're
linking
to
something
with
a
specific
version.
C
C
But
it's
not
it's
not
perfect.
At
this
point,
I
guess,
but
it
should
be
a
lot
better
and
it
should
prevent
folks
from
looking
at
stale
documentation.
A
C
B
A
Thanks
for
the
update
yeah,
so
these
these
are
the
things
that
are
that
seem
to
be
in
progress
in
crosstown
land
right
now
and
in
design.
One
is
genetic
references,
design,
doc.
This
is
put
on
hold
because
of
like
you
know,
we
did
not
feel
a
great
about
its
security
implications
for
now,
and
there
is
an
immediate
need,
at
least
for
now,
for
this
mechanism
in
the
core
projects,
so
this
is
on
hold
and
there's
support
for
pluggable,
secret
stores
and
sound.
Do
you
have
some
of
this
regarding
this.
B
Yeah,
actually
it
was
a
long
running
design,
though
there
were
a
couple
of
points
that
that
we're
kind
of
discussing
and
couldn't
find
a
conclusion.
But
I
I
I
pushed
a
new
commit
yesterday
and
I
feel
like
we
are
very
close
to
get
it
merged,
and
hopefully
we
can
then
start
implementation.
A
Thank
you
for
those
who
are
interested.
You
can
see
the
pr
here
with
the
design
dog
yeah
and
the
next
is
support
patching
from
common
data
sources.
So
this
is
very
similar
to
general
references,
and
I
believe
I
have
a
couple
of
them
together,
yeah
so
they're
the
same
pair
with
tweaks,
both
of
them
and
so
like
you
know,
this
is
also
on
hold.
A
I
believe
this
is
a
little
bit
also
related
to
the
observe,
only
crosstalk
resources
issue,
because
the
observant
crossman
resources
are
requested
by
the
community
so
that
they
can
reference
from
those
resources
into
actual
running
and
reconciling
managed
resources.
For
example,
a
vpc
might
be
used
by,
like
you
know
many
composites
or
like
many
managed
resources
in
the
cluster
or
in
like
no
more
than
one
cluster.
A
Essentially
so,
like
you
know,
you
don't
want
many
controllers,
reconciling
the
same
thing
so
like
indeed,
all
of
these
three
are
kind
of
similar,
at
least
the
requirement
to
patch
or
requirement
fashion.
Information.
A
Arbitrary
force
is
a
requirement,
and
the
last
one
is
the
one
pager
for
pluggable
netbooks.
I
just
moved
it
to
under
indesign,
because
I
had
a
design
draft
pr
about
this-
that
I
didn't
open
publicly
yet,
and
I
just
took
out,
like
you
know,
pass
at
it
and
updated
it.
So
folks
are
very
welcome
to
take
a
look
and
review
it.
A
This
is
essentially
adding
support
for
crossplane,
so
that
providers
can,
like
you
know,
implement
functions
that
will
be
called
like
you
know,
for
well
as
validating
web
hook
or
mutating
web
book,
and
also
conversion
network
for
crd
migrations,
for
example.
We
have,
like
you
know
quite
a
few.
We
want
better
one
resources
in
different
providers,
so
in
order
to
bump
them
to
we
want
and
have
schema
changes.
We
will
need
this
mechanism
so
that,
like
you
know,
we
can
point
kubernetes
to
that.
A
Like
you
know,
hey
use
that
web
hook
for
doing
the
schema
conversion
and
other
good
things
like
you
know,
we've
been
putting
like
comment
marker
immutable,
but
there
is
no
technical
implication
of
that,
so
the
the
web
hooks
will
actually
enforce
this.
So
please
have
a
look
at
this
and
let
you
know
leave
your
thoughts
yeah.
I
think
these.
These
are
the
issues
that
we
want
to
mention
and
prioritization.
I
don't
think
right
now.
There
is
the
updates
about
prioritized
list,
and
is
this
a
different
one
yeah?
A
C
Yeah
this
one
is
not
super
impactful
to
end
users
per
se,
but
for
a
while
we've
been
using
kind
of
some
legacy
tooling,
you
might
say,
depending
on
your
outlook,
I
guess
to
build
and
push
our
images,
and
so
that's
why,
for
all
of
our
providers
and
all
of
our
repos,
essentially
any
image
we
were
publishing.
C
If
we
wanted
to
do
multi
architecture
builds,
we
had
to
push
them
to
different
different
repos
first
right
and
then
use
the
manifest
tool
to
be
able
to
combine
them
into
a
single
image.
You
know
that
works.
Fine,
the
consumption
model
is
pretty
much
the
same.
You
still
reference
a
multi-platform
image,
but
this
was
coming
especially
annoying
when
setting
up
new
providers,
especially
when
we
see
all
these
awesome
new
ones
being
provided
by
the
terrajet
stuff.
C
So
essentially,
now
what
we
do
is
we
utilize
buildex
to
be
able
to
push
a
single
multi-platform
image
at
once
and
also
as
a
side
effect
of
this,
we
have
a
little
more
flexibility
in
how
we
publish
images
which
should
help
with
providers
and
some
of
the
stuff
we're
doing
right
now,
where
we
build
multi-platform
images,
for
instance,
for
for
the
package,
which
doesn't
really
make
any
sense
right.
It
just
says
yaml
in
it,
so
it's
not
really
that
relevant
and
so
there's
a
couple
changes
there.
C
The
last
one
that
I'll
mention
is
that
we
will
now
also
be
publishing
everything
directly
to
the
upbound
registry
as
well
as
docker
hub
folks
are
likely
familiar
with
some
of
the
rate
limiting
that
docker
hub
imposed
on
on
its
repositories.
So
this
gives
us
a
little
more
redundancy
to
be
able
to
have
alternate
solutions,
so
this
has
been
implemented
in
crossplane
and
we'll
roll
it
out
across
the
rest
of
providers.
Here
shortly.
A
C
Yeah,
which
is
essentially
what
what
happens
normally
right.
It's
just
that
when
you
push
the
images
you're,
either
uploading
the
blobs
via
the
upload
of
your
image,
to
a
specific
architecture
repository
and
then
you're,
pointing
at
that
from
the
multi-platform
repository
you're.
Basically,
just
you
know
pointing
at
those
manifests
with
the
manifest
list.
Now
we
just
push
all
that
at
once.
So,
for
instance,
yeah
all
of
those
like
amd,
64
and
arm
64
ones,
for
instance,
will
no
longer
be
required.
A
C
Yeah,
I'm
also-
this
is
I'll-
just
mention
this,
because
it's
sort
of
relevant
right
now
we
pull
down
the
whole
image
in
the
package
manager
for
for
providers
and
configurations,
which
is
fine,
because
our
images
are
just
a
single
layer
right
now.
What
I
am
hoping
to
move
us
to
doing
is
being
able
to
make
fat
images.
If
you
will,
where
we
basically
say
the
controller
and
the
package
are
the
same
image
and
in
crossplane
will
only
pull
the
bottom
layer,
which
will
just
have
the
package
contents
in
it.
A
So
I
will
give
an
update
about
the
telugu
project
that
we
have
been
busy
with
for
the
last
couple
of
months.
So
all
aps
issues
are
resolved
and
we've
got
the
patch
releases
out,
including
I
believe
the
list
is
somewhere
the
release
notes
here.
So
there
are
three
juventus
versions
that
you
can
reliably
use
these
new
providers
because
of
the
number
of
crds
I
mean
it's
not
specific
to
zero.
A
Yet,
if
you
get
to
like
you
know,
install
more
than
500
crds
in
a
minute
you
the
you,
will
hook
the
api
server
and
it
just
stops
responding.
But
with
these
versions
the
problem
is
fixed,
then
you
can
install
version
providers
or
any
other
provider
that
exceed
a
thousand
crds
essentially
but
they're
not
yet
available
in
many
providers.
A
I
just
checked
before
the
meeting.
I
checked
gta,
release,
notes
and
they're
not
available
yet,
but
I
believe
like
in
the
next
couple
of
weeks
they
will
propagate
to
all
big
providers
and
you
can
try
them
with
kind
right
away,
yeah
and
intelligent
releases.
So
we
have
made
a
number
of
releases
in
the
last
two
weeks.
A
One
is
zero
point
two
point,
one
where
we
have
actually
the
release
number
four:
two:
zero:
two
zero
is
more
free
fall,
so
you
see,
like
you
know,
lots
of
prs
landed
and
you
know
we
still
stabilize
the
interfaces
and
added
the
hassan
actually
added
the
document.
Now
that
you
can
follow
and
generate
your
own
provider
and
which,
like
you
know,
a
lot
of
folks,
already
did
right.
We
have
the
provider
equinix
based
on
telejet
we're
going
to
have,
I
believe,
lina
lynette
provider
and
a
few
others
like
you
know
down
the
line.
A
So
yeah
go
ahead
and
check
out
this
like
document,
and
you
can
start
with
the
new
provider's
yet
template
similar
to
provider
template.
We
have
and,
like
you
know,
generate
your
own
first
provider
and
there
are
about
the
releases,
so
we've
had
we've
released
gcpaws
azure,
but
this
time
we've
had
two
different
versions
before,
like
you
know
the
releases
before
that,
for
example,
0.2.0
of
aws
included,
I
believe
70
or
something
crds.
A
A
So
you
can
try
telstra
generate
providers
by
using
these
main
versions,
and
you
can
try,
like
you
know,
if
the
visuals
that
you're
using
not
supported
there,
you
can
just
go
ahead
and
use
the
preview
one
and
see
like
you
know
how
it
all
works
and
you
can
go
ahead
in
the
release.
Notes
and
yeah
see
what
is
supported
here
in
doc.
Crdstab.
A
We
like
first
like
in
some
providers,
the
full
id
or
like
self
link
of
the
of
the
resource,
is
required
to
do
the
referencing,
and
so
that
is
something
we
added
to
all
of
this
to
all
schemas
of
the
resources
where
we
just
have,
like
you
know,
status
at
provider
id
that
has
a
value
of
tenant
form
id
that
we
use
in
the
code.
You're,
not
really.
A
It's
not
really
important
for
users,
but
it's
important
for
us
to,
like
you,
know,
write
the
reference
resolvers
yeah
and
I
just
touched
on
this.
I
believe
the
guide
is
merged.
Please
take
a
look
at
it
and
if
you
have
any
providers
in
mind,
go
ahead
and
test
this
guide
and
let
us
know
in
the
cross
plane
slack
yeah.
Another
update
is
about
the
provider
strategy
doc.
A
So
I
have
been
requesting
feedback
for
this
document
for
a
while.
Now
and
it's
been
merged,
let
me
just
find
it
yeah
there.
It
is
so
here
you
will
see
the
like
how
we
think
about
providers
going
forward.
Like
you
know
we
now
we
have,
you
know
jet
project
based
providers
and
the
native
providers,
so
you
can
take
a
look
at
this
document
long
one
and
see
like
you
know
how
we
think
about
them.
This
summary
of
tools
section
you
can
skip
them.
A
It
is
essentially,
like
you
know,
an
analysis
of
different
tools
that
we
may
end
up
using
and
just
like
you
know
making
the
case
for,
like
you
know,
hey
how
how
much
it
would
cost
to
switch
any
of
those
tools
from
terraform
based
on
so
like
you
know
you,
don't
you
don't
need
to
go
and,
like
you
know,
read
all
of
them,
but
the
fun
part
starts
with
options
like
you
know
how
we
can,
like
you
know,
manage
those
providers
and,
like
you
know,
there
are
three
main
options
and
right
now
we
have.
A
The
proposed
option
is
essentially
the
third
one
like
having
different
versions
based
on
different
tools.
If
you
want
to
and
then
like
no
bump
them
with
conversion
macbooks,
but
right
now
for
initial
releases,
we
went
for
the
option,
one
where
we
have
completely
separate
providers,
just
like
we
do
right
now,
so
for
for
for
a
number
of
releases
will
continue
and
for
the
long
term
will
continue
to
maintain
all
those
providers,
the
the
jet
providers.
A
Just
like
you
know,
native
ones,
and
by
long
term
I
mean
years
and
once
we
you
know,
have
the
strategy
of
merging
them
or
doing
anything.
We
will
have
automatic
migration
by
stuff
in
place.
B
A
D
The
only
update
I've
been
watching,
I'm
still
on
that
aws
code
generator
issue
which
just
to
bring
everybody
up
to
date.
I've
linked
the
two
issues
that
we're
watching,
because
we
have
not
kept
up
with
updates
in
code
generator.
The
fix
that
we
needed
for
the
naming
collisions
on
types
got
hit
by
a
couple
of
other
changes
and
we're
working
with
aws
in
order
to
address
those.
D
Essentially,
if
you
have
a
type
where
the
input
and
output
are
not
of
the
same
type,
it's
screwing
up
the
code
generation
and
getting
us
into
generating
provider
code
that
cannot
compile
and
cannot
pass
linting.
So
I've
opened
an
issue.
It's
part
of
their
current
sprint.
We're
really
hoping
they'll
have
it
fixed
by
the
end
of
this
week,
they've
been
active
on
it,
move
off.
Thank
you
for
jumping
in
and
helping
figure
out
the
field
package
configuration
with
jay,
but
that's
we're
pretty
much
just
blocked
on
that.
D
A
Cool-
and
I
also
saw
another
pr,
I
believe,
regarding
the
api
flag
and
this
one,
but
I
guess
this
is
only
for
documentation
right,
yeah
yeah.
We
don't
have
the
aps
difference.
We
just
generate
the
whole
resource
cool
yeah.
Thank
you.
Thank
you
for
working
on
that.
D
Yeah,
I'm
just
noting
I've
noticed
chris
and
thank
you
for
keeping
on
top
of
it.
If
you
watch
pull
920
we're
tagging
issues
that
are
any
other
pr's
that
are
blocked
by
this
on
this
pr,
just
to
say
that
it's
related
to
these
changes,
so
ec2
volume,
ec2
route
and
target
gateway.
A
Yeah
the
I
believe
we
will
go
into
azure
and
gcp
details
in
a
minute
and
yeah
lots
of
new
providers
yeah,
that's
actually
like.
We
were
kind
of
seeing
like
a
boom
of
providers
in
crosstalk
country.
In
the
last
couple
of
weeks
today
we
have,
I
have
bootstrap
the
influx
db
and
I
believe
folks,
over
in
liberty,
mutual.
They
are
riding
the
provider
kafka
and
there
is
also
a
provider
conflict
coming
in
by
folks
from
the
fds,
the
shipping
company
from
denmark.
A
So
yeah
there
are
lots
of
new
providers
in
crosstalk
humber.
Please
check
them
out
and
there
is
a
new
release
of
provider
sql.
I
believe
it's
got
some
new
features
sandy.
Would
you
mind
giving
an
update
there.
B
B
B
B
However,
when
we
didn't
configure
damage
still
is
enabled
we
had
an
update
loop
problem.
This
issue
was
debugged
and
you
know
resolved
by
sagan,
and
you
know
those
are
the
important
updates
from
azure
site
nice.
A
A
Like
the
update,
looks.
We
have
yeah
thanks
a
lot
guys
yeah
provided
gcp.
I
believe
sound
was
going
to
give
an
update,
but
it
is,
it
doesn't
seem
to
be
online,
so
I'll
I'll
just
go
ahead.
There
there
seems
to
be
a
new
map,
resource
router,
which
could
prove
useful
folks
with
who
are
doing
your
networking
stuff
in
individual
using
crossplay
and
yeah.
I'm
not
aware
of
new
release
of
pcp
well,
actually,
yeah.
There
is
one,
and
there
are
like
quite
a
few
changes.
I
believe.
A
A
By
victor,
I
believe,
yeah,
so
I
believe,
he's
doing
like
a
series
of
clusters,
so
he
can
well
we
characters
here.
Yeah.
B
Yeah
yeah,
it's
it's
one
of
the
steps
towards
some
materials
that
I
need
to
do
for
january,
which
is
going
to
be
composed
of
many
different
things,
and
one
of
them
is
composition.
So
I
kind
of
I
thought
to
make
a
short
video
about
it,
especially
now
that
in
december
things
are
cooling
off.
So
I
can.
I
can
spend
more
time
with
videos.
A
A
Maybe,
like
you
know
something
that
is
like
you
know,
the
biggest
composition
ever
existed
like
you
know,
maybe
hundreds
of
resources,
yeah
I'll,
do
that
and
see
like
you
know
and
watch
your
video
to
see
how
we
can
package
it,
because
that
packaging
stuff
is
always
a
little
bit.
Foreign
to
me
like
danielle,
is,
like
you
know,
very
interested
in
that
area,
and
he
like
did
most
of
the
parts.
So
it's
a
little
bit
yeah
I'll
need
to
watch
this
yeah,
especially
if.
B
You,
if
you're,
actually
making
a
composition
of
hundreds
of
resources,
you
might
actually
want
to
break
those
hundreds
into
smaller
groups,
package
them
and
then
use
it
to
us.
Assemble
those
hundreds
through
packages,
instead
of
all
of
them
directly
in
a
composition,
right,
yeah,.
A
Yeah
yeah
yeah
I'll
do
that
I'll.
Definitely
do
that.
No,
I
I
need
to
find
a
use
case
like
a
globally
distributed
wordpress
or
something.
A
A
Yeah,
for
what
is
worse,
we
had,
like
you,
know,
wordpress
as
the
as
the
main
demo
for,
like
you
know,
I
don't
know
more
like
for
years.
We
were
like
you
know.
We
were
checking
with
wordpress
like
hey.
Is
everything
working?
Let's
deploy
wordpress
using
the
old
kubernetes
applications
here,
which
is
like
you
know,
replaced
by
provider
kubernetes
right
now,
like
very
similar
to
that,
like
that
was
our
end-to-end
test
demos
and
everything
so
yeah,
all
right,
cool.
B
Yeah
yeah,
like
we
released
provider,
sql,
zero
0
and
the
domain
update
there
is
like
we
have
added
msd
cool
support.
So
far
we
had
postgresql
and
my
sequel
support,
but
with
this
pr
and
with
this
release
now
we
are
supporting
a
sql
server
or
I
think
it's
also
known
as
ms
sql
yeah,
so
it
could
be
used
like
combined
with
provider
azure
or
providers
at
azure
resources.
B
Yeah
regarding
provider
gcp-
I
I
just
did
a
release
a
couple
of
hours
ago,
and
this
release
contains
a
couple
of
fixed
tests.
Like
anybody.
Interest
can
check
the
release,
notes
for
the
details,
but
there
is
one
more
one:
more
managed
resource
edit,
which
is
crossband
routers,
which
is
something
added
by
community
members,
yeah
that
one
yeah.
Apart
from
that
there
are
some
other
fixes
and
minor
improvements.
I
would
say.
A
Yeah
and
we
have
a
new
maintainer
being
provided.
A
Been
a
while,
since
it's
been
maintainer,
but
it
just
shows
up
in
this
in
this
resource.
A
Thanks
so
yeah,
I
believe
we
we
run
out
of
usual
things
and
we've
got
like
you
know
after
this
point,
like
you
know,
we're
getting
into
optional
time
for
deeper
technical
discussions.