►
From YouTube: 2020-03-31 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
Okay,
the
recording
is
started,
and
this
is
the
March
31st
2020
cross
playing
community
meeting
will
start
as
usual,
with
our
milestone.
Checkup
and
last
week
we
were
able
to
release
the
0.9
version
of
cross
Blaine
here
in
the
agenda,
are
linked.
The
release
notes
for
some
of
the
notable
updates
and
things
that
we
included
in
that
release.
So
you
can
check
out
these
the
release,
notes
there
and
you
know,
start
using
0.9
and
provide
any
feedback
if
you
haven't
already.
Thank
you
Dan
for
helping
to
run
that
release
again
and
for
writing.
A
The
release,
notes
I,
appreciate
that
work
there,
and
we
could
keep
an
ongoing
conversation
about
how
to
streamline
the
release
process
or
add
more
automation
so
that
it
becomes
less
of
less
manual
steps
and
less
less
burden.
At
least
it's
one
thing.
I
do
like
about
our
releases
right
now
is
that
they
seem
to
be
very
reliable.
We
don't
seem
to
run
into
any
unexpected
issues
while
we're
releasing
the
software
or
doing
builds
or
promoting
things.
A
B
Yeah
right
now
we're
doing
some
final
testing
just
to
make
sure
before
the
release
goes
out,
which
we're
trying
to
do
a
little
more
QA
on
all
of
our
releases
these
days.
So
we're
doing
some
final
tests
there,
but
it's
gonna
be
two
clicks
of
a
button
to
get
that
out.
The
docs
and
references
already
updated.
So
you
should
see
that
landing
today,
excellent.
A
A
A
Our
next
monthly
release
of
0.10,
your
semantic
versioning,
does
allow
double
digits
and
even
triple
digits
for
each
field.
So
we
get
to
0.9.
We
don't
have
to
go
to
one
ton
zero.
Next,
we
are
going
to
continue
on
bumping
the
minor
field
of
the
version,
so
it's
near
that
10
will
be
our
next
release
and
the
we
tend
to
try
to
do
those
around
the
middle
of
the
month.
So
I
proposed
a
tentative
schedule
them
for
future
freeze
around
the
middle
of
the
week
and
March
14th
right,
sorry
that
should
be
April.
A
March
15th
has
already
passed
there.
We
go
the
middle
of
next
month,
April
15th
and
then
release
it
by
Friday.
At
the
end
of
the
week
there
we
could
adjust
those
accordingly,
maybe
not
to
do
a
release
on
Friday.
But
that's
that's
the
target
week
there,
since
it's
the
middle
of
the
week-
and
you
know,
stick
to
our
our
scheduled.
Let
me
try
to
do
the
road
map
has
not
yet
been
updated
and
felt.
Can
you
like
you,
have
done
such
a
great
job
of
for
the
preceding
releases?
A
Can
you
take
a
pass
to
update
the
road
map
for
0.10?
Thank
you,
sir.
Very
much
appreciate
it.
I
said
please
here
showing
some
manners
and
appreciation
of
your
work
awesome.
So
yeah
we're
just
getting
started
on
0.10
and
you
can
add
the
items
since
the
milestone.
That's
the
core
across
plane,
repo
is
there
about
ten
milestone
and
we'll
you
know
with
the
in
the
hope
of
efficiency
and
expediency,
we'll
probably
will
be
releasing
updates
minor
updates
to
all
the
providers
and
stacks
as
well.
A
A
B
Yeah,
so
we
did
a
show
with
Alex
Ellis,
who
is
the
founder
and
maintainer
of
open
Fez,
which
is
basically
serverless
functions
on
kubernetes
and
other
platforms
as
well,
but
for
our
purposes
kubernetes,
and
we
showed
how
you
can
basically
consume
manage
services
from
a
cloud
provider
or
from
kubernetes
from
your
service
functions
using
open
Fez.
So
that's
a
nice
thing
about
standardizing
on
the
kubernetes
api.
You
can
pass
connection
information
around
in
secrets.
There's
a
uniform
format
as
jared
is
bringing
up
here.
B
This
is
a
blog
post
that
kind
of
details,
some
of
the
things
we
went
through
in
the
video.
So
if
you
don't
want
to
watch
the
full
hour
and
15
minutes,
this
is
a
quick
run-through
and
it
also
has
some
some
links
out
to
other
things
and
a
little
more
detailed
description
of
the
value
that
crossplane
is
providing
here.
So
both
those
are
great
resources
if
you're
interested
in
doing
server
lists
on
kubernetes,
and
they
also
link
to
kind
of
timestamps
in
the
video.
B
A
On
dan,
this
is
a
good
string,
really
high-quality
guests
and
collaborations
I
love
how
we're
getting
other
interesting
projects
in
the
ecosystem
and
collaborating
with
them
and
showing
off.
You
know
how
there
is
interesting
scenarios
in
value
that
can
be
fulfilled
by
the
two
projects
working
together.
So
this
is
this
fantastic
in
and
I
like
it.
How
you're
able
to
tell
us
the
guests
for
for
next
episode
already
in
the
community
meeting
here?
A
A
A
All
right
cool
and
then
you
know
we
have
I,
don't
know
what
updates.
Specifically.
There
are
necessarily
from
the
last
time
the
community
meeting
here,
but
you
know
we're
still
continuing
to
do
some
controllers
to
support
remote
propagation
scenarios
and
local
deployment
scenarios
as
well
for
the
4-ohm,
open
application
model.
Dan
I
think
the
work
on
the
remote
implementation
is
pretty
well
far
along
right.
Yep.
B
It's
pretty
much
done
we're
doing
some
testing
with
it.
Now
we
moved
some
of
the
work
that
was
done
there
into
core
cross
plane
and
cross
plane
runtime,
which
basically
allows
us
to
use,
as
for
both
local
and
remote
scenarios,
so
always
want
to
share
code
where
possible.
Also,
some
of
the
code
can
be
used,
reused
for
different
types
of
om
workloads,
so
right
now
we're
just
implementing
core
types,
but
you
can
imagine
that
there
may
be
different
types
of
workloads
that
all
get
translated
to
similar
objects
or
at
least
get
wrapped
up.
B
So
a
great
example
of
this
is
in
the
remote
case.
We
do
all
the
translation
of
the
OEM
workloads
to
kubernetes
native
resources
like
a
deployment
or
pod,
or
something
like
that
or
maybe
a
service,
and
then
we
wrap
those
up
in
a
KU
Bernays
application
schedule
them
to
a
remote
cluster.
So
we've
made
it
pluggable,
so
you
can
essentially
package
up
your
workload.
However,
you
want
with
your
reconciler
and
then
just
pass
to
the
shared
reconciler.
B
You
know
wrap
and
kuba,
or
something
like
that,
and
it
will
wrap
it
up
for
you,
and
so
you
kind
of
get
that
same
functionality
just
with.
Basically,
a
one-line
change
in
your
implementation
of
the
controller
so
should
be
a
pretty
extensible
model
that
allows
us
to
build.
On
top
of
this
kind
of,
like
initial
proof-of-concept
work
really
quickly.
B
A
D
D
D
D
There's
some
there's
a
lot
of
testing
to
do
in
here
to
actually
bring
it
up
and
open
Jepson.
So
some
things
that
in
steps
that
have
to
go
through-
and
you
see
the
file
exchange,
there's
like
all
of
the
crops
playing
see
our
deeds
and
then
to
metadata
files
that
are
not
cosplaying,
see
our
deeds.
And
so
it
will
be
nice
to
automate
this
and
in
the
future.
Somehow
that
for
each
release
you
don't
have
to
and
crap
this
job.
A
Yeah
and
I'd
be
interested
that
maybe
we
can
sync
up
about
like
the
various
transformations
that
have
to
get
done
here,
cuz
yeah,
having
to
do
that
by
hand
like
there's
a
change
in
one
of
our
CR
DS
like
to
add
a
new
field,
or
whatever
do
we
have
to
do
a
whole
bunch
of
steps
manually
or
what's?
What's
that,
like
I,
would
hoping
that
they
would
have
some
upstream
tooling
to
make
this
a
streamlined
process
as
well.
Yeah.
B
D
One
of
the
things
that
neither
offers
that
I
was
thinking
would
be
useful
is
if
the
cute
builder
had
an
annotation
to
say,
here's
an
example,
CR
of
noisy
Rd
and
our
pipeline
of
generating
docks
and
generating.
Examples
could
be
based
on
that
and
then
I
would
want
that
to
make
it
into
some
other
output
that
make
it
into
the
CR
D
and
then
I
want
a
operator
hub
tool
that
will
look
at
all
the
CR
DS
and
generally,
this
metadata
file
said
I
just
want
a
lot
of
turtles.
D
A
Goes
that
sizzle
great
work
getting
that
started
and
that'll
be
really
awesome
to
be
able
to.
You
know,
gain
some
traction
and
you
know
make
the
cross
plain
efforts
available
in
openshift
and
an
operator
UPS,
that's
awesome,
move
offic!
Do
you
want
to
give
us
an
update
about
composition,
model
I,
don't
know
if
it's
been
captured
in
the
PR
yet,
but
I
know
that
you,
you
all
made
some
progress
last
week
on
that
you
and
Nicky
Bassam.
C
A
C
C
C
A
A
B
For
sure,
so,
all
of
these
issues
here
are
around
backup
and
restore
for
a
cross
plane
cluster.
So
the
idea
is
that
you
could
have
backups
essentially
of
all
your
configuration
in
your
communities
cluster,
all
of
your
cross,
plane
resources
and
then,
when
they
are
lost
and
then
bulk
reapplied,
then
they
would
automatically
essentially
assume
the
external
resources
and
reflect
the
exact
state
is
when
they
were
lost.
So
there's
a
couple
of
moving
pieces
there.
B
First
of
all,
the
kind
of
obvious
one
is
being
able
to
query
the
cloud
provider,
the
external
provider
and
see
if
the
resource
already
exists.
So
we
already
support
that
with
a
lot
of
resources,
but
these
three
issues
for
DCP,
AWS
and
Azure
and
making
sure
we
have
that
support
I'm
on
all
of
them.
So
basically,
when
the
manage
resource
gets
created
in
the
observe,
it's
gonna
see
that
that
managed
resource
already
exists,
and
then
it's
gonna
start
managing
that
and
then
some
of
these
other
ones
are
related
to
other
components
of
crossplane.
B
We
don't
want
crossplane
to
be
able
to
create
a
kunai's
application
that
just
establishes
control
over
those
resources,
but
we
do
want
if
that
resource
was
created
by
crossplane,
when
a
crew
neighs
application
gets
recreated
for
it
to
be
able
to
regain
control
of
resources,
it
was
already
controlling.
So
basically,
all
we
did
here
is
that
when
we
check
for
the
owner,
we
remove
the
UID
of
the
kubernetes
application
resource,
because
that
would
change
when
you
restore
it
back
up.
B
So
we
just
make
sure
the
name
and
namespace
exists
and
we
actually
do
still
place
the
UID
annotation
on
the
remote
resource.
But
now
you
won't
be
able
to
assume
control
of
a
resource
that
wasn't
created
by
crossplane,
but
you
also
will
be
able
to
assume
ones
if
you
lost
the
owner
for
a
period
of
time.
So
that's
what
that
is,
and
then
the
second
one
there
is
in
regards
to
making
sure
that
claims
rebind
to
the
correct
managed
resource
when
they're
created
and
if
they're,
in
different
order.
B
So
if
both
resources
are
already
bound,
but
they
actually
or
I
guess
when
they're
recreated
that
that
they
bind
to
each
other
and
then
the
third
one
there
I
actually
don't
remember
what
I
put.
But
we
can.
Click
on
it
looks
like
I've
tagged,
move
offic
on
this,
so
assume.
Oh,
it's
the
doc
for
backup
and
restore
so
I,
don't
know
what
the
timetable
is
for
that,
but
essentially
just
describing
how
to
do
backup
and
restore
of
a
crossplane
cluster.
A
Did
we
have
as
an
issue
for
updating
controllers
of
each
one
of
the
providers
as
well?
Yep
cool,
great
yeah,
but
it's
gonna
be
a
bit
of
effort
to
get
those
scenarios
supported,
but
it's
absolutely
a
a
nice
step
towards
reliability.
Instability
over
time
as
well
spit,
especially
in
the
face
of
disaster
recovery,
cool
I,
said,
and
it
looks
like
you
and
your
copious
spare
time
started
up
a
another
project.
Here,
that's
pretty
exciting
when
it
tell
us
about
this.
One
sure.
B
So
this
is
a
template
repository
which
is
I
feel
like
kind
of
an
underused
to
get
hub
feature
that
basically
allows
you
to
create
a
new
repository
from
an
existing
one.
So
you'll
see
I,
guess
green
I,
don't
know
what
color
that
is
I'm
colorblind,
but
anyway
you
can
click
that
and
create
a
new
repository
with
this
one.
So
this
is
basically
the
bare
bones
of
a
cross
flane
provider.
B
It
doesn't
rely
on
the
bound
build
sub
module,
which
makes
building
providers
a
lot
easier,
but
sometimes
people
don't
want
to
manage
that
dependency
of
a
sub
module
and
they
don't
have
to
update
and
that
sort
of
thing-
and
it's
a
little
bit
simpler,
just
to
kind
of
see
these
this
make
file
here.
So
it
does
the
basics
of
building
your
stack
packaging
it
allowing
you
to
push
it
to
docker
hub
and
then
install
it
into
a
cross
plane
cluster.
B
So
this
works,
as
is
it
basically
just
has
a
provider
resource
and
then
a
resource
called
MyType
which,
just
as
a
dummy
fields
in
it
and
the
controller,
just
prints
the
struct
on
every
reconciliation
loop.
So
it's
meant
to
be
modified
to
fit
your
use
case,
but
it
has
a
bunch
of
this
stuff
built
in
so
you
can
get
going
really
quickly.
I
think
a
lot
of
times,
actually
installing
a
stack
or
a
provider
kind
of
gives
you
a
better
picture
of
what
you
need
to
do
to
continue
to
build
it
out.
B
So
this
is
meant
to
get
you
to
that
installation
step
a
lot
faster.
So
there
needs
to
be
a
live
documentation
to
go
with
this.
Obviously,
there
might
also
be
parts
that
we
don't
want
to
clewd
or
we
do
want
to
include
or
a
better
way
to
demonstrate
an
example
resource,
but
this
will
get
someone
going
relatively
quickly.
So
that's
the
goal
here
also
in
this
board
here
this
cross
flamebook
org,
which
is
basically
just
created,
so
I
could
get
a
free,
github
website.
B
It's
going
to
have
some
documentation
just
about
getting
started
with
cross
plans.
So
it's
more
of
like
an
informal
guide
so
different
than
the
docs
it
starts
with.
Like
learning
go
basically
and
it
is
extremely
incomplete,
extremely
work
in
progress.
But
if
you
are
someone
who
is
working
on
building
new
providers
or
extending
crossplane,
then
this
is
probably
a
good
place
to
start
so
welcome
to
any
and
all
feedback
on
you.
These
different
components
here.
A
Right
on
awesome,
Daniel,
that's
good
stuff
there,
let's
see
yeah
I
appreciate
your
efforts
on
you
know,
facilitating
or
advancing
the
experience
around
adding
codes
across
playing.
You
know
adding
new
extensions
and
you
know
writing
support
for
it.
So
that's
definitely
useful
to
help
adoption
in
the
developer
community
as
well.
Okay,
so
that
was
everything
in
the
community
topics
section,
and
so
we
can
move
on
to
the
PRS
discussions
here.
I
I
just
listed
this
PR
that
I
was
working
on
for
these
process
updates.