diff --git a/content/doc/book/resources/scaling-jenkins-on-kubernetes/Build-job.png b/content/doc/book/resources/scaling-jenkins-on-kubernetes/Build-job.png
new file mode 100644
index 000000000000..7a726568141d
Binary files /dev/null and b/content/doc/book/resources/scaling-jenkins-on-kubernetes/Build-job.png differ
diff --git a/content/doc/book/resources/scaling-jenkins-on-kubernetes/Kubernetes-cloud.png b/content/doc/book/resources/scaling-jenkins-on-kubernetes/Kubernetes-cloud.png
new file mode 100644
index 000000000000..d15529c51979
Binary files /dev/null and b/content/doc/book/resources/scaling-jenkins-on-kubernetes/Kubernetes-cloud.png differ
diff --git a/content/doc/book/resources/scaling-jenkins-on-kubernetes/Pod-template.png b/content/doc/book/resources/scaling-jenkins-on-kubernetes/Pod-template.png
new file mode 100644
index 000000000000..00f39f34ae49
Binary files /dev/null and b/content/doc/book/resources/scaling-jenkins-on-kubernetes/Pod-template.png differ
diff --git a/content/doc/book/scaling/scaling-jenkins-on-kubernetes.adoc b/content/doc/book/scaling/scaling-jenkins-on-kubernetes.adoc
index b57f042cb625..a349bf04d468 100644
--- a/content/doc/book/scaling/scaling-jenkins-on-kubernetes.adoc
+++ b/content/doc/book/scaling/scaling-jenkins-on-kubernetes.adoc
@@ -190,7 +190,7 @@ IP:             172.17.0.4
 
 Now, we are ready to fill in the Kubernetes plugin configuration. In order to do that, open the Jenkins UI and navigate to “Manage Jenkins -> Nodes and Clouds -> Clouds -> Add a new cloud -> Kubernetes and fill in the `Kubernetes URL` and `Jenkins URL` appropriately, by using the values which we have just collected in the previous step.
 
-image::kubernetes-plugin-configuration.png[kubernetes-plugin-configuration]
+image::Kubernetes-cloud.png[kubernetes-plugin-configuration]
 
 In addition to that, in the `Kubernetes Pod Template` section, we need to configure the image that will be used to spin up the agents.
 If you have some custom requirements for your agents, you can build one more dockerfile with the appropriate changes the same way we did for the Jenkins controller.
@@ -199,13 +199,13 @@ On the other hand, if you don’t have unique requirements for your agents, you
 Kubernetes Pod Template Name - can be any and will be shown as a prefix for unique generated agents' names, which will be run automatically during builds
 Docker image - the docker image name that will be used as a reference to spin up a new Jenkins agents.
 
-image::pod-template-configuration.png[pod-template-configuration]
+image::Pod-template.png[pod-template-configuration]
 
 == Using Jenkins Agents
 
 Now all the configuration seems to be in place and we are ready for some tests. Let’s create two different build plans.
 
-image::build-jobs.png[image]
+image::Build-job.png[build-job-image]
 
 Now let’s trigger the execution for both of the builds.
 You should see that both build plans appear in the `Build Queue` box almost immediately.