Skip to content

Latest commit

 

History

History
78 lines (57 loc) · 5.04 KB

File metadata and controls

78 lines (57 loc) · 5.04 KB

Jenkins to Private Docker Registry to Kubernetes cluster

The template allows you to host an instance of Jenkins on a DS1_v2 size Linux Ubuntu 14.04 LTS VM in Azure China.

It also includes a basic Jenkins pipeline that will checkout a sample git repository with a Dockerfile embedded and it will build and push the Docker container in the provisioned private docker registry you provided, then deploy it to Kubernetes cluster.

A. Deploy a Jenkins VM with an embedded Docker build and publish pipeline

  1. Click the "Deploy to Azure" button. If you don't have an Azure subscription, you can follow instructions to signup for a free trial.
  2. Enter the desired user name and password for the VM that's going to host the Jenkins instance. Also provide a DNS prefix for your VM.
  3. Enter a public git repository. The repository must have a Dockerfile in its root.
  4. Provide a private Docker registry url , login user name and password. (if using the HTTP private registry deployed from this project, the registry url should be http://< DNS or Public IP >:5000)
  5. The Kubernetes master FQDN, user name and private key which is base64 encoded, the pipeline will deploy sample project to this kubernetes cluster. You could use some online tool to do encode.

B. Setup SSH port forwarding

By default the Jenkins instance is using the http protocol and listens on port 8080. Users shouldn't authenticate over unsecured protocols!

You need to setup port forwarding to view the Jenkins UI on your local machine. If you do not know the full DNS name of your instance, go to the Portal and find it in the deployment outputs here: Resource Groups > {Resource Group Name} > Deployments > {Deployment Name, usually 'Microsoft.Template'} > Outputs

If you are using Windows:

Install Putty or use any bash shell for Windows (if using a bash shell, follow the instructions for Linux or Mac).

Run this command:

putty.exe -ssh -L 8080:localhost:8080 <User name>@<Public DNS name of instance you just created>

Or follow these manual steps:

  1. Launch Putty and navigate to 'Connection > SSH > Tunnels'
  2. In the Options controlling SSH port forwarding window, enter 8080 for Source port. Then enter 127.0.0.1:8080 for the Destination. Click Add.
  3. Click Open to establish the connection.

If you are using Linux or Mac:

Run this command:

ssh -L 8080:localhost:8080 <User name>@<Public DNS name of instance you just created>

C. Connect to Jenkins

  1. After you have started your tunnel, navigate to http://localhost:8080/ on your local machine.
  2. Unlock the Jenkins dashboard for the first time with the initial admin password. To get this token, SSH into the VM and run sudo cat /var/lib/jenkins/secrets/initialAdminPassword
  3. Your Jenkins instance is now ready to use! You can access a read-only view by going to http://< Public DNS name of instance you just created >.
  4. Go to http://aka.ms/azjenkinsagents if you want to build/CI from this Jenkins master using Azure VM agents.

Important notes

If you are using unsecured private docker registry for example if your docker registry use http instead of https or your certs are not CA signed. You need to do below command on jenkins master all nodes in kuernetes cluster to make whole pipleline works

sudo touch /etc/docker/daemon.json
sudo vim /etc/docker/daemon.json

then add below entry to configuration:

{"insecure-registries" : [ "139.217.12.139:5000" ]}

then save the changes and run below command to restart docker

sudo service docker restart

Sample applications

The pipeline included in this template is based on the sample application(https://github.com/azure-devops/spin-kub-demo) to do build and deployment. You could use your own application, but the build and deployment scripts in Jenkins may need to be updated accordingly.

Troubleshooting

If the deployment does not succeed, or after succeed the Jenkins UI does not show as expected, please ssh to the jenkinsVM with the admin username and password provided in ARM template. Go to /var/lib/waagent/custom-script/download/0/ to check the stdout and stderr files with all the installation details in them.

Reference GitHub projects

Azure-devops-utils (MIT License)

This repository contains utility scripts to run/configure DevOp systems in Azure.