docs snapshot for crossplane version `master`

This commit is contained in:
Crossplane 2019-06-28 23:58:49 +00:00
parent cd2788bae6
commit 4d9605a401
3 changed files with 6 additions and 4 deletions

View File

@ -97,7 +97,7 @@ postgresql-3ef70bf9-0667-11e9-99e1-080027cf2340 Bound Ready cloud-post
Note that both the general `postgresqlinstance` `ResourceClaim` and the cloud provider specific PostgreSQL database have the `Bound` status, meaning the dynamic provisioning is done and the resource is ready for consumption.
The connection information will be stored in a secret with the same name as the `ResourceClaim`.
The connection information will be stored in a secret specified via the `writeConnectionSecretTo` field.
Since the secret is base64 encoded, we'll need to decode its fields to view them in plain-text.
To view all the connection information in plain-text, run the following command:

View File

@ -49,8 +49,9 @@ parameters:
region: us-west2
storageType: PD_SSD
provisioner: cloudsqlinstance.database.gcp.crossplane.io/v1alpha1
providerRef:
providerReference:
name: gcp-provider
namespace: crossplane-system
reclaimPolicy: Delete
```
@ -85,8 +86,9 @@ parameters:
numNodes: "1"
zone: us-central1-a
provisioner: gkecluster.compute.gcp.crossplane.io/v1alpha1
providerRef:
providerReference:
name: gcp-provider
namespace: crossplane-system
reclaimPolicy: Delete
```

View File

@ -55,7 +55,7 @@ For the next steps, make sure your `kubectl` context points to the cluster where
* Verify that Resource Classes have been created
```bash
kubectl -n crossplane-system get resourceclass -o custom-columns=NAME:metadata.name,PROVISIONER:.provisioner,PROVIDER:.providerRef.name,RECLAIM-POLICY:.reclaimPolicy
kubectl -n crossplane-system get resourceclass -o custom-columns=NAME:metadata.name,PROVISIONER:.provisioner,PROVIDER:.providerReference.name,RECLAIM-POLICY:.reclaimPolicy
```
Your output should be: