DEV Community: Prajwal Patil

"Streamlining CI/CD: A Step-by-Step Guide to Setting Up Jenkins on Docker"

Prajwal Patil — Sun, 26 May 2024 10:00:49 +0000

How to Set Up Jenkins on Docker
Introduction
Jenkins is a widely-used open-source automation server that helps automate the non-human part of the software development process. Docker, on the other hand, is a platform that enables developers to create, deploy, and run applications in containers. Combining Jenkins with Docker provides a powerful tool for continuous integration and continuous delivery (CI/CD).
In this guide, we'll walk through the steps to set up Jenkins on Docker.
Prerequisites

Docker installed on your system.
Basic understanding of Docker and Jenkins.
Sufficient privileges to run Docker commands.

Setting up Jenkins on Docker offers several advantages that can streamline and enhance your CI/CD workflow. Here are the key reasons why you might choose to deploy Jenkins using Docker:
1. Consistency and Isolation
Consistency: Docker containers ensure that Jenkins runs in a consistent environment across different development, testing, and production environments. This consistency helps eliminate issues caused by variations in software configurations.
Isolation: Docker containers isolate Jenkins and its dependencies from other applications on the host system. This isolation helps prevent conflicts and makes it easier to manage dependencies.
2. Simplified Setup and Configuration
Ease of Setup: Docker simplifies the setup process by allowing you to pull and run pre-configured Jenkins images. This reduces the complexity involved in manually installing Jenkins and configuring its environment.
Configuration Management: Docker makes it easy to version and manage configurations through Dockerfiles and Docker Compose, ensuring that your Jenkins setup can be easily replicated or modified.
3. Portability
Docker containers can run on any system that supports Docker, making your Jenkins setup highly portable. This portability is particularly useful for developers working in different environments or for teams that need to move their CI/CD pipeline across various stages of development and production.
4. Scalability
Resource Allocation: Docker allows you to allocate specific resources (CPU, memory) to Jenkins containers, ensuring that Jenkins performs optimally without affecting other applications.
Scaling: Running Jenkins in Docker containers makes it easier to scale your CI/CD infrastructure. You can quickly spin up additional Jenkins instances to handle increased workloads or parallelize build processes.
5. Simplified Maintenance and Upgrades
Upgrades: Upgrading Jenkins is straightforward with Docker. You can pull the latest Jenkins image and recreate the container without worrying about breaking the underlying system.
Backup and Recovery: Docker volumes can be used to persist Jenkins data, making it easier to backup and restore configurations, jobs, and build history.
6. Security
Sandboxing: Docker containers provide an additional layer of security by sandboxing Jenkins from the host system. This reduces the risk of potential vulnerabilities in Jenkins affecting the host.
Controlled Access: Docker's networking and permission features allow for fine-grained control over how Jenkins interacts with other services and the network.
7. DevOps Integration
Docker is a staple in modern DevOps practices. Running Jenkins on Docker integrates seamlessly with other containerized services and tools in your DevOps pipeline, promoting a more cohesive and efficient workflow.
Step-by-Step Guide
Step 1: Install Docker
Before setting up Jenkins, ensure Docker is installed on your machine.
For Ubuntu:

sudo apt update
sudo apt install -y docker.io
sudo systemctl start docker
sudo systemctl enable docker

Step 2: Pull the Jenkins Docker Image
Jenkins maintains an official Docker image. To pull the latest Jenkins image, run:

docker pull jenkins/jenkins:lts

The lts tag refers to the Long Term Support version, which is stable and recommended for most users.

Step 3: Run the Jenkins Container
Create and start a Jenkins container with the following command:

docker run -d -p 8080:8080 jenkins/jenkins:lts

Here's a breakdown of the command:
-d: Run the container in detached mode.
-p 8080:8080: Map port 8080 of the host to port 8080 of the container (Jenkins web int)

Step 4: Access Jenkins
Once the container is running, you can access Jenkins by navigating to http://localhost:8080 in your web browser.

Step 5: Unlock Jenkins
On your first visit, Jenkins will ask you to unlock it using a password stored in the Docker container. Retrieve this password with:

docker exec -it jenkins bash
cat /var/jenkins_home/secrets/initialAdminPassword

Copy the password and paste it into the Jenkins unlock page.

Step 6: Install Suggested Plugins
After unlocking Jenkins, you'll be prompted to install plugins. Choose the "Install suggested plugins" option to get started quickly.

Step 7: Create an Admin User
Next, you'll need to create an admin user. Fill in the required details and complete the setup.

Step 8: Configure Jenkins

Now that Jenkins is set up, you can start configuring it to suit your project needs. This includes setting up:
Global Tool Configuration: Define the locations for JDK, Git, Gradle, etc.
Credentials: Add necessary credentials for accessing repositories and other tools.
Jobs/Pipelines: Create jobs or pipelines for your CI/CD process.

Conclusion
Deploying Jenkins on Docker simplifies the setup and management of your CI/CD pipeline. Docker containers provide a consistent environment for Jenkins, enhancing the reliability and scalability of your build process.
By following the steps outlined in this guide, you will have a fully functional Jenkins server running in a Docker container. This setup allows you to explore and leverage Jenkins' extensive range of plugins and configurations to further optimize your CI/CD workflow.

“Automating VPC Peering in AWS with Terraform”

Prajwal Patil — Thu, 09 May 2024 05:53:33 +0000

Introduction:
In today’s cloud-centric world, networking infrastructure plays a crucial role in ensuring the connectivity and security of applications and services. One common networking pattern is VPC peering, which allows different Virtual Private Clouds (VPCs) to communicate with each other securely. In this blog post, we’ll explore how to automate the setup of VPC peering using Terraform, a popular Infrastructure as Code (IaC) tool. By leveraging Terraforms declarative syntax and AWS provider, we can simplify the process of configuring VPC peering connections, saving time and reducing the chance of human error.

Main Content:

Understanding VPC Peering: We’ll start by discussing the concept of VPC peering and its significance in cloud networking. This section will cover the benefits of VPC peering, such as improved connectivity between VPCs and reduced data transfer costs.
Setting Up the Terraform Environment: Next, we’ll guide readers through the setup of a Terraform environment for managing AWS resources. This includes installing Terraform, configuring AWS credentials, and initializing a Terraform project.
Defining VPCs and Internet Gateways: In this section, we’ll use Terraform to define two VPCs and create internet gateways for each VPC. These components are essential prerequisites for establishing VPC peering connections.
Creating VPC Peering Connections: Using Terraforms AWS provider, we’ll programmatically create VPC peering connections between the two VPCs defined earlier. We’ll specify the necessary parameters such as VPC IDs and enable auto-acceptance of peering requests.
Verifying the Peering Connection: After deploying the Terraform configuration, we’ll demonstrate how to verify the status of the VPC peering connection using the AWS Management Console or CLI. This step ensures that the peering connection is successfully established and ready for use.

Launch instance

Install Terraform

#! /bin/bash
wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list

sudo apt update
sudo apt install terraform -y

Install Git

sudo apt update
sudo apt install git

Install awscli

#! /bin/bash
curl "https://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install

Cloning the repo

git clone https://github.com/Prajwal2023/vpc-peering.git

Now hit the terraform init command
“terraform init” is a command used to initialize a Terraform working directory. When you run this command, Terraform reads the configuration files in the directory and downloads any required plugins or modules specified in those files. This command prepares the directory for Terraform operations such as planning, applying, or destroying infrastructure resources. It ensures that the necessary dependencies are available for managing your infrastructure with Terraform.

Now terraform plan
“terraform plan” is a command used to create an execution plan. When you run this command, Terraform compares the current state of your infrastructure with the desired state defined in your Terraform configuration files. It then generates an execution plan that outlines what actions Terraform will take to achieve the desired state. The plan includes information about which resources will be created, modified, or destroyed. Running “terraform plan” allows you to preview the changes that Terraform will make to your infrastructure before actually applying them. This helps you verify that the planned changes are as expected and provides an opportunity to review and confirm them before proceeding.

terraform validate
“terraform validate” checks Terraform configuration files for errors, ensuring correct syntax and structure.

terraform apply
“terraform apply” is a command used in Terraform to apply the changes described in your Terraform configuration files to your infrastructure. When you run this command, Terraform reads the configuration files, creates an execution plan, and then executes that plan to provision, update, or delete the resources specified in the configuration. This command is typically used after running “terraform plan” to review the proposed changes and before making any modifications to your infrastructure.

terraform destroy
The “terraform destroy” command is used to destroy all the resources defined in your Terraform configuration. It deletes all the resources that Terraform manages, effectively tearing down your infrastructure. Use this command with caution as it cannot be undone and may result in the permanent loss of data or resources. Always verify the resources that will be destroyed before executing this command.

Conclusion:
Automating the setup of VPC peering connections with Terraform streamlines the process of configuring cloud networking infrastructure. By codifying infrastructure configurations, teams can easily replicate and manage VPC peering across different environments with consistency and reliability. As organizations embrace cloud-native architectures, Terraform serves as a valuable tool for simplifying complex networking tasks and accelerating the adoption of cloud technologies.

Connect on LinkedIn https://www.linkedin.com/in/prajwal-patil-334002296/

“Implementing AWS Recycle Bin Service for Enhanced Data Recovery”

Prajwal Patil — Tue, 07 May 2024 18:52:52 +0000

Introduction:
In the fast-paced world of cloud computing, data loss can have significant consequences for businesses. Accidental deletions or unexpected failures can lead to critical data loss, resulting in downtime and potential financial losses. To mitigate these risks, AWS offers a powerful solution known as the Recycle Bin Service, which provides enhanced data recovery capabilities for AWS resources like Elastic Block Store (EBS) volumes.

Implementation Steps:

launch Instance

EBS Information

AWS Elastic Block Store (EBS) is a scalable block storage service provided by Amazon Web Services (AWS), offering persistent storage volumes for EC2 instances. Key features include block storage, data persistence, elasticity, snapshots, encryption, and high availability, making it ideal for various storage needs in the cloud.

Taking Snapshot

An AWS EBS snapshot is a point-in-time backup of an EBS volume stored in Amazon S3. It captures all the data on the volume at the time the snapshot is taken, including the data that is in use and any data that is pending writes. Snapshots are incremental, meaning that only the blocks on the volume that have changed since the last snapshot are saved, which reduces storage costs and improves efficiency. EBS snapshots are commonly used for data backup, disaster recovery, and creating new volumes from existing data.

Create Snapshot

Recycle bin

The “Recycle Bin” service, in the context of AWS, is a concept often used to describe a safety mechanism for storing and recovering deleted resources. While AWS doesn’t offer a specific service named “Recycle Bin,” users can implement similar functionality using AWS services like AWS Lambda and Amazon S3.

In this setup, when a resource is deleted, it is not immediately permanently removed. Instead, it is moved to a designated storage area, often called a “Recycle Bin” or “Trash,” where it can be retained for a certain period before final deletion. This provides a safety net, allowing users to recover accidentally deleted resources without having to resort to complex backup and recovery processes.

By leveraging AWS Lambda functions and S3 event notifications, users can automate the process of moving deleted resources to the Recycle Bin and implement policies for retention and permanent deletion, thereby enhancing the overall data protection and management strategy within their AWS environment.

Create retention rule

retention setting

Rule lock settings

Rule created

Now deleted the snapshot

Deleted

Open the recycle bin

Click on the snapshot present in recycle bin

Recovered

Snapshot recovered successfully

Conclusion:
The AWS Recycle Bin Service provides a robust mechanism for protecting critical data and simplifying data recovery processes in AWS environments. By implementing this service and following best practices, businesses can minimize the impact of data loss incidents and ensure continuous operations in the cloud. With its automated recovery workflow and comprehensive features, the Recycle Bin Service is a valuable tool for modern cloud-native architectures.