Task 4: Jenkins Installation and Configuration

[thirdmadman]

Task 4: Jenkins Installation and Configuration

Objective

In this task, you will install Jenkins CI server on your Kubernetes (K8s) cluster using Helm and configure it to be accessible via an encrypted connection.

Steps

1. Install Helm

   • Follow the instructions to install Helm.
   • Verify your Helm installation by deploying and removing the Nginx chart from Bitnami.

2. Prepare the Cluster

   • Ensure your cluster has a solution for managing persistent volumes (PV) and persistent volume claims (PVC). Refer to the K8s documentation and k3s documentation for more details.
   • Install and configure an ingress controller to serve traffic via HTTPS. Obtain a certificate and private key from services like Letsencrypt or ZeroSSL. If you don't have a domain name, you may use a self-signed certificate (not recommended).

3. Install Jenkins

   • Follow the instructions from the Jenkins documentation to install Jenkins using Helm. Ensure Jenkins is installed in a separate namespace.

4. Verify Jenkins Installation

   • Create a simple freestyle project in Jenkins that writes "Hello world" into the log.

5. Additional Tasks

   • Set up a GitHub Actions (GHA) pipeline to deploy Jenkins.
   • Configure authentication and security settings for Jenkins.

Submission

• Provide a PR with the Helm chart for Jenkins deployment in a new repository.
• Provide the Jenkins URL.
• Ensure that Jenkins is accessible via an encrypted connection.
• Provide a screenshot of the Jenkins freestyle project log showing "Hello world".
• Provide a PR with the GHA pipeline code for Jenkins deployment.
• Document the authentication and security configurations in a README file.

Evaluation Criteria (100 points for covering all criteria)

1. Helm Installation and Verification (10 points)

   • Helm is installed and verified by deploying the Nginx chart.

2. Cluster Requirements (30 points)

   • The cluster has a solution for managing persistent volumes (PV) and persistent volume claims (PVC).
   • An ingress controller is installed and configured to serve traffic via HTTPS.
   • A certificate and private key are configured for TLS.

3. Jenkins Installation (30 points)

   • Jenkins is installed using Helm in a separate namespace.
   • Jenkins is available from the internet via an encrypted connection.

4. Jenkins Configuration (10 points)

   • Jenkins configuration is stored on a persistent volume and is not lost when Jenkins' pod is terminated.

5. Verification (10 points)

   • A simple Jenkins freestyle project is created and runs successfully, writing "Hello world" into the log.

6. Additional Tasks (10 points)

   • GitHub Actions (GHA) Pipeline (5 points)
     • A GHA pipeline is set up to deploy Jenkins.
   • Authentication and Security (5 points)
     • Authentication and security settings are configured for Jenkins.

[thirdmadman]

Evaluation Criteria (100 points for covering all criteria)

1. Helm Installation and Verification (10 points)

   • [x] Helm is installed and verified by deploying the Nginx chart.

2. Cluster Requirements (10 points)

   • [x] The cluster has a solution for managing persistent volumes (PV) and persistent volume claims (PVC).

3. Jenkins Installation (50 points)

   • [x] Jenkins is installed using Helm in a separate namespace.
   • [x] Jenkins is available from the internet.

4. Jenkins Configuration (10 points)

   • [x] Jenkins configuration is stored on a persistent volume and is not lost when Jenkins' pod is terminated.

5. Verification (10 points)

   • [x] A simple Jenkins freestyle project is created and runs successfully, writing "Hello world" into the log.

6. Additional Tasks (10 points)

   • [x] GitHub Actions (GHA) Pipeline (5 points)
     • A GHA pipeline is set up to deploy Jenkins.
   • [x] Authentication and Security (5 points)
     • Authentication and security settings are configured for Jenkins.