mirror of https://github.com/crossplane/docs.git
docs snapshot for crossplane version `v1.0`
This commit is contained in:
parent
f46f4ba066
commit
f5ae71f861
|
@ -79,7 +79,7 @@ corresponding `MySQLInstance` claim.
|
|||
## Defining Infrastructure
|
||||
|
||||
New kinds of infrastructure resource are defined by an infrastructure operator.
|
||||
There are three steps to this process:
|
||||
There are two steps to this process:
|
||||
|
||||
1. Define your composite resource, and optionally the claim it offers.
|
||||
1. Specify one or more possible ways your composite resource may be composed.
|
||||
|
|
|
@ -266,5 +266,5 @@ including Velero.
|
|||
|
||||
[api-versioning]: https://kubernetes.io/docs/reference/using-api/api-overview/#api-versioning
|
||||
[velero]: https://velero.io/
|
||||
[api-reference]: api-docs/overview.md
|
||||
[provider]: provider.md
|
||||
[api-reference]: ../api-docs/overview.md
|
||||
[provider]: providers.md
|
||||
|
|
|
@ -101,7 +101,7 @@ documentation of each provider should give you an idea of how that credentials
|
|||
blob should look like. See [Getting Started][getting-started] guide for more
|
||||
details.
|
||||
|
||||
The following is an example usage of Azure `ProviderConfig`, referenced by a
|
||||
The following is an example usage of AWS `ProviderConfig`, referenced by a
|
||||
`RDSInstance`:
|
||||
|
||||
```yaml
|
||||
|
|
Loading…
Reference in New Issue