►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Keynote: Crossplane at the Crossroads - Bassam Tabbara, Founder & CEO, Upbound
A
A
A
The
first
property
is
that
you
interact
with
kubernetes
through
a
restful
api.
This
seems
so
obvious,
but
it's
a
far
departure
from
other
tooling.
In
this
space,
especially
infrastructure
as
code
tooling,
that
expects
templates
or
programs,
the
kubernetes
api
exposes
an
independent
restful
endpoint
for
each
resource.
It
manages
authorization,
access,
control
and
other
policies
can
all
be
enforced
centrally
and
the
granularity
of
a
single
resource,
because
it's
an
api
users
can
pick
any
language
tool
or
framework
to
interact
with
it.
Apis
offer
the
greatest
level
levels
of
interoperability
and
have
fostered
the
largest
of
ecosystems.
A
Storing
configuration
in
git
has
become
an
industry
standard
and
doing
so
enables
teams
to
use
pull
request,
flows
and
source
management
tools
for
collaboration
with
kubernetes
configurations
can
be
authored
via
ammo
programming,
languages
or
templates.
It
really
doesn't
matter
because
they
all
result
in
the
same
api
calls
all
automation,
operational
and
business
policies
live
behind
the
api
line,
kubernetes
apis,
follow
a
thin
crud
approach
and
merely
manipulate
declarative
configuration
within
the
config
store
these
apis.
These
api
calls
do
not
perform
any
synchronous,
provisioning
or
deployment
acts
once
the
declarative
configuration
is
updated.
A
A
A
With
this
new
operating
model,
organizations
can
achieve
a
high
degree
of
automation
once
reserved
for
hyperscale
cloud
providers.
This
democratization
and
implementation
of
control
theory
is
the
reason
kubernetes
won.
The
container
wars
started
crossplane
because
early
on,
we
saw
the
power
of
this
operating
model
and
wanted
to
take
it
beyond
container
orchestration.
A
Crossplane
makes
that
happen.
It
extends
kubernetes
by
adding
apis
and
controllers
that
enable
it
to
manage
resources
and
services
from
multiple
cloud
and
infrastructure.
Vendors
platform
teams
and
application
teams
can
now
simply
author
configurations
for
databases,
caches
networking
and
other
services.
A
A
A
A
A
Control
planes
offer
a
declarative
api
that
promotes
interoperability
and
results
in
a
much
larger
ecosystem.
The
separation
of
concerns
enables
self-service
and
controllers,
enable
full
automation
scenarios
and
avoid
the
drift
we
see.
Crossplane
and
kubernetes
ushering
a
new
era
of
application
and
infrastructure
management
that
will
lead
to
a
much
higher
degree
of
self-service
and
automation.
A
A
Composition
is
the
popular
feature
that
enables
platform
teams
to
define
new
self-service
apis
for
their
application
teams
and,
finally,
a
package
manager
designed
for
crossband
scenarios
building.
All
of
this
takes
a
village
and
we
have
been
humbled
by
the
ecosystem.
We're
seeing
emerge
around
the
cross
plane
project.
A
Part
of
this
is
due
to
the
fact
that
if
your
tooling
works
with
kubernetes,
it
will
automatically
work
with
crossplane
but
we're
starting
to
see
tooling
emerge
which
relies
not
just
on
the
krm,
but
also
on
xrm
in
terms
of
crossplane
providers.
The
community
started
by
bootstrapping
the
major
cloud
providers
ourselves,
but
have
now
transitioned
to
working
directly
with
the
cloud
providers
and
other
infrastructure
vendors.
A
Finally,
we've
recently
added
support
to
generate
crossplane
providers
from
terraform
providers,
bringing
the
entire
terraform
ecosystem
to
crossplane
to
ensure
the
ecosystem
remains
healthy
as
it
grows.
The
cross-plank
community
applied
to
start
a
conformance
program
for
crossplane.
This
program
is
still
subject
to
the
cncf
governing
board
approval
and
will
be
run
by
the
cncf.