the KUESPRAYDIR defined but never used (#8930)
* fix dir error * the command line should align
This commit is contained in:
parent
0761659a43
commit
14c0f368b6
2 changed files with 4 additions and 4 deletions
|
@ -13,7 +13,7 @@ KUBESPRAYDIR=kubespray
|
||||||
ANSIBLE_VERSION=2.12
|
ANSIBLE_VERSION=2.12
|
||||||
virtualenv --python=$(which python3) $VENVDIR
|
virtualenv --python=$(which python3) $VENVDIR
|
||||||
source $VENVDIR/bin/activate
|
source $VENVDIR/bin/activate
|
||||||
cd $KUESPRAYDIR
|
cd $KUBESPRAYDIR
|
||||||
pip install -U -r requirements-$ANSIBLE_VERSION.txt
|
pip install -U -r requirements-$ANSIBLE_VERSION.txt
|
||||||
test -f requirements-$ANSIBLE_VERSION.yml && \
|
test -f requirements-$ANSIBLE_VERSION.yml && \
|
||||||
ansible-galaxy role install -r requirements-$ANSIBLE_VERSION.yml && \
|
ansible-galaxy role install -r requirements-$ANSIBLE_VERSION.yml && \
|
||||||
|
|
|
@ -27,7 +27,7 @@ Check the associated storage class (if you enabled persistent_volumes):
|
||||||
```ShellSession
|
```ShellSession
|
||||||
$ kubectl get storageclass
|
$ kubectl get storageclass
|
||||||
NAME PROVISIONER AGE
|
NAME PROVISIONER AGE
|
||||||
ebs-sc ebs.csi.aws.com 45s
|
ebs-sc ebs.csi.aws.com 45s
|
||||||
```
|
```
|
||||||
|
|
||||||
You can run a PVC and an example Pod using this file `ebs-pod.yml`:
|
You can run a PVC and an example Pod using this file `ebs-pod.yml`:
|
||||||
|
@ -71,8 +71,8 @@ You should see the PVC provisioned and bound:
|
||||||
|
|
||||||
```ShellSession
|
```ShellSession
|
||||||
$ kubectl get pvc
|
$ kubectl get pvc
|
||||||
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
|
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
|
||||||
ebs-claim Bound pvc-0034cb9e-1ddd-4b3f-bb9e-0b5edbf5194c 1Gi RWO ebs-sc 50s
|
ebs-claim Bound pvc-0034cb9e-1ddd-4b3f-bb9e-0b5edbf5194c 1Gi RWO ebs-sc 50s
|
||||||
```
|
```
|
||||||
|
|
||||||
And the volume mounted to the example Pod (wait until the Pod is Running):
|
And the volume mounted to the example Pod (wait until the Pod is Running):
|
||||||
|
|
Loading…
Reference in a new issue