►
From YouTube: 2023-01-12 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
January
12
2023
cross-plane
community
meeting
thanks
everybody
for
turning
out
today
to
the
first
meeting
of
the
new
year,
so
we'll
jump
on
into
our
latest
Milestone
updates
and
then
continue
proceeding
through
the
agenda.
I
will
right
now
drop
a
link
to
the
agenda
documents
into
the
zoom
chat
so
that
you
everybody
can
hop
on
into
that
Dock
and
it's
completely
open
right
now
for
suggestions
so
feel
free.
A
If,
if
you
have
a
topic,
you
want
to
bring
up
to
go
ahead
and
add
it
to
our
community
topics
or
if
you
have
a
specific
PR,
you
can
add
it
there
as
well,
but
yeah
feel
free
to
add
things
that
you
want
to
talk
about
today
into
the
agenda
Doc
and
we'll
get
through
it
all
all
right,
so
biggest
biggest
topic
here
is
v1.11.
So
a
lot
of
really
good
things
have
been
included
into
the
release
already,
and
so
a
lot
of
progress
is
continuing
to
go
on
there.
A
I
did
want
to
talk
with
everybody
here
today
about
a
proposal,
though,
to
push
the
release
back
one
to
two
weeks.
So
the
reason
I'm
thinking
about
for
doing
that
is
that
composition
functions
is
by
far
like
the
you
know,
the
most
demanded
feature
or
one
of
the
most
strategic
ones
for
the
roadmap
here
that
we'll
be
delivering
in
b1.11
in
an
alpha
form
and
so
Nick
Nick
Pope
has
been
working
quite
hard
about
on
that
spent
a
little
time
over
the
holidays
as
well.
A
So
that's
in
a
pretty
good
shape
to
get
that
merged
in
I,
think
some
of
the
reviews
are
being
finalized
and
the
codes
getting
to
a
pretty
good
shape,
but
I
think
that
for
what
I
believe
to
be
a
very
important
feature
for
the
1.11
release,
I
think
it
is
important
enough
to
make
sure
that
it's
included
in
the
release
first
off,
but
then
also
that
we
get
a
little
bit
of
big
time
on
it
before
we
go
ahead
and
ship
well
1.11
out
the
door.
A
The
original
date
for
release
is
on
Tuesday,
so
January
17th,
but
I
would
like
to
push
that
back
at
least
one
week,
and
it
will
get
Nick's
opinion
on
this
year
in
a
second
but
potentially
two
weeks
to
J,
which
would
make
it
January
31st.
B
A
Somebody
disappointed
about
that.
One
I
heard
an
exacerbated
sigh,
but
yeah.
So
are
there
any
comments
that
folks
want
to
want
to
add
for
this
particular
proposal
here
to
give
composition
functions
a
bit
more
big
time.
C
I'll
say
something
sure
Jason
hey:
how
are
you
happy
New
Year
I'm
100,
for
pushing
it
to
whenever
whenever
it
makes
sense
for
composition
functions
there
I
think
it's
such
a
critical
feature
that
I
think
I
I
vote.
We
I
vote,
we
wait
for
it
and
make
it
make
it
make
it
be
part.
That's
just
my
take.
A
Awesome,
that's
that's
great
Jason,
thanks
for
weighing
in
on
that
Nick.
Do
you
want
to
share
a
quick
opinion
on
like
if
a
one
or
two
week
is
is
more
important
from
your
opinion
on
like
Runway
left
for
bake
time
and
stuff.
A
Cool
sounds
good
all
right,
so
yeah
I
think
that
the
so
something
I
think
that
is
that's
important
here
also,
is
that
the
pr
for
composition
functions
is
available
for
I'm
gonna
go
ahead
and
just
put
everybody
on
mute.
So
we
keep
the
conversation
going
here.
A
So
the
the
pr
for
composite
functions
is
available
for
folks
to
start
trying
it
out
as
well.
So
you
know,
as
part
of
that
bake
time
being
able
to
exercise
it.
Take
it
for
a
test
Spin
and
get
some
more
feedback
on
it,
as
well
from
the
community,
will
be
an
important
part
of
improving
the
quality
and
driving
some
driving
some
improvements
there.
A
So
you
know
we
will
make
some
bigger
announcements
here
about
the
release
date
so
that
in
the
typical,
the
typical
places
like
other
readme
and
the
community
calendar
Etc,
then
that
that
will
be
well
known
so
that
we
can
make
sure
that
the
rest
of
the
community
is
aware
of
when
the
release
will
be
coming
out.
A
So
all
right,
let's
go
ahead
and
take
a
look
at
the
release
board
as
well
and
get
a
couple
more
updates,
while
we're
at
it.
A
All
right,
so
we
talked
about
custom
compositions,
you
know,
composition,
functions,
Hassan,
you
walked
us
through
in
the
last
community
meeting,
observe
only
resources,
the
design
for
that
is
there
anything
you
want
to
add
in
terms
of
getting
that
design
finalized
in
one
dot,
11
time
frame.
E
Yeah,
basically
I
couldn't
you
know,
focus
on
this
for
a
while
and
want
to
give
this
some
time
like
consider
this
time
to
get
some
feedback
from
the
community.
But
now
I
I
can
have
some
availability
and
I
started.
Focusing
on
that,
so
I
will
try
my
best
to
get
it
get
to
design
merged
in
the
111
time
frame,
but
yeah.
Let's
see
I
I
can't
make
any
promises.
A
Yeah
and
I
think
Hassan
with
you
know
the
the
two
weeks
additional
time
for
1.11.
You
know
that
that
gives
a
little
bit
more
a
little
bit
more
buffer
as
well.
E
A
Any
any
big
feedback
coming
in
on
that
Hassan
that
you
know
that
that's
that's!
You
know
influencing
us
to
rethink
things
or,
like
anything
major
coming
in.
E
Not
really
currently
I,
don't
think
any
blocker
or
any
big.
You
know
command
that
would
affect
like
the
overall
direction
of
the
design.
There
are
some
for
me.
There
are
some
details
that
we
need
to
agree
and
also
I'm
planning
to
make
some
experiments
to
better
understand
some
concerns
coming
as
feedbacks
to
the
pr.
A
Oud
cool
sounds
good
son
thanks
for
sharing
that
and
Jesse
I
know
that
you
had
made
a
big
push
on
the
the
package.
Signature,
validation,
PR
and
I
know
that
you're
looking
for
a
little
bit
more
feedback
on
that
as
well.
Anything
you
want
to
add
along
along
with
that.
F
No
actually
Dan
just
reached
out
to
me,
and
he
had
he
said.
Oh
did
he
turned
on.
He
turns
on
I
guess
a
little
bit
of
time
and
so
I
appreciate
that
I
appreciate
everyone
else,
who's
who's
kind
of
like
been
helping
me
get
this
coalesced.
There
is
just
some
cleanup
to
do
to
make
it
easier
for
others
to
digest
and
then
I
hope
to
get
more
people's
eyes
on
it.
So
if
you
do
jump
in
there,
please
bear
with
me
I'm
still
trying
to
understand
how
best
to
contribute.
F
There's
there's
you
know
a
lot
of
of
boilerplate.
That's
not
really
necessary
to
review.
If
you
can,
if
you,
if
you,
if
you,
if
you
wanted
to
give
it,
lend
a
hand
and
you
need
help
cutting
through
what
you
know,
my
sprawl
of
boilerplate
looks
like
I'm
happy
to
kind
of
like
Focus
you,
where
I
actually
made
changes
that
are
material,
but
if
not,
then
just
wait
a
few
days,
and
hopefully
with
the
on
top
I'll,
get
it
cleaned
up.
A
Yeah
and
Dan
is
exactly
who,
who
I
was
most
interested
in
and
know,
would
have
the
greatest
context
to
help
out
with
a
good
review
there
so
and
I
think
you
had
asked
about
that
recently,
Jesse,
so
glad
I'm
glad
we
got
Dan
on
that
too.
So
that's
great
and
then
I
also
wanted
to
check
in
with
Pete
I
think,
maybe
for
a
latest
status
on
moving
the
docs
out
to
the
docs
repo
and
out
of
core
crossblade
Pete.
G
So
it
was
finished
day
before
yesterday
this
week,
so
the
docs
now
lived
in
the
repo
by
themselves.
Many
Doc's
contribution
should
go
straight
to
there,
thanks
to
Nick
for
the
hand
there.
A
Sweet
and
then
there
is
there
a
remaining
effort,
then
to
remove
the
docs
then
completely
from
core
cross
plain.
So
there's
not
kind
of
a
two
different
places
issue.
G
Yeah
I'll
speak
for
Nick,
because
I
know
he's
trying
to
stand
mute.
There's
a
PR
there
to
do
that.
An
issue
is
identified
with
generating
meta
something
Stan
I
can't.
D
Remember
offhand
yeah,
we
there's
a
few
different
things:
the
con,
the
getting
shirt
configuration
packages
and
the
the
crds
that
don't
actually
get
installed
right,
the
crosswind
eye,
ammo
types
we
were
just
generating
those
to
the
docs
directory
kind
of
because
they
needed
to
live
somewhere
but
Nick's,
taking
the
great
step
of
removing
the
doctor.
D
So
it's
not
confusing
so
we'll
just
shift
those
to
be
generated
into
like
the
cluster
directory
or
something
like
that,
and
as
long
as
we
update
the
paths
for
the
configuration,
workflows
and
stuff
like
that,
then
it
should
be
a
no-off
for
any
consumers.
A
And
then
that's
that's
in
a
draft
PR
now
right
if
I
recall,
if
I'm
saying
that
yesterday
yep
that's
correct
cool
great
perfect,
all
right,
we'll
talk
about
the
fuzz
testing
in
a
little
bit
more
here
and
I.
Think
we'll
talk
about
the
crd
scaling
stuff
and
a
little
bit
more
here
in
the
community
section
Dan.
Is
there
anything
that
you
wanted
to
add
on
I,
don't
know,
I
think
this
is
maybe
a
little
bit.
This
might
not
be
the
issue.
A
I
was
thinking
of
I
thought
there'd
been
some
updates
around.
Like
you
know,
package
manager,
concurrency
and
potential
load
that
that
might
be
causing,
but
this
one
doesn't
look
like
it's
been
updated
recently,
yeah.
D
There
was
I'm
also
trying
to
find
this
as
we
speak.
If
someone
grabs
it's
a
more
recent
one,
I
think
references
that
one
where
there's
some
really
great
investigation
by
some
Community
folks,
if
you
are
on
this,
call,
feel
free
to
jump
in.
D
But
what
I
think
is
happening
here
is
that
folks
are
updating
and
there
is
a
cycle
of
the
revision
updating
the
parent
package,
so
the
provider
revision,
updating
the
provider
configuration
or
Vision
configuration
and
it's
causing
basically
just
dueling
reconciliation
Loops,
which
is
leading
to
that
higher
CPU
usage.
D
There
was
a
great
walkthrough
of
how
they
addressed
this
basically
by
deleting
an
old
invalid
revision,
and
that
addressed
the
problem,
but
we
obviously
need
to
drill
down
into
you
exactly
what's
causing
sort
of
that
race
condition
there
and
I
I,
don't
have
a
full
write-up
yet,
but
I
did
look
into
this
a
little
bit
and
I'm,
hoping
to
with
that
a
little
more
breathing
room
for
the
release.
D
The
extra
two
weeks
I'm
hoping
to
make
sure
that
we
have
that
fixed
up
for
the
1.11
and
then
also
in
a
patch
for
v1.10
DOT.
Two
I
think
it
is.
A
D
Yeah
exactly
there
is
that's
not
to
say
that
the
package
manager
still
can't
you
know,
have
pretty
high
usage
when
it's
doing
the
installation,
but
the
specific
issue
here
is
we're
seeing
it
just
constantly
reconcile
which
absolutely
shouldn't
be
the
case.
In
fact,
in
most
cases
it
should
be
on
whatever
the
the
you
know
like
Global
sync
interval
is
for
resources.
D
Packages
really
shouldn't
be
reconciling
that
much,
because
we
anticipate
that
folks
aren't
modifying
them
directly,
so
it
this.
This
does
appear
to
be
a
bug,
rather
than
just
the
kind
of
concurrent
establishment
of
resources.
D
I
do
think
that
it
could
have
been
exacerbated
by
the
concurrent
establishment
of
resources,
which
is
why
it
may
have
been
more
noticeable
for
folks,
but
this
one
specifically
is
talking
about
like
the
amount
of
logs,
that's
generating
and
cloudwatch
and
stuff
like
that.
So
it's
definitely
due
to
reconciliation.
D
A
Okay,
cool
Dan,
thanks
for
confirming
that
I
went
ahead
and
then
added
this
issue
here
about
increasing
you
know,
that's
the
dueling
reconciliation
to
the
here.
It
is
right
there
to
the
releases.
The
roadmap
board
here
since
you're
gonna
be
spending
a
couple
times
in
in
progress
foreign,
so
yeah.
So
that's
everything
on
the
release
board.
Any
other
comments
about
V1.
Excuse
me:
V
1.11,
before
we
move
along
to
Providers
and
ecosystem.
B
A
Yes,
good
call
Yuri,
that's
at
the
top
here
of
the
done
column
and
also
a
high
profile
high
demand
feature
that
is
been
requested
by
a
lot
of
folks,
so
definitely
yeah.
It's
got
almost
30
thumbs
up
on
that
one,
so
yeah
a
great
effort
to
Max
to
get
that
in
in
1.11
and
then
Yuri.
Thanks
for
all
your
reviews
on
it
as
well,
man.
A
There
are
a
number
of
recent
releases
for
the
big
three
cloud
provider:
upon's
official
providers
there,
but
there's
links
directly
to
the
marketplace
to
check
those
out
Christopher
Harris
Christopher
on
the
call
today
by
the
way
I
would
have
I
probably
would
have
heard
him
if
he
was
here,
but
Christopher
did
a
release
for
the
Community
provider
AWS
as
well
over
the
holidays,
so
that
one's
pretty
fresh
and
new,
too
and
Hassan
I
think
you
did
a
couple
releases
as
well
for
provider
kubernetes
and
provider
Helm.
A
E
Not
really,
basically,
the
reason
was
it
was
two
months
from
the
last
release
and
if
I'm
not
mistaken,
there
was
a
bug
fix
in
the
provider
Helm
which
actually
I
think
about
some
clients
go
updates.
That
needs
to
be
included
in
a
release.
A
Cool
all
right,
so
those
are
the
recent
releases
for
providers
that
I
knew
of
at
least
off
the
top
of
my
head
and
that
were
in
the
announcements
Channel.
If
folks
want
to
call
out
now
other
releases
of
providers
that
they
want
to
make
known
to
the
community
and
or
add
them
into
this
list
on
the
agenda
doc.
Please
do
feel
free
welcome
to
do
so.
A
All
right,
so
that's
everything
for
ecosystem
releases.
Let's
move
ahead
now
to
the
next
section
for
some
vendor
updates
and
Sean.
Do
you
want
to
share
some
things
going
on
for
your
team,
your
interning
team.com.
H
Yeah
sure
thanks
I'll
skip
the
first
one,
the
sun's
already
kind
of
like
mentioned
the
observingly
resources
design.
H
You
know
we
we're
continuing
with
the
work
on
making
external
secret
Stores
pluggable,
don't
have
anything
yet
to
to
share
for
for
review,
but
hopefully
in
the
year
future,
we'll
be
able
to
do
that.
You
know.
Nick's
already
mentioned
status
on
composition,
functions
and
the
only
new
thing
that
we're
starting
to
have
a
look
at
is
the
issue
around
validating
compositions
via
webhook.
So
a
while
ago
we
did
a
little
bit
of
digging
into
some
of
the
developer
experience
challenges.
H
You
know,
errors
not
being
propagated
and
or
silent
errors
and
so
on,
and
it
all
really
comes
down
to
you
know
typos
or
misconfiguration
and
compositions,
and
so
we
thought
we.
We
want
to
have
a
look
at
this
and
and
think
it
would
be
valuable
to
to
really
kind
of
like
do
that
so
Philippe
who
he's
handless
Fisco.
They
is
a
new
team
member.
He
joined
us
last
week
in
my
team
and
he's
starting
to
have
a
look
at
that.
H
A
Awesome,
that's
exciting,
so
do
you
think
Jean?
Do
you
think
that
that's
something
that
we
should
then
add
to?
Is
it
already
in
the
the
releases
on
the
roadmap
or
we
could
go.
H
Ahead,
no
I
think
you
know
we
we're
still
just
at
the
point
of
exploring
what
the
options
are.
I
think,
once
once
we
settle
on
something
we
can
probably
Target
it
for
for
112.
H
A
Then
that
solution
might
be
yeah
and
that
that
could
indicate
that
a
good
home
for
it
right
now
on
the
roadmap
board
would
be
like
in
the
design
column
as
we're
thinking
through
it
type
of.
I
A
So
Ed
has
a
hard
stop
at
30
after
so,
let's
go
ahead
and
pull
this
up
here,
real
quick.
So
we
can
talk
about
this
issue
here
before
Ed
has
to
get
on
out
of
here
so
yeah
Ed
floor
shares.
J
Thanks
by
way
of
super
brief
introduction,
I'm
at
equinix
in
the
developer
relations
group,
I
know
that
we
put
together
a
provider
infrastructure
for
cross-plane
I
want
to
say
a
year
ago
for
some
of
it.
It
looks
like
two
years
ago
for
some
others
of
it.
J
There's
two
actually
two
different
ones
and
I
want
to
just
get
a
quick
read
from
the
community
on
how
much
the
underlying
infrastructure
might
have
changed
over
the
time
that
the
provider
has
not
been
updated
and
understand,
like
the
Delta
to
to
bring
something
up
to
date,
with
the
current
release,
there's
also
a
Delta
potentially
for
us
making
changes
to
accommodate
any
changes
to
our
apis,
which
I
don't
which
I
don't
expect
you
to
have
any
sense
for
estimating,
but
just
like.
J
If
you
have
a
provider
that
hasn't
been
touched
for
a
year,
how
should
you
start
over?
Should
you
consult
a
change?
Blog
that'll.
Tell
you
what
to
do
next,
or
should
you
just
turn
it
on
and
see
what
breaks
and
fix
the
things
to
break?
And
that's
my
my
quick
take
I.
Don't
know
that
there's
a
quick
answer
to
that,
but
I
might
just
get
some
sense
from
the
project
of
like
how
how
many
and
how
frequent
our
breaking
changes
that
have
come
up
in
the
intervening
relatively
large
amount
of
time.
A
Yeah
really
good
question
and
I'll
take
a
first
stab
at
it
and
then
maybe
folks
can
fill
in
some
details
or
make
some
corrections
as
needed.
So
what
I
would
anticipate
since
so
cross
plain
hit,
1.0
well
good,
a
good
while
ago,
I
think
that
was
like
December
of
maybe
2019
2020,
so
at
least
a
couple
years,
so
the
API,
the
core
API
for
Crossbay,
has
been
somewhat
stable
or
fairly
stable.
Right
we've
been
pretty
pretty
cognizant
as
well
of
of
you
know,
making
things
compatible
not
making.
A
You
know
big
breaking
API
changes,
so
there's
a
there's
a
chance
that
at
least
from
a
runtime
capacity
that
in
a
a
recent
cross-plane
cluster
installing
this,
this
older
provider
that
hasn't
been
touched
could
possibly
work.
There
may
be
something
broken
out
of
it,
but
like
from
a
general
project
standpoint,
since
we
hit
1.0,
we've
been
pretty
good
and
having
a
focus
on.
A
Think
that
a
one
thing
to
consider
is
that,
in
terms
of
velocity,
I
I,
don't
think
I
I
would
assume
that
this
project
this
this
this
provided
that
Marcus
was
writing,
was
done
done
by
hand
right
like
using
like
manually,
writing
the
controllers
and
and
doing
you
know
using
cross-speed
runtime,
so
there's
a
chance
that
it
may
be
nice
to
start
with
a
code
generated
provider
instead,
like
just
from
a
velocity
perspective
of
you
know,
wanting
to
you
know,
get
things
out
there
quickly
and
get
things
moving
quickly,
and
you
know
have
that
velocity
going
into
the
future
that
using
like
up
jet
to
to
generate
a
provider
may
be
a
nice
start
just
to
just
from
a
velocity
standpoint.
A
But
from
does
this
work
standpoint
I'm
more
on
the
side
of
I
hope
we
didn't
break
anything
or
there's
nothing
obvious
in
my
mind,
that
that
would
completely
have
broken
it
over
over
the
last
year
or
so.
Anybody
else
want
to
weigh
in
though,
and
tell
me
I'm
completely
wrong.
J
Hey
chief
I
can
just
add
a
a
little
bit
more
before
anyone
weighs
in.
We
have
also
been
working
towards
automatically
updated
API
code,
so
generated
out
of
the
generated
from
the
spec,
which
should
ease
any
problems
in
getting
things
started.
So
if
it,
if
it
doesn't
work
based
on
our
Baseline,
then
there's
probably
a
other.
H
F
J
A
Yeah,
that's
my
assumption.
Are
you
working
with
is
Marcus
still
involved.
G
A
Nice,
nice,
yeah
and
then
yeah
Marcus
has
a
lot
of
context
as
well
he's
a
great
guy
and
yeah,
and
we
love
Marcus
too
so
yeah.
Let
us
know
if
there's
anything
crazy,
that
comes
up
from
that
or
a
few
there's
other
questions
we
can
follow
up.
You.
J
A
You're,
making
more
progress
and
getting
more
real-time
data
into
yep.
J
And
if
and
if
this
Peaks
anyone's
interest
have
them
contact
me
and
we
can
identify
resources
that
would
that
would
help
for
this.
So.
J
A
Good
all
right
so
yeah,
so
some
in
the
content
section
here
definitely
some
interesting
things
to
talk
about
and
promote.
There
is
a
Linux.
The
Linux
Foundation
is.
F
A
F
That
real
quick
do
do.
We
have
metrics
on
providers
anywhere
like
like
that,
does
the
up
on
Marketplace,
even
if
it's
not
surfaced,
do
you
guys
collect
the
number
of
of
installs
or
polls.
D
Yeah
we,
we
definitely
do
have
some
metrics
and
you
know,
as
we've
kind
of
built
it
out
and
got
the
base
functionality
there
in
terms
of
documentation
and
that
sort
of
thing
we're
trying
to
move
on
to
like
hey
what
is
the
community
find
most
most
valuable
there
and
I
think
metrics
like
polls.
D
Although
everyone
knows
polls
are
or
someone
of
a
lossy
vector
to
judge
something
on,
but
things
like
polls
things
like
potentially
GitHub,
you
know
stats
and
that
sort
of
thing,
as
well
as
like
Star,
accounts
and
stuff
like
that,
are
all
things
that
we
think
are
going
to
be
useful
to
indicate
maturity
of
resources.
You
obviously
can
see
the
number
of
resource
types
or
crds
right
that
are
present
in
there,
but
that
is
definitely
some
of
the
top
of
mind.
D
A
Awesome
yep,
thanks
for
addressing
that
there
Dan
and
giving
sharing
that
information
all
right,
so
yeah
so
back
to
the
webinar
here
so
yeah.
The
Linux
Foundation
is
sponsoring
a
webinar
that
I'm
totally
blanking
on
who's
in
it
who's
presenting
in
it
besides,
Yuri
so
I'm
sure,
there's
other
folks,
and
it's
going
to
be
very,
very
interesting
material
there,
but
yeah
your
your
name
is
the
only
one
that
came
up
with
me
today
in
my
head,
because
we
talked
about
it
yesterday,
maybe
Victor
as
well.
A
Cool
awesome
Yep,
so
that's
January,
18th
I,
think
that's
a
week
from
yesterday
so
feel
free
to
click
that
link
and
register
for
that
webinar
with
the
Linux
Foundation.
If
you
are
interested
in
checking
out
that
stuff,
I
wrote
a
blog
post
that
just
got
published
at
the
beginning
of
the
year
here
for
the
new
stack
that
I
thought
was
a
pretty
interesting
topic,
because
it
kind
of
goes
into
a
number
of
things
that
folks
have
difficulties
with
when
they're,
first
starting
out
with
crossplaying.
A
You
know
demystify
a
couple
of
the
concepts
and
then
also
give
me
some
practical
advice
on
you
know
when
you
run
into
issues
early
on
with
cosplay
and
how
to
how
to
deal
with
them
so
check
out
that
article
in
the
in
the
new
stack
that
that
I
wrote,
edsky
got
her
blog
post
out
about
you,
know,
composition,
revisions
or
have
been
promoted
to
V1
beta
1
and
will
be
stable,
going
forward
as
well
super
useful
feature
and
it's
great
to
have
that
matured.
A
So
another
big
thing
in
b1.11,
so
you
know
another
reason
to
be
excited
about
that
release
and
Esky
has
a
great
blog
post
about
it
as
well,
and
then
a
Community
member
wrote
an
interesting
blog
post
too
about
you
know
their
opinions
on
on
how
cross
plain
is
basically
delivering
get
Ops
experience
for
infrastructure,
any
other
content
that
folks
want
to
add,
go
ahead
and
add
it
in
as
a
suggestion
so
that
if
we
get
some
more
eyeballs
on
it
there
so
I
want
to
give
a
fuzz
testing
update
here.
A
So
the
cncf
and
adalogics
have
been
helping
out
over
the
last
number
of
months
on
doing
fuzz
testing
for
cross-plane
and
so
we're
getting
to
a
point
where
we
want
to
wrap
this
up,
and
so
we
there's
a
few
things.
There's
going
to
be
a
report
that
gets
published
by
the
cncf
that
you
know
captures
all
the
testing
that
was
done.
A
The
issues
that
were
found-
you
know
security,
disclosures
Etc,
so
we'll
make
some
progress
on
that
soon
and
also
make
sure
that
the
fuzz
testing
is
running
on
a
continuous
basis,
along
with
new
additions
to
cross
plane
and
also
make
sure
that
all
the
bugs
that
were
found,
the
handful
of
bugs
that
were
found
from
best
Buzz
testing
get
fixed
as
well.
A
So
you
know
we'll
someone
from
the
team
will
be
following
up
on
this
in
the
near-ish
future,
but
this
is
an
important
part
of
our
security
posture
improvements
and
investment
for
the
graduation
of
the
project
with
cncf.
A
All
right,
I
also
wrote
an
update
here
for
everybody
on
crd
performance,
crd
scaling
stuff,
so
I
just
wanted
to
share
that
with
the
community
as
well,
so
that
there's
a
bit
more
visibility
on
it.
You
know,
but
essentially
over
the
last.
You
know
in
number
of
months
there
have
been
a
whole
bunch
of
in
Investments
and
fixes
into
Upstream
kubernetes
to
you
know,
make
it
more
able
to
handle
large
number
of
crds
being
installed
so
performance
improvements
there.
A
You
know
we
were
happy
to
hear
from
folks
if
you
know
you're
still
having
a
experience
of
degraded
performance.
Etc,
you
know,
hearing
the
specific
environment
details
and
you
know,
resources
available
Etc
will
be
very
useful,
but
so
I
wanted
to
kind
of
confirm
for
everybody
that
this
is
something
that
is
important
right.
We
don't
want
to
be
in
a
situation
where
folks
are
having
a
tough
time
consuming
cross-plane
or
even
getting
started
with
it.
Etc.
A
So
I
wanted
to
confirm
folks
that
this
is
something
that's
important
and
I
want
it
to
be
solved
in
a
complete
way.
So
there
will
be
some
updates
in
the
in
the
near
future
around
you
know
what
will
be
the
roadmap
approach
to
this,
to
you
know,
continue
solving
this
in
a
complete
and
holistic
way
and
a
general
approach
so
that
you
know
all
use.
Cases
are
well
covered
there.
So
that's
something
to
be
on
the
lookout,
for
you
know
confirmation
that
this
is
important.
It
should
be
prioritized.
B
A
Also
we're
going
to
do
a
shorter
term
investment
too,
with
the
documentation
and
guidance
that
people
will
be
driving
to
make
sure
that
you
know
folks,
starting
out,
can
have
you
know
a
good
sense
of
of
how
to
be
successful
with
crossplay
and
given
any
sort
of
potential
performance
constraints.
So
a
couple
things
that
will
you
know
be
be
addressing
in
the
near
future
and
longer
term,
and
you
know
thanks
for
everybody,
for
bringing
up
this
issue,
and
you
know
this
is
something
that's
important
to
us
as
well.
A
All
right,
anybody
that
has
any
questions
about
anything
as
we're
moving
along
feel
free
to
interject
at
any
time.
Dan.
Do
you
want
to
talk
about
this
particular
issue?
You
opened
it
here.
You've
got
some
good
context
about
it.
Do
you
want
to
go
ahead
and
take
this
one
bud
yeah.
D
Absolutely
I
think
it
plays
pretty
well
off
Jesse's
question
earlier
really.
You
know
we
made
a
move
a
few
months
ago
to
push
all
of
our
community
providers
to
the
X
package
registry
and
so
that
they'd
show
up
and
get
that
automatic
documentation.
Previously
you
know
we
had
the
the
crd's
dev
site,
which
gave
a
very
gross
view
of
documentation
and
kind
of
got
the
job
done,
but
it
definitely
limited
the
functionality
we
could
offer
there.
D
So
it's
been
a
great
experience,
I
think
to
move
those
over
we've
been
able
to.
You
know,
add
some
of
those
maturity,
metrics
and
things
like
that,
and
still
a
lot
more
to
do.
We've
also
seen
a
lot
of
reliability.
D
You
know
obviously
we're
in
the
the
folks
who
work
on
the
marketplace
are
also
in
cross-plane
slack
and
have
been
able
to
help
folks
whenever
they're
having
issues
and
typically
it
hasn't
had
you
know
any
issues
with
uptime
or
anything
like
that,
so
we're
really
confident
they
relying
ability
there.
We
want
to
bring
that
same
kind
of
set
of
features
to
cross
plane
itself.
So
speaking
to
the
issue
earlier,
that
Nick
was
tackling
of
moving
out
that
docs
directory
and
putting
the
the
crd
somewhere
else.
D
The
reason
why
we
generate
those
crds
is
not
because
it's
a
cross-plane
package
right.
It's
because
we
want
some
documentation
on
those.
We
also
put
the
Crossland
crds
in
the
cross,
plane
image
and
those
actually
get
installed
by
this
initialization
process
when
cross
plane
starts
up,
so
we
actually
already
have
the
the
crds
we
need
in
the
the
image
so
we're
able
to
do
similar.
D
Parsing
of
that
that
we
would,
for
a
provider
configuration
so
anyway,
we'd
like
to
standardize
on
this
as
a
the
single
place,
where
you
get
all
your
crossline
stuff
and
where
we
can
add
additional
features
for
cross
plane
and
and
if
anyone
has
any,
you
know,
thoughts
about
how
this
could
make
their
experience
consuming
crosswind
easier,
please
feel
free
to
drop
it
on
there.
There's
some
great
comments
already
about
you
know:
alternative
Registries,
that
other
cncf
projects,
use
and
I
think
there's
some
good
history
with
those.
D
A
Awesome
Dan
thanks
for
sharing
that
and
giving
some
of
that
background
context
as
well.
You
know
folks
want
to
make
some
comments
on
this
issue
here.
This
is
this
is
available
for
comments,
and
you
know
continue
to
discuss
along
there
as
well.
A
All
right,
so
that's
the
that
announcement.
There
Dan
looks
like
you
had
the
next
item
on
the
agenda
as
well.
D
Yeah,
so
this
is
something
came
up
recently,
I'm,
not
sure
if
Philippe
is
on
the
call,
but
there
were
some
CVS
reported
in
the
cross
plane
image
they
ultimately
shouldn't
have
too
much
of
an
impact,
but
we
obviously
want
to
get
those
fixed,
and
one
of
the
things
that
came
up
is
folks
might
be
familiar
with
a
couple
of
action
releases
ago
of
the
of
go.
D
There
was
an
issue
in
the
net
library
in
the
standard
Library,
and
so
there
was,
you
know,
a
strong
desire
to
get
up
to
our
new
Go
versions.
There.
The
way
that
we
currently
set
the
Go
version
for
our
builds
and
cross
plain,
is
using
a
really
handy
action
called
setup
and
go
which
basically
will
download
it
and
cache
in
that
sort
of
thing,
which
is
really
nice.
D
We
pinned
to
a
minor
version
there,
which
is
helpful
because
we
don't
have
to
go
through
the
toil
right
of
going
and
updating
for
every
new
patch
version
that
comes
out.
That
should
just
kind
of
automatically
happen.
There
is
some
information
here
about
how
often
that's
happening
and
how
caching
might
be
making
that
less
frequent
than
we
want,
but
the
main
thing
that
this
causes
issues
with
is,
if
you
actually
run
the
same
CI
pipeline
at
the
same,
commit
at
different
points
in
time
it
may
come
with
a
different
build
right.
D
You
may
be
using
a
different
Go
version
for
all
other
dependencies.
We
pin
that
version
whether
it's
like
a
base
image
or
you
know
a
tooling,
that's
from
the
the
build
subdirectory
or
something
like
that
which
gives
us
that
reproducibility.
But
here
we
don't
have
it,
and
so,
when
we
have
something
like
hey,
we
want
to
roll
forward
to
a
new
go
patch
version
and
make
sure
that
happens.
It's
just
kind
of
a
difficult
experience
to
make
that
you
know
codified
in
the
repository.
D
So
this
is
basically
just
proposing
pinning
to
an
actual
specific
patch
version
and
updating
those
patch
versions.
It
does
definitely
bring
with
the
caveat
right
that
that's
more
work
for
maintainers.
However,
there
are
some
nice
automation
that
we
can
do
there
to.
You
know
make
those
PR's
opened
automatically
so
that
we're
not
falling
off
there
and
relying
on
you
know
humans
to
do
these
things.
So
anyway,
it's
open
for
comment.
It's
not
something
that
is
the
most
pressing
thing
ever,
but
be
really
nice
to
get
folks
feedbacks
and
thoughts.
There.
A
Awesome
Dan
yeah
thanks
for
walking
us
through
that
one
as
well
too
yeah.
So
the
the
ask
here
then
is
to
is
the
comments
on
this
issue
and
have
some
discussion.
There
then
too
yep
that
would
be
great
cool,
sounds
good.
A
All
right
next
on
the
agenda
is
ignoring
changes
on
parameters
managed
outside
of
cross
plans.
Let
me
go
ahead
and
open
this
up
here
and
I'm,
not
sure
who
added
it
to
the
agenda,
but
if
you're
you're
still
here,
go
ahead
and
share
some
background
on
this,
for
us.
K
Hi
guys
that
was
me:
I'm
Lena
I'm
from
guide
work
on
delorean's
Old
team,
hi
DeLorean,
so
we've
been
looking
at
adopting
the
upbound
official
AWS
provider
and
we're
starting
with
a
dynamodb
table,
and
we
found
that
when
we
have
Auto
scaling
enabled
cross
plane
just
keeps
resetting
the
read
and
write
capacity
because
I
guess
it's
a
limitation
of
the
terraform
provider.
K
Read
and
write
capacity
are
the
at
initial
provisioning
and
also
the
capacity
as
it
auto
scales.
So
what
we're
looking
for
here-
and
somebody
else
actually
requested
this
about
a
month
ago-
is
something
similar
to
terraforms.
Ignore
changes
so
that
we
can,
if
Auto
scaling,
is
enabled
ignore
changes
on
read
and
write
capacity.
A
E
Like
yeah
yeah,
basically
directly
select
discussion
on
that,
and
it
was
mainly
brought
to
me
because
I
was
interested
in
observe
only
you
know
design,
and
this
sounds
like
to
be
related
at
first
look
because
you
want
to
you
know,
observe
those
resources
after
creation,
rather
than
managing
it.
But
later
you
know,
I
realized
that,
since
we
will
need
to
use
those
parameters
during
the
creation,
this
should
not.
This
should
be
handled
separately
from
the
observe,
only
design,
which
should
be
a
hundred
percent
read-only
by
Design.
E
So,
basically,
I
I
checked
like
how
terraform
is
handling
this
kind
of
situation,
and
there
is
a
life
cycle
book
names
and
more
changes
and
I.
Just
thought
that,
like
grosseling,
could
have
something
similar,
but
I
think
we
need
to
have
this
I.
G
E
A
Yeah
that
makes
sense
to
as
a
rallying
point
to
kind
of
come
together
on
what
the
implementation
should
be
so
Lena
you,
you
mentioned
that
you
were,
you
know
interested
in
in
driving.
It
is
that
something
that
that
you
know
you
and
your
team
would
want
to
you'd
want
to
be
interested
in
taking
on,
like
writing
a
proposal
for
how
this
should
work
or
what
level
it
should
be
implemented
at
in
Cross
plain.
Is
that
something
you
want
you're
excited
about,
or
how
do
you
feel
about
that.
K
With
some
guidance
we
would
be
happy
to
do
that.
We
haven't
actually
made
any
contributions
prior
to
this,
so
we'd
be
going
in
a
blind.
A
Got
it
got
it
I
think
in
general
Lena,
that's
something
that
you
know
as
as
a
community,
and
you
know
within
the
ecosystem
here
that
we're
supportive
of
of
you
know
providing
some
assistance,
and
you
know
you
know
guidance
around
making
progress
for
this
sort
of
stuff,
so
yeah
I
mean
if
this
is
it
looks
like
this
does.
Have
some
people
do
have
some
interest
in
it?
You
know
like,
maybe
maybe
they
could
do
it
like
in
two
phases
here?
A
One
is
that
you
know
if
other
maintainers
here
on
the
call
of
you
know
have
some
ideas
about
you
know.
If
this
is,
you
know
a
good
fit
or
if
there's
maybe
some
caveats
that
we
want
to.
You
know
watch
out
for
before
making
progress
on
this.
You
know
that's
something
good
to
call
out
sooner
than
later,
and
then
otherwise
you
know
if,
if
Lena
your
team,
isn't
you
and
your
team
is
interested
in?
You
know
writing
up
a
proposal
for
this.
A
A
I
think,
like
there's,
there's
a
design
Boulder
right
here
at
the
top
of
the
crosstalk
repo
okay.
A
Cool
yeah
and
then
so
yeah.
So
thanks
for
your
enthusiasm
on
that,
one
Lena
definitely
appreciate
that
and
then
yeah
another
call
to
folks
on
the
call
here
or
watching
the
recording
later.
If
you
know
there's
some
some
ideas
about,
you
know
how
to
go
about
this
or
some
course
Corrections
like
we
can
immediately
do
up
front
early
on
then
that
sounds
like
a
great
idea
too,
so
feel
free
to
add
some
comments
directly
into
this
issue
and
that
would
inform
any
work
that
would
be
going
on
sweet
all
right.
A
All
right
observe
only
resources
related
to
AWS
RAM
resources.
Anybody
want
to
address
this
one
here.
C
That's
just
a
quick
one
for
me,
sorry,
just
a
just
as
a
note
and
I
guess
as
we
go
forward
the
importance
of
of
observe
only
resources
relating
to
RAM,
which
is
resource
access
manager
from
AWS,
which
is
a
an
emerging
feature
in
Amazon,
where
resource
there's
about
20
25
resources
in
Amazon
that
can
be
shared
across
into
another
account
from
like
an
Enterprise.
C
A
a
very
obvious
example
of
that
is
vpcs
and
subnets,
where,
where
there's
a
there's,
a
parent
account
or
an
account
that
controls
the
network
and
and
then
the
network
is
actually
shared
into
the
the
application
teams
accounts.
If
you
will
or
whatever
I
think
you're
gonna
see
we're
going
to
see
a
lot
more
of
using
sharing,
where
it
creates
some
challenges
where
the
current
cross-plane
behaviors
are
it
doesn't
work
at
all?
C
You
can't
adopt
you
can't
you
can't
even
I,
don't
believe
you
can
even
use
the
workaround
in
this
case
to
try
to
use
those
resources,
or
at
least
be
aware
of
them-
to
actually
drop
things
in
vpcs
or
to
to
interact
with
those
other
resources
that
you
otherwise
don't
control
from
the
control
plane
yourself.
C
Maybe
this
is
more
of
a
design
question
for
Hassan
or
whoever
was
working
that
design
issue.
E
Yeah
yeah,
to
be
honest,
I
I,
cannot
say,
I
exactly
get
like
how
realm
you
know
like.
As
far
as
I
understand,
Germany's
RAM
will
be
a
dedicated
resource
like
I
want
to
share
this,
like
where
you
say,
I
want
to
share
this
VPC
with
this
account
kind
of
like
declarative
resource
that
you
create,
and
the
relation
with
observed
only
starts
when
the
you
know.
Other
accounts
wants
to
consume
that
VPC
without
managing
it.
Correct.
C
But
I'd
have
to
be
able
to
be
aware
of
it
before
I
could
do
that,
and
that's
where,
like
using
having
Ram
I'm
happy
to
take
this
offline
with
you,
as
as
that
design
goes
further
and
work
with
you
on
on
whatever
I
can
do
to
help
you
in
that
regard.
E
Yeah
yeah
we
can,
we
can
continue
the
discussion
offline
and
I
can
make
sure
that
it's
include
Tinder
design.
A
Awesome
Jason
thanks
for
bringing
that
up,
okay,
sweet
and
then
Diego.
You
had
reached
out
about
getting
an
update
on
this
particular
PR.
Here.
A
Yeah,
let's
see
yeah
so
I
think
that
yeah
after
the
holidays,
here
that
Nick
had
mentioned
that
this
is
something
that
we'll
try
to
take
a
look
at
today.
Here,
I,
don't
think
there
was
any
major
blocking
things
that
we're
we're
still
remaining
on
this
one,
so
kind
of
you
know
getting
back
for
the
holidays,
shaking
the
rest
off
and
and
getting
back
to
addressing
or
giving
driving
this
one
to
to
a
finalization.
A
Did
anyone
else
have
any?
You
know
big
concerns
to
bring
up
or
anything
beyond
that.
I
I
I
met
this
issue.
I
was
like
installing
cosplaying
on
open
shift.
There's
one
of
the
distribution
that
is
enforcing
this
policy.
I
think
it
may
be
the
only
one,
because
there
is
no
issue
with
the
most
common
Cloud
providers,
manager
distributions,
so
I
found
this
Innovation
and
I
was
trying
to
understand.
This
issue
can
be
handled
by
the
next
release
of
the
1.11
or
not.
A
Yeah
and
so
I
I,
that
seems
like
a
definite
possibility.
Yes,
Diego,
where
you
know
this,
this
com,
this
PR
I,
think,
has
gotten
a
couple
of
you
know
early
rounds
of
feedback,
and
it
looks
like
there's
not
any
known
big
blockers
on
it
so
yeah.
Hopefully,
this
is
something
that
we
can.
You
know
get
in.
You
know
either
the
rest
of
this
week
or
the
next
week,
and
then
that
would
be
included
in
the
Vita
1.11.
A
great.
Thank
you
so
much
yeah
thanks
for
bringing
it
up,
Diego,
definitely
appreciate
it
man
and
then
yeah,
and
if
this
may
not
be
explicitly
blocked
on
Nick.
So
if
you
know
other
maintainers
want
to
take
a
look
at
this
or
other
reviewers,
you
know
if,
like
Yuri
or
her
son,
or
somebody
wants
to
also
take
a
look
at
this
to
maybe
expedite
it,
potentially
with
other
things
on
Nick's
plate.
That
would
always
be
appreciated
as
well.
A
All
right
and
Jesse-
you
mentioned
this
PR
earlier
on
when
we're
talking
about
the
1.11.
A
You
cool,
alrighty,
so
I
think
that's
everything
that
made
it
to
the
agenda
doc.
Did
anybody
have
anything
they
wanted
to
bring
up
and
discuss
that
wasn't
included
in
the
agenda.
A
All
right
well,
I
know
a
couple
folks
in
the
chat
were
saying:
hi
as
well,
so
hey
Sean,
good
to
see
you
and
Carlos
as
well
good
to
see
you
at
the
at
the
community
meetings.
This
time
definitely
good
to
have
more
folks
that
we
know
joining
in
here
too,
and
if
there's
nothing
else,
then
we
could
go
ahead
and
adjourn
for
this
week
and
we'll
keep
on
with
heads
down
on
it's
getting
done.
A
The
1.11
release,
I'll
update
all
of
the
you
know,
public
locations
that
specify
the
release
date.
So
we'll
get
a
couple
more
weeks
there
and
we'll
keep
on
pushing.