Verifying the State Persistence and Exploring the Failures
In this lesson, first, we will verify the state persistence of our Jenkins deployment and then explore different failures that can occur.
Verifying the State Persistence
Now that Jenkins is up-and-running, we’ll execute a similar set of steps as before, and validate that the state is persisted across failures.
open "http://$CLUSTER_DNS/jenkins"
We opened Jenkins home screen.
Creating a New Job
If you are not authenticated, please click the Log in link and type jdoe as the User and incognito as the Password. Click the log in button.
You’ll see the create new jobs link. Click it. Type my-job as the item name, select Pipeline as the job type, and click the OK button. Once inside the job configuration screen, all we have to do is click the Save button. An empty job will be enough to test persistence.
Getting the Pod
Now we need to find out the name of the Pod created through the jenkins Deployment.
POD_NAME=$(kubectl \--namespace jenkins \get pod \--selector=app=jenkins \-o jsonpath="{.items[*].metadata.name}")
Killing a Process
With the name of the Pod stored in the environment variable POD_NAME, we can proceed and kill java process that’s running Jenkins.
kubectl --namespace jenkins \exec -it $POD_NAME pkill java
We killed the Jenkins process and thus simulated failure of the container. As a result, Kubernetes detected the failure and recreated the container.
Verification
A minute later, we can open Jenkins home screen again, and check whether the state (the job we ...