These are the example files for my presentation about GitLab + Kubernetes for Continuous Integration and Delivery. They are also partly used in my GitLab CI posts.
INFO This is one of the ways to deploy an application as a Docker image to your K8s cluster. It is important to note that this repository is just an example of what can be done.
The presentation can be found here: Kubernetes - WYNTK - GitLab CI + Kubernetes Presentation. The blog post these files are specifically used in is here: GitLab + Kubernetes: Using GitLab CI's Kubernetes Cluster feature and old post GitLab + Kubernetes: Perfect Match for Continuous Delivery with Container.
An uptodate list of all my blog posts around GitLab and Kubernetes can be found on this page. This list is just an excerpt of some of my GitLab posts:
This repository shows off/uses the following GitLab CI features:
Other features also shown are:
The following points are required for this repository to work correctly:
>= 13.x) with the following features configured:
cluster-admin) ClusterRole, see Kubernetes.io Using RBAC Authorization - User-facing Roles.
Best is to follow the blog post GitLab + Kubernetes: Using GitLab CI's Kubernetes Cluster feature as it contains more detailed instructions about using GitLab CI for Kubernetes.
You have to replace the following addresses in all files:
gitlab.zerbytes.netwith your GitLab address (e.g.
edenmal.net(in the Ingress manifest) with your domain name.
presentation-gitlab-k8swith the Namespace name of your choice.
If you are using prometheus-operator/prometheus-operator, then you also need to replace
zerbytes-live-proj-monitoring with the Namespace your Prometheus instance is running in,
in this file
You then also want to
kubectl create/apply the file to your Kubernetes cluster during creation/apply process for the manifests in
You also need to create a "Docker Login" Secret which contains your GitLab Registry access data (e.g. Username and Access token with registry access) named whatever your want in the Namespace
A guide for that can be found here: Kubernetes.io - Pull an Image from a Private Registry.
Instead of using the
imagePullSecrets, we'll be using the
ServiceAccount in the Namespace to automatically use the created Docker login
Secret, see Kubernetes - Configure Service Accounts for Pods - Add ImagePullSecrets to a service account.
The Namespace manifest is in the
Then you can just import the repository into your GitLab instance and are ready to go.
For information on how to use these files and setup GitLab Kubernetes cluster/integration, see the above blog post and in specific this post GitLab + Kubernetes: Perfect Match for Continuous Delivery with Container.
As of GitLab
10.3 the Kubernetes Integration is marked as deprecated and with
10.4 it is now disabled, the following docs show the new feature called Clusters:
service-monitor.yaml- Contains a prometheus-operator/prometheus-operator ServiceMonitor manifest to automatically monitor the application(s).
namespace.yaml- Namespace in which the GitLab CI will deploy the application.
rbac.yaml- Contains GitLab CI RBAC Role, RoleBinding and ServiceAccount.
secret.yaml- Contains a TLS wildcard certificate for the application Ingress.
Dockerfile- Contains the Docker image build instructions.
.gitlab-ci.yml- Contains the GitLab CI instructions.
manifests/- Kubernetes manifests used to deploy the Docker image built in the CI pipeline.
Thanks to @shadycuz - GitHub for his comments with improvements for the code in this repository!
The files in this repo can be used under the MIT license, see LICENSE file.