crossplane
/
docs
mirror of https://github.com/crossplane/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs snapshot for crossplane version `v1.1`

This commit is contained in:
Crossplane 2021-03-19 00:35:00 +00:00
parent e960b19618
commit 04d8fb76e0
1 changed files with 35 additions and 49 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

84
docs/v1.1/README.md
View File

@ -2,52 +2,46 @@
![Crossplane](media/banner.png) ![Crossplane](media/banner.png)
Crossplane is an open source Kubernetes add-on that extends any cluster with Crossplane is an open source Kubernetes add-on that enables platform teams to
the ability to provision and manage cloud infrastructure, services, and assemble infrastructure from multiple vendors, and expose higher level
applications using kubectl, GitOps, or any tool that works with the Kubernetes self-service APIs for application teams to consume. Crossplane effectively
API. enables platform teams to quickly put together their own opinionated platform
declaratively without having to write any code, and offer it to their
application teams as a self-service Kubernetes-style declarative API.
With Crossplane you can: Both the higher level abstractions as well as the granular resources they are
composed of are represented simply as objects in the Kubernetes API, meaning
they can all be provisioned and managed by kubectl, GitOps, or any tools that
can talk with the Kubernetes API. To facilitate reuse and sharing of these APIs,
Crossplane supports packaging them in a standard OCI image and distributing via
any compliant registry.
* **Provision & manage cloud infrastructure with kubectl** Platform engineers are able to define organizational policies and guardrails
* [Install Crossplane] to provision and manage cloud infrastructure and behind these self-service API abstractions. The developer is presented with the
services from any Kubernetes cluster. limited set of configuration that they need to tune for their use-case and is
* Provision infrastructure primitives from any provider ([GCP], [AWS], not exposed to any of the complexities of the low-level infrastructure below the
[Azure], [Alibaba], on-prem) and use them alongside existing application API. Access to these APIs is managed with Kubernetes-native RBAC, thus enabling
configurations. the level of permissioning to be at the level of abstraction.
* Version, manage, and deploy with your favorite tools and workflows that
you’re using with your clusters today.
* **Publish custom infrastructure resources for your applications to use** While extending the Kubernetes control plane with a diverse set of vendors,
* Define, compose, and publish your own [infrastructure resources] with resources, and abstractions, Crossplane recognized the need for a single
declarative YAML, resulting in your own infrastructure CRDs being added to consistent API across all of them. To this end, we have created the Crossplane
the Kubernetes API for applications to use. Resource Model (XRM). XRM extends the Kubernetes Resource Model (KRM) in an
* Hide infrastructure complexity and include policy guardrails, so opinionated way, resulting in a universal experience for managing resources,
applications can easily and safely consume the infrastructure they need, regardless of where they reside. When interacting with the XRM, things like
using any tool that works with the Kubernetes API. credentials, workload identity, connection secrets, status conditions, deletion
* Consume infrastructure resources alongside any Kubernetes application to policies, and references to other resources work the same no matter what
provision and manage the cloud services they need with Crossplane as an provider or level of abstraction they are a part of.
add-on to any Kubernetes cluster.
* **Deploy applications using a team-centric approach with OAM** The functionality and value of the Crossplane project can be summarized at a
* Define cloud native applications and the infrastructure they require with very high level by these two main areas:
the Open Application Model ([OAM]).
* Collaborate with a team-centric approach with a strong separation of
concerns.
* Deploy application configurations from app delivery pipelines or GitOps
workflows, using the proven Kubernetes declarative model.
Separation of concerns is core to Crossplane’s approach to infrastructure and 1. Enabling infrastructure owners to build custom platform abstractions (APIs)
application management, so team members can deliver value by focusing on what composed of granular resources that allow developer self-service and service
they know best. Crossplane's team-centric approach reflects individuals often catalog use cases
specializing in the following roles: 2. Providing a universal experience for managing infrastructure, resources, and
abstractions consistently across all vendors and environments in a uniform
* **Infrastructure Operators** - provide infrastructure and services for apps way, called the Crossplane Resource Model (XRM)
to consume
* **Application Developers** - build application components independent of
infrastructure
* **Application Operators** - compose, deploy, and run application
configurations
## Getting Started ## Getting Started
@ -56,11 +50,3 @@ specializing in the following roles:
<!-- Named Links --> <!-- Named Links -->
[Install Crossplane]: getting-started/install-configure.md [Install Crossplane]: getting-started/install-configure.md
[Custom Resource Definitions]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
[reconciling]: https://kubernetes.io/docs/concepts/architecture/controller/
[GCP]: https://github.com/crossplane/provider-gcp
[AWS]: https://github.com/crossplane/provider-aws
[Azure]: https://github.com/crossplane/provider-azure
[Alibaba]: https://github.com/crossplane/provider-alibaba
[infrastructure resources]: https://blog.crossplane.io/crossplane-v0-10-compose-and-publish-your-own-infrastructure-crds-velero-backup-restore-compatibility-and-more/
[OAM]: https://oam.dev/