►
From YouTube: 2021-08-26 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
august
26
2021
prospecting
community
meeting-
feel
free
to
add
yourself
to
the
agenda
the
attendees
list
there,
if
you
feel
so
inclined,
otherwise
you
know
we
can
add
you
on
later
on,
as
it
were,
so,
let's
dive
on
into
milestones,
releases
and
all
that
sort
of
stuff.
A
So
the
first
thing
to
pay
attention
to
is
that
earlier
this
week
we
did
a
series
of
patch
releases
for
1.3,
1.2
and
1.1
all
the
currently
supported
releases
of
crossplane.
So
in
the
the
release,
the
release
notes
are
all
included
right
here.
I
think
hassan
and
now
pair
you
all
were
running
that
release.
A
You
just
want
to
give
us
a
quick
update
about
like
the
important
issues
you
don't
have
to
go
through
every
issue,
but
like
the
important
stuff
that
was
included
in
those
patch
releases.
B
Yeah
sure
I
think
one
of
them
was
run
by
aaron
like
there
are
two
releases
and
all
like
run
by
all
three
of
us.
Everyone
had
right.
One
of
them
so
actually
like
the
updates,
are
the
fixes
and
merged
pr's
in
master
which,
which
makes
sense
to
include
into
the
patch
releases.
B
So
I
I
cannot
like
immediately
comment
on
each
and
every
ticket
right
now
here.
If
others
could
comment
on
that.
That
would
be
appreciated,
because
I
just
like
followed
the
difference
and
marked
the
the
new
new
prs
included
in
the
new
branch.
C
I
can
comment
on
2509.
That
was
an
issue
that
a
few
folks
brought
up
related
to
how
often
we
update
in
the
package
manager.
So
when
you
install
either
a
configuration
or
a
provider,
it
brings
either
in
the
configuration's
case,
xrds
and
compositions
and
in
the
provider's
case
crds
for
the
pretty
much
the
existence
of
the
package
manager.
C
We
have
every
minute
ensure
that
all
of
those
resources
are
matching
and
up
to
date.
The
issue
with
that
is
the
kubernetes
api
server
or
specifically,
the
api
extensions
controllers.
Kubernetes
are
late,
initializing,
some
fields
on
a
crd
potentially
and
the
composition
controllers
in
crossplane
are
also
making
some
modifications
to
the
xrds
and
compositions.
So
we
have
basically
superfluous
updates
on
those
happening
all
the
time
and
so
like
it's
not
just
a
no
operate.
We're
actually
issuing
an
update,
but
it's
kind
of
ineffectual.
C
It's
not
interrupting
any
usage,
but
it
just
issues
a
ton
of
updates,
and
you
can
imagine
you
know,
as
we
have
providers
with
like
almost
get
closing
in
on,
like
a
thousand
crds
for
a
large
cloud
provider.
That's
a
lot
of
updates
we're
issuing
all
the
time.
So,
instead,
what
we
do
now
is
we
don't
re-queue
on
a
successful
reconcile
and
we
basically
say:
we've
installed.
C
These
we've
made
sure
that
you
know
they
they
are
created
correctly
and
if
something
else
takes
control
and
blade
initializes
them,
it's
now
their
responsibility,
and
instead
we
only
re-cue
in
a
provider
case
on.
If
the
deployment
that's
running,
the
controllers
gets
in
an
unhealthy
state
or
changes
there
any
way,
a
controller
config
that
configures
that
deployment
is
changed,
so
it
basically
reduces
the
total
number
of
updates.
That's
not
to
say
that
we'll
never
update
right
now.
C
A
Yeah
awesome
dandy.
I
think
that
yeah
that
sounds
like
that
was
one
of
the
important
issues
that
went
on
in
that
release,
so
1.3
in
1.2
and
1.1.
So
thank
you
for
commenting
on
that
one
there
and
thanks
to
hassan
to
hassan
alpera
and
aaron
for
the
running
those
three
patch
releases
as
well
to
get
all
of
those
out.
I
think
that
was
that's
cool
to
get
more
folks
involved
in
that
and
kind
of
load
balance
the
the
effort
there.
A
You
know
we
have
the
1.4
release
coming
up
as
well
too
next
week,
so
there's
more
efforts
too
or
more
opportunities
to
get
involved
with
getting
the
releases
out
so
yeah.
Let's,
let's,
let's
move
ahead
to
that
so
yeah
1.4
is
the
release.
Date
is
still
expected
to
be
august
31st.
A
I
have
not
seen
any
particular
reasons
or
any
big
blockers
or
anything.
That's
come
up.
That
would
delay
that.
So
I
think
we're
still
on
track
for
august
31st
getting
the
release
out
there.
We've
got
the
tracking
issue
that
serves
as
the
checklist
here
for
getting
like
the
whole
release
process
and
getting
everything
out
and
updated.
So
that's!
That's
all
ready
to
go
for
next
week.
A
I
think
so,
let's
talk
about
what's
in
1.4
and
then
also
roadmap
going
forward
as
well
too,
because
we
have
some
some
changes
that
we
want
for
to
start
putting
there
to
have
a
better
story
for
our
roadmap
down
down
the
pipeline
here
and
getting
community
involvement
in
there
as
well
too.
So,
let's
first
talk
about
1.4,
because
that's
the
next
release.
That's
practical,
pragmatic!
Let's
talk
about
that
real,
quick!
A
So
on
the
1.4
board
here,
you'll
see
a
lot
of
things
in
the
done
column
there
and
it
looks
like
maybe
you
went
through
and
passed,
took
a
pass
to
cleaning
up
this
board
significantly
so
that
it's
very
clear
about
what's
in
the
release
and
what's
not
so
thank
you
very
much
for
doing
that.
I
think
one
of
the
biggest
the
biggest
efforts
here.
The
biggest
feature
is
composition.
Revisions.
A
So
nick
did
a
lot
of
great
effort
recently
to
to
add
support,
for
you
know,
being
able
to
safely
update
and
roll
back
your
the
versions
of
your
compositions
and
that
is
included
in
the
1.4
release.
There's
a
guide
written
about
how
to
use
it,
some
practical
tips
and
some
of
the
underlying
underlying
mechanics
there
as
well
too
nick.
Is
there
anything
specific
you
want
to
add
to
composition,
revisions
or
we've
talked
about
it.
There's
a
live
stream
to
it
as
well,
too.
Folks,
we'll
learn
more.
D
Yeah,
I
feel,
like
we've
already
talked
about
this,
maybe
at
the
last
community
meeting.
Yes,
it
said
there
was
a
live
stream.
So
if
folks
are
interested,
I
recommend
searching
I'm
guessing.
If
you
search
youtube
for
like
crossplay
and
composition
revisions,
you
will
find
that
live
stream.
That
discusses
it
in
detail.
There's.
A
A
Okay,
cool
so
yeah
any
other
notes,
like
that's
the
big,
the
big
feature
for
1.4.
Basically,
I
think
any
anybody
else
wants
to
add
some
some
some
highlights
here
for
other
things
that
will
be
included
in
the
1.4
release
next
week.
Besides,
what's
on,
you
know,
what's
included
in
the
done
column,.
D
Hopefully,
hopefully,
everything
that
is
included
should
be
the
done
column.
If
everyone
knows
of
anything
that
that
is
gonna
ship
in
this
release,
just
for
accounting
purposes,
it
would
be
awesome
to
drop
links
to
stuff
in
the
in
the
done
cold.
I'm
sure
there
is
some
interesting
stuff
in
there,
but
I
I
forget
exactly
what
it
is.
I
know
our
pair's
got
some
work
in
there
to
support
merging
instead
of
replacing
objects
and
arrays
when
you're
patching,
which
is
super
handy.
C
Nick,
I
also
saw
the
issue
around.
I
don't
see
it
on
the
border.
Oh
there
it
is,
and
to
do
the
promote
lock
to
v1
beta
1..
I
think
we
were
aligned
on
promoting
that
I'd,
be
fine
to
go
ahead
and
move
that
up
a
version
if
folks
are
feel
okay
with
that.
D
C
D
C
D
Same
with
that
good
ignore
thing,
I
wasn't
personally
planning
on
doing
that
myself,
but
I
do
feel
that
it
would
be
a
safe
thing
to
do
in
this
release
or
basically,
at
any
time,
that's
kind
of
to
be
fair,
something
I
might
should
have
probably
removed
from
this
release,
because
it's
not
really
a
feature
that
will
ship
with
1.4
or
anything.
It's
just
the
thing
that
we
want
to
do.
A
D
Yeah
but
I,
but
I
did
leave
it
there,
because
I
was
figuring
that
we'd
do
it
this
week
or
next
yeah.
A
Taylor
was
interested
in
specifically
on
helping
out
with
that
as
well
too.
If
we
want
to
ask
him
to
do
that,
one
okay,
cool
yeah,
so
1.4
is
going
out
next
week,
definitely
excited
to
get
another
release
out
there.
You
may
notice
as
well
too,
that
we're
kind
of
cleaning
up
the
the
boards
and
taking
a
bit
of
a
different
approach
to
how
do
we
specify
or
describe
the
roadmap
features
as
well
too.
A
So
I
wanted
to
touch
on
this
real
quick
that
nick
wrote
up
a
proposal
for
how
to
do
a
better
job
of
addressing
our
our
roadmap
and
giving
visibility
into
what's
going
on
down
the
road
here
for
the
crossband
project,
and
then
nick
took
some
steps
to
to
go
ahead
and
create
the
board
here.
Nick
do
you
want
to
kind
of
since
you
wrote
up
this,
you
know
very
well
wrote
up
this
proposal
here
and
put
together
this.
D
Yeah,
it's
it's
intended
to
address
two
things.
One
is
just
that
folks
have
asked
us
for
a
roadmap
for
what
the
cross
playing
community
is
doing
with
cosplaying.
What
is
what
features
are
planned
in
future?
D
I
one
thing:
that's
a
little
unconventional
potentially
about
this
road
map
compared
to
others
is
there
are
no,
as
you
can
see,
looking
at
it,
there
are
no
dates
on
it,
so
we're
not
we're
not
really
promising
particular
timelines
as
to
when
things
will
be
when
features
will
be
released.
But
the
idea
here
is
the
prioritized
column
is
a
roughly
so
far.
It's
actually
just
me
who
prioritized
it
yesterday,
so
take
it
as
possible.
D
We
still
need
to
get
feedback
from
other
folks
to
make
sure
these
priorities
are
sort
of
what
the
whole
community
agrees
on,
but
roughly
prioritized
features
or
bug
fixes
or
large-ish
things
that
we
want
to
work
on
at
cross
plate
this.
This
is
a
first
pass,
so
so
one
thing
I'm
not
super
sure.
D
What
we
want
to
do
here
about
is
I'm
sure
there
are
other
things
that
can
be
added
here,
but
there's
a
question
of:
why
do
we
want
every
bug
and
every
little
issue
and
what
not
to
be
in
this
prioritized
call
of
like
mixed
in
with
big
initiatives
and
whatnot
like
how
do
we?
How
do
we
balance
balance?
Those
things
I
don't
want
to
get
it
too
sort
of
bloated,
then
the
other
two
columns
are
intended
to
track.
We
have.
D
We
have
some
initiatives
that
just
don't
really
make
sense,
so
you
could
you
can
kind
of
think
about
this
roadmap
board
as
basically
stuff
that
was
already
on
our
release
boards,
but
that
probably
shouldn't
have
been
so
previously.
All
of
these
were,
in
the
prioritized
column
was
roughly
the
proposed
column
for
the
releases,
and
what
we
found
we
were
doing
is
we're
just
taking
all
the
stuff
that
was
proposed
for
one
release
and
then,
if
we
didn't
do
it
in
that
release,
we
just
drag
it
to
the
next
release.
D
D
Similarly,
the
indesign
and
in
progress
are
intended
to
be
work
that
you
know
we
are
working
on,
maybe
during
the
1.4
time
frame,
but
there
is
no
commitment,
for
example,
that
generic
resource
references
would
land
in
1.4
and
I
think
going
forward.
It
would
actually
be
a
good
practice
to
keep
things
out
of
a
release
milestone
while
they're
in
design
that
way.
We
can
take
the
time
we
need
to
design
them.
When
we
finish
designing
them,
we've
got
agreement,
then
we
could
say
okay.
D
We
now
have
an
idea
of
like
how
big
this
is,
how
much
work
this
is.
Do
we
want
to
commit
to
putting
one
point
four
or
one
five
or
like
then
move
it
into
a
release,
and
then
so?
Finally,
the
in
progress
column
is
a
bit
of
an
interesting
one.
I
was
thinking
that
we
would
use
this
for
work
in
progress
that
is
not
scoped
to
a
particular
release.
So
some
great
examples
of
this
are
we
want
to
track
that
you
know
move
off.
D
Any
provider
aws
release
that
we're
like
working
to
improve
our
documentation,
for
example,
specifically
how
google
index
that's
not
associated
with
any
cross-plane
release,
and
a
really
big
one
is
that
most
people
upbound,
who
work
full-time
on
crossplane
at
the
moment,
are
really
heads
down
working
on
terraform-based
provider,
co-generation.
D
So
an
ability
to
just
automatically
generate
new
providers
to
really
increase
the
provider
coverage.
That
crossplan
has
that's
actually
something.
We've
been
working
on
most
of
this
quarter.
There
has
been
a
great
way
to
track
that
previously,
because
it's
not
a
particular
cross
plane.
It's
not
part
of
any
one
provider.
There
wasn't
a
place
to
put
that
initiative,
so
the
general
idea
is
anything
that
doesn't
fit
in
the
release
goes
on
this
board.
D
A
A
For
me
here
is
that
you
know
what
you
said.
Nick
of
you
know,
did
you
look
at
the
way
we
were
doing
our
releases
we'd
have
like
1.3
and
it
would
have
a
huge
column
of
a
bunch
of
stuff
that
wasn't
really
necessarily
going
to
get
included
in
the
release,
so
it
was
kind
of
misleading
and
it
was
implicit
that
it
was
a
backlog
of
prioritized
backlog,
but
it
was
very
confusing
about
that.
So
I
really
like
having
this
prioritized
list
that
spans
multiple
releases.
It's
not
necessarily
a
commitment
of
win.
A
You
know
particularly
something
that's
going
to
land,
but
it
is
giving
visibility
and
insight
into
the
ordering
and
what
we
believe
is
the
priority
of
issues,
and
you
know
this
is
definitely
an
opportunity
for
folks
in
the
community
to
weigh
in
and
provide
you
know
their
vote
and
support
for
particular
issues
as
well
too.
You
know
that
can
always
be
done
by
adding
a
comment
or
adding
a
thumbs
up
reaction
to
the
issue
as
well
too,
and
then
we
can
kind
of
keep
this.
You
know
prioritized
list
here.
A
You
know
in
priority
order
for
what
the
community's
needs
are.
So
I
think
this
is
a
good
place
to
start
doing
this
across
milestones
and
it's
a
longer
term
roadmap.
Now.
D
So
the
proposal
issue
I
think
jared-
has
linked
in
the
issue:
25
26.
It
is
closed
now,
but
that
would
be
a
great
place
to
provide
feedback
on
this.
Unless
you
want
to
just
tell
me
now
or
reach
out
on
slack
or
something
you
know
we
did,
we
did
consider
having
a
a
board
with
time
estimates
on
them.
We
like
how
we're
internally
not
bound.
D
We
actually
use
a
process
similar
to
what
github
does
where
they
just
have
a
github
project
broken
down
by
like
month
or
quarter,
and
they
just
drag
things.
It
will
columns
being
months
or
quarters
and
they
just
drag
things
around
that
to
reflect
when
they
could
land
the
tricky
thing
with
crossplane.
Is
you
know
it
is
a
community
driven
open
source
project?
We
don't
really
expect
our
maintainers
to
you
know
commit
to
deliver
a
feature
at
a
particular
time
around
their
other
expectation.
D
You
know
other
responsibilities,
so
I
also
don't
feel
like
I've
seen
too
many
open
source
projects
sort
of
really
commit
to
a
roadmap
but
like
on
this
month
of
this
year,
you
will
get
this
feature.
I
could
be
wrong,
but
so
feedback
definitely
wanted
on
this.
A
Yeah
thanks
for
driving
this
here
nick
or
putting
something
into
place,
that's
definitely
helpful
and
useful
for
the
community
to
get
visibility
into
where
the
project
is
going.
A
So
I
think
this
is
really
nice
and
then
I
think
a
final
step
matthias
was
asking
about
it
earlier
today,
and
you
know,
port
request
is,
is
welcome
for
that
too,
of
what
we
do
with
the
roadmap.nd
file
at
the
root
of
the
crossplay
repo
and
my
proposal
or
suggestion
for
that
would
be
to
like
keep
that
file,
because
it
is
the
natural
place
that
a
lot
of
people
go
to
to
look
at
roadmap.
A
It
is
kind
of
a
standardized
file,
but
basically
just
link
to
there
from
the
roadmap
file
to
our
new
roadmap
project,
which
gives
the
visibility
there
and
then
you
know
maybe
like
sentence
or
two
in
rub.roadmap.md
about
our
philosophy
there
and
then
you
know,
I
think,
that's
a
good
approach
to
get
more
eyes
towards
it
as
a
kind
of
a
launching
point
to
get
to
the
to
the
roadmap.
Here.
A
D
You
you
can,
would
we
feel?
Okay,
if
we
just
like
you,
can
just
link
to
the
projects
board
on
github
which
just
links
to
all
of
them.
That
way,
we
just
don't
have
to
update
it.
Every
release
remember
to
go
point
it
at
a
new
url.
We
can
just
be
like
you
know,
supposed
to
figure
out
what
the
biggest
number
is
on
that
list
of
boards,
but
I
can,
I
can
at
least
I'll
I'll
add
a
pr.
Now
we
can
have
a
little
blurb.
D
That's
like
you
know,
there's
the
road
map
board
and
then
there's
release
boards,
and
we
can
say
like
what
the
difference
is
and
which
ones.
A
That
all
make
sense
yeah.
I
think
this
is
great
great
stuff
here,
cool,
so
yeah.
So
then
there's
plenty
of
opportunities,
then,
for
folks
to
weigh
in
and
add
their
support
for
issues
and
what
they
need
to
see
out
of
the
project.
That's
the
kind
of
a
consistent
theme.
Let's
continue
supporting,
that
of
you
know
giving
a
voice
to
everybody
to
support
what
they
what
they
want
to
see
in
the
project.
D
D
Live
edit,
there
is
a
there's,
a
request:
25
25
from
a
user
named
zodie
baldwin,
whose
name
is
ben.
It's
it's
quite
simple,
and
he
mentioned
that
if
we
would
consider
making
a
exception
for
it
to
go
into
1.4,
he
would
appreciate
that,
but
he
is
not.
You
know
he
understands
that
we
don't
necessarily
want
to
do
that.
I
could
go
with
layout.
I
think
we
really
made
an
exception
to
our
feature
freeze
before,
but
it
is
kind
of
a
like.
D
Apart
from
a
bunch
of
it's
a
it's,
a
relatively
small
change
apart
from
boilerpoint
plate,
I
would
like
to
get
dan's
review
on
it
because
it
is
part
of
the
package
manager
code
that
he
understands
really
well,
but
just
a
just
something
I
wanted
to
call
out.
We
don't
need
to
make
a
decision
on
now.
I'm
totally
happy
to
punt
it
to
1.5
just
wanted
to
represent
for
men
who
asked
nicely
if
we
could
make
an
exception.
C
Yeah
I
took
a-
I
won't,
spend
too
much
time
with
this,
but
I
took
a
quick
look
through
it.
It
looks
pretty
good,
I'm
I'm
pretty
staunchly
in
the
camp
of
that.
We
should
not
include
this
it.
It
is
not
that
big
of
a
change,
but
it's
a
way
to
modify
the
the
root
certs
right,
which
is
like
you
know,
kind
of
a
scary
thing.
C
Potentially
I
mean
I
believe,
it's
being
done
correctly
here,
the
transport
is
being
set
up,
but
I
do
think
it
is
kind
of
a
a
sensitive
thing
to
include
in
a
release
during
code.
Freeze,
the
other
thing
I'll
mention
that's
kind
of
informing
this
decision.
C
If
you
can
achieve
this,
functionality
has
been
already
noted
by
just
mounting
your
own
bundle
of
certs
you'd
have
to
construct
it
right
from
your
existing
ones,
plus
the
other
one
you
wanted
to
support,
but
you
can
mount
that
on
the
pod
already
and
achieve
this
functionality,
albeit
in
a
bit
of
a
more
hacky
way,
so
yeah.
D
Okay,
no
worries:
will
you
just
drop
a
comment
on
and
let
him
know
that
probably
gonna
take
a
bit
more
time
on
this
or
you
know
the
things
that
you
just
said.
C
One
one
follow-up
point
on
that
is:
we
should
go
ahead
and
cut
the
branch
because,
theoretically,
during
code
freeze,
we
should
have
the
v
1.4
branch
already
existing
or
the
release
1.41,
so
that
if
this
one
we
reviewed
it
and
merged
it
right
that
could
go
ahead
and
take
place.
Basically
we're
not
holding
prs,
because
we're
in
code
freeze
for
another
release,
yeah.
D
We
actually
don't
have
a
volunteer
yet
to
run
the
release
we
have.
The
team
are
not
bound
that
works
primarily
on
cosplay
as
their
sprint
planning
meeting
after
this
meeting
today,
I'm
gonna
ask
I'm
not
going
out
of
that
meeting
unless
someone
from
purple
squad
volunteers
to
do
this
release
and
then
that
will
be
their
responsibility.
A
D
Yeah
just
for
context
there,
the
only
reason
we're
doing
that
in
a
private
outbound
forum
is
just
in
practice.
All
of
the
current
maintainers
of
cosplaying
are
in
that
team.
So
I
would
answer
the
quality
of
the
quarry
yeah
yeah,
but
of
course,.
A
Okay,
cool:
let's:
let's:
let's
try
to
pick
up
the
pace
now
we're
about
halfway
through
and
I
think
a
lot
of
things
were
added
here.
They
might
not
be
deep
content,
but
let's,
let's
keep
moving
on
here.
So
we've
got
the
104
release
coming
out
next
week.
We've
got
the
road
map
in
place,
so
then,
in
in
the
stills
in
this
section
here
david
did
you
add
this
this
package
package?
A
C
Did
it's
kind
of
like
a
metadata
change?
It
was
very
small
nick
approved
it
it's
been
merged.
I
think
we
can
oh
good,
so
nothing
to
discuss.
A
Yep
all
right
sounds
good,
okay,
so
that's
a
core
crossband
stuff.
Let's
move
down
to
the
providers
now,
and
so,
let's,
let's
visit
you
know,
like
the
the
point
of
this
section,
really
is
around.
You
know,
first
of
all,
big
updates
for
each
of
the
providers
and
then
secondly,
kind
of
deciding
getting
a
sense
of
releases
from
the
providers
as
well
too,
since
those
are
done
on
a
different
schedule
from
the
core
cross
plane
repository.
So
let's
that's
gonna
re
visit
each
provider
there.
C
D
A
Would
like
to
see
in
aws,
so
I
don't
know
if
muaf
is
on
the
call
but
aaron.
I
think.
A
Yes,
so
do
we
have
do
we
already
review
this
pr?
I
have
not
looked
at
the
status
of
this
myself
so.
E
This
pr
has
not
been
reviewed,
yet
it's
implementing
a
whole
new
service.
It's
currently
triaged
as
a
medium
size,
because
it's
it's
implementing
a
whole
service,
but
it
looks
like
at
a
first
glance.
It
looks
pretty
good
I've
gone
ahead
and
assigned
myself
and
I'll
give
it
a
review
before
the
end
of
week.
And
if
we're
you
know,
assuming
everything
works.
Fine,
it
doesn't
need
any
major
changes.
It
will
probably
be
included
in
the
next
release.
It
can
go
ahead
and
merge,
but
I
that
depends.
That's
based
on
review.
A
Okay
cool,
so
then,
let's,
let's
keep
with
the
provider
aws
updates.
Then
I
I
yeah.
We
don't
have
to
go
through
every
issue,
but
you
know
it's
good
to
have
them
here
and
then
high
level.
Do
you
want
to
kind
of
give
us
an
update
erin,
then
about
progress
on
aws
and
where
we
would
be
in
relation
to
next
release
going
out.
It
seems
like
spoiler,
spoiler
alert.
It
seems
like
there's
a
lot
going
on
so
doing
the
release
soon
makes
it
makes
sense.
Then.
E
Yeah,
so
I've
listed
that
the
pr's
that
were
merged
in
the
last
two
weeks
since
our
last
community
meeting
a
couple
of
new
instance
types
couple:
new
resources
and
a
couple
of
bug
fixes
to
different
other
resources.
There
is
a
breaking
change.
I
think
it
was
just
barely
outside
of
the
two-week
window,
but
we
did
introduce
breaking
change
for
vpcs,
where
we
we've
moved.
The
api
group
over
all
of
the
manually
created
vpc
resources
have
now
been
given
their
own
api
group
to
differentiate
them
from
the
code
generated.
E
I
should
add
that
to
this
the
current
status
on
fighterbase,
we
have
41
open
pr's.
We
have
started
triaging
them,
trying
to
get
the
small
prs
done
quickly,
so
we
can
move
on
to
the
larger
ones.
We
also
added
a
new
maintainer
to
the
project
to
try
and
deal
with
the
backlog.
14
of
the
pr's
are
in
you
know,
have
been
in
motion
in
the
last
two
weeks.
They've
gotten
review,
they've
gotten
comment,
and
there
are
two
issues
that
have
been
active,
one
of
which
is
provider.
E
Attempts
to
remove
tags
from
the
node
group-
all
the
other
issues-
are
still
just
sitting
there
for
you
know
past
the
last
two
weeks,
but
that's
the
current
status
of
provider
aws
there
have
been
24
merges
to
mainline
since
the
last
release,
so
I
think
we're
justified
in
making
a
new
release
and
I'm,
I
think,
it's
more
than
a
patch
based
on
that
change.
We
made
to
the
vpc
resources
and
changing
their
api
group.
We
should
give
it
a
full
version
bump.
D
Just
another
thing
to
throw
in
there
aaron,
that
is,
I
I'm
working
on
two
separate
race
conditions
in
cross
plane
run
time,
but
as
far
as
I
know,
primarily
affect
provider
aws.
At
this
point,
they
theoretically
affect
any
managed
resource,
but
we've
only
observed
them
in
provider
aws.
D
There
is
potentially
a
risk
that
that
might
be
an
update
to
provide
around
time
after
we
ship,
crossplay
1.4,
then
update
provider.
Sorry
across
my
runtime
that
provide
aws,
but
I
guess
please,
someone
come
hit
me
up
before
you
release
the
new
version
provided
because
I'd
love
to
get
this
bug
fix
out
there.
For
for
the
folks
who
are
waiting
on
it.
E
D
Potentially,
I
think
I
could
I
I
so
I
have
two
different.
The
slightly
more
context
is
there's
two
different
problems.
I
have
two
different
working
pull
requests
hassan
gave
me
some
good
feedback
that
they
could
potentially
be
merged
into.
One
pull
request,
I'm
about
half
halfway
through
doing
that,
so
sort
of
sort
of
making
the
two
fixes
a
little
bit
more
of
a
cohesive
whole.
D
C
B
A
Thank
you,
aaron
thanks
nick
yeah,
a
lot
going
on
our
native.
Yes,
no
question
about
that
good
to
see
that
we'll
get
a
release
out
sometime
soon
as
well
too,
so
from
gcp
provider
gcp.
Do
you
want
to
give
us
a
high
level
update
as
well?
There,
too.
B
Yeah
sure
yeah,
actually
there
were
a
couple
of
pr's
reviewed
within
this
two
two
week,
time
frame
and
there
were
a
couple
of
merged
pr's
and,
like
I,
I
tried
to
list
the
important
ones
here.
One
is
a
bug
fix
for
bucket
life
cycle
field,
interestingly,
two
like
bugs
opened
for
the
same
issue
by
different
people.
As
far
as
I
know,
so
we
provided
a
fix
for
that
and
also
a
community
member.
I
think
it's
gabrielle
introduced
resource
record
record
sets
for
dns.
B
This
is
also
something
like
a
like
top
requested
resource.
So
this
is
this
pr
is
also
reviewed
and
merged,
and
I
also
like
check
the
existing
bugs
and
like
issues
and
bugs
and
like
there
are
two
top
priority
or
bugs
that
need
needs
attention.
I
can
talk
about.
One
is
cloud,
sql
instance
keeps
modifying
the
instance.
This
is
actually
a
pretty
I
like
kind
of
a
pretty
common
case.
B
We
see
when,
when
there
is
a
difference
between
the
resource
on
the
provider
side
versus
on
on
our
desired
spec,
like
I
I
remember
there
were
some
recent
discussion
on
how
to
make
the
difference
more
visible
with
provider
logs
versus
events.
I
think,
if,
or
once
we
have
such
a
such
a
feature
available,
it
would
be
much
easier
to
identify
the
root
cause
of
this,
these
sort
of
problems.
B
So
this
is
one
issue.
The
other
one
is,
I
think,
like
most
of
us
are
already
aware
that,
like
gk
cluster,
actually,
google
deputy
case
basic
out
after
juventus
1.18,
so
aaron
was
aaron,
has
provided
a
fix
on
on
provider
home
sites
which
were,
I
think,
planned
to
to
be
moved
on,
crossbane
runtime,
so
that
other
providers
or
other
consumers
could
could
reuse
the
the
thing
that
that
is
implemented
there
yeah
this
is.
This
is
also
about
that
yeah.
That's,
actually,
all
the
updates
on
provider
gcp
sites.
B
I
am
not
sure
about
like
how
it
relates
to
making
a
release
with
the
like,
with
daniel's
work
with
provider.
Gcp
beta,
I
I
couldn't
like
have
a
chance
to
check
that,
and
what?
What
would
it
mean
to
have
a
provider
gcp
new
version
and
provider
gcp
beta
new
version,
so
this
is
maybe
an
open
item
to
check
for
myself
yeah.
That's
that's
pretty
much
it
for.
C
Me
yeah,
the
the
basic
thing
is
that
I
need
to
write
down
what
the
changes
would
be
like
for
moving
from
one
to
the
other,
but
yeah
other
than
that
we
can
sync
up
and
make
sure
everything's
aligned
on
that
yeah
sure.
Thank
you.
A
Awesome
hassan,
thank
you
for
the
update
on
provided,
gcp
and
then
federer
azure
as
well
too.
We've
got,
it
looks
like
we've
got
a
couple
updates
there
as
well
too
alpha.
Do
you
want
to
give
us
a
high
level
summary
of
those
two.
F
So
a
bug
fix
has
been
merged.
That
fixes
you
know
we
get
a
wrong
admin
user
password
in
the
connection
secret
for
post
sql,
sql
server.
F
Actually
you
know
when
we
delve
into
the
details
of
this
issue
quite
different
than
from
you
know:
provider,
aws
or
provider
gcp.
F
We
make
asynchronous
calls
here,
so
the
other
sdk
for
go
provides.
You
know
asynchronous
apis
for
updating
and
deleting
resources
and
creating
them
of
course.
F
So
my
observation
is
that
the
bug
that
causes
the
specific
issue
with
postcard
sql
server
in
fact
affects
other
resources
as
well,
because
we
use
similar
mechanisms,
we
interact
with
the
other
sdk
for
going
a
similar
manner.
F
So
this
issue
also
affects
other
resources.
However,
you
know
most
probably
we
have
observed
this
and
there's
an
explicit
issue,
for
you
know
postgrad
sql
server,
because
we
generate
you
know
a
password,
an
initial
admin
user
password,
and
you
know,
since
we
cannot
prevent
multiple,
create
calls
making
multiple
create
calls.
You
know
we
potentially
generate
multiple
passwords
that
are
not
consistent
with
the
sql
server
being
provisioned,
so
we
may
have
a
long-term
effort
here.
F
F
We
have
done
some
experiments,
multiple
runs
with
postgresql
server
and
this
specific
issue
seems
to
be
solved
there.
So
it's
it's.
I
can
I
I.
I
could
not
reproduce
the
issue
with
the
fix.
Apart
from
that,
then
it
has
merged.
You
know
the
global
polling
turbo
flag,
similar
to
other
providers.
We
now
have
the
poll
interval,
which
provides
aws
provider.
Azure.
Excuse
me
another
pr
is
open,
which
introduces
a
postgrad,
sql
server
configuration
resource.
F
Yes,
this
one
introduces
support
for
configuring,
a
postgresql
server.
F
F
F
Yeah,
why
I
think
why
you
know
said
that
is
the
model
is
not
consistent,
meaning
that,
for
example,
in
the
other
sdk
fargo,
there
is
no
delete
call,
because
whenever
you
create
a
prosecutor,
sql
server
instance,
these
configuration
objects
apparently
become
available,
but
you
know
what's
wrong
about.
It
is.
F
However,
if
it's
manipulated
once
even
if
you
reset
it
to
you,
know
the
default
value
and
even
if
you
reset
the
source
of
it,
which
means
that
whether
a
user
has
overridden
its
value
or
it's
the
default
value
provided
by
the
system,
you
know,
in
that
case
the
source
becomes
system
managed,
even
if
you
reset
its
state,
other
resource
manager
does
not
return
404.
So
there
were
a
couple
of
tricks
that
we
need
to
do
yeah.
That
was
the
tricky
part
about
it.
F
There's
another
issue,
for
you
know
adding.
You
know,
aks
configuration
parameters
and
you
know
the
notebook
support.
I
think
this
will
become
important
in
the
short
term.
We
might
you
know,
give
some
attention
here.
A
A
Okay
and
then
albert
you
had
a
note
here
too,
about
maybe
updating
the
version
of
the
sdk
for
azure.
Yes,.
F
A
E
A
I
think
the
biggest
thing
to
consider
there
is
you
know
if
they're,
if
do,
we
have
a
good
understanding
of
any
breaking
changes,
changes
to
functionality,
changes
to
like
the
programming
model
or
any
of
that
stuff
that
would
be
challenging
to
consume,
or
you
know
like
that,
we
would
have
to
do
a
lot
of
work
to
get
to
you
know
integrate
with.
Do
you
have
any
idea
of
that
yet
upper?
No,
I
didn't
check
yeah.
A
Yeah,
I
think
I
think
in
general,
it's
nice
to
update
our
resources,
but
yeah
that
we
can
make
a
measured
assessment
of
performing
that
once
we
kind
of
have
a
better
idea
of
what
the
cost
is
or
the
risk
as
well
too.
Maybe
even
more
importantly,
the
risk
of
upgrading
this
too.
A
All
right,
thanks
for
the
update
up
here,
I
appreciate
it:
okay,
cool!
So
that's
you
know,
1.4
all
the
providers
and
their
upcoming
releases
as
well
too.
Then
any
other
topics
here
that
on
upcoming
releases
or
milestones
before
we
move
into
community
topics,.
A
A
Okay,
so
yeah,
so
we
got
to
play
in
for
our
releases
coming
up
a
lot
of
stuff
going
on
with
providers
as
well
too.
Thank
you,
everybody
for
all
the
contributions
there
and-
and
you
know,
ownership
of
those
providers-
and
you
know
helping
out
the
community.
That's
been
really
really
helpful,
so
we
got
a
as
usual
here
now
we
got
a
bunch
of
awesome
content
that
that
victor
and
others
have
been
creating
around
crossplane.
A
So
we
have
direct
links
here
for
a
number
of
various
videos
and
podcasts
as
well
too,
that
have
been
put
out
recently.
So
a
couple
ones
around
you
know
nick
was
talking
about
the
composition
revisions.
We
were
talking
about
this
earlier.
That's
the
big
feature
in
1.4,
and
this
is
a
live
stream
that
nick
and
victor
did
together
to
explain
how
it
works.
Show
a
demo
things
like
that,
so
you
can
check
out
that
recording
from
that
there
victor
made
a
couple
good
videos.
A
I
think
I
haven't
gotten
to
get
a
chance
yet
to
watch
this
one.
The
automated
drift
detection-
one
victor,
I
think
you
did-
is
that
one
of
you
did
a
little
bit
of
like
not
really
chaos,
testing
but
kind
of
monkey
around
with
some
changes
and
see
what
happens.
B
Exactly
I
mean
I
actually,
I
did
want
to
make
real
chaos,
testing.
F
Experiments
in
that
video,
but
it
turned
out
that
all
three
tools
that
I
want
to
use
don't
really
do
well.
Infra
are
mostly
focused
on
applications,
so
I
gave
up
and
just
did
it
manually
kind
of
like
hey
how
about
I
destroy
this
thing
and
see
what
happens.
D
D
A
Exactly
right
on,
and
then
I
also
got
a
chance
to
victor-
also
created
some
content
around
policies
and
using
caverno
to
do
that
as
well
too,
which
is
which
is
definitely
interesting
to
see
and
then
kind
of
understanding.
You
know
how
carverno's
approach
differs
from
from
over
policy
agents
and
seeing
other
options
for
policies
and
ecosystems.
A
That's
definitely
interesting
too,
and
then
dan
and
I
we're
on
a
podcast
for
the
change
log
called
ship
it
a
new
podcast,
we're
doing
there
we're
kind
of
talking
about
you,
know,
crosstalking
project
and
and
some
of
the
shipments
or
change
logs.
A
I
guess
infrastructure
that
they
want
to
be
running
on
crossfit
as
well
too,
so
that
was
a
good
episode
that
dan
doesn't
like
to
listen
to
himself,
but
I
listened
to
the
whole
thing,
so
I
wanted
to
hear
myself
talk,
so
I
listened
to
it
right
away,
cool
so
yeah
all
that.
That's
all
the
latest
content
there,
every
every
community
meeting
we
have
a
bunch
of
new
cool
stuff
to
talk
about
and
show
off
there.
A
So
thanks
everybody
for
the
contributions
there
and
victor's
doing
some
amazing
work
on
that
stuff.
So,
thank
you.
Thank
you.
So
much
for
that
news
on
incubation
is
we
got
all
the
votes
that
we
need
for
incubation
we've
been
talking
about
this
since
march,
going
to
the
process,
and
now
we
have
gotten
the
votes
from
the
technical
oversight
committee,
sufficient
votes
to
be
approved
to
move
to
incubation,
so
that
is,
is
complete
and
we're
done
with
that
and
we'll
be
announcing
the
move.
A
The
cncf
will
be
making
the
announcements
about
the
promotion
to
incubation
there.
I
think,
probably
early
next
week
we're
drafting
a
blog
post
announcement,
pr
press
release
sort
of
stuff
around
that,
so
that
will
be
announced
next
week,
but
hooray
for
getting
that
done
and
thank
you
for
all
the
efforts
on
from
everybody
on
making
that
incubation
movement
happen.
A
It'll
be
nice
to
soon
remove
this
from
the
template
for
our
agenda
doc,
because
it's
been
on
here
for
like
months,
okay,
cool
and
then
items
of
community
interest,
interesting
discussions,
interesting
observations,
interactions
within
the
community
that
folks
have
been
having
aaron
you.
You
added
this
this
item
here
about
adding
carl
as
a
maintainer
to
aws,
which
is
fantastic.
Yeah
carl's
been
quite
a
contributor
in
aws
and
opening
issues
providing
pull
requests
and
stuff.
So
it's
great
to
recognize
him
in
that
role
as
well
too.
A
Welcome,
indeed,
carl
any
has
anybody
else
like
you
know
conversations
or
you
know,
observations
of
slack
like
any
any
recent.
You
know
interactions
to
the
community
for
things
that
are
in
highly
heightened
demands.
You
know
patterns
we're,
seeing
any
interesting
interactions
with
the
community
that
people
want
to
highlight
here.
A
Does
anybody
like,
I
know
people
are
using
their
own
compositions,
anybody
noticing
any
like
patterns
there
or
like
issues
that
people
are
running
into?
I
think
nick
you,
you
opened
an
issue
recently
to
kind
of
document.
Some
of
the
you
know,
patterns
or
gotchas,
or
things
like
pain
points
for
for
complicating
your
compositions.
D
Yeah,
I
did
that's.
I
don't
know
what
issue
it
is
one
of
the
top
ones
on
on
on
crossplane,
slash
cross
plane
at
the
moment.
In
fact,
there's
a
there's:
a
label
docks
that
we
did
a
bit
of
grooming
the
other
day.
So
if
you
search
for
cross
plane
issues,
labeled
docks,
that's
generally
a
place
that
would
like
feedback
at
the
moment
on
any
of
those
which
includes
that
issue
that
jared
just
referenced.
A
All
right,
we
went
through
a
lot
of
prs
and
and
in
issues
specifically
earlier,
so
I
don't
see
any
that
are
specifically
on
the
agenda
here.
So
I
think
we're
out
of
agenda
topics
now.
Was
there
anything
else
that
folks
wanted
to
bring
up
or
make
note
of
while
we
still
have
this
quorum
today,.
A
All
right
cool,
okay,
so
I
think
that's
everything
for
the
agenda
here
and
you
know
we'll
be
getting
those
1.4
and
provider
releases
out
soon
and
you
know
happy
to
continue
accepting
and
taking
community
feedback
on
the
roadmap.
We
have
that
new
process
there.
It's
a
lot
of
things
going
on
a
lot
of
activity,
a
lot
of
great
work
around
the
whole
community
as
well
too.
So,
thanks
to
everybody
for
all
your
efforts,
good
to
see
everybody,
and
we
will
see
everybody
in
two
weeks
and
on
slack
as
well.