Merge pull request #143 from Namanv0509/img-fix

Namanv0509 · web-flow · commit 08dae8b5bacd · 2025-07-26T01:20:25.000+05:30
broken image and alt fix
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/cronjob/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/cronjob/_index.md
@@ -9,4 +9,4 @@ weight: 7
 
 Use familiar cron syntax to schedule tasks. CronJobs are part of the Batch API for creating short-lived non-server tools. CronJobs provide a method for scheduling the execution of Pods. They are excellent for running periodic tasks like backups, reports, and automated tests.
 
-![image](cronjob.png)
+![cronjob](cronjob.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/daemonset/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/daemonset/_index.md
@@ -9,4 +9,4 @@ weight: 5
 
 DaemonSets have many use cases – one frequent pattern is to use DaemonSets to install or configure each host node. DaemonSets provide a way to ensure that a Pod copy is running on every node in the cluster. As a cluster grows and shrinks, the DaemonSet spreads these specially labelled Pods across all nodes.
 
-![image](deamonset.png)
+![deamonset](deamonset.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/deployment/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/deployment/_index.md
@@ -9,4 +9,4 @@ weight: 4
 
 A Deployment is a higher-order abstraction that controls deploying and maintaining a set of Pods. Behind the scenes, it uses a ReplicaSet to keep the Pods running, but it offers sophisticated logic for deploying, updating, and scaling a set of Pods within a cluster. Deployments support rollbacks and rolling updates. Rollouts can be paused if needed.
 
-![image](deployment.gif)
+![deployment](deployment.gif)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/imp-building-blocks/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/imp-building-blocks/_index.md
@@ -13,4 +13,4 @@ A critical fault on the node where your Pod runs means that all the Pods on that
 
 Instead, you can use workload resources that address a set of Pods on your behalf. These resources configure controllers that ensure the correct number and right kind of Pods are running to match the state you specified. Kubernetes provides several built-in workload resources: Pods, ReplicaSet, Deployment, DaemonSet, Ingress, and CronJob, to name a few of those building blocks.
 
-![image](kubernetes5.png)
+![kubernetes5](kubernetes5.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/ingress/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/ingress/_index.md
@@ -9,4 +9,4 @@ weight: 6
 
 Route traffic to and from the cluster. Provide a single SSL endpoint for multiple applications. Many implementations of an ingress allow you to customize your platform. Ingresses provide a way to declare that they should channel traffic from the outside of the cluster into destination points within the cluster. One single external Ingress point can accept traffic destined to many internal services.
 
-![image](ingress2.png)
+![ingress2](ingress2.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/pod/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/pod/_index.md
@@ -9,7 +9,7 @@ weight: 2
 
 Pods are the basic building blocks to run containers inside of Kubernetes. Every Pod holds at least one container and controls the execution of that container. If all containers terminate, the Pod terminates too. Mounting storage, setting environment variables, and feed information into the container are all functions provided by the Pod.
 
-![image](pod.png)
+![pod](pod.png)
 
 Pods are the smallest deployable units of computing that you can create and manage in Kubernetes. Pods in a Kubernetes cluster are used in two main ways:
 
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/replicaset/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-building-blocks/content/replicaset/_index.md
@@ -9,4 +9,4 @@ weight: 3
 
 A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time to guarantee the availability of a specified number of identical Pods. However, a Deployment is a higher-level concept that manages ReplicaSets and provides declarative updates to Pods and other useful features. Therefore, Deployments are recommended instead of directly using ReplicaSets.
 
-![image](replicaset.gif)
+![replicaset](replicaset.gif)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-details/content/features/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-details/content/features/_index.md
@@ -7,7 +7,7 @@ weight: 3
 
 ### Features
 
-![image](features.png)
+![features](features.png)
 
 ### Kubernetes provides the following features
 #### self-healing
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-details/content/imperative-vs-declarative/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-details/content/imperative-vs-declarative/_index.md
@@ -12,4 +12,4 @@ What a difference a configuration make :).
 The significant change in this new IT world is that well-trained and practiced processes are outdated and useless. The imperative was the old world, you defined step-by-step guidance, and you also executed or overseen the execution of those configuration steps. The declarative way is to determine the desired state and an intelligent system conducts and supervises the configuration and operation steps.
 
 
-![image](impvsdec.png)
+![impvsdec](impvsdec.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-details/content/kubernetes-is/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-details/content/kubernetes-is/_index.md
@@ -11,7 +11,7 @@ weight: 3
 
 ... extensible, and lets users integrate their logging, monitoring, alerting, and many more solutions because it is not monolithic, and these solutions are optional and pluggable.
 
-![image](kubernetes4.png)
+![kubernetes4](kubernetes4.png)
 
 ### Kubernetes does NOT ...
 **... limit the types of applications supported.**
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-details/content/kubernetes/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/kubernetes-details/content/kubernetes/_index.md
@@ -11,6 +11,6 @@ Google open-sourced the Kubernetes project in 2014. Kubernetes combines over 15
 
 The name Kubernetes originates from Greek, meaning helmsman or pilot.
 
-![image](kubernetes3.png)
+![kubernetes3](kubernetes3.png)
 
 **Kubernetes is a portable, extensible, open-source platform for managing containerized workloads and services that facilitates both automation and declarative configuration.**
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-containers/content/container-benefits/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-containers/content/container-benefits/_index.md
@@ -9,11 +9,11 @@ weight: 3
 
 - **dev and ops separation of concerns** create application container images at build/release time rather than deployment time, thereby decoupling applications from infrastructure
 
-![image](benefit1.png)
+![benefit1](benefit1.png)
 
 - **continuous development, integration, and deployment** provides for reliable and frequent container image build and deployment with quick and efficient rollbacks – due to image immutability
 
-![image](benefit2.png)
+![benefit2](benefit2.png)
 
 - **environmental consistency across dev, test, and prod** runs the same on a laptop as it does on an on-premises server, virtualized server, and in the cloud
 
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-containers/content/experiences-we-want-to-change/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-containers/content/experiences-we-want-to-change/_index.md
@@ -9,21 +9,21 @@ weight: 1
 
 Many people have a complex job building, testing, and running systems based on old concepts and technology in today's IT — the results you can see below (Experiences we want to change!). Modern ways to build, test, and run IT systems are not adopted as broadly as possible. Hence, a lot of pain is still out there that we could ease by changing IT processes and utilizing the new ways.
 
-![image](containers.png)
+![containers](containers.png)
 
 ### Experiences we want to change!
 
 #### BUILD - Life of a Developer
 Here you see a developer who brought her code into production, only to find out that it didn't run like on her laptop ...
 
-![image](exp1.png)
+![exp1](exp1.png)
 
 ### TEST - Life of System Architects
 Here you can see system architects who mistakenly made a load test on a production server ...
 
-![image](exp2.png)
+![exp2](exp2.png)
 
 #### RUN - Life of a System Administrator
 Here you can see a system administrator who was woken at 3 am to restart a process ...
 
-![image](exp3.png)
+![exp3](exp3.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-containers/content/history-of-deployment/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-containers/content/history-of-deployment/_index.md
@@ -7,7 +7,7 @@ weight: 4
 
 ### History of Application Deployments
 
-![image](history.png)
+![history](history.png)
 
 #### Traditional Deployment
 Early on, organizations ran applications on physical servers. There was no way to define resource boundaries for applications in a physical server, and this caused resource allocation issues. For example, if multiple applications run on a physical server, there can be instances where one application would take up most of the resources, and as a result, the other applications would underperform. A solution for this would be to run each application on a different physical server. But this did not scale as resources were underutilized, and it was expensive for organizations to maintain many physical servers.
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-containers/content/new-idea-concepts/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-containers/content/new-idea-concepts/_index.md
@@ -15,4 +15,4 @@ Replication of success is always desirable and sparked a new way of operating IT
 
 Container Technology in the shipping industry Instead of thinking up a separate way of shipping for each product, placing the goods in steel containers designed for pickup by the crane on the dock and fit into the ship is a more efficient way to do transport at scale.
 
-![image](ship.png)
+![ship](ship.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-exoscale-sks/content/packaging-and-pricing/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-exoscale-sks/content/packaging-and-pricing/_index.md
@@ -7,4 +7,4 @@ weight: 2
 
 ### Packaging & Pricing
 
-![image](pricing.png)
+![pricing](pricing.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-exoscale-sks/content/scalable-kubernetes-service/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-exoscale-sks/content/scalable-kubernetes-service/_index.md
@@ -9,7 +9,7 @@ weight: 1
 
 Start with a privacy-minded public cloud to host from single applications to complex architectures. Deploy a production-ready cluster in 90 seconds and manage it with a simple web portal, CLI, API or your choice of tools (Terraform).
 
-![image](exoscale.png)
+![exoscale](exoscale.png)
 
 ### SKS Features
 **Access to all compute instance types**
@@ -35,4 +35,4 @@ With a free STARTER version and an affordable PRO plan, SKS provides straightfor
 
 Deploy your cluster where you need to, in the region that suits your latency, privacy or redundancy strategy.
 
-![image](kubernetes6.png)
+![kubernetes6](kubernetes6.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-kubernetes/content/kubernetes-plain-english/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-kubernetes/content/kubernetes-plain-english/_index.md
@@ -7,11 +7,11 @@ weight: 2
 
 ### Kubernetes in Plain English
 
-![image](kubernetes2.png)
+![kubernetes2](kubernetes2.png)
 
 **Containerization** is this trend that’s **taking over the world** to allow people to run all kinds of different applications in a variety of different environments. When they do that, they **need an orchestration solution** in order to keep track of all of those containers and schedule them and orchestrate them. **Kubernetes is an increasingly popular way to do that.**
 
-![image](dankohn.png)
+![dankohn](dankohn.png)
 
 Dan Kohn, former executive director of the CNCF
 
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-kubernetes/content/without-container/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-kubernetes/content/without-container/_index.md
@@ -9,7 +9,7 @@ weight: 1
 
 Running services in containers tend to produce numerous containers pretty quick. Handling many containers with no additional aid is a very cumbersome job. Hence, an orchestration solution is necessary to run services in containers efficiently.
 
-![image](containers2.png)
+![containers2](containers2.png)
 
 ### Without Container Orchestration
 
@@ -20,4 +20,4 @@ Running services in containers tend to produce numerous containers pretty quick.
 - Scaling services/applications becomes more and more **difficult**.
 - Public cloud provider resource usage becomes more and more **expensive**.
 
-![image](kubernetes.png)
+![kubernetes](kubernetes.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-managed-kubernetes/content/managed-ecosystem/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-managed-kubernetes/content/managed-ecosystem/_index.md
@@ -13,7 +13,7 @@ Container lifecycle management as well as monitoring, backup, CI/CD, security, l
 
 K8s comes with multiple options and plugins for each layer. Each team has its preferences for ecosystem decisions.
 
-![image](ecosystem.png)
+![ecosystem](ecosystem.png)
 
 ### Managed Container Orchestration Ecosystems
 
@@ -29,4 +29,4 @@ VSHN's APPUiO is the leading Kubernetes based Container Platform for the design,
 
 Elastisys' Compliant Kubernetes (CK8s) is a security-hardened, CNCF certified Kubernetes distribution that allows organizations to enjoy the benefits of Kubernetes while fulfilling regulatory requirements – all the way from development to deployment to operations and audits. Compliant Kubernetes comes pre-configured with CNCF approved open source projects that make life easier at audits and enforces compliance policies for your workloads, helping fulfil regulatory standards. You can rely on pre-configured templates and best practices and define your policies to achieve your regulatory goals. The managed service scope is fully managed.
 
-![image](ecosystem2.png)
+![ecosystem2](ecosystem2.png)
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-managed-kubernetes/content/managed-kubenetes/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/intro-kubernetes/why-managed-kubernetes/content/managed-kubenetes/_index.md
@@ -16,6 +16,6 @@ Suppose you don't have the time, the budget, and the human resources to master a
 
 A simple who is responsible for what and pain versus gain comparison from available solutions should paint a clear picture of the golden mean, which is managed Kubernetes for most newcomers to the topic at hand.
 
-![image](manages-kubernetes2.png)
+![manages-kubernetes2](manages-kubernetes2.png)
 
 To say that **Kubernetes is the leading container orchestration platform** is an understatement. It’s the only container orchestration platform that counts. However, to say that Kubernetes is complex is also an understatement. **The learning curve is both steep and long.**
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/kubernetes-workshop/concepts/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/kubernetes-workshop/concepts/_index.md
@@ -59,7 +59,7 @@ To run a Pod we often rely on a higher level resource, instead of running it dir
 
 A request that reaches a Service is load-balanced between the exposed Pods
 
-![service]({{< usestatic "service.png" >}})
+![service](service.png)
 
 
 A Pod can use several resources
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/kubernetes-workshop/main-resources/content/configuration/content/learn/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/kubernetes-workshop/main-resources/content/configuration/content/learn/_index.md
@@ -231,7 +231,7 @@ spec:
 
 The previous exercise left the app with the following components:
 
-![votingapp-1]("votingapp-1.png)
+![votingapp-1](votingapp-1.png)
 
 We will now add a Secret to store the password required to connect to the PostgreSQL database.
 
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/exoscale-managed-kubernetes/content/creating-sks-cluster/content/exoscale-account.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/exoscale-managed-kubernetes/content/creating-sks-cluster/content/exoscale-account.md
@@ -38,14 +38,14 @@ The last step is to generate an API Key; you need this key pair to configure the
 
 First, go to the IAM menu and create a role. Exoscale offers a very granular and unique role configuration. In this example you will make a role with rights on the compute service. You can select the Compute service class and allow all the operations.
 
-![role](role)
+![role](role.png)
 
 Then, create a key associated with this role; you can give this key the name of your choice. Associate the role you created above.
 
-![apikey](apikey)
+![apikey](apikey.png)
 
 This process generates a key pair.
 
-![dummy-keypair](dummy-keypair)
+![dummy-keypair](dummy-keypair.png)
 
 Store these keys in the EXOSCALE_API_KEY and EXOSCALE_API_SECRET environment variables as you need them in the next step.
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/exoscale-managed-kubernetes/content/creating-sks-cluster/content/using-pulumi.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/exoscale-managed-kubernetes/content/creating-sks-cluster/content/using-pulumi.md
@@ -168,7 +168,7 @@ We can verify the stack exists in the Pulumi backend.
 pulumi stack ls
 ```
 
-![pulumi-template](pulumi-template)
+![pulumi-template](pulumi-template.png)
 
 Before deploying the stack, we preview the resources it will create.
 
@@ -206,7 +206,7 @@ Resources:
 > [!INFO]
 > It takes about 2 minutes for the cluster and the associated resources to be available.
 
-![pulumi-cluster](pulumi-cluster)
+![pulumi-cluster](pulumi-cluster.png)
 
 Next, we retrieve the kubeconfig file.
 
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/exoscale-managed-kubernetes/content/deploying-votingapp/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/exoscale-managed-kubernetes/content/deploying-votingapp/_index.md
@@ -125,8 +125,8 @@ Using the following command, get the external IP of any node and verify you can
 $ kubectl get no -o wide
 ```
 
-![access-nodeport](access-nodeport)
+![access-nodeport](access-nodeport.png)
 
-![access-nodeport2](access-nodeport2)
+![access-nodeport2](access-nodeport2.png)
 
 Using NodePort Services is not a recommended way to expose production application; for this purpose, we need to use a LoadBalancer Services, as we will explore in the next section.
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/exposing-votingapp/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/exposing-votingapp/_index.md
@@ -23,7 +23,7 @@ helm install traefik traefik/traefik --version 33.2.1 -n traefik --create-namesp
 
 In the background, this creates a Kubernetes Service of type LoadBalancer responsible for exposing the Traefik Ingress Controller. This Service triggers the creation of a Network Load Balancer on the Exoscale infrastructure to expose the Ingress Controller to the internet. From the Exoscale portal, we can get the details of this Load Balancer, including its IP address.
 
-![nlb](nlb)
+![nlb](nlb.png)
 
 You can also get the LoadBalancer’s IP Address from the command line:
 
@@ -66,9 +66,9 @@ NOTE: you need to use the IP address of your own LoadBalancer
 159.100.240.231 result.votingapp.cc
 ```
 
-![nlb-votingapp1](nlb-votingapp1)
+![nlb-votingapp1](nlb-votingapp1.png)
 
-![nlb-votingapp2](nlb-votingapp2)
+![nlb-votingapp2](nlb-votingapp2.png)
 
 If you do not have permission to modify your */etc/hosts*, you can temporarily use [nip.io](https://nip.io), a handy DNS resolver tool. For example, with *nip.io*, the domain *vote.159.100.240.231.nip.io* automatically resolves to *159.100.240.231.*
 
@@ -90,7 +90,7 @@ helm upgrade --install vote oci://registry-1.docker.io/voting/app --version v1.0
 
 Open a browser at http://vote.LOAD_BALANCER_IP.nip.io to access the application.
 
-![nlb-nip.io](nlb-nip.io)
+![nlb-nip.io](nlb-nip.io.png)
 
 > [!WARNING]
 > Before going any further, make sure to remove the changes we made previously in the /etc/hosts file.
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/managing-secrets/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/managing-secrets/_index.md
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/persisting-data/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/persisting-data/_index.md
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/using-object-storage/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/using-object-storage/_index.md
diff --git a/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/votingapp/_index.md b/content/learning-paths/98e16360-a366-4b78-8e0a-031da07fdacb/practice-on-exoscale/votingapp/_index.md

Original file line number	Diff line number	Diff line change
`@@ -9,4 +9,4 @@ weight: 7`
`9`	`9`
`10`	`10`	`Use familiar cron syntax to schedule tasks. CronJobs are part of the Batch API for creating short-lived non-server tools. CronJobs provide a method for scheduling the execution of Pods. They are excellent for running periodic tasks like backups, reports, and automated tests.`
`11`	`11`
`12`		`-![image](cronjob.png)`
	`12`	`+![cronjob](cronjob.png)`
Original file line number	Diff line number	Diff line change
`@@ -9,4 +9,4 @@ weight: 5`
`9`	`9`
`10`	`10`	`DaemonSets have many use cases – one frequent pattern is to use DaemonSets to install or configure each host node. DaemonSets provide a way to ensure that a Pod copy is running on every node in the cluster. As a cluster grows and shrinks, the DaemonSet spreads these specially labelled Pods across all nodes.`
`11`	`11`
`12`		`-![image](deamonset.png)`
	`12`	`+![deamonset](deamonset.png)`
Original file line number	Diff line number	Diff line change
`@@ -9,4 +9,4 @@ weight: 4`
`9`	`9`
`10`	`10`	`A Deployment is a higher-order abstraction that controls deploying and maintaining a set of Pods. Behind the scenes, it uses a ReplicaSet to keep the Pods running, but it offers sophisticated logic for deploying, updating, and scaling a set of Pods within a cluster. Deployments support rollbacks and rolling updates. Rollouts can be paused if needed.`
`11`	`11`
`12`		`-![image](deployment.gif)`
	`12`	`+![deployment](deployment.gif)`
Original file line number	Diff line number	Diff line change
`@@ -13,4 +13,4 @@ A critical fault on the node where your Pod runs means that all the Pods on that`
`13`	`13`
`14`	`14`	`Instead, you can use workload resources that address a set of Pods on your behalf. These resources configure controllers that ensure the correct number and right kind of Pods are running to match the state you specified. Kubernetes provides several built-in workload resources: Pods, ReplicaSet, Deployment, DaemonSet, Ingress, and CronJob, to name a few of those building blocks.`
`15`	`15`
`16`		`-![image](kubernetes5.png)`
	`16`	`+![kubernetes5](kubernetes5.png)`
Original file line number	Diff line number	Diff line change
`@@ -9,4 +9,4 @@ weight: 6`
`9`	`9`
`10`	`10`	`Route traffic to and from the cluster. Provide a single SSL endpoint for multiple applications. Many implementations of an ingress allow you to customize your platform. Ingresses provide a way to declare that they should channel traffic from the outside of the cluster into destination points within the cluster. One single external Ingress point can accept traffic destined to many internal services.`
`11`	`11`
`12`		`-![image](ingress2.png)`
	`12`	`+![ingress2](ingress2.png)`
Original file line number	Diff line number	Diff line change
`@@ -9,4 +9,4 @@ weight: 3`
`9`	`9`
`10`	`10`	`A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time to guarantee the availability of a specified number of identical Pods. However, a Deployment is a higher-level concept that manages ReplicaSets and provides declarative updates to Pods and other useful features. Therefore, Deployments are recommended instead of directly using ReplicaSets.`
`11`	`11`
`12`		`-![image](replicaset.gif)`
	`12`	`+![replicaset](replicaset.gif)`
Original file line number	Diff line number	Diff line change
`@@ -12,4 +12,4 @@ What a difference a configuration make :).`
`12`	`12`	`The significant change in this new IT world is that well-trained and practiced processes are outdated and useless. The imperative was the old world, you defined step-by-step guidance, and you also executed or overseen the execution of those configuration steps. The declarative way is to determine the desired state and an intelligent system conducts and supervises the configuration and operation steps.`
`13`	`13`
`14`	`14`
`15`		`-![image](impvsdec.png)`
	`15`	`+![impvsdec](impvsdec.png)`