How to scale and create a StatefulSet

Now, since I'm just creating it again, I already have the PVs created, and I already have the PVCs. They will be attaching directly, and they have HTML5 already in there. Now, let's first see some of the resources we already have. We will use the kubectl get storageclass command, and we can see that we are using a rancher local path provisioner, which is very simple to install with the YAML file. We'll have that put in the video's description, where we will see how to deploy the local path provisioner.

You can see that the local path name over here matches the local path name. Now, when we use the kubectl create -f statefulset.yaml, it creates the service and StatefulSet. Now, let's verify the pods through kubectl get pods. First, the web-0 pod started running, and then the web-1 pod started creating. We can get the StatefulSet through the kubectl get statefulset command. We can see that the name is the web. Hence, we define the name as web, and the pod names are very simple, web-0 and web-1. Now, another interesting thing that we were talking about was the service. It's a headless service, so it has its own characteristics and it has its own properties. Now, we'll try to scale the replica set with the >kubectl scale --replicas=3 statefulset/web command, which has been scaled. Now through kubectl get pods, we can see that it has started creating. Through kubectl get pvc, we can see that a new persistent volume claim just got created, and with kubectl get pv, we can see the persistent volumes. Since it's a dynamic provisioner that I'm using, the PV was automatically created. You should have some mechanism for this. With kubectl get pods, we can see that the name of the new pod is web-2, a predictable name, so as we were told.

Now first, let's go inside one of the pods. We can do that using the kubectl exec -it web-0 --bash command. Now, we have over here that whenever we create a headless service, it will also have created a network entity, so it has its own DNS name that can be referred to. How we can check that is we can use the curl command. Use the curl web-0.nginx.default.svc.cluster.local command, and you will get the Hello world! response which was the HTML we had. You can see that we can curl this. We can also curl web-0.ngnix using the curl web-0.nginx command and, similarly, the other ones, and we will get the same response. Web-2.nginx should not have anything because I just created the PVC, and I do not have an index.html file, and that's why this particular thing is coming.