This project is an example of a complete CI/CD pipeline of a simple static web application from sources to deployed Kubernetes pods.
This project uses Artifactory as its Docker registry. You can get a free trial and try it out!
Follow the documentation for setting up your Docker registry.
This project uses Artifactory as its Helm repository. You can get a free trial and try it out!
Follow the documentation for setting up your Helm repository.
Setup a Jenkins running with
- Docker. Can build and push images
- Kubectl. Kubernetes CLI that will link Jenkins with the Kubernetes cluster
- Helm. Kubernetes package manager to simplify deployment of your Docker containers to Kubernetes
There is a GitHub example of such a Docker image, to be used in Kubernetes.
Jenkins running in Kubernetes can be found in this GitHub example.
- This project is used to build a Jenkins master that has the required tools (
docker
,kubectl
andhelm
) already installed - You can deploy this Jenkins to Kubernetes using the helm chart in the same repository
- Notice that this is an example, and should not be used for production
- The Jenkins pipeline example (Jenkinsfile) is using calls to external cli tools such as
docker
,kubectl
,curl
and other shell commands. Some of these can be replaced with groovy code and functions or built in pipeline steps, but are implemented like this to demonstrate the simple use of these tools. - The
kubectl
andhelm
clients are not configured in this example. It's assumed the Jenkins instance is pre-configured, or run it in your Kubernetes cluster, where it picks up the local pod credentials to access the Kubernetes API.
You can build the web application directly by running build.sh
. You can create the Docker image and run it locally. See the build.sh options.
# See options
$ ./build.sh --help
You can also pack and push the Docker image and Helm chart.