►
From YouTube: 2021-04-22 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
the
recording
has
started-
and
this
is
the
april
22nd
2021
cross,
plane
community
meeting.
If
you
pop
in
after
we
get
started
here,
are
you
feel
free
to
add
your
name
to
the
attendees
list?
There
we'll
try
to
keep
that
updated
as
always
we're
going
to
start
with
our
releases
and
upcoming
milestones,
roadmap
sort
of
stuff
the
1.2
release
is
coming
in
soon.
We
are,
I
think,
about
a
week
out
from
that.
A
B
Yep,
I'm
planning
on
cutting
them
either
today
or
tomorrow,
and
then
we'll
have
our
official
release
on
tuesday
right.
A
Excellent
yeah,
so
I
think
that
you
know
things
that
we'd
be
taking
at
this
point
now,
you're
kind
of
in
the
code
freeze
area
there
is,
you
know,
documentation
stuff,
maybe
user,
guide,
stuff,
or
maybe
some
critical
bugs.
If
somebody
finds
something
that
really
is,
you
know
kind
of
a
release
blocker,
and
we
want
to
get
it
in
there
before
putting
that
out
to
the
to
the
to
the
world.
Then
that's
kind
of
stuff
we'd
be
taking
on
now,
but
mostly
it's
baked
baking
right
now.
A
A
So
if
anybody
finds
any,
you
know
issues
or
or
has
things
that
they,
you
know
think
are
a
good
candidate
to
get
in
later.
At
this
phase,
please
do
you
know
ping
us
on
slack
and
we
can
have
that
conversation
kind
of
do
a
triage
in
real
time
as
things
are
coming
up.
A
So,
in
terms
of
you
know,
roadmap
milestones,
sort
of
stuff.
You
know
as
as
a
reminder
here
in
the
community
meeting
here.
This
is
a
great
chance
for
folks
to
kind
of
speak
up
about
issues
they
think
are
are
of
high
importance.
A
You
know
we
are
in
the
code
freeze
for
1.2,
so
you
know
there
aren't
going
to
be
any
more
features
or
big
things
getting
into
the
release,
but
as
we
move
on
into
the
next
release
the
cadence
and
the
cycle
for
the
1.3
release,
this
will
be
a
good
chance
for
folks
to
speak
up,
and
you
know,
make
a
case
or
express.
You
know
their
need
for
particular
features
and
scenarios
that
are
on
the
roadmap,
so
I'll
bring
the
board
up
here.
A
Real
quick,
I
know
in
the
past
community
meeting
we
had
done,
we
had
talked
about
some
of
the
higher
priority
roadmap
things,
and
so
the
proposed
column,
I
think,
is
pretty
well
up
to
dates
in
terms
of
what
we've
heard
for
high
priority
features
on
the
roadmap
and
impact,
and
you
know
unblocking
scenarios
and
things
like
that.
So
these
you
know
first
five
or
so
I
think
are-
are
pretty
we've
gotten
some
pretty
consistent
feedback
about
the
the
importance
or
need
for
those.
You
know.
A
Folks
are
more
than
welcome
to
weigh
in
now
and
speak
up
about
an
issue
that
you
find
important
or
you'd
like
to
see,
so
people
can
jump
in
on
that
there
was
a
particular
issue.
I
was
looking
for
on
the
board
here
as
well,
too.
I'm
going
to
start
dragging
windows
out
of
the
way
again.
B
One
that
was
kind
of
important
there
is
that
required
patch
policy.
So
that's
one
that
we've
had
in
progress
for
a
while.
It
will
not
go
into
this
release.
The
reasoning
for
that
is,
it
involves
how
we
currently
refer
to
basically
the
the
templated
resources
or
the
composed
resources
when
they're
going
through
the
composition
engine
and
so
right
now,
if
you're
not
able
to
render
all
of
your
composites
or
all
of
your
composed.
B
I
guess
then
there's
basically
it
just
airs
out
right
and
says:
I'm
not
able
to
do
this.
This
is
breaking
the
use
case
or
not.
Enabling
might
be
more
apt
a
way
to
say
it.
An
expected
use
case
where
you
are
able
to
you
know
create
a
resource
in
a
composition
before
another
one
can
be
created,
because
it
depends
on
something
that's
going
to
get
patched
back
to
the
composite
resource
of
the
claim
and
then
go
through
right.
So
you
temporarily
are
going
to
have
one
of
the
resources
in
your
composition
unavailable.
B
However,
you
can
imagine
right
if
you
don't
have
that
resource
available
when
we
render
them
all
out,
you
have
a
gap
in
resources
there,
because
we
basically
can't
produce
a
representation
of
it.
So
there's
kind
of
some
back
and
forth
on.
If
we're
going
to
have
a
placeholder
there
or
we're
just
going
to
omit
it.
B
This
isn't
an
issue
if
you're
naming
your
templates
in
the
composition,
but
for
backwards
compatibility,
we've
continued
to
support
the
ability
to
have
unnamed
templates,
so
there's
kind
of
some
some
complex
machinery
there
that
we
didn't
want
to
mess
with
too
late
in
the
release
cycle,
but
you
can
expect
that
to
go
into
the
next
one.
The
only
other
one
I'd
mention
is
that
multi-tenant
support
guide
that
is
just
documentation
and
I
do
plan
for
that
to
be
in
the
docs
for
the
1.2
release
on
on
tuesday.
A
Oh
nice
day,
I
was
good.
That
was
what
I
wanted
to
hear
about
as
well,
too.
That's
great
that
that
you
know
it's
a
doc's,
only
change
right!
There's
no
code
change
there.
So
that's
perfectly
reasonable
to
go
in
at
this.
A
At
this
phase
of
the
release
cycle,
yeah,
I'm
happy
to
see
that
one
make
it
in
that's
great
dan
thanks
for
following
up
on
that
another
one
that
I
was
I
was
you
know,
we've
had
it
in
review
for
for
a
bit
and
I
think
it's
a
pretty
cool
feature
as
well
too.
I
I
at
this
point
I
don't
think
we'll
be
able
to
get
it
in
for
1.2
it's.
You
know,
there's
way
too
much
turn
at
this
point,
but
around
you
know
patching
from
multiple
sources.
A
I
thought
that
was
a
really
strong
feature,
so
hopefully
we
can
and
early
on
in
the
1.3
release
cycle.
We
can
get
that
reviewed
and
feedback
in
and
go
ahead
and
get
that
one
merged,
so
we'll
have
it
for
1.3.
B
Yeah
yeah:
I
think
that
is
a
really
important
one.
We've
seen
a
lot
of
folks
bring
that
up.
Another
thing
I
want
to
mention
is
most
of
these
kind
of
like
larger
feature
areas.
We've
talked
about
have
been
primarily
implemented,
at
least
recently
by
myself,
mubaffic
or
nick.
These
are
feature
areas
that
are
open
to
anyone,
the
community
to
work
on
absolutely,
and
so
this
is
something
that
folks
really
want
to
see.
If
you
have
the
bandwidth,
we
are
more
than
happy
to
support
you
in
that
and
enable
you
to
do
that.
B
Another
thing
I
want
to
mention
is
because
of
the
release
cadence,
we
have
missing
this
release.
Isn't
that
big
of
a
deal,
because
the
next
one
will
be
coming
very
very
quickly
with
a
two-month
release
cadence
and
you
can
obviously
utilize
incremental,
builds
of
that
as
well.
B
The
last
thing
I
want
to
mention
is
a
lot
of
these
are
for
provider
aws.
Here
there
are
a
lot
of
pr's
in
flight
on
provider
aws
and
some
pretty
big
changes
on
provider
gcp.
B
A
lot
of
the
folks
on
this
call
have
worked
on
a
lot
of
those
changes
and
a
number
of
them
are
very
close
to
getting
merged,
especially
some
of
those
provider.
Aws
forms-
and
I
just
want
to
reiterate
that
those
are
not
coupled
to
the
cross
plane
release
cycle.
B
So
we
can
choose
to
to
release
those
at
any
point.
One
of
the
things
that
has
been
identified
as
an
important
thing
for
a
while,
and
I
think
it's
even
kind
of
raised
in
importance
lately
because
of
some
changes
to
provider.
Gcp
that
we'll
talk
about
late
lately.
B
We
we
need
to
start
right
having
formalized
release
cadences
around
these,
as
well
as
having
release
notes.
So
folks
are
aware
of
how
apis
are
changing
over
time,
but
all
that
to
say,
if
you're
someone
who
consumes
these
providers
or
works
on
them,
you
can
obviously
have
a
voice
in
dictating
the
kind
of
cadence
we
have
for
those.
So
as
we
start
to
define
that,
please
feel
free
to
speak
up
and
engage
in
that
conversation.
So
we
can
make
sure
that
you
know
folks.
B
Different
consumption
models
are
all
all
satisfied
with
whatever
strategies
we
choose
for
each
provider.
A
Yeah
thanks
for
those
reminders,
dan,
especially
about
providers-
not
being
you
know,
coupled
to
the
cross,
plane
itself,
one
not
two
release
so
yeah
there's.
We
could
still
continue
making
making
progress
on
getting
those
those
features
that
are
related
to
you
know
like
the
aws
services
and
things
like
that.
A
Yes,
so
I
think
those
are
some
of
the
things
that
are
in
flight
that
didn't
make
it
for
1.2
that
we
talked
about
like
the
multi-batch
one
and
high
priority
like
what
we
believe
is
priorities
for
the
community
as
a
whole
in
the
proposed
column.
Here
these
will
get
moved
onward
to
a
1.3
board
that
will
open
up
after
we
get
1.2
out,
but
I
I'll
go
ahead
and
open
the
floor
as
well
too.
A
For
anybody
who
has
a
feature-
or
you
know,
scenario
or
desire-
they
want
to
bubble
up
here
as
a
priority
for
them
as
well
too
I'll.
Take
any
requests
for
that
right
now.
C
Oh
hey
jared
yeah,
so
I
was
thinking
about
the
plugable
books,
which
is,
I
think,
kind
of
critical
with
resources
having
a
lot
of
immutable
fields
and
not
being
able
to
enforce
that
through
provider.
So
is
there
a
plan
around
implementation,
or
I
would
like
to
help
with
it.
B
A
Yeah,
I
think
that
yeah,
that's
something
that
you
know
muafek
had
done.
You
know
one
pager
design
for
this
a
little
bit
ago
and
had
you
know,
made
some
progress
on
that,
but
implementation
for
it,
you
know,
was,
was
not
able
to
make.
We
made
progress
and
or
finish
off
or
yeah,
probably
yeah,
it's
more
more
design,
heavy
and
less
implementation
for
1.2,
so
yeah.
A
So
if
you
are
interested
in
helping
contribute
in
that
for
like
the
1.3
time
frame,
then
that's
that
could
certainly
be
reasonable
and
probably
a
good
first
step
would
be
to
you
know,
read
through
at
least
the
design
that
mafik
had
started
on
and
then
probably
consult
with
mafik
and
kind
of
get
a
conversation
going
around
what
the
implementation
would
look
like,
or
are
there
tasks
that
could
be
split
up,
maybe
like
what
would
be
the
ownership
of
those
tasks
and
kind
of
take
it?
Take
it
from
there.
C
B
Yeah
and
if
you
wouldn't
mind
just
dropping
a
comment
on
there,
mentioning
that
you'd
like
to
work
on
that,
then
we
can
obviously
make
sure
that's
tracked
in
and
stuff
like
that.
C
Yeah
yeah
I
have
like.
I
have
some
thoughts
because
we
could
like
there
are
a
couple
of
strong
reasons
or
like
strong
policies.
We
would
like
to
enforce
right,
so
I
was
thinking
instead
of
just
a
validation
or
a
mutation
web
book.
Maybe
we
can
consider
something
more
like
using
oppa
and
having
policies
to
enforce
the
same.
C
So
that's
maybe
something
to
consider.
I
guess.
B
Yeah
yeah,
I
think
so,
and
and
how
that
fits
into
the
packaging
system
and
how
you
also,
you
know
like
request
that
in
your
in
your
provider,
if
we
want
some
of
those
to
be
turned
on
by
default
or
we
want,
you
know
those
to
be
explicitly
provided
those
are
all
things
that
should
go
into
consideration.
B
One
thing
I
would
encourage
just
from
a
kind
of
like
design
perspective,
is
trying
to
keep
it
flexible
early
in
terms
of
not
committing
to
any
strategies
that
we're
gonna
have
to.
You
know,
support
in
perpetuity
and
keeping
that
in
mind
as
we
design
this
feature.
A
Well,
awesome
thanks
for
thanks
for
bringing
that
up
and
speaking
on
that,
one
any
other
input
or
feedback
about
roadmap,
high
priority
features
or
anything
like.
B
B
A
All
right
yep,
so
we
can
always
have
to
continue
that
conversation
on
slack
or
in
issues.
You
know
on
github.
You
know
anytime,
that
you
think
something's
important.
You
can
always
add
a
comment
to
an
issue
or
if
there's
not
an
issue,
we'll
go
ahead
and
open
one
up,
so
we
can
always
keep
those
conversations.
You
know
async
as
well
too.
We
don't
have
to
wait
until
the
next
community
meeting
to
have
those
all
right.
So
we've
got
a
handful
of
topics
here
for
the
community
topic
section.
A
So,
let's,
let's
move
on
head
on
down
to
there
then
and
dan.
You
want
to
kick
us
off
here
with
some
updates
about
live
streams.
B
Yup
so
tomorrow,
at
12,
30
or
excuse
me,
8,
30,
pacific
we're
gonna,
have
a
informal
live
stream
with
marcus
and
david
from
equinix
metal.
Equinix
we've
had
some
streams
related
to
equinix
metal
provider.
In
the
past,
we're
actually
going
to
be
working
on
an
equinix
provider
which
is
kind
of
the
parent
company
now
and
has
actually
different
apis
from
the
equinix
metal
services.
B
That's
building
towards
some
additional
streams,
we're
going
to
do
with
them
around
the
equinix
fabric,
feature
which,
if
you're,
not
familiar
equinix
kind
of
runs
data,
centers
and
partners
with
a
lot
of
the
large
cloud
providers
and
in
doing
so
is
able
to
basically
provide
you
dedicated
links
between
different
cloud
providers
between
their
data
centers,
which
is
definitely
really
cool.
B
There
are
a
number
of
features
that
need
to
go
into
an
equinix
provider,
as
well
as
into
the
existing
cloud
provider
providers
for
crossplane
to
enable
this
functionality
and
we're
gonna
live
stream.
Working
on
that.
Just
so
folks
who
are
interested
in
building
providers
and
also
interested
in
this
multi-cloud
functionality
can
kind
of
get
an
inside
look
at
what
that
looks
like,
but
definitely
keep
an
eye
out
for
additional
streams
coming
up
we're
gonna
kind
of
split
those
between
our
channels
and
theirs.
B
The
other
thing
mentioned
there,
which
I
know
this
has
been
on
here
for
quite
a
while-
and
it's
mostly
just
been
scheduling
back
and
forth
with
some
folks
from
the
flux
team,
but
we
do
have
a
live
stream
coming
up.
I
know
some
of
y'all
have
already
seen
the
demo,
or
at
least
the
manifest
for
the
demo
for
that.
But
hopefully
we
can,
you
know,
provide
some
more
insight
on
how
folks
can
use
git
ops
alongside
crossplane
to
kind
of
maximize.
B
You
know
the
the
usage
of
the
kubernetes
api
for
provisioning
infrastructure
within
their
organization,
so
keep
an
eye
out
for
that
one
as
well,
and
we'll
try
we're
going
to
try
to
have
that
before
kubecon,
but
it's
now
kind
of
sneaking
up
on
us,
but
we'll
also
be
at
the
flux
booth.
Give
me
a
demo
at
cubecon
that
week,
if
you
are
going
to
be
attending.
B
I
you'd
have
to
ask
them.
I
guess
I'm
from
you
know
on
our
side.
I
know
our
booth
is
kind
of
like
a
constantly
running
thing,
so
I
doubt
that
there's,
I
think
they'll
informally,
you
know
say
like
this
is
gonna
happen
at
this
time.
If
you'd
like
to
see
it,
but
I
don't
think
there's
any
sort
of
like
you
know,
event
time,
although
there
is
kind
of
like
that
meet
the
maintainers
scheduled
portion.
I
know
so
yeah.
A
Yeah,
exactly
okay,
cool
nice
yeah,
that's
cool
to
do
that
kind
of
have
that
integration
between
the
two
projects
and
kind
of
collaborating
there.
I
like
that
a
lot.
That's
great
awesome,
thanks
dan,
quick
update
on
the
incubation
process
for
crossplane.
So
since
the
last
community
meeting,
we
presented
our
proposal
and
due
diligence
and
everything
to
the
special
interest
group
for
app
delivery.
A
It
was
well
received
there
and
we
got
a
little
bit
of
feedback
from
one
of
the
sig
leads
on
our
due
diligence
documents.
So
they're
engaged
and
that's
good.
The
next
step
there
that
they
want
to
do
both
the
sig
and
the
technical
oversight
committee
is
that
they
want
to
do
end
user
interviews
with
some
of
the
adopters
that
we
mentioned
in
the
proposal
of
the
production
doctors
of
crossman.
A
So
we're
trying
to
get
that
scheduled
and
make
moves
on
that
which
would
be
the
final
thing
preventing
the
sig
to
give
approval
to
the
technical
oversight
committee,
which
would
then
open
the
two-week
public
commentary
period
before
the
glc
can
then
vote.
So
there's
a
couple
steps
still
left
here,
but
we
have
done.
You
know
most
everything.
Our
side
with
the
proposal,
the
due
diligence
and
the
presentation
and
all
that
sort
of
stuff-
so
that's
that's
all
going
pretty
well,
okay
and
then
yeah
there's
some
resources
here
as
well
too.
A
If
you
haven't
checked
out
the
proposal
or
you
want
to
see
some
of
the
due
diligence
and
stuff,
that's
that's
there.
The
presentation
to
app
delivery-
that's
also
linked
here
is
you
know,
it's
kind
of
has
a
good
good
introduction
material
to
crossplan,
so
feel
free.
If
anybody
you
know
is
wanting
to
reuse,
some
of
the
slides
or
you
know,
take
that
material
and
present
it
somewhere
else
feel
free
to
use
it
completely.
You
know
for
whatever,
whatever
your
needs
are.
A
A
Cool
and
then
lfx
mentorship
rahul
is
continuing
to
to
do
some
of
the
work
that
he's
been
doing
on
provider
knob
recently
rahul.
Do
you
want
to
go
ahead
and
give
us
a
quick
update.
C
Hi
so
since
the
unlock
was
completed,
and
I
made
a
pr
on
that
as
well
and
now
we
have
started
with
the
implementation
part
and
probably
today's
sync
up
with
dan
and
maybe
moffat
will
also
join.
So
I
will
just
try
to
finish
that
find
a
pattern
and
then
we'll
move
on
to
listing.
Hopefully.
A
Awesome
yeah
good
progress
on
that
and
for
folks
to
have
a
little
a
little
bit
more
context
on
on
that
project.
There,
the
the
whole
idea
around
the
provider,
no
op
is
that
you
know
in
our
integration
into
end
testing
for
cross
plane.
You
know
like
to
test
the
composition
engine
or
you
know
various
scenarios.
It's
very
useful
to
have
basically
a
fake,
a
mock
provider
that
you
know
we
can
kind
of
instruct
it
how
to
behave
so
that
we
can.
A
You
know,
exercise
the
integration
tests
with
those
scenarios
in
mind
and
have
the
provider
behave
that
we
want
to
and
make
sure
that
we,
the
engine
and
machinery
for
composition
and
cross
plane
as
a
whole
around
that
provider
is
behaving
the
way
that
we
want
it
to
in
response
as
well
too.
So
it
gives
us
a
way
to
do
test
scenarios
in
a
consistent
fashion,
and
so
that's
as
the
whole
integration
into
and
testing
effort
that
whole
has
been
working
on
as
part
of
the
mentorship
program.
A
A
Awesome
thanks
thanks
for
cool,
I
wanted
to
drop
a
note
here
on
cross
plane,
related
conformance
and
certification.
A
This
is
just
kind
of
mentioning
this
out
to
the
community
and
we
can
do
more
follow-ups
later
on,
but
essentially
we
are
wanting
to
start
a
certification
program
for
cross,
plane
providers
and
then
distributions
of
crossplane
as
as
well
so
we'll
have
it's
very
similar
to
the
upstream
kubernetes
conformance
and
certification
stuff
that
you
may
be
familiar
with
already
where
you
know
to
have
a
distribution
or
have
a
provider.
You
know
there's
a
certain
set
of
functionality,
behavior
expectations,
etc,
that
that
will
be
defined
such
that
you
know.
A
If
you
meet
all
those
criteria,
then
the
provider
can
be
certified,
and
so
that
will
be
in
conjunction
with
the
cncf
as
well
too,
to
establish
that
conformance
program
there.
And
if
anyone
is
interested,
if
you
own
or
maintain
a
provider
like
the
equinix
or
your
ibm
provider,
ibm
cloud
provider
or
aws,
then
you
know
please
do
reach
out
to
jared
and
grant
on
the
crossband
slack
or
send
us
email
whatever.
A
Whatever
there
then,
we
kind
of
start
talking
about
you,
get
you
early
in
and
involved
in
that
conformance
program
and
helping
design
it
and
stuff
too.
So
you
can
be
a
part
of
collaborating
on
that
as
well
too
so
just
reach
out.
If
anybody
has
any
interest
in
you
know
getting
their
provider
certified
we're
happy
to
kind
of
do
that
in
a
very
collaborative
and
open
fashion.
A
Cool
and
then
kubecon
eu
they
chuckled
a
little
bit
earlier.
Damn-
and
you
mentioned
that
you
know
kukan's
sneaking
up
on
us
because
I
never
feel
like
kubecon's
too
sneaky.
I
feel
like
it's
always
like
a
thousand
pound
gorilla
stopping
around
as
it
comes,
but
so
for
kubecon
eu,
which
is
in
just
a
couple
of
weeks
so
like
starting
may
4th
is
the
the
first
day
of
kubecon.
A
A
One
of
them
is
an
office
hours
meet
the
maintainers
session,
that
is
on
wednesday
may
5th,
and
then
there's
also
some.
The
cncf
gave
us
a
booth
in
the
project,
pavilion
area
that
if
you
are
interested
in
talking
to
users-
and
you
know
representing
crossfit
and
answering
questions
and
stuff
like
that,
then
there's
some
spots
there-
that
you
can
sign
up
for
and
participate
as
at
the
booth
as
well
too
so
two
different
opportunities
there
feel
free
to
reach
out
to
me
like
on
the
crossband
slack.
A
If
you
want
to
get
to
know
more
and
talk
more
about
that,
one
of
the
interesting
things
is
that
it
is,
is
eu
daylight
hours,
so
it's
it's
not
as
north
america,
friendly
as
the
last
kubecon
eu
was
last
year.
So
it's
you
know.
It's
gonna
be
more
much
more
common
to
think
for
eu
people
to
be
getting
involved
than
north
america.
People
will,
but
the
opportunities
are
there
for
anybody
who
wants
to
get
involved.
Nope.
No,
no
problems
at
all.
A
Okay
and
then
the
and
then
also
along
with
kubecon,
is
you
know,
we've
talked
about
this
before
the
crossband
community
day.
That's
coming
up,
that
is
on
the
first
day
of
of
kubecon
as
a
co-located
event
on
may
4th.
There's
a
link
here
in
the
dock
to
see
the
schedule
see
all
the
talks
you
can
get
registered
there
if
you
haven't
already,
but
it's
gonna
be
a
really
cool
day,
full
of
some
good
information.
A
Good
speakers
good
talks
that
we're
all
really
excited
about,
and
thank
you
to
everybody
here
on
the
call
to
that
submitted
talks
that
got
them
recorded
and
you
know
everything
is
in
and
the
content
is
all
lined
up.
So
I
think
we're
looking
good
to
go
there.
I'm
very
excited
about
that,
and
thanks
everybody
for
the
efforts
on
getting
that
together
and
every
part
that
everyone
played
in
that.
A
And
do
you
want
to
take
the
the
next
one
here
on
newark
numbers.
B
Yeah
for
sure,
so
I
just
added
this
in
and
I'm
gonna
put
it
in
our
template
for
each
of
our
meetings.
Just
so,
we
can
recognize
new
folks
that
are
have
joined
the
crossplane
org
on
github,
so
we
introduced
this
process
to
make
it
a
little
more
formal
for
folks
to
be
able
to
be
assigned
things.
I
know
many
people
on
this
call
are
not
probably
currently
in
the
crossline
org,
but
you
are
eligible
to
do
so.
B
B
There
is
documentation
on
how
you
can
do
that,
and
this
morning
oper
went
ahead
and
requested
a
org
membership
and
was
endorsed
by
myself
and
hassan,
who
are
current
board
members,
and
there
is
a
pr
open
pending
steering
committee
approval
to
go
ahead
and
add
him
so
welcome
to
offer
and
encourage
anyone
else,
who's
interested
to
also
apply.
A
But
I
just
dropped
the
link
there
underneath
that
to
read
me
for
becoming
a
member,
so
anybody
who
wants
to
become
a
member
of
the
github
org
for
cross
plan.
The
link
is
right
there
and
you
can
follow
that
process.
That
dan
was
just
describing
and
we're
happy
to
help
out
with
that,
as
well
too.
So
check
that
out.
If
you,
if
you
want
to
join
the
crossband
org
did,
is
that
has
has
the
process
been
automated
yet
to
to
sync
the
like
new
members
from
the
ammo
to
the
github
api.
B
No,
it
is
not,
but
we
do
have
the
pr
open
with
that
functionality
and
I
would
guess
post
kubecon
when
we
have
some
other
kind
of
announcements
going
out
that
we
will
likely
set
that
up
to
automate
some
of
our
org-
and
I
know
steven
who
recently
joined
upbound
is
also
interested
in
driving
some
of
that.
So
I
would
expect
that
we
get
that
automated,
hopefully
pretty
soon,.
A
Awesome
cool,
yep,
happy
to
add
people
manually
until
then,
just
just
let
me
know,
and
I'm
happy
to
take
care
of
that
sounds
good
all
right,
moving
right
along
here,
making
good
progress.
So
the
next
thing
we
have
on
the
agenda
dock
is
is
around
the
provider
gcp
beta,
so
dan,
do
you
want
to
go
ahead
and
fill
us
in
on
that
one
in
the
progress
there.
B
B
Importantly-
and
this
is
going
to
be
kind
of
a
driving
factor
for
being
more
clear
in
our
release-
notes
for
providers,
there
is
going
to
be
some
functionality,
changes
of
beta
resources
in
provider
gcp
because
of
this,
notably
the
cluster
resource,
the
node
group
resource-
and
I
think
that's
it.
Actually.
Cloud
sql
also
uses
a
beta
gsp
api,
but
I
believe
it's
remain
stable.
So
from
this
point
forward,
all
resources
that
go
into
the
standard
provider
gcp
will
rely
on
v1
google
apis.
B
You
can
use
that
alongside
you
can
use
those
two
providers
alongside
each
other
until
we
have
generic
cross
resource
references,
which
this
is
also
kind
of
a
motivator.
For
that
you
won't
be
able
to.
Actually,
you
know,
perform
references
so,
for
instance,
if
you
create
a
beta
version
or
the
provider
gcp
beta
version
of
a
cluster
you're
not
going
to
be
able
to
reference
a
network
from
provider
gcp.
B
However,
you
know
if
we
do
have
generic
references
in
the
future.
That
should
be
possible,
but
overall,
this
should
allow
both
added
stability
and
the
ability
to
get
features
faster
depending
on
the
type
of
environment
you're
operating
in.
So
we
will
go
ahead
and
do
that
and
the
pr
is
open
but
needs
some
refactoring
to
go
ahead
and
fix
up
some
of
those
resources
that
depend
on
beta
apis
in
the
gcp
provider.
Gcp
and-
and
so
those
will
be
changing
in
the
coming
release
in
terms
of
a
few
fields
that
are
enabled
there.
A
B
Yeah,
so
if
you
wanted
to
transition
to
using
provider
gcp
beta,
it
could
be
as
simple
as
you
know,
taking
down
the
provider
gcp
and
installing
fighter
gcp
beta,
it
could
also
be
if
you
want
to
use
them
alongside
each
other,
you
could
use.
You
could
just
switch
the
the
group
of
the
instance
to
provider
gcp
beta
if
you're
using
provider
gcp,
currently
functionality
of
one
of
the
resources
changes.
Once
again.
This
is
notably
the
cluster
api
and
the
node
group
api.
B
It's
only
additional
fields
that
are
there
currently
to
my
knowledge
at
least
last
time
I
checked.
So
what
would
happen
in
that
case
is
likely
nothing
actually,
but
your
fields
would
just
be
stripped
off
right.
They
would
be
pruned
away
the
extraneous
ones
that
are
only
applicable
to
the
beta
api,
so
so
there
shouldn't
be
too
much
disruption.
B
That
being
said,
we'll
definitely
test
some
of
those
scenarios
and
also,
if
you're,
if
you
are
depending
on
that
provider
right
now,
I
would
encourage
you
to
look
at
the
release.
Notes
for
the
upcoming
release
for
provider,
gcp
provider
g
speed
beta
will
start
on
its
own
symbol,
cadence
right.
So
its
first
release
will
be
0.1
and
it
will
operate
mostly
independently
from
provider
gcp
moving
forward.
A
Oh,
that
makes
sense
dan
thanks
for
helping
explain
that.
Okay,
then
that's
everything
that
was
in
the
agenda
dock
ahead
of
time,
but
I
will
open
the
floor
for
any
other
topics,
questions,
prs,
etc.
That
other
folks
might
have
on
their.
A
A
Okay,
well,
if
if
there
are
no
other
topics
that
folks
want
to
bring
up
in
this
venue
right
here,
then
we
are
always
available
for
chatting
on
slack
and
github
issues.
Discussions
so
always
feel
free
to
reach
out
on
those
those
couple
of
other
options
there,
and
then
we
can
go
ahead
and
adjourn
for
the
week.
Then.