<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Prudhvi Keshav on Medium]]></title>
        <description><![CDATA[Stories by Prudhvi Keshav on Medium]]></description>
        <link>https://medium.com/@prudhvi_keshav?source=rss-5d06d9718839------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Prudhvi Keshav on Medium</title>
            <link>https://medium.com/@prudhvi_keshav?source=rss-5d06d9718839------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:04:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@prudhvi_keshav/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Kubernetes Challenge 1: Deploying Jekyll Static Site Generator on Kubernetes ]]></title>
            <link>https://medium.com/@prudhvi_keshav/kubernetes-challenge-1-deploying-jekyll-static-site-generator-on-kubernetes-2bc6bdcae510?source=rss-5d06d9718839------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bc6bdcae510</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Prudhvi Keshav]]></dc:creator>
            <pubDate>Fri, 06 Sep 2024 09:28:27 GMT</pubDate>
            <atom:updated>2024-09-06T09:28:27.237Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the KodeKloud Kubernetes Challenge 1! In this challenge, we’ll deploy a Jekyll Static Site Generator (SSG) on a Kubernetes cluster. The task involves configuring Kubernetes resources like PersistentVolume (PV), PersistentVolumeClaim (PVC), Pod, and Service, as well as setting up user permissions and contexts in the kubeconfig file. Let’s dive into the step-by-step solution!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*_mOIqtMylwkAlsI3qfNqaA.png" /></figure><h3>🎯 Challenge Breakdown</h3><p>Here’s what you need to do:</p><ol><li><strong>User Configuration</strong>: Create a user named martin in the kubeconfig file and set up a new context called developer.</li><li><strong>PersistentVolumeClaim (PVC) Setup</strong>: Define and bind a PVC to an existing PV.</li><li><strong>Pod Configuration</strong>: Create a Pod with an Init Container to initialize the Jekyll site and a main Container to serve it.</li><li><strong>Service Configuration</strong>: Expose the Jekyll site via a Service.</li><li><strong>Role and RoleBinding Configuration</strong>: Set up roles and bindings to manage permissions.</li></ol><h3>🛠️ Prerequisites</h3><p>Before starting, ensure you have:</p><ul><li><strong>Kubernetes Cluster</strong>: Access to a Kubernetes cluster.</li><li><strong>kubectl</strong>: The command-line tool for interacting with Kubernetes.</li><li><strong>Kubeconfig File</strong>: Access to your kubeconfig file.</li></ul><h3>🧑‍💻 User and Context Configuration</h3><h3>1. User Configuration</h3><p>Create a new user martin in your kubeconfig file with the following credentials:</p><pre>kubectl config set-credentials martin --client-key=/root/martin.key --client-certificate=/root/martin.crt</pre><h3>2. Context Configuration</h3><p>Set up a new context called developer using the martin user and the kubernetes cluster. Make this context the current one:</p><pre>kubectl config set-context developer --user=martin --cluster=kubernetes<br>kubectl config use-context developer</pre><h3>📦 Setting Up PersistentVolumeClaim (PVC)</h3><h3>1. Define PersistentVolumeClaim</h3><p>Create a file named jekyll-pvc.yaml with the following content:</p><pre>apiVersion: v1<br>kind: PersistentVolumeClaim<br>metadata:<br>  name: jekyll-site<br>  namespace: development<br>spec:<br>  accessModes:<br>    - ReadWriteMany<br>  resources:<br>    requests:<br>      storage: 1Gi</pre><p>Apply the PVC definition:</p><pre>kubectl apply -f jekyll-pvc.yaml</pre><p>Verify that the PVC is bound to the existing PersistentVolume named jekyll-site:</p><pre>kubectl get pvc -n development</pre><h3>🛠️ Configuring the Pod</h3><h3>1. Define the Pod</h3><p>Create a file named jekyll-pod.yaml with the following configuration:</p><pre>apiVersion: v1<br>kind: Pod<br>metadata:<br>  name: jekyll<br>  labels:<br>    run: jekyll<br>spec:<br>  initContainers:<br>  - name: copy-jekyll-site<br>    image: gcr.io/kodekloud/customimage/jekyll<br>    command: [&quot;jekyll&quot;, &quot;new&quot;, &quot;/site&quot;]<br>    volumeMounts:<br>    - name: site<br>      mountPath: /site<br>  containers:<br>  - name: jekyll<br>    image: gcr.io/kodekloud/customimage/jekyll-serve<br>    volumeMounts:<br>    - name: site<br>      mountPath: /site<br>  volumes:<br>  - name: site<br>    persistentVolumeClaim:<br>      claimName: jekyll-site</pre><p>Apply the Pod configuration:</p><pre>kubectl apply -f jekyll-pod.yaml</pre><h3>🌐 Configuring the Service</h3><h3>1. Define the Service</h3><p>Create a file named jekyll-service.yaml with the following content:</p><pre>apiVersion: v1<br>kind: Service<br>metadata:<br>  name: jekyll<br>  namespace: development<br>spec:<br>  type: NodePort<br>  ports:<br>  - port: 8080<br>    targetPort: 4000<br>    nodePort: 30097<br>  selector:<br>    run: jekyll</pre><p>Apply the Service definition:</p><pre>kubectl apply -f jekyll-service.yaml</pre><h3>🔐 Configuring Role and RoleBinding</h3><h3>1. Define the Role</h3><p>Create a file named developer-role.yaml with the following content:</p><pre>apiVersion: rbac.authorization.k8s.io/v1<br>kind: Role<br>metadata:<br>  name: developer-role<br>  namespace: development<br>rules:<br>- apiGroups: [&quot;&quot;]<br>  resources: [&quot;services&quot;, &quot;persistentvolumeclaims&quot;, &quot;pods&quot;]<br>  verbs: [&quot;*&quot;]</pre><h3>2. Define the RoleBinding</h3><p>Create a file named developer-rolebinding.yaml with the following content:</p><pre>apiVersion: rbac.authorization.k8s.io/v1<br>kind: RoleBinding<br>metadata:<br>  name: developer-rolebinding<br>  namespace: development<br>subjects:<br>- kind: User<br>  name: martin<br>  apiGroup: rbac.authorization.k8s.io<br>roleRef:<br>  kind: Role<br>  name: developer-role<br>  apiGroup: rbac.authorization.k8s.io</pre><p>Apply the Role and RoleBinding configurations:</p><pre>kubectl apply -f developer-role.yaml<br>kubectl apply -f developer-rolebinding.yaml</pre><h3>✅ Verification</h3><p>To ensure everything is set up correctly, perform the following checks:</p><ol><li><strong>Verify PVC Binding:</strong></li></ol><pre>kubectl get pvc -n development</pre><p>2. <strong>Check Pod Status:</strong></p><pre>kubectl get pods -n development</pre><p>Ensure the Pod is running and has the run=jekyll label.</p><p>3. <strong>Check Service:</strong></p><pre>kubectl get services -n development</pre><p>Ensure the Service is exposed on NodePort 30097.</p><p>4. <strong>Check Logs:</strong></p><p>Verify that the Jekyll site is being served correctly:</p><pre>kubectl logs -n development jekyll</pre><h3>📋 Summary</h3><p>Congratulations! we have successfully completed KodeKloud Kubernetes Challenge 1 by deploying a Jekyll Static Site Generator. Here’s a summary of what we achieved:</p><ul><li><strong>PersistentVolumeClaim</strong>: Created and bound to jekyll-site.</li><li><strong>Pod</strong>: Configured with Jekyll images for initialization and serving.</li><li><strong>Service</strong>: Exposed the Jekyll site on NodePort 30097.</li><li><strong>Role and RoleBinding</strong>: Set up to manage user permissions.</li></ul><p>Feel free to revisit and adjust configurations based on your requirements. Happy Kubernetes-ing! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bc6bdcae510" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Redis Deployment in Kubernetes: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@prudhvi_keshav/mastering-redis-deployment-in-kubernetes-a-step-by-step-guide-93daf1afd1a8?source=rss-5d06d9718839------2</link>
            <guid isPermaLink="false">https://medium.com/p/93daf1afd1a8</guid>
            <dc:creator><![CDATA[Prudhvi Keshav]]></dc:creator>
            <pubDate>Tue, 06 Aug 2024 11:57:15 GMT</pubDate>
            <atom:updated>2024-08-06T11:57:15.406Z</atom:updated>
            <content:encoded><![CDATA[<p>When optimizing application performance, caching can be a game-changer. The application development team has decided to integrate Redis into their Kubernetes cluster to enhance the efficiency of their database services. In this guide, we’ll walk you through the process of deploying Redis on Kubernetes, from creating the necessary configuration to verifying that everything is up and running smoothly.</p><h3>Step 1: Create the ConfigMap</h3><p>To start, we need to define the Redis configuration that will control its behavior. For this setup, we’re focusing on setting a maximum memory limit. Kubernetes ConfigMaps are a great way to manage configuration data separately from application code.</p><ol><li><strong>Create a ConfigMap</strong> named my-redis-config with a setting for maxmemory of 2mb. This configuration ensures Redis will use a maximum of 2 megabytes of memory.</li></ol><p>Run this command:</p><pre>kubectl create configmap my-redis-config --from-literal=maxmemory=2mb</pre><p>Expected Output:</p><pre>configmap/my-redis-config created</pre><p>This output confirms that your ConfigMap has been created successfully.</p><h3>Step 2: Define the Redis Deployment</h3><p>Now, we need to set up a Kubernetes Deployment for Redis. A Deployment in Kubernetes manages the deployment of pods and ensures that the specified number of replicas are running. Here’s what we’ll be configuring:</p><ul><li><strong>Deployment Name:</strong> redis-deployment</li><li><strong>Image:</strong> redis:alpine (a lightweight Redis image)</li><li><strong>Container Name:</strong> redis-container</li><li><strong>Replicas:</strong> 1 (we want only one Redis instance for this setup)</li><li><strong>CPU Request:</strong> 1 CPU</li><li><strong>Volumes:</strong> Two volumes — an empty directory and a ConfigMap</li><li><strong>Port Exposure:</strong> Port 6379 for Redis</li></ul><p>Here’s the YAML configuration for the Redis Deployment:</p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  labels:<br>    app: redis-deployment<br>  name: redis-deployment<br>spec:<br>  replicas: 1<br>  selector:<br>    matchLabels:<br>      app: redis-deployment<br>  strategy: {}<br>  template:<br>    metadata:<br>      creationTimestamp: null<br>      labels:<br>        app: redis-deployment<br>    spec:<br>      containers:<br>      - image: redis:alpine<br>        name: redis-container<br>        ports:<br>        - containerPort: 6379<br>        resources:<br>          requests:<br>            cpu: 1<br>        volumeMounts:<br>        - name: data<br>          mountPath: /redis-master-data<br>        - name: redis-config<br>          mountPath: /redis-master<br>      volumes:<br>      - name: redis-config<br>        configMap: <br>          name: my-redis-config<br>      - name: data<br>        emptyDir: {}<br>status: {}</pre><h3>Step 3: Apply the Configuration</h3><p>With the YAML configuration ready, it’s time to deploy Redis:</p><ol><li><strong>Save the YAML Configuration</strong> to a file named redis-deployment.yaml.</li><li><strong>Apply the Configuration</strong> using:</li></ol><pre>kubectl apply -f redis-deployment.yaml</pre><p>Expected Output:</p><pre>deployment.apps/redis-deployment created</pre><p>This output confirms that the deployment has been successfully created.</p><h3>Step 4: Verify the Deployment</h3><p>To ensure everything is running as expected:</p><ol><li><strong>Check Deployments:</strong></li></ol><pre>kubectl get deployments</pre><p>2. <strong>Check Pods:</strong></p><pre>kubectl get pods</pre><p>You should see redis-deployment listed, and the pod associated with it should be in the Running state.</p><h3>Summary</h3><p>In this guide, we’ve set up Redis on a Kubernetes cluster by creating a ConfigMap for configuration, defining a Deployment for Redis, applying the configuration, and verifying the deployment. By following these steps, you’ve laid the groundwork for leveraging Redis in your Kubernetes environment, which will be crucial for boosting the performance of your application.</p><p>Happy deploying! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93daf1afd1a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Terraform Challenge Series 1: Kubernetes Resource Deployment]]></title>
            <link>https://medium.com/@prudhvi_keshav/terraform-challenge-series-1-kubernetes-resource-deployment-6325b27ba469?source=rss-5d06d9718839------2</link>
            <guid isPermaLink="false">https://medium.com/p/6325b27ba469</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Prudhvi Keshav]]></dc:creator>
            <pubDate>Tue, 06 Aug 2024 09:45:06 GMT</pubDate>
            <atom:updated>2024-08-06T09:45:06.674Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the first installment of our Terraform Challenge Series, where we’ll dive into the exciting world of Kubernetes resource deployment using Terraform. Whether you’re a seasoned DevOps engineer or just getting started with infrastructure as code, this challenge will help you master the essential skills needed to define and deploy Kubernetes resources efficiently.</p><h3>Challenge Overview</h3><p>In this challenge, you’ll use Terraform to define and deploy Kubernetes resources. Follow the detailed instructions below to complete the task and gain hands-on experience in managing Kubernetes clusters with Terraform.</p><h3>Step 1: Verify Terraform Installation</h3><p>First, ensure that Terraform version 1.1.5 is installed on your control plane.</p><h3>Step 2: Configure Provider Settings</h3><p>Next, set up Terraform to interact with your Kubernetes cluster by creating a configuration file named provider.tf in the /root/terraform_challenge directory. This file should:</p><ul><li>Use the hashicorp/kubernetes provider.</li><li>Assign the local name kubernetes to this provider.</li><li>Set the provider version to 2.11.0.</li><li>Configure the provider to use the kubeconfig file located at /root/.kube/config for connecting to your Kubernetes cluster.</li></ul><h3>Step 3: Define the Kubernetes Service</h3><p>Create a Terraform resource to define a Kubernetes service within a file named service.tf. This service will be of type NodePort, making it accessible externally on a specific port. The service should have the following specifications:</p><ul><li><strong>Service Name:</strong> webapp-service</li><li><strong>Service Type:</strong> NodePort</li><li><strong>Port:</strong> 8080 (the port exposed by the service)</li><li><strong>NodePort:</strong> 30080 (the port on each node that routes traffic to the service)</li></ul><h3>Step 4: Define the Kubernetes Deployment</h3><p>Create another Terraform resource for a Kubernetes deployment in a file named deployment.tf. This deployment will manage the lifecycle of your application pods. Configure it with the following details:</p><ul><li><strong>Deployment Name:</strong> frontend</li><li><strong>Deployment Labels:</strong> name: frontend</li><li><strong>Replicas:</strong> 4 (number of pod replicas to be maintained)</li><li><strong>Pod Labels:</strong> name: webapp</li><li><strong>Container Image:</strong> kodekloud/webapp-color:v1</li><li><strong>Container Name:</strong> simple-webapp</li><li><strong>Container Port:</strong> 8080 (the port on which the container listens)</li></ul><p>Ensure that your configurations reflect these specifications to correctly deploy and manage the resources in your Kubernetes cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*MzLYxvwjp7Sq0qPkcQBjfg.png" /><figcaption>Terraform Challange 1</figcaption></figure><h3>Solution Walkthrough</h3><p>Let’s walk through the solution step-by-step, ensuring you have all the details needed to successfully complete this challenge.</p><p>To start, we needed to verify whether Terraform was installed on the control plane. We initially checked for the presence of Terraform by running the command:</p><pre>$ terraform<br>&gt; bash:terraform: command not found</pre><p>The output indicated that Terraform was not installed. To resolve this, we proceeded with the following steps:</p><ol><li><strong>Update the Package List:</strong> Update the package list to ensure we had the latest information on available packages:</li></ol><pre>$ apt update</pre><p>2<strong>. Install Unzip:</strong> Install the unzip utility to extract the Terraform binary:</p><pre>$ apt install unzip -y</pre><p>3. <strong>Download Terraform:</strong> Download the specific version of Terraform (1.1.5) from the HashiCorp release page using curl:</p><pre>$ curl -L -o /tmp/terraform_1.1.5_linux_amd64.zip https://releases.hashicorp.com/terraform/1.1.5/terraform_1.1.5_linux_amd64.zip</pre><p>4. <strong>Extract and Install Terraform:</strong> Unzip the downloaded file and move the Terraform binary to /usr/local/bin, making it available system-wide:</p><pre>$ unzip -d /usr/local/bin /tmp/terraform_1.1.5_linux_amd64.zip</pre><p>5. <strong>Verify Installation:</strong> Confirm the installation by checking the Terraform version:</p><pre>$ terraform -version<br><br>&gt; Terraform v1.1.5<br>on linux_amd64</pre><p>This confirmed that Terraform v1.1.5 was successfully installed.</p><h3>Step 2: Configure Provider Settings</h3><p>To enable Terraform to interact with our Kubernetes cluster, create a provider.tf file in the /root/terraform_challenge directory with the following configuration:</p><pre>terraform {<br>  required_providers {<br>    kubernetes = {<br>      source  = &quot;hashicorp/kubernetes&quot;<br>      version = &quot;2.11.0&quot;<br>    }<br>  }<br>}<br><br>provider &quot;kubernetes&quot; {<br>  config_path = &quot;/root/.kube/config&quot;<br>}</pre><p>This configuration:</p><ul><li><strong>Specifies the Provider:</strong> Use the hashicorp/kubernetes provider with version 2.11.0.</li><li><strong>Configures the Provider:</strong> Set the config_path to point to the kubeconfig file located at /root/.kube/config, which Terraform uses to connect to the Kubernetes cluster.</li></ul><h3>Step 3: Define the Kubernetes Service</h3><p>Next, define a Kubernetes service in the service.tf file:</p><pre>resource &quot;kubernetes_service&quot; &quot;webapp-service&quot; {<br>  metadata {<br>    name = &quot;webapp-service&quot;<br>  }<br><br>  spec {<br>    selector = {<br>      name = kubernetes_deployment.frontend.metadata[0].labels.name<br>    }<br>    port {<br>      port      = 8080<br>      node_port = 30080<br>    }<br>    type = &quot;NodePort&quot;<br>  }<br>}</pre><p>In this configuration:</p><ul><li><strong>Service Name:</strong> The service is named webapp-service.</li><li><strong>Service Type:</strong> Set the service type to NodePort, which allows the service to be accessed externally on a specific port.</li><li><strong>Port Configuration:</strong> The service listens on port 8080 and exposes it on port 30080 on each node.</li><li><strong>Selector:</strong> Use the label selector to match the pods created by the frontend deployment.</li></ul><h3>Step 4: Define the Kubernetes Deployment</h3><p>Create a deployment.tf file to define the Kubernetes deployment:</p><pre>resource &quot;kubernetes_deployment&quot; &quot;frontend&quot; {<br>  metadata {<br>    name = &quot;frontend&quot;<br>    labels = {<br>      name = &quot;webapp&quot;<br>    }<br>  }<br><br>  spec {<br>    replicas = 4<br><br>    selector {<br>      match_labels = {<br>        name = &quot;webapp&quot;<br>      }<br>    }<br><br>    template {<br>      metadata {<br>        labels = {<br>          name = &quot;webapp&quot;<br>        }<br>      }<br><br>      spec {<br>        container {<br>          image = &quot;kodekloud/webapp-color:v1&quot;<br>          name  = &quot;simple-webapp&quot;<br>          port {<br>            container_port = 8080<br>          }<br>        }<br>      }<br>    }<br>  }<br>}</pre><p>In this configuration:</p><ul><li><strong>Deployment Name:</strong> The deployment is named frontend.</li><li><strong>Labels:</strong> The deployment uses labels to categorize its resources.</li><li><strong>Replicas:</strong> Set the deployment to manage 4 replicas to ensure high availability.</li><li><strong>Pod Template:</strong> Each pod created by this deployment will use the kodekloud/webapp-color:v1 image and listen on port 8080.</li></ul><h3>Step 5: Initialize, Validate, and Apply the Configuration</h3><p>With the configurations in place, execute the following Terraform commands:</p><ol><li><strong>Initialize Terraform:</strong> Initialize the Terraform working directory, which downloads the necessary provider plugins and sets up the environment:</li></ol><pre>$ terraform init</pre><p>2. <strong>Validate Configuration:</strong> Validate the configuration files to ensure they are syntactically correct and free of errors:</p><pre>$ terraform validate</pre><p>3. <strong>Plan the Deployment:</strong> Generate an execution plan to review the proposed changes before applying them:</p><pre>$ terraform plan</pre><p>4. <strong>Apply the Configuration:</strong> Apply the configuration to create the Kubernetes deployment and service:</p><pre>$ terraform apply</pre><p>Confirm the deployment by entering yes when prompted to proceed with the actions.</p><p>5. <strong>Verify the Deployment:</strong> After applying the configuration, use kubectl commands to verify the resources:</p><ul><li><strong>List Deployments:</strong> Confirm that the frontend deployment was created with 4 replicas:</li></ul><pre>$ kubectl get deployments.apps</pre><ul><li>Expected Output:</li></ul><pre>NAME       READY   UP-TO-DATE   AVAILABLE   AGE <br>frontend    4/4       4            4       3m28s</pre><ul><li><strong>List Services:</strong> Verify that the webapp-service was created as a NodePort service and was mapped correctly:</li></ul><pre>$ kubectl get service</pre><ul><li>Expected Output:</li></ul><pre>NAME             TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE<br>kubernetes       ClusterIP   10.96.0.1        &lt;none&gt;        443/TCP          35m<br>webapp-service   NodePort    10.101.182.159   &lt;none&gt;        8080:30080/TCP   2m54s</pre><ul><li><strong>List Pods:</strong> Check the status of the pods to ensure they are running as expected:</li></ul><pre>$ kubectl get pods</pre><ul><li>Expected Output:</li></ul><pre>NAME                        READY   STATUS    RESTARTS   AGE<br>frontend-6ff676678c-45pth   1/1     Running   0          4m17s<br>frontend-6ff676678c-4sl92   1/1     Running   0          4m17s<br>frontend-6ff676678c-h8rzr   1/1     Running   0          4m17s<br>frontend-6ff676678c-m2k94   1/1     Running   0          4m17s</pre><p>This comprehensive deployment process confirms that Terraform was successfully used to manage and deploy Kubernetes resources, ensuring that the frontend deployment and webapp-service were created and configured correctly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6325b27ba469" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>