►
From YouTube: 2021-09-09 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,
as
the
lady
told
us,
the
recording
has
started,
and
so
this
is
the
september
9th
2021
cross,
plane
community
meeting
we
had
the
most
recent
update
is
the
1.4
release
that
went
out
just
about
a
week
or
so
ago.
So
we
will
dive
into
some
details
on
that.
A
We'll
talk
about
the
upcoming
1.5
release,
which
we
are
just
starting
on
the
early
phases
of
that
that
release
cycle-
and
you
know,
milestone,
planning
and
things
like
that,
and
then
a
lot
of
updates
on
providers
that
have
been
released
recently
are
about
to
be
released
as
well
too
so
a
bunch
of
things
to
jump
into
and
feel
free
folks
to
hop
in
and
interrupt
at
any
time.
If
you
want
some
clarification,
or
do
you
want
to
hear,
you
know
get
to
get
a
question
answered.
A
This
is
definitely
a
dialogue
for
everybody
to
join
in
on
here,
so
feel,
free
to
jump
in
whenever
you
want
to.
We
can
also
start
too
with
anybody
who
is
new
to
the
meeting
here.
If
you
want
to
unmute
yourself
and
introduce
yourself
to
us,
you
are
more
than
welcome
to
as
well.
So
I
will
take
a
quick
pause
for
anybody
who
might
want
to
introduce
themselves
as
their
first
first
time
at
the
meeting
here.
B
I
can
just
quickly
introduce
myself
hi,
I
I'm
just
a
user
of
crossplay,
and
I
mean
we
haven't
really
used
it
in
production,
but
I'm,
like
you
know,
looking
into
prospering,
to
manage
our
cloud
resources
and
it's
a
very
interesting
concept.
So
I
just
come
here
and
I
wanted
to
learn
more
and
yeah.
I've
always
been
quite
impressed
by
how
you
guys
like
manage
this
like
releases
and
this
whole
kind
of
also
like
your
workflow,
so
yeah
just
hope
to
get
inspired.
A
Awesome,
that's
fantastic
to
hear
really
happy
to
have
you
here
to
collaborate
with
us
here
today
and
yeah.
I
definitely
wouldn't
consider
anybody
just
a
user
right.
That's
what
this
project
is
for
is
is
the
users
of
it.
So
that's
a
huge
part
of
the
community
and
definitely
something
that's
really
valuable,
so
yeah,
I'm
really
excited
to
you
know
to
have
you
join
here
and
any
questions
or
you
want
to
dig
in
deeper
with
us.
A
We're
always
happy
to
spend
time
with
folks
so
happy
to
have
you
all
here
today,
all
right
sweet.
So
let's
talk
about
the
1.4
release
that
went
out.
I
believe
it
was
after
the
last
community
meeting.
So
I
move
off.
I
ran
this
release
there
and
did
some
interesting
automation
for
generating
the
release
notes.
Muafik,
do
you
want
to
kind
of
talk
about
that
release
process
there?
Some
of
the
highlights
from
it
as
well
too,
and
maybe
some
of
your
interesting
scripting
to
to
build
out
the
automated
release.
C
Yeah
yeah
sure,
so
the
major
things,
a
real
team
after
this
release,
is
actually
the
composition
revision
that
nick
has
implemented.
So
this
will
allow
yes
right
so
far.
The
flow
was
that
you've
got
like,
let's
say,
10,
composed
resources
that
are
bound
to
claims
or
not
bound
to
any
claim.
C
C
C
Yeah,
the
the
there
was
a
type
I
couldn't
remember
like
alternative
to
deployment,
but
yeah.
That
has
also
like
revision.
So
the
same
mechanism.
You
will
have
a
new
revision
for
every
change.
You
do
you
make
on
the
composition
and
then
you
can
choose
which
xrs
to
use
this
new
revision,
one
by
one,
I
believe
by
default.
It's
still
like
you
know
propagate
as
propagates
this
one,
but
if
you
configure
it,
it
will
not
do
that
automatically
and
you
would
be
able
to
choose
the
latest
composition
revision.
C
There
is
a
log
object
that
has
existed
like
for
a
long
time
and
we
just
bumped
it
and
we
won
better
one
because
it
hasn't
changed
and
it's
working
as
intended
and
and
there
is
also
the
labels
on
the
labels
and
annotations
on
the
composed
resources
so
before
we
would,
and
so
essentially,
when
you
patch
the
whole
annotations
object,
which
is
a
map,
the
whole
object
in
demand
resources
in
the
composite
resource
changes,
because
we
would
just
like
you
know,
set
the
whole
map,
but
with
alpha's
change
you
will
be
able
to.
C
You
will
be
able
to,
like
you
know,
make
additions
on
the
existing
labels
and
annotations
with
patching,
and
so
that,
like
you,
know,
enabled
some
of
the
like.
You
know
community
users
workflows
and
there
is
the
darwin
arm
64
support
for
new
mac
users,
so
you
will
be
able
to
like
you
know,
build
the
cross
plane
using
that
architecture.
I
think
it
was
possible
to
run
it
if
I'm
not
mistaken,
but
I'm
not
sure.
C
A
C
Change
I'll
introduce
to
patching
mechanism
is
that
it's
it's
similarly
made
with
the
earlier
one,
but
like
this
this
in
this
last
one,
you
can
actually
choose
the
policy
of
any
patch,
so
you
would,
you
would
be
able
to
say,
okay,
replace
the
whole
object
or,
like
you
know,
merge
the
merger
to,
like
you,
know,
key
value
pairs,
for
example,
if
I'm
not
mistaken,
I
I
think
I
would
have
more
details
there.
So
these
are,
I
believe,
like
you,
know,
most
notable
updates.
C
That,
actually,
like
you
know,
extracts
the
every
pr
that
is
merged
since
the
last
release
and
prints
out
it
prints
them
out
in
this
fashion,
so
that
we
can,
you
know,
capture
all
of
them
like
before
that
it
was
a
manual
process,
and
I
think
we
were
missing
some
of
the
things,
but
even
if
we
didn't
miss
like
it's
just
really
plumbing,
so
I
added
a
script
upon
build
sub
module
that
crossband
uses
the
pr
is
still
open,
but
that
script
will
be
like
you
know,
you
will
be
able
to
use
it
for
any
release
for
any
repository.
C
A
Nice,
nice
workbook,
I
think
that's
super
useful
and
definitely
makes
like
the
release
process
easier.
So
I
appreciate
your
your
automation,
innovation
there
that
I
think
oftentimes
oftentimes,
we'll
see
a
lot
of
innovation
come
from
laziness
which
is
awesome.
I
think
that
drives
forward
a
lot
of
things.
A
Yeah
awesome,
sweet,
so
yeah
the
1.4
release
is
out
thanks
to
everybody
who
you
know
was
contributing
in
that
release
and
adding
a
lot
of
fixes
there.
So
we've
got
a
lot
of
you
know
pr
authors
names
in
here.
Some
of
those
folks
are
on
the
call
here
as
well
too.
So,
thanks
to
everybody
for
another,
really
successful
release,
and
you
know
we
will
turn
our
sights
and
our
eyes
towards
the
next
release,
which
will
be
1.5.
A
So
we
can
kind
of
start
talking
about
that
release,
1.5
or
sorry.
There's
going
to
be
a
1.4
that
one
patch
release
that's
coming
out
tomorrow.
I
I
can't
remember
off
top
of
my
head
at
least
what
that
what
that's
going
to
include.
Could
somebody
refresh
my
memory
on
what
1.1
will
have.
C
Since
it's
the
the
breaking
the
interface
that
people
use
in
hand
parameters,
we
decided
that
it
would
be
worth
to
have
a
patch
release,
and
in
addition
to
that,
I
am
planning
to
include
another
fix
actually
in
that
patch,
which
will
allow
more
than
like
you
know,
certain
number
of
cds
to
be
installed
for
the
contacts
we
I
mean,
I
will.
C
I
will
go
into
details
in
the
next
sections,
but
in
its
essence,
with
the
telegen
project,
we
are
able
to
produce
providers
from
terraform,
and
some
of
them
has,
like
you
know,
like
enormous
number
of
crds.
For
example,
tf
aws
provider
will
have
770
crds,
so
right
now,
package
manager.
C
A
Cool
that
sounds
great
mafik,
thanks
for
the
update
on
the
next
1.4.1
patch,
and
so
we
can
kind
of
start
talking
about
1.5.
Now,
it's
still
so,
as
we
see
here,
I
put
this
release
date
here,
that's
the
eight
weeks
since
the
last
release,
so
I
think
that's
you
know,
in
accordance
with
our
typical
cadence
of
every
eight
weeks,
doing
a
release
so
october.
26Th
is
what
we'll
be
looking
at
for
our
next
minor
release
here
with
1.5.
A
For
folks
or
if
we
need
to
make
any
adjustments,
but
that
should
be
on
cadence
there's,
I
expect
that
to
work.
Okay,
we,
as
we
talked
about
in
the
last
community
meeting.
We
now
have
a
roadmap
board
which
shows
some
of
the
you
know
the
thing
like
the
things
in
progress
and
what
are
the
priorities
for
the
community
as
a
whole,
and
this
is
spanning
across
releases.
A
So
this
is
not
a
you
know,
a
necessarily
a
commitment
to
have
these
features
in
the
next
given
release,
but
it
is
hey.
These
are
things
that,
as
a
community
folks
have
been
asking
about,
we've
identified
to
be
priority
a
priority,
and
so
these
will
be
things
that
we
think
should
be.
You
know
on
the
upcoming
set
of
releases-
and
you
know
folks
to
want
to
be
addressing
these
as
well
too.
A
So
I
think
this
column
here
should
be
prioritized
with
things
that
we
think
are
pretty
important
and
what
we'll
be
diverting
some
attention
to-
and
these
ones
here
that
are
already
in
progress-
are
things
that
are
more
likely
to
be
included
within
the
next
release.
This
is
something
that's
very
open
to
community
feedback.
Obviously
this
is
driven
by
the
community
at
large
and
so
folks
that
want
to
weigh
in
on
you
know
what
they
want
to
see
in
here.
A
What
they
think
is
important,
you
know,
please
do
feel
free
to
speak
up,
have
a
voice
and
contribute
to
the
the
roadmap.
Here
I
don't
know
if
we,
since
we're
very
early
in
the
release
cycle
here,
we
just
did
1.4.
I
don't
know
if
we've
got
this
1.5
board
up
to
date,
but
we
do
have
some
things
that
are
included
in
it,
at
least
so.
These
are
things
we'll
be
working
on
in
1.5,
we're
already
making
some
progress
on
some
of
them.
Some
of
them.
A
It
looks
like
you
know,
we're
not
going
to
going
to
visit
every
item
on
the
board
here,
but
does
anybody
want
to
call
out
anything
of
note
or
anything
specific
on
this
board
here
that
we're
making
progress
on
as
we're
working
towards
our
1.5
release
at
the
end
of
october.
D
I
mostly
just
dropped
these
on
right
before
it.
I
wasn't
sure
if
we
were
populating
this
at
this
point
most.
These
are
probably
things
that
we
should
discuss
more
or
something
like
that,
and
then
some
are
in
progress.
Is
this
just
for
clarification
for
myself
and
maybe
the
whole
community,
as
anything
is
in
progress
right
on
crossplane?
We
expect
for
it
to
show
up
on
the
v
1.5
board
if
it
is
going
to
be
included
in
the
v
1.5
release.
Is
that
right.
A
Yeah
that
makes
a
lot
of
sense
to
me
dan.
Yes,
I
think
that's
totally
reasonable
yeah
and
then
people
you
know
should
feel
free
to
you
know
ping
ping
us
for
getting
items
onto
this
board
as
well.
I
don't
think
it's
it's
it's
publicly
accessible,
but
I
don't
think
it's
publicly
editable
so
folks
that
want
to
add
items
to
it
if,
like
maybe
they're,
picking
up
a
contribution
or
they're
working
on
a
pr
or
they
want
to
see
something
get
fixed
in
a
particular
release.
A
A
So
yeah,
so
there's
a
a
lot
of
you
know
things
on
the
interesting
things
on
the
roadmap:
we're
just
getting
started
with
the
1.5
release.
You
know
I'll
open
the
floor
here
for
an
opportunity
for
anybody
who
wants
to
add
their
their
perspective
on
things
that
they
want
to
see
prioritized
or
you
know
fixes
that
are
interesting
for
the
community.
So
if
anybody
wants
to
add
a
comment
on
the
upcoming
roadmap
and
1.5
release
I'll
go
ahead
and
pause
for
anybody
to
do
that
now,.
A
Okay,
well,
if
anybody
can
make
those
comments
known
at
any
time,
you
can
do
it
asynchronously
on
slack
as
well
too.
So
there's
always
opportunities
to
get
involved
there.
All
right,
so
we
can
move
down
into
you
know,
starting
1.5
104
is
out
starting
1.5
for
the
main
cross
plane.
Now,
let's
talk
about
all
the
providers
as
well
too,
in
in
focus
there,
so
I
know
there's
going
to
be
a
specific
focus
from
the
maintainers
of
some
of
the
major
providers
over
the
next
few
weeks,
muafik
hassan
al
pere.
A
I
know
that
you
all
will
be
in
erin
as
well
too.
I
think
you
all
will
be
doing
a
bit
of
a
focus
on
each
one
of
their
providers
of
ownership.
There
aws
gcp,
azure
and
getting
through
some
of
the
pr
backlogs
and
making
progress
on
getting
things,
feedback
known
and
getting
things
merged
and
integrated
into
the
provider
as
well
too.
So
we
should
have
a
lot
of
content
and
you
know
upcoming
releases
for
the
providers
as
well
too,
as
we
continue
to
merge
all
that
functionality.
A
Any
other
things
of
note
for
for
that
effort.
From
from
you
all
that
we'll
be
spending
time
as
maintainers
on
those
providers.
C
Yeah,
so
so
the
reason
we're
doing
this
is
that
there
are
some
like
no
lingering
pr's
and
issues
in,
like
you
know
all
three
big
providers
because
of
like
our
recent
focus
on
teres
yet
and,
like
you
know,
generating
controllers
and
like
ncr
dispatchers
based
providers.
A
Yeah
yep
that
will
definitely
be
appreciated
by
the
community
and
kind
of
you
know,
make
some
rapid
progress
on
some
of
the
great
contributions
from
from
everybody
into
those
providers
mwafek.
I
think
that
you
have
a
couple
of
updates
next
here
for
some
of
the
co-generation
and
provider
coverage
stuff.
If
you
want
to
take
all
of
those
too.
C
Yeah
yeah
sure,
so
the
first
one
is
reference
dissolver
generation,
so
we
have,
we
have
like
we
have,
but
we
were
planning
to
do
it
for
teresa,
but
like
it's
generic
enough
that
we
can
use
the
old
crosstrain
providers.
C
So
if
you
click
to
that
link,
you
will
you
will
see
the
pr
the
main
gist
of
it
is
that
now
you
will
be
able
to
put
only
one
command
on
the
field
that
can
reference
to
another
resource.
For
example,
if
you
have
a
cluster
and
it
references
the
ppc
id,
you
will
be
able
to
put
a
command
on
top
of
that
field,
and
then
we
will
generate
the.
C
Resolver
functions
automatically,
so
that's
that's
the
that
has
been
a
pain
for,
for
especially
people
who
use
ack
generation
pipeline,
like
you
know
like
for
them
to
be
to
write
the
results
in
like
complex
situation.
So
this
will
take
some
of
that
work
from
there
from
their
workload.
C
It
will
be
essentially,
like
you
know,
automated
away
completely,
covering
all
cases
that
at
least
we
have
for
now
and
yeah.
So
this
is
like
you
know,
for
all
providers
and.
A
Yeah,
I
think
this
is
this
is
like
pretty
darn
important
as
well
too.
I
think,
like
the
ergonomics
around
this,
like
the
ability
to
like
the
contribution
it
makes
to
the
crossbar
resource
model
and
like
the
burden
takes
off
of
some
of
the
code
generation.
Efforts
is
really
really
huge.
It
allows
you
to
do
more
interesting
scenarios
here,
so
I'm
really
happy
to
see
this
in
a
generic
way
across
all
the
providers.
The
entire
the
entire
ecosystem
here
gets
benefit
from
this.
C
Yeah
yeah
exactly
I
mean
it
will
be
very
useful
for
like
especially
like
not
having
to
do
that
for
in
the
prs,
because
I
remember,
like
you
know,
reviewing
many
pr's
that,
like
you
know,
we
were
stuck
in
that
step,
like
you
know,
for
a
few
rounds.
So
that
will
also,
like
you
know,
ease
reviewing
those
pr's,
because
it's
just
like
let's
go
to
review
and
make
sure
it
works.
C
A
I
love
it.
I
love
it
cool
them
off.
If
you
want
to
get
us
an
update
on
terajet
and
kind
of
give
a
bit
of
a
background
as
well
too
a
quick
background
on
that
to
get
everyone
up
to
speed
too
yeah
yeah.
C
Definitely
so
so
so
we
have
been
working
on
this
storage,
yet
I
mean,
I
believe,
in
the
last
two
minutes
meeting
we
announced
it
but
and
there's
a
design
dock
in
cross-claim
repo
that
has
been
approved
about
like
lg,
general
structure
and
architecture
of
the
project
and
the
main
our
main
goal
is
essentially
to
be
able
to
generate
cross-plane
providers
using
terraform,
existing
telephone
providers
and
the
terajet
itself
is
a
repository
is
a
framework
of
tools
that
you
can
use
to
build
your
code
generation
pipeline.
So
it's
it's.
C
It
doesn't
have
like
a
hey
yeah,
give
me
that
provider
repo
and
I
will
generate
everything,
it's
more
like
a
framework
that
you
can
build
your
code
generation
pipeline
and
so
it
at
the
end
of
this
week.
I
believe
we
have
issued
like
some
some
of
some
important
milestones
in
regards
to,
like
you
know,
making
the
generated
crds
and
controllers
xrm
compliant.
C
For
example,
we
will
be
able
to
do
the
late
initialization,
which
is
an
important
feature
in
cross
play
and
with
the
reference
dissolver,
we
will
be
able
to
use
like
strong
type
references.
Just
like
other
resources
and
like
you
know,
we
are
now
able
to
package
those
providers
that
have
been
generated
by
terror.
Yet
so,
like
you
know,
we
were
and
shoot
out
to
like.
You
know,
alpha
and
hassan
for,
like
you
know,
working
on
this
stuff
and
it's
it's
yeah,
it's
it's!
It's
pretty!
C
It's
it's
moving
pretty
fast
and
today
I
added
a
readme,
and
so
that,
like
you
know,
other
people
like
it's,
it's
still
not
as
stable
as
we
would
like
it's
in
very
early
stages,
but
if
people
feel
adventurous,
I
think
you
can
like
you
know
now
by
following
this
readme,
you
can
build
your
own.
Like
you
know,
small
pipeline,
that
generates
a
telephone,
a
cross-plane
provider
using
the
using
the
terraform
one.
C
There
are
some
details
that
will
change
breaking
changes
here.
For
example,
we
will
probably
have
a
provider
tf
template
repo
or
a
branching
provider
template
so
that
this
packaging
stuff
is
handled
for
you,
because
it's
just
common
to
all
telephone
providers,
but
yeah
you
can,
you
can,
like
you,
know,
get
started
and,
like
you
know,
get
familiar
with
the
whole
structure.
C
So
the
the
plan
right
now
is
that
we
would
have
like
provided
tf
aws,
for
example,
or
providers.
You
have
azure
as
separate
providers
from
the
native
ones
that
call
out
the
sdk
of
the
providers.
C
But
since
we're
like
you
know,
getting
more
and
more
extreme
compliant,
we
will
consider
actually,
like
you
know,
merging
the
generated
crds
into
the
native
provided
repos.
C
C
People
would
have
the
support
and
we
would
like
you
know,
convert
them
to
native
ones
as
like.
You
know
as
we
as
needed
so
yeah.
There
are
lots
of
things
going
on
there
and
you
can
see
the
like.
You
know
rough
road
map
when
you
click
that,
like
roadmap
link,
you
will
see
issues
marked
as
post
alpha
post
alpha
doesn't
mean
like
we're
over
alpha
and
it's
kind
of
usable,
but
it's
just
like
you
know
a
milestone
name,
maybe
maybe
a
bad
name.
C
In
fact,
like
you
know,
we
could
have
said
like
it's
alpha
and
earlier
one
like
pre-alpha
or
something
but
yeah
this
these
post,
alpha
ones,
the
ones
that
you
see
as
assigned
are
what
we
will
work
in
this
sprint
in
in
the
next
two
weeks,
and
yet
the
other
post,
alpha
label
issues
are
the
ones
that
we
call
tackle.
Next,
there
is
also
the
the
ones
that
are
labeled
as
beta,
and
those
ones
like
you
know
are
mostly
like
you
know,
polishing
and
making
it
production
ready
and
usable.
C
Like
you
know,
you
know
in
a
more
in
a
more
like
in
an
angry
way,
let's
say
and
yeah.
A
Awesome
yeah
that
sounds
great,
there's
been
tons
of
progress
on
this
like
there's.
I'm
really
really
really
impressed
with
the
effort
from
the
full
team
on
on
getting
this
up
to
up
to
speed
and
running
here
and
ready,
almost
ready
for
you
know
broader
broader
trial
and
usage
of
it
as
well.
If
it's
early
in
its
alpha
phase,
so
this
is
really
cool
to
see
like
so
many
providers,
so
many
resources,
all
that
sort
of
stuff,
there's
a
lot
of
progress
there
and
like
the
xrm.
A
Compliance
of
it
is
something
that
I
find
particularly
awesome
as
well
too,
like
the
the
experience
and
the
economic
surrounding
they're
gonna
be
really
good,
yeah
great
mafik.
Thank
you
so
much
for
the
update
there.
So
then
you
know
the
providers
were
continuing
to
make
progress
on.
It
feels
like
so
many
fronts
right
now,
which
is
really
cool,
but
we're
getting
some
recent
releases
of
providers
out.
A
We
don't
have
to
go
through
each
one
here,
but
there
are
links
we'll
go
to
more
details
on
each
provider
further
below,
but
there
are
links
here
to
each
one
of
the
releases.
The
recent
releases
we've
done
for
azure
aws
htcp.
A
I
think
that
we
can
kind
of
talk
about
each
one
of
the
providers
in
turn
here
and
then,
in
that
context,
for
each
provider
you
know
folks
can
feel
free
to
speak
up
and
voice
some
of
their.
You
know
their
needs
or
requirements
for
each
provider
as
well
too.
So,
let's
do
that
in
these
questions
here
in
context
of
each
one
of
the
providers
that
we're
about
to
go
through.
A
So
let's,
let's,
let's
go
through
each
one
here,
aws
could
be
either
aaron
or
muafik
and
we
don't
have
to
you
know,
click
in
and
go
to
every
single.
You
know
fix
and
thing
that
we're
focusing
on.
But
you
know,
high
level
updates
on
each
service
providers
is,
is
perfect
to
focus
on
right
now.
C
B
C
Regards
to
releases-
maybe
I
can
mention
what's
why
we
did
a
release
of
wider
aws
for
the
last
two
versions,
so
that
there
was
a
bug
in
well,
maybe
like
it
can
be
considered
about
to
some
extent.
A
C
Able
to
get
a
faithful
response
from
the
describe
operation,
so
nick
has
solved
this
problem
on
crosstalk
runtime
level,
fixing
it
like
for
all
resources
and
with
the
test
we
saw
like
you
know,
I
think
it
was
like
mostly
root
table
and
like
some
ec2
resources
that
were
leaking
like
we
would
create
twice,
but
you
would
know
only
one
about
only
one
of
them,
so
this
pr
fixes
them
and
we.
A
C
Two
patch
releases
for
the
two
last
versions
of
aws.
That
includes
it
so
now
we
we
don't
have
that,
like
you
know,
leaking
problem
making
it
like
you
know,
making
it
work
for
eventually
consistently
apis.
A
Yeah,
I
think
that
was
a
really
good
investigation,
first,
starting
with
the
on
the
community
side,
which
was
really
really
useful
to
get
all
that
data
there,
and
so
that
was
really
helpful
and
then
nick
diving
into
this
and
kind
of
fixing.
So
what
we
believe
to
be
some
of
these
root
causes,
I
think,
will
help
out
the
kind
of
reliability.
I
guess
in
more
loaded
stressed
situations,
but
overall
improving
the
reliability
and
consistency
of
the
providers
is
something
that's
really
good.
A
So
yeah
we
did
a
patch
release
for
19.1
in
18.2
for
aws
for
that,
because
that
was
what
we
found
to
be
the
most
affected,
at
least
so
we
can.
We
can
did
that
frostbite
runtime
core
fix
there
will
make
it
into
other
provider
releases
as
as
they
come
in
any
other
big
updates,
aaron
from
you
on
on
aws
or
anything.
You
wanted
to
call
out,
sir.
A
A
A
really
far
away
zip
code,
it's
not
down
the
street,
all
right,
sweet,
okay,
cool
cool!
Then
we
can
go
ahead
on
to
gcp
as
well
hassan.
Do
you
want
to
get
us
up
to
speed
with
what's
going
on
with
provider
gcp.
C
So
the
listed
issues
npr's
in
both
aws
and
gcp,
especially
the
ones
that
are
like
you,
know,
new
issues
and
bugs
needing
attention
into
energy
speed.
C
C
Provider,
aws
updates.
I
think
we
will
be
able
to
get
to
review
them,
but
if
anyone
wants
to,
like
you
know,
give
it
an
earlier
pass
that
would
be
really
appreciated
and
yeah.
I
think
that
the
provided
gcp
employed
gcp
beta,
is
not
something
that
I'm
very
familiar
with.
So
maybe
daniel
could
give
an
update
there.
D
D
We
talked
about
an
rfc
around
breaking
into
a
provider
gcp
and
provider
gcp
beta
and
around
that
time
I
went
ahead
and
made
some
modifications
to
provider
gcp,
basically
to
make
sure
that
we're
only
using
stable
versions
of
gcp
apis,
because
we
found
ourselves
in
a
place
where
we
had
to
pin
the
like
go:
sdk
version
in
provider
gcp,
because
some
some
types
like
gk
cluster
and
node
pool
were
based
on
unstable
api
versions
from
the
sdk,
which
meant
that
we
couldn't
update
the
sdk
to
include
new,
stable
features
and
other
resources,
because
we
had
to
keep
it
pinned
because
it
dropped
features
in
gk,
cluster
and
node
pool.
D
So
obviously,
we
are
kind
of
at
an
impasse
there
and
needed
to
make
some
breaking
changes.
So
those
breaking
changes
have
been
made.
We
have
a
long
list
of
the
api
changes
that
happen
and
then
our
strategy
was
to
take
what
was
existing
for
gk
cluster
and
node
pool
and
go
ahead
and
bootstrap
provider
gcp
beta
with
those
resources.
D
That
being
said,
if
you
were
using
gk,
cluster
or
node
pool-
and
you
want
to
upgrade,
there
will
be
some
manual
steps
required-
or
at
least
that's
the
thought
right
now,
unless,
if
hassan
determines
an
automated
way
to
be
able
to
do
this
and
that
will
most
likely
involve
doing
something
like
cube
control,
get
the
yaml
for
all
of
your
existing
gk
clusters,
save
that
make
one
minor
modification
in
the
group
version,
install
provider,
gcp
beta
and
then
recreate
those
and
have
cross
play
and
assume
control
of
them.
D
So
it's
it's
not
a
super
error
prone
process,
but
there
are
some
manual
breaking
changes
there
and
honestly,
that's
just
been
delayed
for
quite
a
while.
So
it's
kind
of
time
to
do
the
hard
thing
or
bite
the
bullet.
If
you
will
on
this
so
that
will
be
happening
next
week
and
hassan
is
going
to
make
sure
to
exercise
the
different
paths
that
folks
might
encounter
there.
A
And
just
to
emphasize
as
well
too
like
it
is
a
manual
migration
step.
You
know
for
this
transition
here,
but
it
is
a
non-destructive
operation
as
well,
though
too
so
you're
again,
then
you
kind
of
mentioned
that
I
just
want
to
emphasize
that
that
you
won't
lose
any
resources
during
that
migration
at
all.
D
Yes,
if
you
go
through
the
migration
properly,
that's
true.
If
you
try
to
up
upgrade
it's
going
to
fail,
so
we
took
the
approach
of
instead
of
upgrading
and
saying
that
you
know
your
stuff
gets,
wiped
away
or
features
get
dropped.
We're
actually
the
upgrade
will
actually
just
say
like.
I
can't
progress
because
you
know
of
breaking
changes
here.
So
if
you
have
it
like
tagged
to
master
or
something
like
that,
then
you're
gonna
automatically
have
it
break,
which
will
be
a
nice
feature
actually.
D
But
if
you
did
try
to
like
force
that
upgrade,
then
you
could
have
data
loss
so
do
make
sure
to
go
through
that
migration,
if
you're
using
the
affected
resources,
if
you're
just
using
it
for
things
that
aren't
gk,
cluster
or
node
pool,
then
you
can
just
roll
forward
and
you'll
also
get
the
braking
change
notification.
You
can
just
delete
that
crd
and
it'll
recreate
it
so
we'll.
A
D
We'll
have
each
of
the
different
kind
of
like
scenarios
that
you
could
be
in
outline
and
then
what
steps
you
need
to
take
for
those.
A
Sweet
thanks
for
that.
Those
further
details
there,
dan
on
the
provider,
gcp
upcoming
release.
Another
note
we
have
in
here
is
the
provider
kubernetes.
There
is
now
an
official
release
version
out
the
0.1
release,
so
this
is
now
how
sweet
sony
put
a
heart
on
it
and
oh
carl,
nice
to
meet
you.
I
also
heard
this
so
yeah.
A
There
is
now
an
official
release
of
the
provider
kubernetes
functionality
to
to
manage
just
general
generic
kubernetes
api
objects,
so
that's
out
there
and
ready
for
consume
consumption
and
some
adoption
as
well
too,
and
you
know
I'm
happy
to
accept
feedback
on
that
hope.
Just
open
issues
in
that
repo
and
we
can
address
those
al
pair.
Do
you
want
to
give
us
a
quick
update
about
azure
and
the
release
you
did
for
0.17
last
week?
I
think
it
was.
B
Yeah
sure
so,
as
you
mentioned
last
week,
we
have
released
0.17.0
for
provider
azure.
It
contains
a
number
of
important
bug,
fixes
the
global
poll
interval
flag
flag
from
daniel
and
also
a
new
managed
resource
for
configuring,
postgresql
servers
and
it's
ready
for
consumption.
Thank
you.
A
Awesome
yeah
thanks
for
getting
that
out
there
out
there
and
keeping
all
the
all
of
us
for
keeping
all
these
providers
running
as
well,
too
so
sweet.
So
we
talked
about
crosslink
core
1.4
1.5
coming
soon
or
starting
on
we're
starting
to
work
on
that
all
the
providers
we've
gotten
some
updates
on
those
as
well
too.
Any
other
notes
on
releases
milestones:
priorities
roadmap,
all
that
sort
of
stuff.
Before
we
move
to
the
next
community
topics.
A
All
right:
let's,
let's
talk
about
community
topics,
then
here
so
you
know
a
whole
bunch
of
amazing
content
here
in
interesting
talks,
live
streams,
etc.
Victor
do
you
want
to
this
is
a
lot
of
your
content.
Is
here
obviously
you're
doing
an
amazing
job
with
that?
Any
highlights
that
you
want
to
share
with
the
community
about
some
of
your
recent
live
streams
and
other
contents.
B
I
mean
nothing
special,
but
there's
so
many
things
happened
in
the
last
week
or
two
that,
to
be
honest,
I
don't
know
anymore
where
I
was
and
where
I
spoke
and
stuff
like
that.
The
interesting
thing,
probably
the
cncf,
that
was
that
was
really
cool.
If
I
would
need
to
select
one
that
would
be
cncf
and
maybe
the
one
withdraw
code
and
there
is
cncf
next
week
as
well.
So
two
to
two
weeks,
two
cncf
events
come
and
come
and
watch
it.
A
That
sounds
awesome,
yeah,
we'll
make
sure
to
tweet
about
that
and
get
that
out
there
is
there
a
victor
is
there.
I
had
asked
this
before.
I
don't
know
if
you
were
around,
is
there
any
like
the
twitch
episodes
for
cloud
native
foundation?
They
expire
and
they
go
away
after,
like
30
days
60
days,
not
a
very
long
time.
Is
there
something
we
could
do
to
persist
that
or
get
that
on
our
youtube
channel
or
something
so
it
lasts
longer.
B
If
you
get
the
copy,
then
yes,
but
I
think
that
that's
that's
all
that's
in
hands
on
cnc.
I
don't
think
that
we
can
get
it
and
post
it
ourselves,
but
I
think
that
it
was.
I
think
that
that
one
was
on
youtube
as
well.
Oh.
A
Sure
got
it
yeah.
Okay,
I
should
get
a
link
to
that
as
well
too.
Instead
of
linking
to
twitch
good
point
good
point,
yeah
great,
so
you
have
some
some
really
great
content
there.
I
wanted
to
call
out
this
one
as
well
too
so
the
open
core
summit.
This
is
actually
from
2019.
A
I
think
bassam
was
a
keynote
speaker
there
and
was
speaking
about
the
vision
of
the
crossplane
project,
and
so
we
just
recently
uploaded
it,
though
to
our
the
crossplane
youtube
channel
and
it's
actually
a
really
interesting
insight
into
the
longer
term
vision.
For
you
know,
a
control,
plane,
centric
approach
to
managing
your
infrastructure
so
definitely
check
that
out,
because
it's
quite
an
interesting
talk-
and
you
know
it
is
for
2019,
but
it's
it's
like
it's
very
visionary
and
forward-looking.
So
it's
still
quite
applicable
today
as
well
too.
A
If
you
haven't
gotten
a
chance
to
see
that
one
yep
so
we'll
keep
that
pattern
going
there
of
cour,
really
amazing
content
and
educational
experiences
for
everybody,
the
so
incubation
with
the
cncf.
The
vote
did
complete
on
that
one,
and
we
got
more
than
enough
votes
from
the
technical
oversight
committee
members
to
approve
it.
The
official.
A
Yay,
oh
people
have
been
saying
saying:
please
yay
for
months
now,
so
the
the
official
announcement,
though,
will
be
next
week
and
we
there
will
be
many
years
then
so
tuesday
september
14th.
We
expect
to
have
blog
posts
with
cncf
and
the
crossplane
blog
and
some
press
and
analysts
and
stuff
like
that
too.
A
So
a
big
push
will
be
next
week
to
announce
that
more
broadly
across
the
ecosystem,
but
here
in
this
more
intimate
group
of
crossman
community
members,
that
is
the
news
that
that's
that
we're
moving
incubation
and
we're
announcing
it
on
tuesday.
A
So
I
have
this
section
here
that
folks
can
continue
to
add
things
to
it's
intended,
for
you
know
interesting
conversations
and
adoption,
and
you
know
just
genuine
general
things
of
of
notes
across
the
community
that
don't
fit
anywhere
else.
One
thing
I
wanted
to
call
out
that
I
thought
it
was
really
interesting.
Is
that
a
provider
mind
ctl
or
mind?
Cuddle
was
started
just
recently
and
so
myctl
is
like
a
provisioning
tool
for
hosting
minecraft
servers.
A
So
the
author
of
that
chose
to
to
create
a
crossplane
provider
that
does
that
type
of
functionality
of
provisioning
and
managing
like
minecraft
servers.
So
I
think
this
is
super
interesting
adoption
or
scenario
for
for
cross
plane,
so
building
kind
of
a
platform
to
do
this
stuff
for
minecraft.
So
I'm
super
interested
to
see
where
this
goes
and
the
investment
that
gets
made
here.
It's
it's
brand
new.
A
It
was
just
started,
I
think
last
week,
so
there's
gonna
be
more
of
an
investment
in
this,
but
crossplane
will
be
provisioning,
minecraft
stuff
soon
too.
That's
that's,
definitely
interesting.
Anything
else
that
folks,
remember.
Good
conversations
with
community
members
think
interesting
questions
that
have
come
up
on
slack
or
things
of
note.
There.
B
A
That
is
a
really
really
good
question,
so
we
have
done
a
couple
of
things
to
explicitly
address
that
one
of
them
is
that
we
added
some
metadata
information
for
robots
for
crawlers,
the
indexers
from
google
to
say:
do
not
follow
these
don't
index
them,
don't
show
them
anymore.
So
those
are
across
all
of
the
pages
that
are
no
longer
recent
releases.
A
Then
we
went
a
step
further
to
go
ahead
and
remove
old
releases
so
that
only
the
currently
supported
releases
are
on
the
documentation
site
and
we
went
and
requested
with
google
to
re-index
the
site
and
remove
all
the
stale
stuff
from
their
search
results.
Unfortunately,
with
google
there
that
it's
there's
no
guarantee
about
when
those
get
removed
from
the
search
results.
A
So
at
this
point
I
personally
don't
have
a
good
answer
for
how
to
continue
to
get
those
out
of
the
search
results
or
what
we
can
do
next,
because
we've
taken
three
different
steps
and
you
know
specifically
made
a
request
to
google
to
reindex
them.
So
I
definitely
apologize
for
the
hassle.
There's
you're
not
the
first
person
who
said
that,
and
it
is
an
annoying
thing
to
continue
to
get
those
results.
Those
old
results
showing
up.
A
So
I
hope
that
google's
you
know
background
indexing
continues
to
make
progress
on
that
and
if
more
ideas
come
up
that
we
have
to
improve
that
experience,
we'll
definitely
take
them.
But
yeah.
Sorry,
sorry,
that's
been
a
hassle
recently
and
we
hope
to
improve
on
that
still.
If
you
can
make
more
progress
on
that.
A
Yeah,
thanks
for
bringing
that
up,
definitely
appreciate
that
anything
else
that
folks
want
to
want
to
bring
up
today.
A
D
Yeah,
it's
it's
not
a
a
huge
thing
per
se,
but
I
wanted
to
mention
it
because
it
is
interesting
for
some
folks,
I
think,
and
it's
kind
of
in
limbo,
a
bit
right
now.
So
I
thought
I'd
provide
some
context
and
also
if
anyone
else
wants
to
weigh
in
you're
welcome
to
as
well.
So
we
fetch
our
packages
from
oci
image
registries
using
either.
D
You
know
anonymous
credentials
if
it's
a
public
package
which
a
lot
of
ours
are
or
by
using
package,
pull
secrets
where
you
explicitly
create
like
a
docker
credentials
secret
and
put
in
there
and
then
reference
that
you
want
to
use
those
there's,
also
the
ability
right
when
you're
running
on
a
various
providers,
the
ability
to
make
use
of
kubernetes
credential
providers.
So
this
is
what
the
cube
uses
to
pull
images
right
if
you're
running
on
like
gke,
and
you
have
some
gcr
images
or
something
like
that.
D
Go
container
registry,
the
library
that
we
use
to
do
our
or
all
of
our
interaction
with
the
registry.
It
has
support
for
kate's
credential
providers.
So
basically,
there's
like
a
fork
of
the
kubernetes
credential
providers
that
an
individual
maintains
and
is
bundled
in,
and
you
actually
compile
them
in
to
to
your
project
rather
than
just
include
the
library.
So
you
actually
see
in
our
make
file-
and
this
is
what
this
is
changing-
is
the
that
we're
disabling
compiling
those.
D
In
the
reason,
why
is
some
of
you
may
have
noticed
a
few
releases
back
when
we
used
to
get
these
like
spurious
logs
that
were
from,
like
google
and
stuff
saying
you
know
like
failed
to
authenticate?
They
didn't
cause
any
issues,
but
they
were
kind
of
confusing.
That
was
one
reason.
Then
we
also
had
a
crossplane
user
actually
have
this
break
their
crossplane
installation,
because
the
azure
credentials
provider
had
a
bug
in
it
where
it
didn't
have
a
timeout
on
its
on
its
context
that
it
was
passing
for
the
http
request.
D
They
were
running
in
a
firewall
environment,
so
basically
that
that
request
is
hung
forever,
and
so
their
reconciliation
would
eventually
just
time
out
on
its
context
deadline.
So
anyway,
we
just
went
ahead
and
disabled
this
because
it
wasn't
really
a
stated
feature
at
that
time.
I
did
fix
the
azure
credentials
provider,
so
it
will
timeout,
but
it
still
makes
me
a
little
uncomfortable
with
the
fact
that
we
kind
of
like
attempt
to
do
this
credential
authentication
when
we
don't
need
to
so
anyway.
D
The
long-term
solution
here
is
to
fix
upstream,
go
container
registry,
but
we
may
opt
to
enable
or
disable
this
in
the
short
term,
you
can
kind
of
see
my
logic
for
it
written
down
there,
but
I
thought
I'd
bring
this
up
didn't
know.
I
haven't
heard
many
people
asking
for
this
to
be
honest,
but
we
did
have
this
individual,
who
it
actually
needs
it
and
was
using
it,
and
so
just
just
something
to
consider
here.
D
I'm
probably
gonna
see
what
the
effort
is
to
fix
this
and
go
container
registry
or
make
it
a
little
more
ergonomic,
perhaps
and
see.
If,
if
it's
a
ton
of
work,
then
maybe
we'll
go
ahead
and
include
this
for
now.
If
not,
then
I
think
that
we'll
we'll
probably
go
ahead
and
try
to
fix
that
before
re-enabling
this
functionality,
but
if
anyone
has
thoughts
or
any
users
or
needing
this
functionality
feel
free
to
weigh
in
there's
a
corresponding
issue.
That's
linked
as
well.
A
Right
awesome,
dan
thanks
for
that.
The
update
on
that
and
and
get
like
background
context
as
well
too.
A
Okay,
sweet!
So
then,
now
that's
the
end
of
the
agenda
items.
I'm
sorry
for
almost
neglecting
you
dan.
That
would
have
been
ever
so
rude
of
me:
okay,
sweet!
So
I
didn't
sound
like
there
was
other
topics
that
folks
wanted
to
bring
up.
A
So
I
think
we
can
go
ahead
and
adjourn
for
the
week
and
you
know
in
between
community
meetings,
we
are
quite
quite
active
on
slack.crossplane.io,
so
feel
free
to
join
us
there
and
take
the
discussion
there,
and
definitely
thanks
for
everybody
for
joining
in
and
looking
forward
to
another
couple,
a
couple
weeks
of
progress
here
together.