Skip to content

Commit b4a722a

Browse files
committed
Talk about configuring software - not deploying it
Signed-off-by: Nic Cope <[email protected]>
1 parent 9188eb5 commit b4a722a

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

content/v2.0-preview/_index.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ cascade:
88
Welcome to the Crossplane documentation. Crossplane is a control plane framework
99
for platform engineering.
1010

11-
Crossplane lets you build control planes to manage your apps, infrastructure, or
12-
anything else. It lets you design the APIs and abstractions that your users use
13-
to interact with your control planes.
11+
Crossplane lets you build control planes to manage your cloud native software.
12+
It lets you design the APIs and abstractions that your users use to interact
13+
with your control planes.
1414

1515
Crossplane has a rich ecosystem of extensions that make building a control plane
1616
faster and easier. It's built on Kubernetes, so it works with all the Kubernetes
@@ -20,10 +20,12 @@ tools you already use.
2020
**A control plane is software that controls other software.**
2121

2222
Control planes expose an API. You use the API to tell the control plane what
23-
software it should deploy and how - this is your _desired state_. It could be
24-
any cloud native software, like an app, a load balancer, or a GitHub repository.
23+
software it should configure and how - this is your _desired state_.
2524

26-
The control plane deploys your software, then monitors it throughout its
25+
A control plane can configure any cloud native software. It could deploy an app,
26+
create a load balancer, or create a GitHub repository.
27+
28+
The control plane configures your software, then monitors it throughout its
2729
lifecycle. If your software ever _drifts_ from your desired state, the control
2830
plane automatically corrects the drift.
2931

0 commit comments

Comments
 (0)