docs snapshot for crossplane version `v1.6`

This commit is contained in:
Crossplane 2022-03-07 16:30:03 +00:00
parent 199b675425
commit a06df8768d
3 changed files with 9 additions and 9 deletions

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.3
kubectl crossplane push configuration ${REG}/getting-started-with-aws:v1.6.4
```
> 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.3
kubectl crossplane push configuration ${REG}/getting-started-with-aws-with-vpc:v1.6.4
```
> 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.3
kubectl crossplane push configuration ${REG}/getting-started-with-gcp:v1.6.4
```
> 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.3
kubectl crossplane push configuration ${REG}/getting-started-with-azure:v1.6.4
```
> Note that the Crossplane CLI will not follow symbolic links for files in the

View File

@ -243,7 +243,7 @@ provider that can satisfy a `PostgreSQLInstance`. Let's get started!
> section.
```console
kubectl crossplane install configuration registry.upbound.io/xp/getting-started-with-aws:v1.6.3
kubectl crossplane install configuration registry.upbound.io/xp/getting-started-with-aws:v1.6.4
```
Wait until all packages become healthy:
@ -300,7 +300,7 @@ kubectl apply -f https://raw.githubusercontent.com/crossplane/crossplane/release
> section.
```console
kubectl crossplane install configuration registry.upbound.io/xp/getting-started-with-aws-with-vpc:v1.6.3
kubectl crossplane install configuration registry.upbound.io/xp/getting-started-with-aws-with-vpc:v1.6.4
```
Wait until all packages become healthy:
@ -357,7 +357,7 @@ kubectl apply -f https://raw.githubusercontent.com/crossplane/crossplane/release
> section.
```console
kubectl crossplane install configuration registry.upbound.io/xp/getting-started-with-gcp:v1.6.3
kubectl crossplane install configuration registry.upbound.io/xp/getting-started-with-gcp:v1.6.4
```
Wait until all packages become healthy:
@ -430,7 +430,7 @@ spec:
> section.
```console
kubectl crossplane install configuration registry.upbound.io/xp/getting-started-with-azure:v1.6.3
kubectl crossplane install configuration registry.upbound.io/xp/getting-started-with-azure:v1.6.4
```
Wait until all packages become healthy:

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.3`) and
(e.g. `kubectl crossplane install provider crossplane/provider-aws:v1.6.4`) 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