Fix yaml paths. (#3648)
parent
0f881b20d7
commit
ca91dd2869
|
@ -62,7 +62,7 @@ and a StatefulSet.
|
|||
Create the ConfigMap from the following YAML configuration file:
|
||||
|
||||
```shell
|
||||
kubectl create -f http://k8s.io/docs/tutorials/stateful-application/mysql-configmap.yaml
|
||||
kubectl create -f http://k8s.io/docs/tasks/run-application/mysql-configmap.yaml
|
||||
```
|
||||
|
||||
{% include code.html language="yaml" file="mysql-configmap.yaml" ghlink="/docs/tutorials/run-application/mysql-configmap.yaml" %}
|
||||
|
@ -82,7 +82,7 @@ based on information provided by the StatefulSet controller.
|
|||
Create the Services from the following YAML configuration file:
|
||||
|
||||
```shell
|
||||
kubectl create -f http://k8s.io/docs/tutorials/stateful-application/mysql-services.yaml
|
||||
kubectl create -f http://k8s.io/docs/tasks/run-application/mysql-services.yaml
|
||||
```
|
||||
|
||||
{% include code.html language="yaml" file="mysql-services.yaml" ghlink="/docs/tutorials/run-application/mysql-services.yaml" %}
|
||||
|
@ -108,7 +108,7 @@ writes.
|
|||
Finally, create the StatefulSet from the following YAML configuration file:
|
||||
|
||||
```shell
|
||||
kubectl create -f http://k8s.io/docs/tutorials/stateful-application/mysql-statefulset.yaml
|
||||
kubectl create -f http://k8s.io/docs/docs/tasks/run-application/mysql-statefulset.yaml
|
||||
```
|
||||
|
||||
{% include code.html language="yaml" file="mysql-statefulset.yaml" ghlink="/docs/tutorials/run-application/mysql-statefulset.yaml" %}
|
||||
|
|
|
@ -54,7 +54,7 @@ Next create a PersistentVolume that points to the `mysql-disk`
|
|||
disk just created. Here is a configuration file for a PersistentVolume
|
||||
that points to the Compute Engine disk above:
|
||||
|
||||
{% include code.html language="yaml" file="gce-volume.yaml" ghlink="/docs/tutorials/stateful-application/gce-volume.yaml" %}
|
||||
{% include code.html language="yaml" file="gce-volume.yaml" ghlink="/docs/docs/tasks/run-application/gce-volume.yaml" %}
|
||||
|
||||
Notice that the `pdName: mysql-disk` line matches the name of the disk
|
||||
in the Compute Engine environment. See the
|
||||
|
@ -65,7 +65,7 @@ environments.
|
|||
Create the persistent volume:
|
||||
|
||||
```
|
||||
kubectl create -f http://k8s.io/docs/tutorials/stateful-application/gce-volume.yaml
|
||||
kubectl create -f http://k8s.io/docs/tasks/run-application/gce-volume.yaml
|
||||
```
|
||||
|
||||
|
||||
|
@ -84,11 +84,11 @@ Note: The password is defined in the config yaml, and this is insecure. See
|
|||
[Kubernetes Secrets](/docs/concepts/configuration/secret/)
|
||||
for a secure solution.
|
||||
|
||||
{% include code.html language="yaml" file="mysql-deployment.yaml" ghlink="/docs/tutorials/stateful-application/mysql-deployment.yaml" %}
|
||||
{% include code.html language="yaml" file="mysql-deployment.yaml" ghlink="/docs/tasks/run-application/mysql-deployment.yaml" %}
|
||||
|
||||
1. Deploy the contents of the YAML file:
|
||||
|
||||
kubectl create -f http://k8s.io/docs/tutorials/stateful-application/mysql-deployment.yaml
|
||||
kubectl create -f http://k8s.io/docs/tasks/run-application/mysql-deployment.yaml
|
||||
|
||||
1. Display information about the Deployment:
|
||||
|
||||
|
|
|
@ -44,12 +44,12 @@ You can run an application by creating a Kubernetes Deployment object, and you
|
|||
can describe a Deployment in a YAML file. For example, this YAML file describes
|
||||
a Deployment that runs the nginx:1.7.9 Docker image:
|
||||
|
||||
{% include code.html language="yaml" file="deployment.yaml" ghlink="/docs/tutorials/stateless-application/deployment.yaml" %}
|
||||
{% include code.html language="yaml" file="deployment.yaml" ghlink="/docs/tasks/run-application/deployment.yaml" %}
|
||||
|
||||
|
||||
1. Create a Deployment based on the YAML file:
|
||||
|
||||
kubectl create -f http://k8s.io/docs/tutorials/stateless-application/deployment.yaml
|
||||
kubectl create -f http://k8s.io/docs/tasks/run-application/deployment.yaml
|
||||
|
||||
1. Display information about the Deployment:
|
||||
|
||||
|
|
Loading…
Reference in New Issue