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 `master`

This commit is contained in:
Crossplane 2019-04-03 18:52:53 +00:00
parent 4bbfd41388
commit c4ba59f8a9
1 changed files with 15 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/master/workloads/gcp/wordpress-gcp.md
View File

@ -39,17 +39,6 @@ For the next steps, make sure your `kubectl` context points to the cluster where
sed "s/BASE64ENCODED_CREDS/`cat key.json|base64 | tr -d '\n'`/g;s/DEMO_PROJECT_ID/$DEMO_PROJECT_ID/g" cluster/examples/workloads/wordpress-gcp/provider.yaml | kubectl create -f -
```
- Verify that GCP Provider is in `Ready` state
```bash
kubectl -n crossplane-system get providers.gcp.crossplane.io -o custom-columns=NAME:.metadata.name,STATUS:.status.Conditions[0].Type,PROJECT-ID:.spec.projectID
```
Your output should look similar to:
```bash
sed "s/BASE64ENCODED_CREDS/`cat crossplane-gcp-provider-key.json|base64 | tr -d '\n'`/g;s/DEMO_PROJECT_ID/$DEMO_PROJECT_ID/g" cluster/examples/workloads/wordpress-gcp/provider.yaml | kubectl create -f -
```
- Verify that GCP Provider is in `Ready` state
```bash
@ -81,7 +70,7 @@ For the next steps, make sure your `kubectl` context points to the cluster where
`Crossplane` Kubernetes cluster dynamic provisioning.
```bash
kubectl apply -f cluster/examples/workloads/wordpress-gcp/kubernetes.yaml
kubectl apply -f cluster/examples/workloads/wordpress-gcp/cluster.yaml
```
- Verify that Kubernetes Cluster resource was created
@ -185,7 +174,7 @@ Once you are done with this example, you can clean up all its artifacts with the
- Remove `KubernetesCluster`
```bash
kubectl delete -f cluster/examples/workloads/wordpress-gcp/kubernetes.yaml
kubectl delete -f cluster/examples/workloads/wordpress-gcp/cluster.yaml
```
- Remove GCP `Provider` and `ResourceClasses`