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 `v0.3`

This commit is contained in:
Crossplane 2019-09-19 00:44:22 +00:00
parent 086605dc42
commit 2e2d6cbb26
6 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/v0.3/install-crossplane.md
View File

@ -72,7 +72,7 @@ metadata:
name: stack-gcp name: stack-gcp
namespace: gcp namespace: gcp
spec: spec:
package: "crossplane/stack-gcp:master" package: "crossplane/stack-gcp:v0.1.0"
``` ```
Then you can install the GCP stack into Crossplane in the `gcp` namespace with the following command: Then you can install the GCP stack into Crossplane in the `gcp` namespace with the following command:
@ -97,7 +97,7 @@ metadata:
name: stack-aws name: stack-aws
namespace: aws namespace: aws
spec: spec:
package: "crossplane/stack-aws:master" package: "crossplane/stack-aws:v0.1.0"
``` ```
Then you can install the AWS stack into Crossplane in the `aws` namespace with the following command: Then you can install the AWS stack into Crossplane in the `aws` namespace with the following command:
@ -122,7 +122,7 @@ metadata:
name: stack-azure name: stack-azure
namespace: azure namespace: azure
spec: spec:
package: "crossplane/stack-azure:master" package: "crossplane/stack-azure:v0.1.0"
``` ```
Then you can install the Azure stack into Crossplane in the `azure` namespace with the following command: Then you can install the Azure stack into Crossplane in the `azure` namespace with the following command:

2
docs/v0.3/services/aws-services-guide.md
View File

@ -421,7 +421,7 @@ metadata:
name: stack-aws name: stack-aws
namespace: crossplane-system namespace: crossplane-system
spec: spec:
package: "crossplane/stack-aws:master" package: "crossplane/stack-aws:v0.1.0"
EOF EOF
kubectl apply -f stack-aws.yaml kubectl apply -f stack-aws.yaml

2
docs/v0.3/services/azure-services-guide.md
View File

@ -119,7 +119,7 @@ metadata:
name: stack-azure name: stack-azure
namespace: crossplane-system namespace: crossplane-system
spec: spec:
package: "crossplane/stack-azure:master" package: "crossplane/stack-azure:v0.1.0"
EOF EOF
kubectl apply -f stack-azure.yaml kubectl apply -f stack-azure.yaml

2
docs/v0.3/stacks-guide-aws.md
View File

@ -68,7 +68,7 @@ infrastructure stack, we need to specify that it's cluster-scoped by
passing the `--cluster` flag. passing the `--cluster` flag.
```bash ```bash
kubectl crossplane stack generate-install --cluster 'crossplane/stack-aws:master' stack-aws | kubectl apply --namespace ${INFRA_NAMESPACE} -f - kubectl crossplane stack generate-install --cluster 'crossplane/stack-aws:v0.1.0' stack-aws | kubectl apply --namespace ${INFRA_NAMESPACE} -f -
``` ```
The rest of the steps assume that you installed the AWS stack into the The rest of the steps assume that you installed the AWS stack into the

2
docs/v0.3/stacks-guide-azure.md
View File

@ -63,7 +63,7 @@ control over how the stack's installation is handled. Everything is
a Kubernetes object! a Kubernetes object!
``` ```
kubectl crossplane stack generate-install --cluster 'crossplane/stack-azure:master' stack-azure | kubectl apply --namespace crossplane-system -f - kubectl crossplane stack generate-install --cluster 'crossplane/stack-azure:v0.1.0' stack-azure | kubectl apply --namespace crossplane-system -f -
``` ```
If we wanted to use whatever the current namespace is, we could have If we wanted to use whatever the current namespace is, we could have

2
docs/v0.3/stacks-guide-gcp.md
View File

@ -63,7 +63,7 @@ a Kubernetes object!
``` ```
kubectl create namespace gcp kubectl create namespace gcp
kubectl crossplane stack generate-install --cluster 'crossplane/stack-gcp:master' stack-gcp | kubectl apply --namespace gcp -f - kubectl crossplane stack generate-install --cluster 'crossplane/stack-gcp:v0.1.0' stack-gcp | kubectl apply --namespace gcp -f -
``` ```
If we wanted to use whatever the current namespace is, we could have If we wanted to use whatever the current namespace is, we could have