kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

upup: update same vpc docs

This commit is contained in:
Justin Santa Barbara 2016-06-27 20:22:36 -04:00
parent 46be00c79f
commit ddd81010c4
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
upup/docs/run_in_existing_vpc.md
View File

@ -8,12 +8,14 @@ config before we apply it.
```
export KOPS_STATE_STORE=s3://<somes3bucket>
export CLUSTER_NAME=<sharedvpc.mydomain.com>
cloudup --zones=us-east-1b --state s3://clusters.awsdata.com/${CLUSTER_NAME} --name=${CLUSTER_NAME} \
cloudup --zones=us-east-1b --name=${CLUSTER_NAME} \
--vpc=vpc-a80734c1 --network-cidr=10.100.0.0/16 --dryrun
```
Then `upup edit cluster --state s3://clusters.awsdata.com/${CLUSTER_NAME}` should show you something like:
Then `upup edit cluster --name=${CLUSTER_NAME}` should show you something like:
```
metadata:
@ -37,7 +39,7 @@ because subnets in a VPC cannot overlap.
You can then run cloudup again in dryrun mode (you don't need any arguments, because they're all in the config file):
```
cloudup --dryrun --state s3://clusters.awsdata.com/${CLUSTER_NAME}
cloudup --dryrun --name=${CLUSTER_NAME}
```
Review the changes to make sure they are OK - the Kubernetes settings might not be ones you want on a shared VPC (in which case,
@ -50,7 +52,7 @@ Note also the Kubernetes VPCs (currently) require `EnableDNSHostnames=true`. Cl
Once you're happy, you can create the cluster using:
```
cloudup --state s3://clusters.awsdata.com/${CLUSTER_NAME}
cloudup --name=${CLUSTER_NAME}
```