►
From YouTube: Spotlight Live - Crossplane
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
Today,
on
the
show
we
have
a
founder
and
ceo
bossam
tabara
of
crossplane
crossplane
is
an
open
source,
kubernetes
add-on
that
adds
platform
teams
to
assemble,
that
enable
excuse
me,
platform
teams
to
assemble
infrastructure
from
multiple
vendors.
It's
a
sandbox
project
rocketing
towards
incubation.
I've
been
a
fan
of
these
folks
for
a
long
time.
Spotlight
starts.
A
A
All
right
so
before
I
bring
in
boston,
I
just
want
to
do
the
disclaimer.
This
is
an
official
live
stream
of
the
cncf
and
such
is
a
subject
to
the
cncf
code
of
conduct.
Please
do
not
do
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct.
Basically,
please
be
respectful
of
all
welcome
to
spotlight
live
bassam.
How
are
you.
A
And
we've
been
friends
for
a
while.
You
know
I've
been
like
how
like,
let's
we
want
to
figure
out
the
perfect
time
to
like
just
sit
down
and
talk
about
cosplay,
because
you
know
I've
been
a
fan
of
y'all
because
I
did
a
live
stream
with
sig
dan.
Remember
dan
mangum
and
I
was
like
this
project
is
so
fantastic
and
I
was
like
you
know.
A
B
So
the
crossplane
origin
story
goes
back
to
probably
2016..
I
was
working
on
another
project
and
it
was
called
the
rook
project
that
I
had
helped
start
and
if
you,
if
you
remember,
rook,
is
essentially
a
control
plane
for
storage
and
it
was
built
on
kubernetes
and
it
was
designed
to
kind
of
manage
storage
infrastructure
and
it
was
so
cool
because
it
was
early
days.
I
was
looking
at
kind
of
kubernetes
and
thinking
about
this
was
the
year
kind
of
when
kubernetes
won
the
container
orchestration
war.
B
If
you
remember-
and
it
was
kind
of
starting
to
emerge
as
the
clear
winner
and
what
I
saw
was
not
kubernetes
as
a
container
platform,
I
saw
kubernetes
as
a
generic
control
plane
that
could
be
used
in
scenarios
well
beyond
containers,
and
so
rook
was
a
great
example
of
that,
because
it
built
it
was
a
control
plane
for
storage.
It
was
using
the
kubernetes
control
plane,
but
it
was
essentially
built
for
to
manage
storage
systems,
and
so
you
know
I
got
excited
about
the
whole
approach
I
saw.
B
I
saw
the
you
know
that
this
could
be
this.
You
know
the
kubernetes
control
thing
can
be
used
to
manage
all
things,
all
things,
infrastructure
and
cross
clouds,
or
hybrid
or
multi-cloud,
and
then
went
off
and
started
a
company
and
crossplane
was
born
at
upbound,
with
a
charter
of
essentially
bringing
the
control
plane
approach
that
was
pioneered
in
kubernetes
to
the
general
problem
of
managing
cloud
infrastructure.
In
some
ways
you
can
think
of
say
cross
plane
as
uncontainerizing
kubernetes,
which,
which
is
you
know
par.
B
A
B
Yes,
there's
a
lot
of
people
that
that
you
know
kubernetes
is
not
known
for
being
simple,
but
I
think
if
you
change
the
perspective
a
little
bit
and
think
of
kubernetes
as
not
the
developer
facing
you
know
a
platform
but
more
of
a
middle
layer
in
between
say
application
developers
and
whatever
they
consume,
whether
it's
pipelines
or
consoles
or
cli's
or,
however,
they're
doing
their
work
and
building
their
applications.
B
And
then
you
think
of
think
of
kubernetes
as
the
middle
layer
that
it
sits
between
them
and
the
cloud
or
infrastructure
in
general.
And
so
in
some
ways,
if
you
think
of
kubernetes
as
a
middle
layer,
it
middle
layers
tend
to
be
complex.
They
tend
to
be.
They
tend
to
offer
a
lot
of
flexibility
they
because
people
are
using
them
to
build
their
own
kind
of
opinionated
platforms
and
others
other
things
on
top
and
so
yeah.
I
I
share
the
sentiment,
but
I
also
think
it's
a
matter
of
perspective.
A
I
understand
so
for
everybody
who's
just
joining
us
again.
I
have
bassam
tabata,
he's
the
ceo
and
founder
of
crossplane
and
we're
just
going
through
the
motions.
I
want
to
ask
you,
this
love
the
logo,
the
ice
cream.
Look,
I
mean
you,
you
know
like
we
all
love
ice
cream
and
we
all
love.
Icicles.
Tell
me,
explain
the
the
logo.
Can
we
talk
about
cross
plains,
logo.
B
So
so
credit
for
the
logo
goes
to
our
our
designer
matt
heilman
and,
to
be
quite
honest,
I
was
kind
of
against
it
I
to
just
to
be
to
be,
but
the
idea
was
you
know,
so
we
we
picked
the
name
crossplane
among
many
other
choices
that
were
there
I'll
someday
I'll.
B
Tell
you
about
how
many
domain
names
and
github
organizations
I'm
boarding,
but
so
so
we
landed
on
crossplane
and,
and
it
was
essentially
a
player
play
on
the
both
the
word
cross
cloud
and
control
plane,
and
so
we
were
kind
of
trying
to
go
for
a
name
that
becomes
a
noun
or
you
know
you
could
say,
hey
look
I
brought
in
a
cross
plane
and
I
connected
it
up
to
aws
and-
and
I
don't
know
if
that's
stuck
that
way,
but
that
was
the
intention
of
that.
B
You
can
basically
drop
crossplane
anywhere
you're
using
the
word
control
plane,
and
so
the
popsicle
came
kind
of
fall
off.
That
thinking,
which
is
you
know,
if
it's
cross
cloud,
then
you
need.
We
were
looking
for
something
that
had
multi-flavor
in
it
multi-cloud
multi-things,
and
so
we
ended
up
with
and
we
wanted
something
that
was
playful,
and
I
think
that
the
idea
was
hey.
B
What
was
a
what,
if
it
was
a
multi-flavored
multi-colored
popsicle
pop
everybody
loves
popsicles
so,
and
so
there
is
your
multi-flavored
popsicle
and
that's
how
we
landed
on
it.
You
should
see
that
other.
A
A
A
Yep,
it
was
fate,
so
so
carlos
bernardo
asked
that
question
you
you
nailed
it.
You
got
that
one
out
there
and
also
we
have
our
friend
which,
by
the
way
I
could
spend
an
hour
just
talking
about
hash
dan.
That
guy,
like
you
lo,
I'm
sorry
that
guy
you
could
build
10
companies
around
that
dude.
So
we
loved
him
not
a
doubt.
So
let's
go
back
to
again
you're
at
rook
and
there's
this
original
problem
you
trying
to
solve
and
it
was
like
what
are
we
doing
like.
A
A
B
Operations,
engineers
and
cloud
engineers
in
general,
I
mean
you
see
it
like
when
when
you
keep
ctl
apply-
and
you
say:
okay
kubernetes,
please
run
you
know
three
replicas
of
this
container
for
me
right
that
you
give
it
this
declarative
statement
and
then
kubernetes
goes
off
and
make
sure
there
are
three
three
replicas
of
the
container
running.
If
a
node
goes
away,
if
a
node
comes
back,
it's
still
managing
that
on
your
behalf.
You
don't
have
to
get
involved
it'll.
B
If
a
note
goes
down,
that's
running
one
of
your
replicas
it'll,
restart
it
somewhere
else
that
logic
and
that
approach
motivated
us
to
kind
of
start
crossplane,
and
so
that
we
can
bring
that
approach
to
all
of
cloud
infrastructure
and
not
just
containers
right
like
when
you,
when
you
want
to
you
know
when,
when
you
want
to
kind
of
light
up
infrastructure,
say
in
aws
right,
you
should
be
able
to
in
the
same
way
cube
ctl
apply,
it
apply
the
change
and
then
let
the
control
plane
from
that
point
onward
handle
the
deployment
the
provisioning
scaling.
B
The
life
cycle
management
handle
all
of
it,
that
that
should
be
an
autonomous
process
and
it
should
be
something
that
humans
don't
have
to
get
involved
in,
and
so
once
we
saw
that
happening
in
the
kubernetes
space
we
got
motivated
to
kind
of
say
look:
can
we
bring
that?
Can
that
be
the
new
way
that
we
manage
infrastructure
in
the
cloud?
B
Can
that,
and
ironically,
like
the
the
thing
you
know,
people
don't
realize,
but
that's
literally
how
the
largest
platforms
in
the
world
are
built
if
you
peek
behind
the
scenes
in
aws
that
who
are
when
you
ask
for
an
s3
bucket,
what's
the
entity
behind
the
scenes,
that's
serving
that
api,
that's
taking
that
request,
that's
deploying
allocating
a
bucket
and
that
you
know
essentially
allocating
to
you
doing
all
the
billing
doing
all
the
metering
around
it.
It's
the
control
plane
in
aws
everything
in
most
large
cloud
providers.
A
One
of
the
things
like
I
said
I
was
I
did
that
live
stream
hashtag
and
you
know
he
kind
of
showed
me
what
was
going
on.
I
played
with
it,
and
I'm
like
this
is
incredible
because
it
was
before
I
was
like.
Okay,
I
go
to
my
cloud
for
information
scripts.
I
would
do
all
these
things
together
to
play,
then
I
have
to
put
my
applications
on
top
of
it,
and
I'm
like
this
is.
This
is
great,
but
like
one
of
the
things
that
you
know
here
is
okay.
What
would
I?
A
Why
would
I
use
this
over
say
like
a
terraform
or
like
cloud
volt
or
something
like
that
like?
Why
would
I
you
know,
use
cross
plane
or
upbound
over
other
tools.
B
Yeah,
it
might
be
useful
to
kind
of
just
kind
of
review
the
differences
between
the
approaches-
and
you
know
so
terraform-
is
in
the
class
of
tooling
that
up,
you
know
commonly
referred
to
as
infrastructure
as
code
right
and
and
infrastructure.
Score
tooling,
is
amazing,
like
it's.
A
terraform
terraform
as
well
is
fanta
is
a
fantastic
and
widely
adopted
project
right
and
but,
if
you
think
about
the
problem
being
sold
there,
it
was
how
do
we
arrive
at
a
declarative
configuration
that
we
can
reproduce
easily
reproduce
right?
B
It's
designed
for
a
human
operator
to
run
so
you're,
basically
saying
look.
I
want
to
describe
my
infrastructure,
I
author
it
as
a
configuration.
Typically,
it's
a
domain
specific
language
like
hcl
or
more
popular
these
days
are
traditional
programming,
languages,
python,
typescript,
etc
right.
But
what
I'm
doing
is
I'm
authoring
a
declarative
configuration
of
a
set
of
infrastructure,
the
design.
B
The
design
point
is
that,
once
you
have
that
configuration
you
as
a
human
get
to
apply
it,
whether
it's
you
know,
tf
apply
or
it's
run
a
program
you're
applying
you,
the
human
are
applying
the
the
configuration
and
you
as
a
human,
are
looking
at
the
diff
of
what
changes
are
to
be
made
in
you
know
your
cloud
provider
and
so
you're
approving
these
changes
and
you
apply
it
and
that
point
the
infrastructure
is
lit
up
and
the
tool's
out
of
the
way
right
and
if
you
want
to
make
other
additional
changes,
you
have
to
come
back
edit.
B
B
First
of
all,
they
serve
not
you,
don't
you
can
author
things
in
templates
or
configuration
like
camel
or
or
you
can
also
do
that.
You
know
whatever
pick
your
your
tooling
of
choice,
but
the
first
primary
difference
is
that
you,
once
you
author,
these
things
you're
interacting
with
an
api,
the
api
there's
an
api
that
represents
every
resource
that
you
want
to
configure,
deploy,
manage
right
versus.
So
the
interaction
is
you're
talking
to
restful
endpoints,
to
create
the
configuration
you're,
not
just
authoring
the
configuration
in
a
template
and
then
invoking
and
applying
the
tool.
B
But
the
more
interesting
scenarios
come
in
when
the
human
workflows
end.
When
you
apply
the
configuration
to
control
you're
out
of
the
way
you
don't
have
to
sit
and
wait
for
it
to
come
up
or
manage
the
order
in
which
it
comes
up
or
if
you
have
a
scale
act
or
a
upgrade
act
that
can
be
done
autonomously
by
a
set
of
robots
controllers
that
are
running
inside
the
control
plane.
B
So
the
the
the
workflow
becomes
you
as
humans.
Collaborate
on
configuration,
whether
it's
git,
you
know,
git
ops,
is
a
popular
term.
These
days,
the
human
workflow
ends
as
soon
as
you
hand
it
over
to
the
control
plane
and
from
that
point
onwards,
the
control
plane
is
autonomously
making
changes,
applying
changes
in
order
when
things
go
down,
it's
able
to
reconcile
them
and
essentially
bring
up
infrastructure
and
fix
it.
B
That
is
a
fundamental
difference
between
infrastructure,
as
code
tooling
and
control
planes,
and
so
so
back
to
your
original
question,
how
why
would
I
use
this
over
terraform
honestly
that
it
comes
down
to
a
few
things?
One
you
can
achieve
a
much
higher
degree
of
automation
with
control
planes
than
you
can
with
any
infrastructure
as
go
tooling.
B
It's
it's
that
it's
that
simple,
because
you're
running
autonomous
controllers,
the
other
is
is
one
that's
less
obvious
is
that
you
can
actually
organize
around
control
planes
because
they
the
units
that
they
expose
as
an
api,
and
so
you
can
consume
apis
from
any
tool
any
framework.
Any
language
look
at
the
healthy
ecosystem
built
around
the
kubernetes
api.
It's
unbelievable
how
many
tools
and
consoles
and
ui
and
pipelines,
and
that
have
built
and
talk
kubernetes
api
on
the
back
end
right.
B
Compare
that
to
any
of
the
popular
infrastructures
code
tooling,
and
look
at
the
ecosystem
around
them
right,
apis,
promote
a
larger
ecosystem,
apis,
promote
organizational
boundaries
that
enable
teams
to
scale
and
so
and
they
come
with
access
control
and
they
come
with
all
sorts
of
other
benefits.
But
but
those
are
the
primary
reasons
I
would,
I
would
think
of
when
you
know
making
a
choice
between
using
you
know:
infrastructure,
score,
tooling
and
and
control
planes.
B
One
one
other
thing.
I'd
say
that
comes
up,
especially
in
the
cloud
native
world.
If
you've
already
adopted
kubernetes
and
you're
running
kubernetes,
there
is
much
less
friction
to
use
something
like
crossplane,
then,
to
figure
out
how
to
shell
out
to
some
external
process
and
run
multiple
pipelines
and
figure
out.
B
You
know,
run
infrastructure
as
code
tooling
and
light
up
one
part
of
it
and
bring
credentials
back
and
stuff
them
into
secrets,
and
you
can
avoid
all
of
that
by
letting
your
developer
self-service
on
infrastructure
using
the
same
tooling
and
pipelines,
and
you
know
that
they're
used
to
and
using
today
with
kubernetes.
That
part
makes
the
whole
process
frictionless.
A
Fantastic
and
again
I
mean
if
I
was
a
tldr,
it's
just
that
you
know
it's
a
control
plan
over
a
tool.
You
have
all
the
you
know
the
the
aspects
of
that
the
authorization
all
all
that
that
you
can
bind
into
you
know
and
and
that's
fantastic
and
you're,
touching
the
apis
directly.
You
have
a
question
from
carlos
panado.
It's
a
new
guy.
I've
never
heard
of
him.
I've
heard
of
him
once
a
couple
times.
Is
it
possible
to
import
existing
infrastructure
to
crossplane.
B
Yes,
it
is
possible,
so
every
managed
resource
in
crossplane
has
a
notion
of
an
external
identity
and
you
could
use
that
to
adopt
existing
resources,
we're
actually
looking
into
and-
and
we
mentioned
hash
dan
earlier-
but
we're
looking
into
a
set
of
tooling.
That
actually
makes
that
a
lot
easier
so
that
you
can
go
directly
to
a
account
and
say
aws
and
then
generate
and
adopt
the
resources
that
are
already
running
there
as
part
of
crossplane.
B
A
B
Yeah,
so
so
one
of
the
things
that
is
a
fundamental
difference
is
that
every
resource
think
of
s3
buckets
and
rds
instances
and
ec2
instances
and
all
of
the
resources
that
are
exposed
by
say
cloud
providers
get
their
own
api
endpoints
in
crossbind.
So
you
can
go
to
a
crossplane.
B
B
A
can
deploy,
rds
instances
and
team
b
can
deploy
ec2
instances,
and
you
can
even
change
your
mind
about
access
control
without
having
to
change
any
of
the
configurations
that
you
have
in
place,
and
so
it
becomes
a
lot
easier
to
support
multiple
teams
with
different
separation
of
concerns
or
dev
suck
ops
versus
devops,
or
you
know
all
within
one
control
plane
and
set
the
access,
control
policies,
and
do
so
without
having
to
you
know
artificially
break
put
things
into
smaller
modules
or
you
know,
have
to
refactor
everything
as
you
change
access
control,
and
so
that's
a
that's,
a
power
of
being
in
a
control
plane
that
you
don't
see
in
most
other
infrastructure.
B
A
Awesome,
I
have
a
question,
but
before
we
get
to
that
you
all,
if
you
haven't
already,
please
go
ahead
and
click
that,
like
like,
follow
over
there
in
the
top
and
said
and
subscribe
to
cloudnativetv
on
twitch
we're
always
looking
to
subscribe
here.
You're
going
to
see
a
lot
of
these
amazing
shows
just
like
this,
and
we
try
to
do
this
all
week,
but
this
is
for
the
community
it's
by
the
community.
A
B
I
have
to
say
we
have
a.
We
have
a
fantastic
team
at
up
end,
so
I'm
like
every
day,
I'm
wowed
by
by
all
the
things
that
we're
doing
around
crossland
and
everything
else,
but
the
more
general
question
kind
of
community-wise,
I
think
so
so
a
project
like
crosman
is
very
central
right
it.
B
You
have
to
build
a
lot
of
providers
and
integrations
to
it
to
to
connect
it
to
different
things
right
and,
and
so
like
every
day
we
see
or
every
week
we
see
another
integration
into
crossband
that
makes
you
know,
puts
it
to
use
in
a
domain
that
we
haven't
necessarily
thought
about,
or
in
an
approach
that
we
even
thought
about
like
just
yesterday.
B
B
If
you're
using
spinnaker
you're
happy
with
spinnaker,
you
can
now
use
it
to
deploy
infrastructure
and
let
your
team
self-service
from
the
same
pipelines
they're
using
more
and
more
of
this
you'll,
see
we're
seeing
on
it
on
a
daily
and
a
weekly
basis
around
the
crossband
community,
one
of
one
of
one
of
the
folks
that
we
know
is
kind
of
deploying
cross-plain
production.
B
You
know
like
they
use
it,
they're
using
it
in
a
you
know,
a
lot
of
financial
context,
we're
seeing
we're
seeing
it
applied
in
all
sorts
of
different
segments
of
the
industry,
and
it's
just
super
super
exciting
to
see
the
adoption.
It's
super
exciting
to
see
how
people
are
integrating
it
as
a
centerpiece
of
their
modernization
effort.
A
It's
fantastic
and
again
because
of
that
easy
use,
because
it's
able
to
touch
so
many
different
things
at
the
api
level.
I
just
that's
why
I
when,
when
he
showed
it
to
me
original,
I'm
like
right
now,
it's
amazing
and
that
this
was
like
six
months
ago
or
six
to
eight
months
ago.
It's
incredible.
We
have
another
question
and
what
about
integration?
Modern
tools
like
data
dog
or
prometheus,
or
anything
like
that.
B
So
so,
there's
two
things
that
I
think
of
here,
one
is:
does
cro.
Crossplane
itself
exposes
a
set
of
you,
know,
telemetry
and
and
tracing
that
could
be
used
by
a
lot
of
tools
for
it.
You
know
for
crossband
itself
and
I
think
the
other
way
to
think
about
this
is,
can
crossplane
be
used
to
automate.
B
You
know
monitoring
systems
like
prometheus
and
datadock,
and
I
think
that
would
require
a
provider
for
datadog,
which
I
don't
believe
exists,
although
I
I've
heard
rumors
that
somebody's
working
on
one.
A
If
you
use
like
some
of
the
native
primitives
like
prometheus
and
stuff,
like
that,
I
think
that
you
originally
were
like
outputting
to,
like
you
know,
just
regular,
like
you
know,
cube
system
level,
logging
and
all
of
that
fun
stuff,
because
I
remember
I
was
able
to
get
cystic
to
be
able
to
get
some
of
the
data
out
of
it
when
we
were
working
through
it.
So
I
think
it's
infinitely.
B
Possible
yeah
again
we
support
a
bunch
of
that
today,
so
you
you
can
actually
integrate
cross
blind
telemetry
into
your
your
prometheus
systems
and
and
and
others
yeah.
A
B
Very
very
good
question,
so
so
we
support
aws,
we
support
azure,
we
support
google,
we
support
alibaba
cloud
and
ibm
cloud.
Those
are
the
kind
of
providers
that
are
out
there
today
and
and
obviously
more
cover.
Iquenex
is
another
one
that
I
think
has
support
today
and
they're
more
more
coming.
B
It
brings
up
a
really
interesting
point
because,
like
when
you
think
of
crossplane
for
it
to
be
used
everywhere,
we
have
to
have
a
provider
for
every
infrastructure
vendor
out
there,
and
so
there
are
really
two
ways:
we're
approaching
this
problem
as
a
community
one.
We
welcome
contributions.
We
work
with
the
vendors
directly
we're
doing.
We
have
a
great
relationship
with
cloud
providers
and
we
work
with
them
on
generating
cross-plane
providers
from
their
back-end
infrastructure.
B
So
we
do,
for
example,
we're
doing
this
with
amazon
and
we
have
a
project
together
that
essentially
generates
across
buying
resources
directly
from
their
back-end,
go
sdks
right
and
we
support
that
effort
and
it
works
really
well.
So
it's
going
to
take
time
to
get
to
full
coverage
and
we're
working
on
on
accelerating
that
as
a
community.
But
it's
also
going
to
take
a
village
right
to
bring
all
the
missing
resources
and
try
to
get
to
100
coverage
of
every
infrastructure
vendor
out
there
right.
B
The
other
approach
that
that
we're
we've
invested
in
and
we're
going
to
see
us
do
a
lot
more
to
kind
of
get
get
more.
Bootstrapped
here
is
we're
wrapping
terraform
providers
and
bringing
them
into
the
control
plane,
and
so
that's
an
effort
that
we
started
last
year.
B
B
It
start
it
looks
like
native
crds
and
controllers
for
them,
and
you
don't
have
to
you
know,
do
anything
with
terraform
and
so
that,
with
that
approach,
we
think
we
can
get
to
fuller
coverage
sooner,
while
still
investing
in
native
providers
and
and
you'll
be
able
to
swap
them
out
in
the
future.
A
One
of
the
things
I
thought
was
cool:
let's
talk
about
that
vmware
provider,
because
I
remember
when
that
kind
of
somewhat
kicked
off
it
was
like
a
twitter.
Somebody
said
hey.
I
wanted
to
do
this
and
everybody
hopped
on
and
that's
the
beauty
of
the
community.
All
it
was
like
hey.
We
want
to
do
this,
crossband
put
this
out
there
and
then,
like
everybody,
some
vmware
people
jumped
in
and
that
provider
was
out
there
within
a
week.
B
Like
there's,
you
know
when
you,
when
you
build
something
it's
available
for
everyone
to
use,
anyone
can
become
a
maintainer
there's
a
ladder
level
that
you
can.
You
know
through
basically.
A
B
Oh
simplest
ways
to
join
our
slack
channel
slack.crossplane.io:
you
can
it's
a
very
friendly
community.
It's
there
probably
3000
people.
Now,
in
the
slack
workspace,
we
can
help
you
get
started
on
contributing,
whether
it's
documentation
or
all
the
way
to
writing
a
provider
in
crossplane,
and
we
document
our
we
have
a
you
know,
go
to
the
crossplane
repo
governance.md
describes
the
process
for
how
you
become
a
maintainer
or
even
a
steering
committee.
Member
again,
the
project
is
hosted
by
the
cncf.
It
follows
an
open
source
model.
B
It
follows
an
open
governance
model,
it's
designed,
but
it's
by
design.
You
know
for
the
community
by
the
people,
for
the
people
type
project
and
it's
it's
fitting,
because
it's
so
central
and
you,
if
you're,
if
we're
gonna,
arrive
at
essentially
you
know
a
control
plane
that
connects
to
everything.
B
It
can't
be
con
that
control
thing
can't
be
necessarily
tied
to
one
vendor
or
one
platform
or
one
company
right.
It
has
to
be.
It
has
to
be
something
that
we
as
a
community
rally
around.
We
put
all
our
effort
around
and
then
we
arrive
at
something
that
is
much
larger
than
the
sum.
Much
larger
than
the
you
know,
the
individual
pieces
but
is
is,
is,
is
much
stronger
project
for
it.
A
I
just
remember
like
when
autopilot
came
out.
You
all
had
a
you
know:
provider
in
there
like
in
like
a
day,
it
was
incredible.
Even
kelsey
was
like
hey,
you
know
within
a
day
you
all
had
it.
So
that's
exactly
what
you
just
said,
because
it's
just
open
enough
for
people
to
contribute
and
all
that.
Let
me
ask
you
this:
what's
the
difference,
I
see
an
upbound
in
the
in
the
end
upbound.
What's
the
difference
between
upbound
and
crossplane,
just
so
folks
understand
the
differences.
B
So
so
about,
as
is
the
company
behind
crossplane,
we
started
the
project
we
donated
it
to
the
cncf
and
we
offer
a
set
of
commercial
offerings
around
crossblind,
so
starting
with
a
downstream
distribution
of
crossband,
which
biso
is
also
open
source,
it's
called
upbound
universal,
crossplane,
uxb
and
then
upon
cloud,
which
is
a
management
layer
that
gives
you
a
single
point
of
control
to
you
know,
essentially
all
your
infrastructure
and
gives
you
visibility
on
what
your
teams
are
doing
and
the
apply
registry
which
is
a
free
offering
and
is
a
library
for
you
know,
crossplaying
providers
and
configurations,
and
so
we
we,
you
know,
think
of
upbound
as
helping
enterprises
that
are
adopting
crossplane
accelerate
time
to
market.
B
We
help
them.
You
know,
be
successful,
quicker
with
control
planes
and
typically
they
come
to
us
and
say
help
us
get
this
control
plane
technology
deployed
into
our
environments,
help
us
scale.
It
help
us,
you
know
be
the
vendor
that
we
we
want
to
rely
on
and
that's
that's
kind
of
what
upbound
does
around
us.
Obviously
having
started
a
project.
We
have
a
lot
of
folks
that
work
on
crossline,
but
you
know
there.
A
B
You
yeah
so
so
on
the
crossplane
side,
obviously
getting
to
incubation.
The
vote
is
imminent.
We're
it
about
to
be
kicked
off
publicly
and
the
other
thing
that's
happening
is
that
we're
we
created
a
conformance
program
around
crossplane.
That
also
is
still
subject
to
a
vote
on
the
cncf
side.
B
But
the
idea
there
was
to
you
know
enable
folks
to
when
they're
building
providers
to
ensure
that
there's
consistency
across
them
and
that
you
can
become
a
certified
provider
for
crossband
or
a
certified
distribution
of
crossline,
just
like
upbounds
uxb,
and
so
that
that
that
effort
we
think,
will
help
bootstrap
and
accelerate
the
adoption
of
crossplane
and
the
ecosystem
around
it.
B
B
So
you'll
see
more
of
that
in
future
releases
and
actually
there's
there's
a
a
live
stream
on
it.
On
on
monday,
on
the
12th
around
the
whole
terraform
thing
and.
B
B
It'll
be
part
of
our
crossband
crossband
channel
on
youtube
as
well,
so
got
it
and
then
so
that's
you
know,
and
then
we're
looking
at
improving
composition
and
all
the
cool
things
we're
doing
around
letting
people
kind
of
compose
infrastructure
and
expose
it
both
in
terms
of
develop
the
developer
experience
around
it.
So
it
can
make
it
easier
for
people
to
kind
of
author
compositions,
but
also
the
flexibility
and
support.
That's
in
it.
B
So
you'll
see
more
more
happening
in
that
in
that
space
as
well
and
an
accelerating
provider
coverage.
So
you've
heard
me
talk
about
this.
It's
one
of
our
biggest
challenges
and
it's
you
know
what's
something
that
we
are
putting
a
ton
of
ton
of
effort
around
on
the
upbound
side.
Obviously
there
is
a
lot
of
really
cool
features
as
well
around
uxb
and
upbound
cloud,
and
but
we're
mostly
focusing
on
right
now
trying
to
get
folks
to
to
production
quicker
with
with
crossblind
and.
B
A
We're
just
like
you
all
tune
in
there.
So
again,
if
you
go
to
like
their
youtube
or
you
can
go
to
crossplane
io
or
you
can
go
to
crossplane
underscore
io
for
their
twitter
it'll
have
the
details
for
that.
Well,
I
really
appreciate
you
being
on
the
show
today.
We
we
tackled
a
lot
of
stuff
today.
Is
there
any
last
last
words
you
got.
B
You
know
it
takes
a
village,
so
please
come
join
us
on
the
you
know,
crossplane
slack
again
lots
of
really
interesting
things
happening
in
this
project.
If
you're
looking
for
a
project
to
start
with
or
kind
of
get
into
open
source
with
crossplane
is
a
fantastic
place
to
do
that.
So
we
would
welcome
everyone
in
the
community
to
come.
Come
play
with
it
contribute
use
it.
B
A
All
right
everyone,
so
you
know
I'm
again
super
fan
of
of
crossplane,
I'm
so
happy.
I
got
to
talk
to
bassam,
so
we
got
I'll.
Just
tell
you
about
the
next
week,
so
I'm
going
to
be
off
next
week,
every
two
weeks
when
we
off
next
week,
solid
state,
starts
up
on
monday
with
tim
banks.
Again,
if
you
are
watching
that
show
you
need
to,
I
mean
it's
just
great,
because
he's
he's
getting
underrepresented
folks
on
talking
about
their
their
journeys.
It's
it's
great
cloud
native
latinx
again
with
leonardo.
A
It's
just
a
you
know,
a
bunch
of
you
know,
latinx
folks
that
are
in
the
community
doing
great
things.
You
all
should
definitely
check
that
out.
I
think
that's
on
tuesday
cat
cat's
back
with
cloud
native
classroom
and
there's
such
a
bunch
of
stuff
next
week,
so
we
had
a
little
lull
since
the
holiday,
but
then
we're
coming
back
strong
appreciate
all
of
you
for
following
us
tell
everybody
about
this.
Everyone
just
go.
Tell
everybody
about
cloudnative.tv
last
thing.
I'll
talk
about
is
registration
for
kubecon
and
cloud
nativecon.
A
North
america
is
open
and
in
person
you
know
just
make
sure
you're
checking
out
the
you
know
that
and
if
you
haven't
registered,
please
go
ahead
and
register.
Lastly,
I'm
not
going
to
hope
to
see
you
all
there.
I
really
want
to
give
you
all
hugs.
If
that's
okay
at
some
point
just
say
hello
to
you
all
and
just
remember
community,
the
spotlight
is
on.