Skip to content

Latest commit

 

History

History
214 lines (136 loc) · 7.02 KB

jenkins.md

File metadata and controls

214 lines (136 loc) · 7.02 KB
Raw

Create Cluster using kubeadm script

In this POC we need 1 master and 2 worker machine and jenkins machine separately

Controlplane
sudo -i

bash <(curl -s https://raw.githubusercontent.com/killer-sh/cks-course-environment/master/cluster-setup/latest/install_master.sh)

Worker-node
sudo -i

bash <(curl -s https://raw.githubusercontent.com/killer-sh/cks-course-environment/master/cluster-setup/latest/install_worker.sh)

once done take joined command from Controlplane and paste on worker node





### How to deploy Jenkins with Our custom domain and ssl ###

For install jenkins we need to follow below shell script i am using ubuntu 20.04 this script also work for ubuntu 22.04

vi jenkins.sh

#! /bin/bash

sudo apt update
sudo apt install openjdk-11-jre -y
curl -fsSL https://pkg.jenkins.io/debian-stable/jenkins.io-2023.key | sudo tee \
  /usr/share/keyrings/jenkins-keyring.asc > /dev/null
echo deb [signed-by=/usr/share/keyrings/jenkins-keyring.asc] \
  https://pkg.jenkins.io/debian-stable binary/ | sudo tee \
  /etc/apt/sources.list.d/jenkins.list > /dev/null

sudo apt-get update
sudo apt install -y maven
sudo apt-get install jenkins -y
sudo systemctl enable jenkins
sudo systemctl start jenkins
sudo systemctl status jenkins

Run script using this command

sh jenkins.sh

After that we need to check using jenkins using ec2 instance id for example:- 34.203.34.186:8080 for checking purpose but our end goal its should not be run on this after configuring nginx reverse proxy will be remove port 8080 from ec2 instnace security group and check

step-by-step guide to configure SSL on Jenkins using Let's Encrypt and NGINX reverse proxy

  1. Install NGINX on your server if it's not already installed. You can do this by running the following command:
sudo apt-get update

sudo apt-get install nginx

2. Create a new server block configuration file for Jenkins. You can do this by creating a new file in the /etc/nginx/sites-available/ directory. For example:

vi /etc/nginx/sites-available/jenkins

3. Add the following content to the file:

server {
    listen 80;
    server_name jenkins.example.com;

    location / {
        proxy_pass http://localhost:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;        
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Note: Replace jenkins.example.com with your Jenkins domain name.
  1. Create a symbolic link to the server block configuration file in the /etc/nginx/sites-enabled/ directory:
sudo ln -s /etc/nginx/sites-available/jenkins /etc/nginx/sites-enabled/

5. Test the NGINX configuration and restart the NGINX service:

sudo nginx -t
sudo systemctl restart nginx

6. Install Certbot, the Let's Encrypt client, by running the following commands:

sudo apt-get update

sudo apt-get install certbot python3-certbot-nginx

7. Obtain an SSL certificate for your Jenkins domain name using Certbot:

sudo certbot --nginx -d jenkins.example.com

Note: Replace jenkins.example.com with your Jenkins domain name.

Follow the prompts to provide your email address and agree to the Let's Encrypt terms of service.

Choose whether or not to redirect all HTTP traffic to HTTPS. This is recommended for security purposes.

Test your SSL configuration by visiting your Jenkins domain name using HTTPS.

That's it! You have successfully configured SSL on Jenkins using Let's Encrypt and NGINX reverse proxy.

### for jenkins run behind vpn need to configure like this ###
vi /etc/nginx/sites-available/jenkins

server {
    server_name jenkins.cloudworld.fun;

    location / {
        allow 54.226.177.182; #allow pritunl ip here
        deny all; # add this property as well
        proxy_pass http://localhost:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;        
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/jenkinsdev.techmobi.site/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/jenkinsdev.techmobi.site/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}

server {
    if ($host = jenkins.cloudworld.fun) {
        return 301 https://$host$request_uri;
    } # managed by Certbot
  

    listen 80;
    server_name jenkins.cloudworld.fun;
    return 404; # managed by Certbot

}

#### Docker Install on jenkins machine ###
sudo apt install docker.io -y
sudo chown jenkins:docker /var/run/docker.sock ----need to provide owenership  from root to jenkins user as the jenkins user has permission

#### Helm Install on Jenkins Machine and Master #####
curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
chmod 700 get_helm.sh
./get_helm.sh

#### Jenkins Plugins and creds configuration ###
In Jenkins we need to install this 2 plugins
1.docker :- all respective docker plugins
2. kubernetes:- all respective kubernetes plugins

Creds which we need to configure in jenkins
1. docker :- use dockerhub username and password as API token
2. Kubernetes:- need kubeconfig file from master node steps to take config file from master node

Note:- config file is in root so we need to copy from root to /home/ubuntu and also change permission

root@controlplane:~/.kube# ls
cache  config
root@controlplane:~/.kube# cp config /home/ubuntu/

ubuntu@controlplane:~$ ls -ltrh config
-rw------- 1 root root 5.6K Nov  3 13:09 config

as checking here permission is with root need to change with ubuntu user because we need to scp this file from server to local

ubuntu@controlplane:~$ sudo chown ubuntu:ubuntu config
ubuntu@controlplane:~$ ls -ltrh config
-rw------- 1 ubuntu ubuntu 5.6K Nov  3 13:09 config

exit from the server
ubuntu@controlplane:~$ exit
logout
Connection to 23.20.188.108 closed.

now fire this command

Admin@MINGW64 ~/Downloads
$ scp -i cicd.pem [email protected]:/home/ubuntu/config .

and check the file in local


### How to Set Up the Jenkins + GitHub Integration ###

Configuring GitHub
Step 1: go to your GitHub repository and click on ‘Settings’.
Step 2: Click on Webhooks and then click on ‘Add webhook’.
Step 3: In the ‘Payload URL’ field, paste your Jenkins environment URL. At the end of this URL add /github-webhook/. In the ‘Content type’ select: ‘application/json’ and leave the ‘Secret’ field empty.
Ex:-http://54.211.236.223:8080/github-webhook/
https://jenkins.cloudworld.fun//github-webhook/

Step 4: In the page ‘Which events would you like to trigger this webhook?’ choose ‘Let me select individual events.’ Then, check ‘Pull Requests’ and ‘Pushes’. At the end of this option, make sure that the ‘Active’ option is checked and click on ‘Add webhook’.

Now try to do modifications in code and push it to github and see pipeline is trigger automatically or not