whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Changes all API object references to PascalCase (e.g Stateful Set

Browse Source 
becomes StatefulSet)
This commit is contained in:
Kenneth Owens
2016-11-29 10:01:38 -08:00
parent ad59c9f827
commit eead3799b9
3 changed files with 90 additions and 90 deletions
Download Patch File Download Diff File Expand all files Collapse all files
_data/tutorials.yml
+1 -1
View File
@@ -53,5 +53,5 @@ toc:
path: /docs/tutorials/stateless-application/expose-external-ip-address/ path: /docs/tutorials/stateless-application/expose-external-ip-address/
title: Stateful Applications title: Stateful Applications
section: section:
- title: Stateful Set Basics - title: StatefulSet Basics
path: /docs/tutorials/stateful-application/basic-stateful-set/ path: /docs/tutorials/stateful-application/basic-stateful-set/
docs/tutorials/index.md
+1 -1
View File
@@ -17,7 +17,7 @@ The Tutorials section of the Kubernetes documentation is a work in progress.
#### Stateful Applications #### Stateful Applications
* [Stateful Set Basics](/docs/tutorials/stateful-application/basic-stateful-set/) * [StatefulSet Basics](/docs/tutorials/stateful-application/basic-stateful-set/)
### What's next ### What's next
docs/tutorials/stateful-application/basic-stateful-set.md
+88 -88
View File
@@ -11,9 +11,9 @@ assignees:
{% capture overview %} {% capture overview %}
This tutorial provides an introduction to the This tutorial provides an introduction to the
[Stateful Set](/docs/concepts/controllers/statefulsets.md) concept. It [StatefulSet](/docs/concepts/controllers/statefulsets.md) concept. It
demonstrates how to create, delete, scale, and update the container image of a demonstrates how to create, delete, scale, and update the container image of a
Stateful Set. StatefulSet.
{% endcapture %} {% endcapture %}
{% capture prerequisites %} {% capture prerequisites %}
@@ -23,48 +23,48 @@ following Kubernetes concepts.
* [Pods](/docs/user-guide/pods/single-container/) * [Pods](/docs/user-guide/pods/single-container/)
* [Cluster DNS](/docs/admin/dns/) * [Cluster DNS](/docs/admin/dns/)
* [Headless Services](/docs/user-guide/services/#headless-services) * [Headless Services](/docs/user-guide/services/#headless-services)
* [Persistent Volumes](/docs/user-guide/volumes/) * [PersistentVolumes](/docs/user-guide/volumes/)
* [Persistent Volume Provisioning](http://releases.k8s.io/{{page.githubbranch}}/examples/experimental/persistent-volume-provisioning/) * [PersistentVolume Provisioning](http://releases.k8s.io/{{page.githubbranch}}/examples/experimental/persistent-volume-provisioning/)
* [Stateful Sets](/docs/concepts/controllers/statefulsets.md) * [StatefulSets](/docs/concepts/controllers/statefulsets.md)
* [kubeclt CLI](/docs/user-guide/kubectl) * [kubeclt CLI](/docs/user-guide/kubectl)
This tutorial assumes that your cluster is configured to dynamically provision This tutorial assumes that your cluster is configured to dynamically provision
and Persistent Volumes. If your cluster is not configured to do so, you and PersistentVolumes. If your cluster is not configured to do so, you
will have to manually provision five 1 GiB volumes prior to starting this will have to manually provision five 1 GiB volumes prior to starting this
tutorial. tutorial.
{% endcapture %} {% endcapture %}
{% capture objectives %} {% capture objectives %}
Stateful Sets are intended to be used with stateful applications and distributed StatefulSets are intended to be used with stateful applications and distributed
systems. However, the administration of stateful applications and systems. However, the administration of stateful applications and
distributed systems on Kubernetes is a broad, complex topic. In order to distributed systems on Kubernetes is a broad, complex topic. In order to
demonstrate the basic features of a Stateful Set, and to not conflate the former demonstrate the basic features of a StatefulSet, and to not conflate the former
topic with the latter, a simple web application will be used as a running topic with the latter, a simple web application will be used as a running
example throughout this tutorial. example throughout this tutorial.
After this tutorial, you will be familiar with the following. After this tutorial, you will be familiar with the following.
* How to create a Stateful Set * How to create a StatefulSet
* How a Stateful Set manages its Pods * How a StatefulSet manages its Pods
* How to delete a Stateful Set * How to delete a StatefulSet
* How to scale a Stateful Set * How to scale a StatefulSet
* How to update the container image of a Stateful Set's Pods * How to update the container image of a StatefulSet's Pods
{% endcapture %} {% endcapture %}
{% capture lessoncontent %} {% capture lessoncontent %}
### Creating a Stateful Set ### Creating a StatefulSet
Begin by creating a Stateful Set using the example below. It is similar to the Begin by creating a StatefulSet using the example below. It is similar to the
example presented in the example presented in the
[Stateful Sets](/docs/concepts/controllers/statefulsets.md) concept. It creates [StatefulSets](/docs/concepts/controllers/statefulsets.md) concept. It creates
a [Headless Service](/docs/user-guide/services/#headless-services), `nginx`, to a [Headless Service](/docs/user-guide/services/#headless-services), `nginx`, to
control the domain of the Stateful Set, `web`. control the domain of the StatefulSet, `web`.
{% include code.html language="yaml" file="web.yaml" ghlink="/docs/tutorials/stateful-application/web.yaml" %} {% include code.html language="yaml" file="web.yaml" ghlink="/docs/tutorials/stateful-application/web.yaml" %}
You will need to use two terminal windows. In the first terminal, use You will need to use two terminal windows. In the first terminal, use
[`kubectl get`](/docs/user-guide/kubectl/kubectl_get/) to watch the creation [`kubectl get`](/docs/user-guide/kubectl/kubectl_get/) to watch the creation
of the Stateful Set's Pods. of the StatefulSet's Pods.
```shell ```shell
$ kubectl get pods -w -l app=nginx $ kubectl get pods -w -l app=nginx
@@ -72,7 +72,7 @@ $ kubectl get pods -w -l app=nginx
In the second terminal, use In the second terminal, use
[`kubeclt create`](/docs/user-guide/kubectl/kubectl_create/) to create the [`kubeclt create`](/docs/user-guide/kubectl/kubectl_create/) to create the
Headless Service and Stateful Set defined in `web.yaml`. Headless Service and StatefulSet defined in `web.yaml`.
```shell ```shell
$ kubectl create -f web.yml $ kubectl create -f web.yml
@@ -82,7 +82,7 @@ statefulset "web" created
The command above creates two Pods, each running a The command above creates two Pods, each running a
[NGINX](https://www.nginx.com) webserver. Get the `nginx` Service and the [NGINX](https://www.nginx.com) webserver. Get the `nginx` Service and the
`web` Stateful Set to verify that they were created successfully. `web` StatefulSet to verify that they were created successfully.
```shell ```shell
$ kubectl get service nginx $ kubectl get service nginx
@@ -96,7 +96,7 @@ web 2 1 20s
#### Ordered Pod Creation #### Ordered Pod Creation
For a Stateful Set with N replicas, when Pods are being deployed, they are For a StatefulSet with N replicas, when Pods are being deployed, they are
created sequentially, in order from {0..N-1}. Examine the output of the created sequentially, in order from {0..N-1}. Examine the output of the
`kubectl get` command in the first terminal. Eventually, the output will `kubectl get` command in the first terminal. Eventually, the output will
look like the example below. look like the example below.
@@ -119,11 +119,11 @@ Notice that the `web-0` Pod is launched and set to Pending prior to
launching `web-1`. In fact, `web-1` is not launched until `web-0` is launching `web-1`. In fact, `web-1` is not launched until `web-0` is
[Running and Ready](/docs/user-guide/pod-states). [Running and Ready](/docs/user-guide/pod-states).
### Pods in a Stateful Set ### Pods in a StatefulSet
#### Ordinal Index #### Ordinal Index
Get the Stateful Set's Pods. Get the StatefulSet's Pods.
```shell ```shell
$ kubectl get pods -l app=nginx $ kubectl get pods -l app=nginx
@@ -133,11 +133,11 @@ web-1 1/1 Running 0 1m
``` ```
As mentioned in the [Stateful Sets](/docs/concepts/controllers/statefulsets.md) As mentioned in the [StatefulSets](/docs/concepts/controllers/statefulsets.md)
concept, the Pods in a Stateful Set have a sticky, unique identity. This identity concept, the Pods in a StatefulSet have a sticky, unique identity. This identity
is based on a unique ordinal index that is assigned to each Pod by the Stateful is based on a unique ordinal index that is assigned to each Pod by the Stateful
Set controller. The Pods names take the form Set controller. The Pods names take the form
`$(statefulset name)-$(ordinal index)`. Since the `web` Stateful Set has two `$(statefulset name)-$(ordinal index)`. Since the `web` StatefulSet has two
replicas, it creates two Pods, `web-0` and `web-1`. replicas, it creates two Pods, `web-0` and `web-1`.
#### Stable Network Identity #### Stable Network Identity
@@ -177,14 +177,14 @@ The CNAME of the headless serivce points to SRV records (one for each Pod that
is Running and Ready). The SRV records point to A record entries that is Running and Ready). The SRV records point to A record entries that
contain the Pods' IP addresses. contain the Pods' IP addresses.
In one terminal, watch the Stateful Set's Pods. In one terminal, watch the StatefulSet's Pods.
```shell ```shell
$ kubectl get pod -w -l app=nginx $ kubectl get pod -w -l app=nginx
``` ```
In a second terminal, use In a second terminal, use
[`kubectl delete`](/docs/user-guide/kubectl/kubectl_delete/) to delete all [`kubectl delete`](/docs/user-guide/kubectl/kubectl_delete/) to delete all
the Pods in the Stateful Set. the Pods in the StatefulSet.
```shell ```shell
$ kubectl delete pod -l app=nginx $ kubectl delete pod -l app=nginx
@@ -233,23 +233,23 @@ Address 1: 10.244.2.8
The Pods' ordinals, hostnames, SRV records, and A record names have not changed, The Pods' ordinals, hostnames, SRV records, and A record names have not changed,
but the IP addresses associated with the Pods may have changed. In the cluster but the IP addresses associated with the Pods may have changed. In the cluster
used for this tutorial, they have. This is why it is important not to configure used for this tutorial, they have. This is why it is important not to configure
other applications to connect to Pods in a Stateful Set by IP address. other applications to connect to Pods in a StatefulSet by IP address.
If you need to find and connect to the active members of a Stateful Set, you If you need to find and connect to the active members of a StatefulSet, you
should query the CNAME of the Headless Service should query the CNAME of the Headless Service
(e.g. `nginx.default.svc.cluster.local`). The SRV records associated with the (e.g. `nginx.default.svc.cluster.local`). The SRV records associated with the
CNAME will contain only the Pods in the Stateful Set that are Running and CNAME will contain only the Pods in the StatefulSet that are Running and
Ready. Ready.
Alternatively, if you only need a predefined set of addresses, for instance if Alternatively, if you only need a predefined set of addresses, for instance if
your application already implements connection logic that tests for your application already implements connection logic that tests for
liveness and readiness, you should use the SRV records of the Pods in the liveness and readiness, you should use the SRV records of the Pods in the
Stateful Set (e.g `web-0.nginx.default.svc.cluster.local`, StatefulSet (e.g `web-0.nginx.default.svc.cluster.local`,
`web-1.nginx.default.svc.cluster.local`). `web-1.nginx.default.svc.cluster.local`).
#### Stable Storage #### Stable Storage
Get the Persistent Volume Claims for `web-0` and `web-1`. Get the PersistentVolumeClaims for `web-0` and `web-1`.
```shell ```shell
$ kubectl get pvc -l app=nginx $ kubectl get pvc -l app=nginx
@@ -257,15 +257,15 @@ NAME STATUS VOLUME CAPACITY ACCE
www-web-0 Bound pvc-15c268c7-b507-11e6-932f-42010a800002 1Gi RWO 48s www-web-0 Bound pvc-15c268c7-b507-11e6-932f-42010a800002 1Gi RWO 48s
www-web-1 Bound pvc-15c79307-b507-11e6-932f-42010a800002 1Gi RWO 48s www-web-1 Bound pvc-15c79307-b507-11e6-932f-42010a800002 1Gi RWO 48s
``` ```
The Stateful Set controller created two Persistent Volume Claims that are The StatefulSet controller created two PersistentVolumeClaims that are
bound to two [Persistent Volume](/docs/user-guide/volumes/). As the cluster used bound to two [PersistentVolume](/docs/user-guide/volumes/). As the cluster used
in this tutorial is configured to dynamically provision Persistent Volumes, the in this tutorial is configured to dynamically provision PersistentVolumes, the
Persistent Volumes were created and bound automatically. PersistentVolumes were created and bound automatically.
The containers NGINX webservers, by default, will serve an index file at The containers NGINX webservers, by default, will serve an index file at
`/usr/share/nginx/html/index.html`. The `volumeMounts` field in the `/usr/share/nginx/html/index.html`. The `volumeMounts` field in the
Stateful Sets `spec` ensures that the `/usr/share/nginx/html` directory is StatefulSets `spec` ensures that the `/usr/share/nginx/html` directory is
backed by a Persistent Volume. backed by a PersistentVolume.
Write the Pods' hostnames to their `index.html` files and verify that the NGINX Write the Pods' hostnames to their `index.html` files and verify that the NGINX
webservers serve the hostnames. webservers serve the hostnames.
@@ -278,13 +278,13 @@ web-0
web-1 web-1
``` ```
In one terminal, watch the Stateful Set's Pods. In one terminal, watch the StatefulSet's Pods.
```shell ```shell
kubectl get pod -w -l app=nginx kubectl get pod -w -l app=nginx
``` ```
In a second terminal, delete all of the Stateful Set's Pods. In a second terminal, delete all of the StatefulSet's Pods.
```shell ```shell
$ kubectl delete pod -l app=nginx $ kubectl delete pod -l app=nginx
@@ -315,14 +315,14 @@ web-1
``` ```
Event though `web-0` and `web-1` were rescheduled, they continue to serve their Event though `web-0` and `web-1` were rescheduled, they continue to serve their
hostnames because the Persistent Volumes associated with their Persistent hostnames because the PersistentVolumes associated with their Persistent
Volume Claims are remounted to their `volumeMount`s. No matter what node `web-0` Volume Claims are remounted to their `volumeMount`s. No matter what node `web-0`
and `web-1` are scheduled on, their Persistent Volumes will be mounted to the and `web-1` are scheduled on, their PersistentVolumes will be mounted to the
appropriate mount points. appropriate mount points.
### Scaling a Stateful Set ### Scaling a StatefulSet
When we refer to scaling a Stateful Set, we mean increasing or decreasing the When we refer to scaling a StatefulSet, we mean increasing or decreasing the
number of replicas in the Stateful Set. This is accomplished by by updating number of replicas in the StatefulSet. This is accomplished by by updating
the `replicas` field. You can use either the `replicas` field. You can use either
[`kubectl scale`](/docs/user-guide/kubectl/kubectl_scale/) or [`kubectl scale`](/docs/user-guide/kubectl/kubectl_scale/) or
[`kubectl patch`](/docs/user-guide/kubectl/kubectl_patch/) to scale a Stateful [`kubectl patch`](/docs/user-guide/kubectl/kubectl_patch/) to scale a Stateful
@@ -330,7 +330,7 @@ Set.
#### Scaling Up #### Scaling Up
In one terminal window, watch the Pods in the Stateful Set. In one terminal window, watch the Pods in the StatefulSet.
```shell ```shell
$ kubectl get pods -w -l app=nginx $ kubectl get pods -w -l app=nginx
@@ -367,21 +367,21 @@ web-4 0/1 ContainerCreating 0 0s
web-4 1/1 Running 0 19s web-4 1/1 Running 0 19s
``` ```
The Stateful Set controller scaled the number of replicas. As with The StatefulSet controller scaled the number of replicas. As with
[Stateful Set creation](#ordered-pod-creation), the Stateful Set controller [StatefulSet creation](#ordered-pod-creation), the StatefulSet controller
created each Pod sequentially with respect to its ordinal index, and it created each Pod sequentially with respect to its ordinal index, and it
waited for each Pod's predecessor to be Running and Ready before launching the waited for each Pod's predecessor to be Running and Ready before launching the
subsequent Pod. subsequent Pod.
#### Scaling Down #### Scaling Down
In one terminal, watch the Stateful Set's Pods. In one terminal, watch the StatefulSet's Pods.
```shell ```shell
$ kubectl get pods -w -l app=nginx $ kubectl get pods -w -l app=nginx
``` ```
In another terminal, use `kubectl patch` to scale the Stateful Set back down to In another terminal, use `kubectl patch` to scale the StatefulSet back down to
3 replicas. 3 replicas.
```shell ```shell
@@ -414,7 +414,7 @@ in reverse order, and it waited for each to be completely shutdown
(past its [terminationGracePeriodSeconds](/docs/user-guide/pods/index#termination-of-pods)) (past its [terminationGracePeriodSeconds](/docs/user-guide/pods/index#termination-of-pods))
before deleting the next. before deleting the next.
Get the Stateful Sets Persistent Volume Claims. Get the StatefulSets PersistentVolumeClaims.
```shell ```shell
$ kubectl get pvc -l app=nginx $ kubectl get pvc -l app=nginx
@@ -427,21 +427,21 @@ www-web-4 Bound pvc-e11bb5f8-b508-11e6-932f-42010a800002 1Gi RWO
``` ```
There are still five Persistent Volume Claims and five Persistent Volumes. There are still five PersistentVolumeClaims and five PersistentVolumes.
When exploring a Pod's [stable storage](#stable-storage), we saw that the When exploring a Pod's [stable storage](#stable-storage), we saw that the
Persistent Volumes mounted to the Pods of a Stateful Set are not deleted when PersistentVolumes mounted to the Pods of a StatefulSet are not deleted when
the Stateful Set's Pods are deleted. This is still true when Pod deletion is the StatefulSet's Pods are deleted. This is still true when Pod deletion is
caused by scaling the Stateful Set down. This feature can be used to facilitate caused by scaling the StatefulSet down. This feature can be used to facilitate
upgrading the container images of Pods in a Stateful Set. upgrading the container images of Pods in a StatefulSet.
### Upgrading Container Images ### Upgrading Container Images
Stateful Set currently *does not* support automated image upgrade. However, you StatefulSet currently *does not* support automated image upgrade. However, you
can update the `image` field of any container in the podTemplate and delete can update the `image` field of any container in the podTemplate and delete
Stateful Set's Pods one by one, the Stateful Set controller will recreate StatefulSet's Pods one by one, the StatefulSet controller will recreate
each Pod with the new image. each Pod with the new image.
Patch the container image for the `web` Stateful Set. Patch the container image for the `web` StatefulSet.
```shell ```shell
$ kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"gcr.io/google_containers/nginx-slim:0.7"}]' $ kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"gcr.io/google_containers/nginx-slim:0.7"}]'
@@ -521,26 +521,26 @@ gcr.io/google_containers/nginx-slim:0.7
gcr.io/google_containers/nginx-slim:0.7 gcr.io/google_containers/nginx-slim:0.7
{% endraw %}``` {% endraw %}```
All the Pods in the Stateful Set are now running a new container image. All the Pods in the StatefulSet are now running a new container image.
### Deleting Stateful Sets ### Deleting StatefulSets
Stateful Set supports both Non-Cascading and Cascading deletion. In a StatefulSet supports both Non-Cascading and Cascading deletion. In a
Non-Cascading Delete, the Stateful Set's Pods are not deleted when the Stateful Non-Cascading Delete, the StatefulSet's Pods are not deleted when the Stateful
Set is deleted. In a Cascading Delete, both the Stateful Set and its Pods are Set is deleted. In a Cascading Delete, both the StatefulSet and its Pods are
deleted. deleted.
#### Non-Cascading Delete #### Non-Cascading Delete
In one terminal window, watch the Pods in the Stateful Set. In one terminal window, watch the Pods in the StatefulSet.
``` ```
$ kubectl get pods -w -l app=nginx $ kubectl get pods -w -l app=nginx
``` ```
Use [`kubectl delete`](/docs/user-guide/kubectl/kubectl_delete/) to delete the Use [`kubectl delete`](/docs/user-guide/kubectl/kubectl_delete/) to delete the
Stateful Set. Make sure to supply the `--cascade=false` parameter to the StatefulSet. Make sure to supply the `--cascade=false` parameter to the
command. This parameter tells Kubernetes to only delete the Stateful Set, and to command. This parameter tells Kubernetes to only delete the StatefulSet, and to
not delete any of its Pods. not delete any of its Pods.
```shell ```shell
@@ -566,7 +566,7 @@ $ kubectl delete pod web-0
pod "web-0" deleted pod "web-0" deleted
``` ```
Get the Stateful Set's Pods. Get the StatefulSet's Pods.
```shell ```shell
$ kubectl get pods -l app=nginx $ kubectl get pods -l app=nginx
@@ -575,15 +575,15 @@ web-1 1/1 Running 0 10m
web-2 1/1 Running 0 7m web-2 1/1 Running 0 7m
``` ```
As the `web` Stateful Set has been deleted, `web-0` has not been relaunched. As the `web` StatefulSet has been deleted, `web-0` has not been relaunched.
In one terminal, watch the Stateful Set's Pods. In one terminal, watch the StatefulSet's Pods.
``` ```
$ kubectl get pods -w -l app=nginx $ kubectl get pods -w -l app=nginx
``` ```
In a second terminal, recreate the Stateful Set. Note that, unless In a second terminal, recreate the StatefulSet. Note that, unless
you deleted the `nginx` Service ( which you should not have ), you will see you deleted the `nginx` Service ( which you should not have ), you will see
an error indicating that the Service already exists. an error indicating that the Service already exists.
@@ -614,7 +614,7 @@ web-2 0/1 Terminating 0 3m
web-2 0/1 Terminating 0 3m web-2 0/1 Terminating 0 3m
``` ```
When the `web` Stateful Set was recreated, it first relaunched `web-0`. When the `web` StatefulSet was recreated, it first relaunched `web-0`.
Since `web-1` was already Running and Ready, when `web-0` transitioned to Since `web-1` was already Running and Ready, when `web-0` transitioned to
Running and Ready, it simply adopted this Pod. Since we recreated the Stateful Running and Ready, it simply adopted this Pod. Since we recreated the Stateful
Set with `replicas` equal to 2, once `web-0` had been recreated, and once Set with `replicas` equal to 2, once `web-0` had been recreated, and once
@@ -630,21 +630,21 @@ web-0
web-1 web-1
``` ```
Even though we deleted both the Stateful Set and the `web-0` Pod, it still Even though we deleted both the StatefulSet and the `web-0` Pod, it still
serves the hostname originally entered into its `index.html` file. This is serves the hostname originally entered into its `index.html` file. This is
because the Stateful Set never deletes the Persistent Volumes associated with a because the StatefulSet never deletes the PersistentVolumes associated with a
Pod. When you recreated the Stateful Set and it relaunched `web-0`, its original Pod. When you recreated the StatefulSet and it relaunched `web-0`, its original
Persistent Volume was remounted. PersistentVolume was remounted.
#### Cascading Delete #### Cascading Delete
In one terminal window, watch the Pods in the Stateful Set. In one terminal window, watch the Pods in the StatefulSet.
```shell ```shell
$ kubectl get pods -w -l app=nginx $ kubectl get pods -w -l app=nginx
``` ```
In another terminal, delete the Stateful Set again. This time, omit the In another terminal, delete the StatefulSet again. This time, omit the
`--cascade=false` parameter. `--cascade=false` parameter.
```shell ```shell
@@ -673,11 +673,11 @@ web-1 0/1 Terminating 0 29m
As we saw in the [Scaling Down](#ordered-pod-termination) section, the Pods As we saw in the [Scaling Down](#ordered-pod-termination) section, the Pods
are terminated one at a time, with respect to the reverse order of their ordinal are terminated one at a time, with respect to the reverse order of their ordinal
indices, and, before terminating a Pod, the Stateful Set controller waits for indices, and, before terminating a Pod, the StatefulSet controller waits for
the Pod's successor to be completely terminated. the Pod's successor to be completely terminated.
Note that, while a cascading delete will delete the Stateful Set and its Pods, Note that, while a cascading delete will delete the StatefulSet and its Pods,
it will not delete the Headless Service associated with the Stateful Set. You it will not delete the Headless Service associated with the StatefulSet. You
must delete the `nginx` Service manually. must delete the `nginx` Service manually.
```shell ```shell
@@ -685,7 +685,7 @@ $ kubectl delete service nginx
service "nginx" deleted service "nginx" deleted
``` ```
Recreate the Stateful Set and Headless Service one more time. Recreate the StatefulSet and Headless Service one more time.
```shell ```shell
kubectl create -f web.yaml kubectl create -f web.yaml
@@ -693,7 +693,7 @@ service "nginx" created
statefulset "web" created statefulset "web" created
``` ```
When all of the Stateful Set's Pods transition to Running and Ready, retrieve When all of the StatefulSet's Pods transition to Running and Ready, retrieve
thecontents of their `index.html` files. thecontents of their `index.html` files.
```shell ```shell
@@ -702,11 +702,11 @@ web-0
web-1 web-1
``` ```
Even though you completely deleted the Stateful Set, and all of its Pods, the Even though you completely deleted the StatefulSet, and all of its Pods, the
Pods are recreated with their Persistent Volumes mounted, and `web-0` and Pods are recreated with their PersistentVolumes mounted, and `web-0` and
`web-1` will still serve their hostnames. `web-1` will still serve their hostnames.
Finally delete the `web` Stateful Set and the `nginx` service. Finally delete the `web` StatefulSet and the `nginx` service.
```shell ```shell
$ kubectl delete service nginx $ kubectl delete service nginx
@@ -721,7 +721,7 @@ statefulset "web" deleted
{% capture cleanup %} {% capture cleanup %}
Whether your cluster was configured to use dynamic provisioning or you used Whether your cluster was configured to use dynamic provisioning or you used
manually provisioned volumes, you will need to manually delete the five 1 GiB manually provisioned volumes, you will need to manually delete the five 1 GiB
Persistent Volumes that were provisioned for this tutorial. PersistentVolumes that were provisioned for this tutorial.
{% endcapture %} {% endcapture %}
{% include templates/tutorial.md %} {% include templates/tutorial.md %}