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.6`

This commit is contained in:
Crossplane 2022-01-06 23:01:03 +00:00
parent 760eefc7b2
commit d9eea658a6
4 changed files with 11 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/v1.6/concepts/composition.md
View File

@ -86,6 +86,9 @@ spec:
names:
kind: XPostgreSQLInstance
plural: xpostgresqlinstances
claimNames:
kind: PostgreSQLInstance
plural: postgresqlinstances
versions:
- name: v1alpha1
served: true

6
docs/v1.6/concepts/providers.md
View File

@ -57,7 +57,7 @@ kind: Provider
metadata:
name: provider-aws
spec:
package: "crossplane/provider-aws:v1.6.0"
package: "crossplane/provider-aws:v1.6.1"
```
The field `spec.package` is where you refer to the container image of the
@ -68,9 +68,9 @@ There are a few other ways to to trigger the installation of provider packages:
* As part of Crossplane Helm chart by adding the following statement to your
`helm install` command: `--set
provider.packages={crossplane/provider-aws:v1.6.0}`.
provider.packages={crossplane/provider-aws:v1.6.1}`.
* Using the Crossplane CLI: `kubectl crossplane install provider
crossplane/provider-aws:v1.6.0`
crossplane/provider-aws:v1.6.1`
You can uninstall a provider by deleting the `Provider` resource
you've created.

8
docs/v1.6/getting-started/create-configuration.md
View File

@ -591,7 +591,7 @@ you may specify a specific package by using the `-f` flag.
```console
# Set this to the Docker Hub username or OCI registry you wish to use.
REG=my-package-repo
kubectl crossplane push configuration ${REG}/getting-started-with-aws:v1.6.0
kubectl crossplane push configuration ${REG}/getting-started-with-aws:v1.6.1
```
> Note that the Crossplane CLI will not follow symbolic links for files in the
@ -631,7 +631,7 @@ you may specify a specific package by using the `-f` flag.
```console
# Set this to the Docker Hub username or OCI registry you wish to use.
REG=my-package-repo
kubectl crossplane push configuration ${REG}/getting-started-with-aws-with-vpc:v1.6.0
kubectl crossplane push configuration ${REG}/getting-started-with-aws-with-vpc:v1.6.1
```
> Note that the Crossplane CLI will not follow symbolic links for files in the
@ -670,7 +670,7 @@ you may specify a specific package by using the `-f` flag.
```console
# Set this to the Docker Hub username or OCI registry you wish to use.
REG=my-package-repo
kubectl crossplane push configuration ${REG}/getting-started-with-gcp:v1.6.0
kubectl crossplane push configuration ${REG}/getting-started-with-gcp:v1.6.1
```
> Note that the Crossplane CLI will not follow symbolic links for files in the
@ -709,7 +709,7 @@ you may specify a specific package by using the `-f` flag.
```console
# Set this to the Docker Hub username or OCI registry you wish to use.
REG=my-package-repo
kubectl crossplane push configuration ${REG}/getting-started-with-azure:v1.6.0
kubectl crossplane push configuration ${REG}/getting-started-with-azure:v1.6.1
```
> Note that the Crossplane CLI will not follow symbolic links for files in the

2
docs/v1.6/reference/troubleshoot.md
View File

@ -21,7 +21,7 @@ indent: true
## Requested Resource Not Found
If you use the kubectl Crossplane plugin to install a `Provider` or `Configuration`
(e.g. `kubectl crossplane install provider crossplane/provider-aws:v1.6.0`) and
(e.g. `kubectl crossplane install provider crossplane/provider-aws:v1.6.1`) and
get `the server could not find the requested resource` error, more often than
not, that is an indicator that the kubectl Crossplane you're using is outdated.
In other words some Crossplane API has been graduated from alpha to beta or stable