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-08-28 04:03:40 +00:00
parent 2edeff706d
commit 1e015f7f6e
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/master/workloads/aws/wordpress-aws.md
View File

@ -154,7 +154,7 @@ sed -e "s|BASE64ENCODED_AWS_PROVIDER_CREDS|`base64 ~/.aws/credentials|tr -d '\n'
Create cluster:
```console
kubectl create -f cluster/examples/workloads/kubernetes/wordpress/cluster.yaml
kubectl create -f cluster/examples/workloads/kubernetes/wordpress/aws/cluster.yaml
```
It will take a while (~15 minutes) for the EKS cluster to be deployed and become available.
@ -182,7 +182,7 @@ This section covers tasks performed by an application developer. These include:
Now that the EKS cluster is ready, let's begin deploying the workload as the application developer:
```console
kubectl create -f cluster/examples/workloads/kubernetes/wordpress/app.yaml
kubectl create -f cluster/examples/workloads/kubernetes/wordpress/aws/app.yaml
```
This will also take awhile to complete, since the MySQL database needs to be deployed before the WordPress pod can consume it.
@ -274,13 +274,13 @@ kubectl get nodes
First delete the workload, which will delete WordPress and the MySQL database:
```console
kubectl delete -f cluster/examples/workloads/kubernetes/wordpress/app.yaml
kubectl delete -f cluster/examples/workloads/kubernetes/wordpress/aws/app.yaml
```
Then delete the EKS cluster:
```console
kubectl delete -f cluster/examples/workloads/kubernetes/wordpress/cluster.yaml
kubectl delete -f cluster/examples/workloads/kubernetes/wordpress/aws/cluster.yaml
```
Finally, delete the provider credentials:

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

@ -74,7 +74,7 @@ For the next steps, make sure your `kubectl` context points to the cluster where
The `Application Developer(s)` will use the `complex` namespace.
```bash
kubectl apply -f cluster/examples/workloads/kubernetes/wordpress/cluster.yaml
kubectl apply -f cluster/examples/workloads/kubernetes/wordpress/gcp/cluster.yaml
```
* Verify that the Kubernetes Cluster resource was created
@ -121,7 +121,7 @@ Let's begin deploying the workload as the application developer:
* Deploy workload
```bash
kubectl apply -f cluster/examples/workloads/kubernetes/wordpress/app.yaml
kubectl apply -f cluster/examples/workloads/kubernetes/wordpress/gcp/app.yaml
```
* Wait for `MySQLInstance` to be in `Bound` State
@ -182,13 +182,13 @@ Once you are done with this example, you can clean up all its artifacts with the
* Remove the `App`
```bash
kubectl delete -f cluster/examples/workloads/kubernetes/wordpress/app.yaml
kubectl delete -f cluster/examples/workloads/kubernetes/wordpress/gcp/app.yaml
```
* Remove the `KubernetesCluster`
```bash
kubectl delete -f cluster/examples/workloads/kubernetes/wordpress/cluster.yaml
kubectl delete -f cluster/examples/workloads/kubernetes/wordpress/gcp/cluster.yaml
```
* Remove the GCP `Provider` and Crossplane `ResourceClasses`