►
From YouTube: 2022-02-10 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
february
10th
2022
cross,
plane
community
meeting
feel
free
to
continue
adding
yourselves
to
the
attendees
list.
Here.
You've
got
that
special
special
resolved
attendee
functionality,
there
you're
the
most
special
one
on
the
list
so
far,
nice
work
thanks
all
right
and
then
so
now
we
can
start
talking
as
usual
about
milestones
and
upcoming
releases,
etc.
A
So
we
are
now
in
the
midst
of
the
timeline
for
the
1.7
release.
We
typically
have
a
two-month
cadence
for
all
of
our
releases.
A
You
can
always
follow
along
with
expected
and
upcoming
releases
in
the
schedule
here
at
crossfit
crossplane
on
the
main
readme
there
in
the
releases
section.
So
we
a
quick
note
there
is
that
we
typically
have
been
doing
releases
near
the
end
of
months
like
around
the
20
low
20s
of
the
month.
A
The
last
release
that
you
know
kind
of
coincided
with
a
lot
of
holiday
breaks,
so
we
pushed
it
to
the
beginning
of
the
month,
beginning
of
the
year
here
around
early
january,
like
january,
4th
or
5th
or
so,
and
so
that
kind
of
shifted
the
release
time
frame
for
for
everything
else
now,
and
so
I
think
we'll
probably
do
that
going
forward.
But
we
erroneously
had
the
1.7
release
mentioned
or
listed
for
the
end
of
march.
Minutes
actually
would
be
the
beginning
of
march
every
two
months,
beginning
of
january,
beginning
of
march.
A
So
that
was
a
mistake
and
we're
rectifying
that
there.
But
there
is
a
bit
of
a
discussion
here,
because
the
general
theme
for
1.7
here
is
that
we're
kind
of
undertaking
some
massive
features,
we're
we're
getting
back
in
the
swing
of
of
putting
investments
into
large
scale,
features
that
are
in
high
demand
by
the
community.
So
that's
super
exciting
to
be
having
a
rich
road
map
that
we're
executing
on.
But
a
lot
of
these
won't
be
making
it
into
a
1.7
release.
A
So
nick
brought
up
a
valid
question
here
on
if
we
should
continue
with
the
1.7
release
or
not-
and
I
was
looking
nick-
I
don't
know
if
you
looked
at
it
too,
but
when
I
looked
at
the
commits
and
such
that
are
in
main
branch
that
would
be
part
of
a
1.7
release.
I
think
that
the
vast
at
least
the
vast
majority
of
those
are
have
all
been
back
ported
to
1.6
and
with
releases
there.
A
So
I
don't
know
of
the
delta
between
main
and
the
1.6,
but
I
think,
like
a
lot
of
them
are
in
1.6.
Did
you
look
into
that
more
deeply
yourself?
Nick.
B
Not
much
more
deeply,
but
I
did
have
a
quick
skim
and
what
you
saw
matches
what
I
saw.
I
don't
there's
nothing
in
there
at
the
moment
that
I'm
aware
of
that
would
count
towards
a
warrant,
so
a
1.7
release.
So
it's
an
interesting
question
generally,
like
I,
I
feel
like
we've
had
a
lot
of
movement
happening
in
providers
lately
with
everyone
having
been
investing
in
interrogating
other
things,
but
then
core
cross
player
has
kind
of
slowed
down.
B
The
last
couple
of
releases
and
we've
had
like
one
or
two
things
in
each
release.
I've
started
to
question
the
sort
of
cadence
that
we
have
releasing
every
eight
weeks,
given
that
we
don't
have
a
ton
in
each
of
these
releases.
I
wonder
if
it's
time
to
drop
down
it's
like
three
times
a
year
or
something
like
that
which
is
kind
of
a
bigger
question.
B
So
I
I
guess
you
know
one
thing
is:
do
we
course
correct
the
mistake
that
I
made
when
I
wrote
that
this
would
be
released
on
march
22
when
it
should
have
actually
been
released
on
last
march?
First,
if
it's
march
22,
I
feel
slightly
better
about
like
the
thing
that
sergeant
and
I
are
working
on,
which
is
custom,
compositions
no
guarantees,
but
I
feel
slightly
better
about
that
being
in
1.7
as
an
alpha
very,
very
early
feature.
C
Yeah,
the
there
are
also
other
a
few
other
features
as
well
that
we
could
get
into
the
1.7.
I
think
hassan
is
working
on
external
secret
stores,
I'm
not
sure
like
if
it's
going
to
make
it
to
that
time,
but
for
webhooks
that
I'm
working
on,
I
believe
we
would.
We
would
be
able
to
have
a
a
provider
using
that
functionality
from
crosspin
runtime
and
package
manager
and
everything
having
some
kind
of
web
hook
like
immutability
check,
etc.
C
So
I
would
be
in
favor
of
doing
that
change,
but.
D
Okay,
I
would
just
ask
like
maybe
I'm
talking
about
postponing
or
delaying
it
to
march
22
like
the
release
day
and
I
think
two
weeks
before
his
future
freeze.
So
we
are
kind
of
like
talking
about
making
it
ready
for
the
first
week
of
march
right
so.
D
So,
in
that
case
I
I
would,
I
would
totally
be
in
favor
of
that,
and
I
would
like
give
it
a
try
to
make
an
initial
alpha
release
of
external
secret
stores.
Given
like
it,
we
couldn't
roll
out
to
all
providers.
Maybe
I
just
like
mentioned:
we
can
at
least
have
it
for
one
provider
and
get
some
early
feedback.
B
B
The
provider
releases
decoupled
from
crossplane
releases,
and
you
know
we
really
consider
some
providers
having
a
feature
to
be
like
a
thing
that
is
associated
with
costly
1.7.
B
So
I
know
that
for
secret
stores,
part
of
that
will
affect
core
cross
plate
as
well,
because
we
need
to
do
that
for
the
composite
resources
and
whatnot
custom
composition
is
definitely
going
at
1.7.
It
sounds
like
webhooks
might
be
more
of
a
provider
thing
than
something
that's
built
into
core.
What
do
you
think
of
that?.
C
A
And
what
you
said
there
would
be
package
manager
changes,
though,
as
well
to
like
deploy
the
maybe
the
infrastructure
that's
needed
for
for
for,
like
web
hooks
and
like
some
of
the
commonality
there
or
I
haven't,
looked
I'm
not
up
to
speed
on
the
architecture,
so
I
might
be
wrong
about
that.
Yeah.
C
E
I
only
have
one
thing
in
this
milestone
and
it's
just
adding
the
support
for
the
annotations
to
be
able
to
specify
a
layer
in
your
package
image
which
supports
the
the
provider
fat
packages
which
I'm
not
concerned
about
getting
in
on
any
of
these
dates,
really
because
it's
not
a
huge
change.
E
That
being
said-
and
this
may
be
somewhat
in
contrast
to
what
some
folks
have
said-
but
I
would
advocate
first
going
ahead
and
having
the
conversation
about
formally
changing
the
release
process
to
trimesters
or
something
like
that,
rather
than
making
a
one-time
exception,
I
think
that
does
a
better
job
of
communicating
to
the
community
when
things
are
going
to
arrive,
I'm
a
little
nervous
about
saying
like
well.
E
You
know
this
one
is
going
to
be
a
little
bit
later
and
obviously
there's
context
around
that,
but
I
think
having
a
reliable
release
date
and
not
necessarily
changing
it.
When
folks
may
be
expecting
you
know
a
small
bug
fix
or
something
like
that
or
a
feature
that
was
seems
minor
to
others,
basically
having
some
reliability
around
when
things
are
going
to
be
released
and
not
get
delayed.
For
you
know,
some
features
that
an
individual
or
a
group
or
something
like
that
wants.
B
So
I
I
broadly
agree,
but
given
the
context
around
this
wherefore
many
weeks
now
for
the
whole
time,
the
thing
has
said
march
22nd
and
I
don't
think
anyone
but
maintainers
have
noticed
that
that
date
was
incorrect.
So
just
to
be
clear
here,
if
folks,
you
know
just
to
be
explicit,
it
should
have
been
due
in
march.
First,
we
released
in
eight
week
cycles
when
I
did
the
math
to
figure
out
what
was
eight
weeks
after
the
last
release.
B
Somehow
I
added
a
bunch
of
weeks
and
wrote
down
on
march
22nd,
so
it's
just
a
mistake
on
my
part,
but
that
is
the
date
that
we
committed
to.
That
is
the
date.
That's
been
written
down.
So
while
it's
not
eight
weeks,
I
imagine
that
most
folks
probably
are
expecting
march
22nd
rather
than
having
you
know,
be
like
wait
a
second
and
like
mastered
and
been
like
that's
the
wrong
date.
So
I
feel
pretty
good
about
just
keeping
march
22nd
personally.
B
Because
it
gives
us
that
little
bit
of
extra
wiggle
room
to
maybe
get
some
more
stuff
into
this
release,
ramping
up
out
of
the
holidays
at
the
start
of
the
year
and
what
not
a
lot
of
companies,
including
my
own,
are
doing
q1
planning
that
you
know
slows
things
down,
but
I
agree
with
dan
that
I
would
also
like
this
is
not
the
first
time
we've
had
a
release
of
cosplay
in
recent
months
that
has
been,
you
know,
only
had
one
or
two
big
features
in
it,
so
I
think
I
think
we
have,
you
know,
slowed
down
and
hit
the
point
where
there's
just
not
that
much
changing
in
cross
plane
core,
don't
get
me
wrong.
B
We
have
great
ideas,
there's
many
more
features
to
come.
We
want
bug,
fixes
in
there
etc,
etc.
But
it's
not
the
pre
1.0
days
where,
like
there's
like
700
new
features
in
every
release,
so
I
I
personally
would
push
for
changing
to
every
to
a
trimester-based
release
cycle
yeah.
Do
you
think
that
we
had
discussed
this
in
the
past,
though?
And
there
was
kind
of
a
feeling
that
we're
like
just
on
the
cusp
of
like
a
bunch
of
people,
spending
much
more
time
on
call
cross
playing
having
like,
especially
from
the
folks.
B
Those
of
us
who
work
at
outbound,
we're
busy
with
with
terajet
and
they've,
got
that
in
a
sort
of
a
decent
state
sort
of
thing
and
sort
of
looking
for
other
work
to
do
so.
I
feel
like
last
time
we
discussed
this,
which
I
forget:
what
forum
was
it?
There
was
a
bit
of
a
sense
of
like
you
know.
We
want
to
keep
the
eight-week
releases
because,
because
we
do
actually
feel
like
we're
going
to
be
wanting
to
ship
stuff,
pretty
pretty
swiftly.
E
Yeah,
I
I
think
it
sounds
like
a
it's
a
bit
of
an
open
question,
but
just
just
to
I
guess
be
clear.
Where
I
stand,
I
don't
feel
good
about
march
22nd
as
a
date,
because
that
seems
like
a
cadence
that
we
would
never
do
like
that's
like
10
or
11
weeks,
or
something
like
that.
So,
unless
we
think
we're
going
to
do
that,
I'd
advocate
for
bumping
it
out
to
like
later
than
that
to
be
online
with
our
new
schedule.
E
E
B
E
Yeah,
I
I
I
get
that
kind
of
like
strategy
as
well.
I
guess
I'm
also
looking
at
like
we
have
written
down
elsewhere
that
we
release
every
eight
weeks
and
that
sort
of
thing
which
that
would
also
be
incorrect.
If
we
move
to
the
trimester,
you
know
so
point
point
taken
for
sure
I
think
yeah
I
I
guess
I
I
would.
I
would
want
us
to
maybe
explore
at
least
going
to
the
trimester
now,
if
we
think
that's
what
we're
going
to
do,
but.
A
And
I'd
actually
be
I'm
probably
not
in
favor
of
going
to
a
trimester
schedule,
because
things
are
ramping
back
up
and
more.
You
know,
commitments
and
features
are
being
you
know
dedicated
to
right
now,
so
I'd
actually
want
to
keep
the
same.
You
know
like
if
give
me
march
22nd.
That
was
what
was
put
down.
That's
what
we've
been
kind
of
publishing
and
stick
with
that-
that's
okay
for
me,
but
then
from
there
then
keep
the
same,
published
cadence
of
eight
weeks
cycle
after
that,
because
I
feel
like
the
velocity
is
picking
up
again.
E
Gotcha
in
that
context,
I
think
potentially
that
would
make
sense,
then
yeah.
So
I
don't
know
I
it's
it's
an
open
question.
I
guess
sort
of.
I
just
want
us
to
maybe
consider
what
we're
gonna
do
and
let
that
maybe
play
into
the
decision
we
make
here.
B
Yeah,
I
I
feel
pretty
sold
on
keeping
march
22nd
unless
anyone
else
strongly
descends
with
that,
I'm
not
as
convinced
that
sticking
with
eight
week
release
cycles
makes
sense,
just
having
seen
us
go
through
three
to
four
releases
with
that
are
pretty
light
on
the
ground.
B
I
I
don't
really
want
to
make
the
decision
in
this
meeting,
though
I
I
do
wonder
if
there's
there's
some
way
to
do
effectively
a
one-pager
or
some
kind
of
you
know
something
somewhat
data-driven
to
figure
out
like
how
you
know
whether
it
would
significantly
impact
anyone,
a
community
survey
or
something
like
that
to
you
know
see
if
changing
the
release,
frequency
might
might
make
sense.
C
Yeah
yeah
I'm
I'm
kind
of
on
the
similar
page
with
jared.
I
think
much
too.
Energy
was
fine
because
we
communicated
it,
but
I
would
also
like
you
know,
be
in
favor
of
more
like
the
eight
weeks
cadence
essentially
and
to
see
like
you
know,
because,
like
you
know,
to
see
hey
like
you
know,
we
are
added
eight
weeks
and
we're
still
not
investing
or
something
so
but
like
that.
That
is
not.
That
would
not
be
the
change
now
and
we
already
have
like
you
know,
new
features
plated
so
yeah.
B
Okay,
well
one
way
we
can
address
this
yeah
I'll,
open
an
issue,
and
maybe
we
can
set
a
check-in
date
effectively
to
say
that
in
a
quarter
from
now
or
six
months
from
now,
if
we
look
back-
and
we
really
have
only
been
shipping
like
a
feature
with
each
release
or
something-
maybe
then
you
know.
Basically,
if
we
don't
see
the
acceleration
that
we're
forecasting
that
we'll
see
over
the
next
couple
of
releases,
then
then
maybe
we
should
consider
slowing
down
to
try
best
early
cycles.
B
B
And
like
it
happens,
right
like
when
you're
post
1.0
like
you're,
not
just
watching
like
headline
new
feature
like
every
release,
sort
of
thing
every
like
in
a
couple
of
weeks.
So
so
I
think
it
is
totally
fine
to
slow
down
as
well
on
this
I'll.
Take
an
action
to
go
and
just
put
a
tracking
issue
for
us
to
come
back
and
reassess
in
let's
say
six
months
or
something.
E
So
we
decide
march
22nd
for
this
one
and
future
discuss
any
changes
to
cadence
yeah.
E
A
E
A
Okay
cool,
so
then,
let's
let's
commit
to
that
then
and
we'll
stick
with
it.
This
will
also
I
was
going
to
try
to
spell
serendipitously.
Let's
just
keep
that
word
out
of
this
completely
enable.
A
A
Okay
cool,
so
I
think
you
know
we
can
pick
up
the
pace
a
little
bit
here,
but
yeah.
So
you
know
I
some
of
the
big
things
here
that
we've
talked
about
are
on
the
road
map
here,
such
as
custom
compositions
that
are
getting
seregan
and
nick
dedicated
to
that
right.
Now,
external
secret
stores
that
hassan
is
dedicated
to.
A
I
don't
know
what
that
noise
was
downstairs.
Something
just
fell.
That's
kind
of
scary.
The
the
plugable
like
web
hooks
converted
workbooks
et
cetera
framework
that
moffix
doing
what
else
is
is
big
on
the
road
map
here
that
the
resources
are
getting
dedicated
to
that
we
want
to
bring
up.
C
We
can
okay,
so
in
progress
means
implementation.
I
guess
right
not.
Act
in
design
like
active,
designing
is
probably
under
in
design
column.
C
A
Did
I
miss
any
the
major
features
that
are
you
know
at
least
getting
early
starts
design
or
alpha
level
support
in
1.7?
Did
I
miss
any.
C
Actually,
there
is
one,
so
it's
so
so
you
see
a
consider
allowing
provider
partition
on
provider
config.
Yes,
so
this,
but,
like
you
know,
this
specific
issue
is
about.
Like
you
know,
a
feature
request
and
an
issue
that
will
be
opened
by
alpha
will
actually,
like
you
know,
ask
the
question
of
ask:
will
state
the
problem
that
this
specific
issue
is
solving,
so
that
issue
is
going
to
be
like
you
know
the
start
of
that
work
like
you
know,
hey.
C
We
buy
identity,
configurations
of
cloud
providers
and
how
we
can
resolve
it,
and
this
is
like
one
of
the
proposed
solutions,
so
I
think
in
the
next
community
meeting
we
will
be
able
to
move.
We
will
be
able
to
have
that
issue
and
then
put
it
under
indesign.
A
No,
that's
not
well
you
could.
I
think
you
could
do
that
with
the
old
boards
too,
but
no
okay,
but
yeah.
So
when
opera
makes
progress
on
that
one,
then
we
can
get
that
included
in
there.
Yep
cool,
okay,
anything
else
for
core
crosswind
crosstalk
runtime
to
bring
up
before
we
move
on
to
providers.
A
All
right:
let's:
let's
go
ahead
and
move
on
to
waffle,
crease,
hey
something.
C
A
Sounds
good
all
right,
so,
let's,
let's
start
with
providers-
and
you
know
we
had
talked
last
time
about
the
you
know
major
announcements
of
the
jr
jet-based
providers
being
you
know
available
now
and
you
know
folks
starting
to
use
those
get
feedback
et
cetera.
So
let's
get
another
update
here
on
everything.
Since
the
last
community
meeting
and
welfare.
C
A
C
Sir
yeah,
I
can
give
some
updates,
so
the
first
one
is
using
schema
from
cli,
which
is
hassan,
is
working
on
and
finishing.
C
It's
essentially
like
now
right
now,
we're
importing
telephone
provider
code
code
bases
to
get
the
schema
indigo,
but
we're
moving
to
a
model
where
we
have
where
we
use
terraform
cli
to
give
us
the
schema
json,
and
then
we
use
that,
as
as
the
input
for
for
our
schema
generation,
which
would
enable
us
not
having
to
import
those
providers
which
usually
has
like
you
know
quirks
around
like
dependencies
or
somehow,
internal
and
stuff,
I
mean
hassan
king
can
go
into
more
detail,
actually
he's
here.
C
D
Yeah,
actually,
you
pretty
much
described
the
the
work,
but
maybe
I
can
like
just
say
that
it
is
kind
of
solving
the
most
problematic
part
of
generating
your
providers
with
terajet
and
yeah,
even
like
the
guide
is
being
updated
in
the
same
pr,
and
you
can
see
the
difference
in
the
guide
as
well
yeah.
I
hope
it
will
be
ready
next
week
or
so.
A
C
Yeah
yeah,
all
right
so
for
the
second
one
that
is
about
a
well-rated
use
of
long-running
provided
up
server.
So
that's
something
alpha
is
working
on,
so
in
terraform,
when
you
run
a
terraform,
apply
it
spins
up
a
new
grpc
server
that
is
provider
talks
with
it
and
only
shuts
it
down.
C
So
what
we're
evaluating
right
now
there
is
a
mode
of
terraform
that
we
can
keep
a
provider,
give
server
up
all
the
time
and
terraform
cli
executions
would
would
just
talk
with
that
single
provider
server,
so
we
wouldn't
pay
the
cost
of,
like
you,
know,
bringing
it
up
and
down
and
also
the
memory
usage
of,
like
you
know,
different
grpcs,
like
multiple
grpc
servers
for
telephone
providers
working
at
the
same
time.
C
So
that
is
that
also
has
an
issue
that
I
will
link
in
a
second
but
yeah.
It's
got
the
images
ready
and-
and
we
are
right
now-
testing
whether
it
is
actually
worth
doing
that
because
it's
not
like
you
know
the
production
mode
of
terraform.
It's
more
like
you
know,
a
development
feature
that
is
not
documented,
so
yeah.
C
B
C
Yeah
yeah:
well,
not
not
the
exactly
the
same
pattern
because
he
was
he
was
keeping
the
grp
server
and
talking
to
it.
What
we're
aiming
here
is
that,
like
you,
know,
we're
going
to
keep
grpc
server
and
pass
a
flag
to
terra
from
cli,
actually
to
always
talk
to
that
grpc
server
instead
of,
like
you
know,
spinning
up
and
down,
like
you
know,
new
servers
for
each
request,
yeah,
so
so
the
next
one
is
crd
scaling
status
update.
C
So
if
just
to
recap,
we
had
some,
like
you
know,
scaling
problems
in
kubernetes
regarding
the
number
of
cids
that
we're
deploying,
which
is
over
500
for
certain
jet
providers.
So
there
are,
there
were
three
main
problems.
C
One
was
there
was
a
peak
during
the
installation,
time
related
to
open
api
aggregation
of
the
schemas
that
would
like
you
know,
make
your
cluster
unusable
for,
like
you
know,
40
to
50
minutes,
because
it
would
just
eat
all
of
your
cpu
and
a
lot
of
memory
and
cloud
providers
would
try
to
scale
up
the
data
api
servers
and
during
that
time
you
would
get
like
you
know,
timeouts
and
stuff,
and
that
problem
is
fixed.
C
So
we
have
accelerated
process
or
patching
process
of
that
fix
and
it's
got
into
like
you
know
several
patch
release
and
major
release
of
123..
So
that
is
good,
but
the
other
two
problems.
One
was
continuous
load
on
the
api
server.
C
C
What
we
have
seen
is
that
the
the
patch
versions
made
it
to
club
providers
and
then
now
we
have
started
like
you
know,
I
I'll.
I
believe
he
was
going
to
open
an
issue
today,
but
he
will
probably
open
it
in
the
next
hour.
So
I
I
can
link
it
here
again
to
share
the
data.
What
we
see
right
now,
we
don't
have
the
peak
of
cpa
usage,
but
some
of
the
providers
like
gke,
zonal
and
gk
regional.
C
Those
are
those
like
you
know,
really
low
resources
and
the
scale
up
process
takes
takes
quite
a
few
quite
a
time.
So
in
gk
zone
regional,
you
would
still
see
some
like
you
know
you
would
get
into
repairing
state
for
a
while
and
then
after
the
scaling
up
is
done.
C
There
is
no
problem
like
you
know
about
them
being,
like
you
know,
in
a
repairing
state
or
something
it's
just
about
like
how
they
handle
internally
the
scaling
up
the
api
server
for
the
increased
memory
usage,
which
is
like
a
pretty
parallelizable,
because
it's
just
about
http
endpoints
having
memory
footprint.
C
As
far
as
we
know
at
this
point,
and
that
makes
client
more
link
effects
go
so
when
you
have
a
slow
api
server,
then
client
scrolling
is
even
worse,
because
now
every
call
takes
more
time
instead
of
20
seconds
you
get
like
you
know,
one
or
two
minutes
in
some
cases,
so
yeah.
So
what
what
has
changed
from,
like
you
know
three
months
ago,
is
that
we've
got
the
inversions.
Now
we
don't
see
the
peak,
but
the
continuous
makes
it
makes
some
of
the
api
server
implementation
sweat
as
well.
C
So
what
we're
going
to
do
is
to
actually
write
a
design
dock
with
one
page
or
design
dock
that
will,
like
you
know,
list
all
those
findings,
everything
we
have
so
far
and
then
add
some
tooling
to
reproduce
these
problems
and
some
ideal
cri
exit
criteria,
like
you,
know,
hey.
This
is
the
request
time
that
we
will
say.
Okay,
like
you
know,
we
don't
have
that
problem
anymore
and
the
tools
to
produce
reproduce
that
and
test
it.
So
that's
what
we're
going
to
do
and
you
will
see
more
details
on
the
issue.
C
Yeah
yeah,
that
was
a
that
was
a
long
update.
Sorry
if
if
that
was
too
long,
so
yeah,
and
just
to
note
this
effects
only
so
we
have
integer
providers,
we
have
two
versions,
one
with,
like
you
know,
slash
preview
suffix,
which
has
all
the
crds
aws
750
or
something,
but
we
also
have
the
normal
version
where
we
include
only
the
configure
resources,
which
is
not
that
much
that
many,
I
think,
the
maximum
we
have
they're
like
115.,
so
it's
safe
to
use
that
use
those
right
away
yeah.
C
So
I'm
moving
on
to
the
next
one
release.
Cadence,
so
we
had
a
discussion
about
like
you
know,
so
the
jet
providers
get
like
with
one
pr
you
can
configure
like
you
know.
15
is
15
or
20
resources
and
it
would
get
they
would
get
to
be
one
alpha.
Two
and
the
question
would
be
like
you
know:
hey,
should
we
release
now
or
like
you
know,
should
we
like
you
know?
What
do
we
do?
C
How
do
we
make
it
to
the
hand
of
the
users
so
that
issue
this
discusses
release
cadences
for
the
the
the
most
popular,
the
three
most
popular
club
providers
providers
so
yeah?
That
is
I
in
that
issue.
I
have
suggested
I
believe,
six
weeks
but
feel
free
to
chime
in
I
believe
next
week
we
will
wrap
that
issue
up
and
add
it
to
the
readme
of
those
jet
providers
that
they're
going
to
be
released
for
every
six
weeks
and
yeah.
I
think
that's,
that's
that's
it
for
the
updates
hassan.
C
D
Really
maybe
we
can
just
mention
that,
like
there
are
a
good
number
of
projects
that
started
using
erajet,
I
think,
as
per
github,
it
says
there
are
35
repositories
that
depends
on
target
as
of
today.
So
it's
we
see
a
good
five.
D
C
E
A
Yeah,
it's
accelerating
a
lot
of
the
you
know,
integration
efforts
here,
it's
it's
absolutely
accelerating
things,
that's
fantastic
cool!
Those
are
really
useful
updates.
Thank
you
for
sharing
all
those
about
the
you
know.
Third
updates
really
good
context
to
share
awesome.
So,
let's,
let's
keep
on
moving
here
and
so
other
release.
Recent
releases
of
providers
so
daniel.
You
added
that
there's
the
first
official
release
of
digitalocean.
F
Yes,
just
based
features
like
droplets,
grannies
clusters
and
database
clusters.
A
That's
fantastic
man.
Do
you
do
you
have
a
couple
of
ideas
already
of
like
what
other
support
will
be
coming
down
the
pipeline
in
the
next
releases.
F
Yeah,
since
the
standard,
my
heart
since
I'm
on
the
storage
team,
we'll
be
doing
spaces,
which
is
our
s3,
offering,
as
well
as
adding
some
extra
database
features
such
as
like
database
users
and
things
that
nature
and
then
to
hark
on
the
turn
out,
hark
on
that
to
add
to
the
terror
jet
working
on
the
using
our
terraform
provider.
Since
it's
fairly
up
to
date.
To
then
do
also
a
digital
terror
jet
provider.
I
can
add
to
the
the
speed.
D
C
Yeah,
I
was
actually
going
to
ask
I
I
believe
daniel.
It
was
you
that
we
had
a
chat
in
the
cross
playing
slack
about,
like
you
know,
mixing
them.
So
sorry,
if
I
missed
like,
did
you
give
an
update
about
this
or,
like
you
know,
do
you
plan
to
do
that
or
like
no?
What
are
your
thoughts
about
about
that.
F
I
think
for
now
we
were
going
to
keep
them
separate
until
we
can
look
specifically
into
it.
I'm
more
interested
in,
like
I
say,
the
the
failings
of
the
therajet
or
why
you
would
choose
one
over
the
other
and
then
once
I
once
I
can
more
easily
identify
that
trying
to
then
bake
that
into
the
terajet
provider.
Instead
of
maintaining
two.
A
Good,
okay,
so
then
provider
aws
the
0.24,
is
plans
to
go
out
today.
So
if
you
know
christopher,
if
you
want
to
share
some
more
context
on
that
one,
what's
important
what's
in
that
one
and
then
also
in
the
context
of
if
there
are
breaking
api
changes
associated
with
it,
then
that
would
be
great
to
know
too.
G
C
Yeah
yeah,
I
believe
there
are
lots
of
news,
new
resources
in
this
release
as
well
and
also
against
enhancements,
especially
regarding
the
rds
and
as
christopher
mentioned.
It's
like
you
know,
a
lot
of.
C
We
want
better
one
level
support
for
some
for
some
of
the
resources
so
yeah,
and
there
was
there
was
one
thing
about
this
release-
is
that
it
was
actually
supposed
to
go
out
yesterday,
but
I
I
wanted
to
include
those
be
one
better,
one
changes
which
are
like
non-risky
at
all
into
this
release,
and
I
was
like
no
out
of
the
office
yesterday,
so
we
we
were
cutting
it
today,
which
is
communicated
in
the
issue,
so
yeah
no
breaking
changes
as
christopher
said.
A
A
Yeah,
and
so
so,
for
the
the
resources
that
are
maturing
to
beta.
Can
you
give
me
just
like
a
30-second
refresher
update
of
what
actions
like
consumers
of
those
resources
would
need
to
do
to
start
using
the
beta
ones
in
in
their
environments?
If
they're
already
out
and
running.
C
Yeah,
so
the
there
are
two
actual
two
cases
that
we
handle.
One
is
that
you
have
existing
resources
with
those
like
ssns
subscription
and,
like
you
know,
vp
ceiling
and
other
stuff,
so
they're
not
gonna
break
at
all.
They're
they're
gonna
keep
working
and
you
will
have
the
chance
to
like
you
know
you
will
have
the
instructions
to
make
them
like.
C
You
know,
for
the
sns
ones
to
to
use
the
new
versions,
be
one
better
one,
because
they
they
got
a
rename
as
well
for
others
they
will
just
saved,
as
we
want
better
one
to
the
api
server.
So
you
can
still
like
you
know.
V1
alpha
one
is
still
served,
but
you
can
just
start
use
in
your
new
yaml,
so
you
can
use
start
usb
one
better
one.
So
the
only
action
you
need
to
take
I
mean
not.
C
You
don't
need
to
take
it
right
now,
which
is
like
you
know
what
makes
it
non-breaking
they're
all
still
served,
but
in
the
future,
at
some
point
we
will
drop.
We
want
other
one
schema,
so
it's
advised
that
you
move
to
the
new
version
in
your,
like
you
know,
in
your
file
system
in
your
yaml,
because
in
a
city
it's
already
converted
by
the
api
server
and
for
the
sns
ones,
old
ones
will
still
work
which
is
not
similar
to
iam.
C
C
C
C
Yeah,
which
will
like
you
know,
give
people
more
time
to
move
it's
I
mean
just
just
typically
like
because
this
will
be
one
alpha
one.
We
did
not
really
have
to
do
that,
but
we
got
like
you
know
some
feedback
from
the
community
that
it's
it's
easier
to,
like
you
know,
have
one
or
two
releases
of
time
at
least
to
do
those
migrations,
even
though
they
are
aviva
alpha
one
because
they're
just
they
have
been
only
one
of
them
for
a
really
long
time.
A
That
that
sounds
good
and
then
being
very
proactive,
a
bike
in
the
release,
notes,
etc.
To
say
hey,
you
know,
these
are
the
chains
that
are
making
you
don't
have
to
right
now,
but
you
know
doing
it
sooner
than
later.
So
it's
not
like
a
fire
drill
when
you
know
we're
finally,
completely
obsoleting
them
and
removing
them.
Then
you
deal
with
them,
then
like
being
proactive
about
it
is
very,
is
a
better
situation
to
be
in
yeah
cool.
Okay,
that's
great!
A
Thank
you
for
that
explanation,
christopher
anything
else
to
add
for
from
you
on
friday,
aws,
so
any
new
features
anything
you
want
to
call
out.
G
A
I'm
not
I
I
remember
seeing
like
something
in
some
other
docs
that
was
old,
that
we
just
this
needs
to
be
updated,
but.
C
A
Christopher,
if
you
want
to
drop
a
link
to
that
right
right
here,
then
that
sounds
like
something
that
the
community
keeps
running
into
it,
that
we
definitely
should
fix.
G
G
Yeah
because
we
see
really
very
often
the
old,
iam
resources.
And
then
you
know
that
this
because
of
the
using
what
providers.
A
Yeah
yeah
exactly
and
I've
run
into
that
a
couple
times
of
you
know
something
not
like
a
composition.
You
know
not
getting
rendered
out
because
that
that
old
I
am
resource,
doesn't
exist
or
the
identity
resource
as
it
were.
You
see
that
immediately
you're,
like
oh
dang,
I
know
what
this
is.
Yep
good
point,
man
good
point,
christopher,
okay,
cool
hassan:
do
you
want
to
get
us
a
quick
on
provider
gcp.
D
Yeah,
actually,
there
are
not
too
much
activity
on
provider
gcp
site,
but
there
is
a
long
like
running
issue
like
requested
by
a
couple
of
people
which
is
supporting
workload.
Identity
similar
to
provider.
Aws
does
so.
There
is
an
open
pr
for
that.
Thanks
for
opening
that
from
like
it
is
a
like
pr
coming
from
community,
so
it
is
ready
for
merch,
I'm
expecting
it
to
get
merged
in
the
following
days
and
right
after
it's
merged.
D
I
think
we
will
cut
the
release
in
in
provider
gcp.
So
that
is
also
another
thing
to
expect.
A
Yeah,
I
was
really
excited
to
see
that
pr
as
well
or
to
you
know
enable
identity
stuff
too.
That
was
pretty
cool,
okay,
cool
yeah,
so
it'll
be
conscious
of
time.
So
15
minutes
left
here.
Let's
keep
keep
on
moving
is
for
provider.
Azure
is
sergeant
here
to
give
a
quick
little
update
on
that
one
or.
C
I
I
added
that
actually,
so
I
think
sergey
know
that
they're
not
here
at
this
moment,
but
one
of
the
big
things
that
that
we
might
start
doing
it.
It's
not
for
certain
yet
is
that
we
we
might
be
able
to
move
to
the
new
azure,
identity,
libraries
and
apis.
C
C
I
think
there
are
other
updates
as
well,
but
that
is
what
I
had
in
mind.
A
Thanks
for
sharing
that,
then,
on
their
behalf
dan,
you
wanted
to
talk
about
fat
packages.
E
Yeah
since,
since
we're
pretty
far
along
I'll,
keep
this
really
short,
but
basically
now
that
we
support
them,
it
would
be
in
my
mind-
and
I
think
in
some
other
folks,
mind
a
simpler
experience
to
for
there
just
to
be
one
image
produced
for
a
provider
on
a
build
and
be
able
to
push
that
there
is
some
tooling
that
needs
to
go
in
place
to
make
that
a
reality,
but
we
could
likely,
since
all
of
the
providers
are
using
similar
tooling,
introduce
that
pretty
quickly.
E
It
also
would
be
backwards
compatible
because
of
the
fact
that
you
can
omit
the
controller
image
now
so
just
because
we
supported
them
doesn't
mean
that
you
couldn't
use
them
with
old
versions
of
crossplane.
So
anyway,
if
people
have
big
concerns
about
doing
that,
for
some
reason,
which
I
certainly
don't
anticipate.
But
if
you
do
please,
let
me
know.
A
Good
day,
I,
like
the
the
thinking
on
that
one
perfect
all
right.
Keep
on
moving
along
here.
Nick
looks
like
you
inserted
something
at
the
top
of
the
community
section.
B
I
have
to
head
off
in
a
minute,
so
I
wanted
to
get
this
in
just
a
heads
up
that
there's
something
that
jared
and
bassam-
and
I
who
are
the
we
have
a
steering
committee
for
this
project
who
sort
of
the
leadership
of
the
governance
team.
So
we
help
maintainers,
coordinate
across
repositories
and
just
you
know,
sort
of
act
as
tie
breakers
and
in
the
case
that
there
are
disagreements
which
I
think
has
ever
actually
happened.
B
So,
as
is
hypothetical,
but
we
were
chatting
the
other
day
and
we
kind
of
realized,
there's
not
any
great
forums
to
get
in
touch
with
the
steering
committee
for
for
cross
play.
If
folks
want
to
reach
out,
you
know
we
see
every
now
and
again.
You
know,
folks
from
other
open
source
projects
wanting
to
chat,
and
you
know
figure
out
hey
you
know.
Is
there
a
way
for
our
projects
to
collaborate
or
something
like
that?
B
And
you
know
we
think
the
steering
committee
is
a
good
place
for
those
folks
to
go
among
other
use
cases.
So
a
long
story
short
we're
doing
a
little
bit
of
improvement
on
the
steering
committee
and
two
things
that
are
very
likely
to
happen
as
one
we're
gonna
have
some
more
obvious
forums
to
get
in
touch
with
us,
rather
than
just
like.
B
I
don't
know,
dming
jared
and
disarmed
I
on
on
slack,
so
we'll
probably
set
up
separate
steering
committee
sessions
from
from
these
community
meetings,
as
well
as
have
like
a
mailing
list
or
something
to
contact
us,
and
the
other
thing
that,
for
the
other
first
thing
that
we
identified
that
we
want
to
do
is
we've
never
really
made
an
easily
discoverable
charter
for
the
crossblade
project
like
to
sort
of
really
specify
it's
its
vision
and
what
it's
for?
B
It's
pretty
easy
to
discover
what
it
you
know
what
it
is,
it's
kind
of
at
the
top
of
our
readme
and
it's
in
the
cncf
documents
we
put
together,
but
we
are
going
to
actually
or
I
am
going
to
take
a
password
writing
a
charter
this
week.
So
just
a
heads
up
look
forward
to
some
more,
I
don't
know
a
more
active
steering
committee,
but
going
forward.
A
Arthur
nick
thanks
for
sharing
that
update
there
cool,
then
I
I
like
this
section
here
every
week
where
we
I've
collected
all
the
different
writings
and
blog
posts
and
live
streams
and
videos
etc
about
crossplane.
We
don't
need
to
get
into
all
of
these,
of
course,
but
they
are
all
available
here
for
your
perusal
if
you
want
to
dive
into
them.
A
A
special
note,
I
think,
are
the
part
two
and
part
three
of
the
geek
dives
into
the
terror
jet
providers
and
run
time
that
hassan
and
alper
wrote
muaffik
had
done
part
one
of
the
deep
dives
and
that
was
available
for
the
last
community
meeting,
so
you
can
refer
to
it
there,
but
then
part,
two
and
part
three
are
out
now
dan
wrote
a
particularly
interesting
blog
post
about
the
missing
kubernetes
type
system.
A
A
A
Nate
worked
on
a
reference
platform,
a
configuration
package
for
azure
to
join
the
the
other
ones
that
we
have,
such
as
you
know,
aws
gcp,
a
multi-cloud
kubernetes
one
etc.
So
you
can
read
about
that
that
latest
reference
platform
too,
that
they
wrote
about
cool
and
then
yeah
some
other
great
stuff
there.
Obviously,
so
all
the
links
are
available,
so
custom
compositions
work
has
started
on
this
in
in
earnest
now
and
so
nick.
You
want
to
give
us
a
quick,
quick
note
on
your
progress
service
sergeant.
B
Is
a
link
to
a
document
that
has
our
brainstorming
saying
progress
has
started
in
earnest
feels
a
little
bit
strong.
We
have
been
doing
research
and
development
on
it.
That's
that's
about
it.
What
the
most
interesting
thing
is
that
we
are
actually
starting
a
separate
breakout
session
for
this.
B
That
that
is,
is,
if
you
click
through
the
link
from
the
from
this
document
here
you'll
see
that
there's
there's
another
document
we're
meeting
at
9pm,
pst
on
which
is
depending
on
where
you
are
in
europe
pretty
early
in
the
morning.
Just
because
sergeant-
and
I
are
the
main
folks
working
on
this-
and
we
don't
have
a
lot
of
overlap,
time
zone
wise
and
we
wanted
to
open
it
up
for
everyone
to
join.
B
I
would
say:
please
do
join
if
you,
if
you
like,
really
are
interested
in
this
topic
and
like
especially
if
you
think
you
might
want
to
help
out
with
it
or
something
like
that.
I'd
love
to
keep
the
forum
relatively
small,
so
you
know
everyone's
welcome,
but
definitely
more
welcome.
B
If
you
are,
if
you
want
to
come
and
help
out,
rather
than
just
like,
hang
out
and
see
what
we're
doing,
but
so
yeah,
maybe
more
updates
next
week
on
at
the
moment,
it's
really
just
sort
of
exploration
and
notes,
while
being
in
alignment
between
sergeant,
and
I.
A
Cool,
well,
that's
great
progress
to
me,
in
my
opinion,
so
glad
you
all
are
getting
going
on
that
one
and
opening
up
for
folks
to
participate
as
well,
because
it
certainly
is
a
pretty
important
feature
and
you
know
getting
the
the
experience
in
the
api
like
to
a
great
place
is
going
to
be
really
important.
I
got
a
lot
of
faith
in
you
all
to
be
able
to
do
that.
Yeah.
B
I
think
the
biggest
technical
challenge
with
it
at
the
moment-
and
I
just
occurred
to
me-
that
I'll
just
throw
this
out
there
in
the
in
the
interest
of
crowd
sourcing,
technical
solutions.
The
biggest
challenge
that
we're
facing
at
the
moment
is
we.
B
We
try
thinking
about
using
krm
functions,
which
is
something
that
kpt
and
customize
the
use
which
basically
allows
you
to
just
put
in
our
case
composition,
logic
inside
a
pipeline
of
oci
images,
so
oci
containers,
but
actually
executing
those
sort
of
server
side
in
kubernetes
is
challenging.
If
you
want
to
you
know,
let's
say
someone
has
like
four
containers
and
they
want
to
pipe
stood
in
from
one
to
stood
out
to
another
one.
B
You
know
I
could
imagine
us
just
spitting
up
four
pods
or
whatever
and
a
story
state
between
them.
That's
pretty
slow
to
do
for
reconciliation,
long
story
short!
If
anyone
has
any
great
ideas
there
about
how
to
do
that,
hit
me
up
I'll.
Give
you
I'll
give
you
credit
in
the
design,
doc.
A
I
don't
think
that
is
the
interesting
technical
problem,
okay
cool
then
so
for
kubecon
eu,
which
is
like
may
15th
or
something
in
valencia.
Spain,
quick
updates
for
everybody,
is
that
I
have
signed
us
up
for
a
maintainer
track
session
as
an
incubating
project.
We
get
a
session
there
that
we
get
to
present
and
do
intro
deep
dive
sort
of
stuff.
A
I've
also
signed
this
up
for
some
of
the
project
benefits
you
get
for
being
part
of
the
cncf,
so
I
signed
this
up
for
a
project
kiosk.
They
call
it,
which
is
another
name
for
a
booth,
doing
a
virtual
office
hours.
Components
is
because
that
was
has
been
massively
successful.
I
think
in
the
in
the
previous
kubecons,
so
I
would
love
us
to
do
that
again
and
then
getting
some
pr
support
from
the
cncf
for
any
announcements
that
we
might
have
been.
A
I
don't
know
exactly
what
we'll
be
announcing
in
may,
but
I
have
a
feeling
with
some
of
these
large
features,
we're
undertaking
that,
having
support
from
the
cncf
to
amplify
some
of
that
that
messages-
those
messages
there
that'll
be
pretty
good
too.
So
the
thing
to
note
here
is
that
you
know
they
have
language
that
they
haven't
had
before.
I
think
around,
like
guaranteed.
Acceptance
like
signing
up
for
them
does
not
mean
we'll
definitely
get
one,
but
I've
put
in
everything
that
we
can
to
get,
and
so
hopefully
we'll
get.
A
You
know
some
at
least
some
combination
of
these
opportunities
for
kubecon.
So
you
know,
since
there
are
multiple
opportunities,
that
means
there's
multiple.
You
know
chances
for
people
to
participate
as
well.
So
especially,
I
think
around
the
virtual
office
hours
there
will
be
opportunities
for
folks
from
the
community
to
speak
and
present
and
participate
in
that.
A
So,
if
you're
interested
in
speaking
on
behalf
of
the
cross,
plain
project
and
you're,
sharing
your
expertise
with
the
attendees
to
those
sessions,
then
that
that's
open
for
for
folks
to
join
in
just
reach
out
to
me
cool,
and
then
I
also
I'm
trying
I'm
going
to
organize
some
sort
of
get
together
as
well
in
valencia.
A
A
Yep,
so
kubecon's
a
few
months
away,
but
you
know
always
always
planning
to
do
for
that
stuff.
Okay,
so
then
I
don't
see
any
specific
links
to
anything
else
on
the
agenda
but
moaf.
I
remember
you
saying
that
you
had
something
that
you
might
bring
up
later
on
an
issue
or
something.
C
Yeah
I
yeah
there.
It
is
I'll
just
copy
it,
so
the
the
issue
is
that
I
believe
christopher
is
also
aware
of
it.
So
in
aws
we
have
some
resources
that
reference
the
same
kind,
for
example
in
security
group.
You
can
actually
refer
to
the
same
security
group
in
your
egress
roles.
C
So
and
it's
because
it's
id
is
decided
by
the
cloud
provider
by
aws.
C
We
don't
start
with
reconciliation,
because
we
can't
resolve
that
reference
and
reference
cannot
be
resolved
because
it
is
not
able
to
find
the
external
name
on
the
same
resource.
So
you
guys
can
this
kind
of
like
a
circular
dependency.
It
is
not
like
you
know
very
common,
but
it
happens.
So
there
is
one
issue
about
this.
Like
you
know,
hey
like
you
know.
What
should
we
do
about
this,
and
I
propose
that
we
can
have
an
optional
policy
field
on
the
reference
struct
by
default.
C
It
would
be
by
default
like
today
required,
but
you
would
be
able
to
make
it
optional
so
that,
even
though
that
reference
is
not
resolved,
the
reconciliation
pass
would
move
forward,
create
the
reason
and
the
next
reconciliation
it
would
find.
The
value
that
it
would
require
and
then
it
can
make
other
calls
that
it
wants
so
yeah.
C
I
just
wanted
to
bring
that
up.
So
now,
I'm
trying
to
find
the
agenda
link.
G
C
Yeah
so
feel
free
to
chime
in
and
please
do
let
us
know
like
you
know.
If,
if
that
proposal
does
that
make
sense
or
like
you
know,
you
have
some
concerns,
I
think
we
can
we
can.
This
could
be
something
like
you
know
pretty
like
impactful,
but
also,
like
you
know,
straightforward
for
in
terms
of
implementation.
C
Also,
like
you
know,
I
would
call
it
like
if
anyone
is
interested
in
actually
implementing
it
feel
free
to,
like
you
know,
drop
a
comment
on
the
issue.
It's
going
to
be
like
it
will
it
will
land
on
crossplan
runtime
repo?
I
believe.
A
That's
an
interesting
problem.
It's
like
self-referential
links,
oh
yeah,
thanks
for
thanks
for
bringing
that
up
and
and
mentioning
a
potential
way
to
approach
that
problem.
C
A
All
right
cool
cool,
so
I
think
that's
the
end
of
the
agenda
doc
here
I
don't
see
anything
else
that
we
haven't
covered
so
pretty
much
right
on
time.
It
looks
like
any
parting
words
or
anything
else
that
anybody
needs
to
bring
up
for
me
adjourned
for
the
week.
G
C
Yeah
I'll
I'll
make
sure
to
review
it
tomorrow
well
or
at
the
latest,
beginning
of
the
next
video.
I
believe
I
took
a
look
at
it.
It's
like
now
very
straightforward
because
we
already
used
the
authentication
methods
from
provider
aws
native
one,
so
it's
yeah
cool.
D
I
think
there
is
one
last
item
which
is
added
by
I
guess:
ricardo
asking
for
some
good
first
issues.
Oh.
H
I'm
sorry
I
missed
that
yeah,
that's
fine,
I'm
just
you
know
looking
for
some
guys.
I
I
know
that
you,
you
folks,
have
like
a
good
first
issue,
whatever
you
know
github,
but
you
know
just
wondering
you
know
besides
that,
if
there's
anything
that
you
know
there's
like
a
focus
because
I
know
I
know
how
projects
work
where
you
know
you
know
the
issues
start
piling
up
and
you
know
it's
hard
to.
A
A
Typically,
what
I
have
seen
is
that
a
lot
of
times
first
contributions
will
be
around
like
adding
a
new
support
for
a
new
resource
using
using
code
generation
stuff
so
either
in
one
of
the
tearjet
providers,
like
you
know,
adding
like
maturing
one
of
the
resources
from
viewing
alpha
one
to
v1
output,
two
and
there's
a
guide
on
that
or
like
inprovider
aws,
using
the
ack
code
generation,
stuff
to
add
support
for
a
new
resource.
So
that's
typically
one
common
path
for
new
contributors.
H
A
Yeah,
I
don't,
I
don't
know
if
there's
going
to
be
like
an
explicit
missing
list,
but
the
doc.crds.dev
site
is
super
super
useful
to
to
see
like
what
are
the.
What
is
there
right
now
and,
like
you
know,
resources
that
you
want
to
want
to
add
is
it
could
be?
A
You
know
you
can
cross-reference
it
there
and
see
very
quickly
if
it's,
if
it's
there
or
not,
like,
for
instance,
without
aws
like
this,
you
can
see,
it's
got
119
resources
there,
here's
all
the
api
groups,
the
kinds,
the
version
and
stuff,
so
this
is
a
great
way
to
explore.
What
is
there
right
now.
H
Gotcha
and
if
I
understand
correctly,
the
product,
the
provider
dash
whatever
is
kind
of
like
the
stable
thing
and
the
the
new
way
of
doing
things
may
seem
like
it's
like
the
terror.
Jet
kind
of
you
know
project
right,
or
am
I
getting
that
wrong.
A
Yeah,
there's
a
there's,
a
there's,
a
whole
write-up
on
that
so
I'll.
Let
make
handle
that
more
directly
right
here
and
then,
but
there
is
like
a
provider
strategy
right
up.
That's
we'll
be
able
to
give
details
as
well.
Gotcha.
A
H
Right,
oh
okay,
thanks
daniel
yep!
Oh
I
got
that
look.
A
Awesome
ricky
and
there's
you
know.
One
thing
I
was
gonna
say
is
that
you
know
a
lot
of
times.
The
new,
adding
new
resources
is
demand
driven.
So
like
hey
something
that
you
want
to
use,
you
know
so
you're.
You
know
you
want
to
see
it
then
that
that's
a
common
way
that
people
get
involved
too.
So
something
you
want
to
see
in
the
project
you'll
feel
free
to
chat
with
us
and
and
get
some
feedback
on
ideas.
H
A
Awesome
ricky
glad
to
have
you
on
the
community
man
yep
all
right,
all
right!
Thanks,
everybody
good
to
see
everybody
and
we'll
journey.