Deploy to a Kubernetes cluster with cluster certificates (deprecated) (FREE)
Deprecated in GitLab 14.5.
A Kubernetes cluster can be the destination for a deployment job. If
- The cluster is integrated with GitLab, special
deployment variables are made available to your job
and configuration is not required. You can immediately begin interacting with
the cluster from your jobs using tools such as
- You don't use the GitLab cluster integration, you can still deploy to your cluster. However, you must configure Kubernetes tools yourself using CI/CD variables before you can interact with the cluster from your jobs.
Using Kubernetes 1.18+:
kubectl create secret docker-registry gitlab-registry --docker-server="$CI_REGISTRY" --docker-username="$CI_DEPLOY_USER" --docker-password="$CI_DEPLOY_PASSWORD" --docker-email="$GITLAB_USER_EMAIL" -o yaml --dry-run=client | kubectl apply -f -
Using Kubernetes <1.18:
kubectl create secret docker-registry gitlab-registry --docker-server="$CI_REGISTRY" --docker-username="$CI_DEPLOY_USER" --docker-password="$CI_DEPLOY_PASSWORD" --docker-email="$GITLAB_USER_EMAIL" -o yaml --dry-run | kubectl apply -f -
||Equal to the API URL.|
||The Kubernetes token of the environment service account. Prior to GitLab 11.5,
||The namespace associated with the project's deployment service account. In the format
||Path to a file containing PEM data. Only present if a custom CA bundle was specified.|
||(deprecated) Raw PEM data. Only if a custom CA bundle was specified.|
||Path to a file containing
||From GitLab 11.8, this variable can be used to set a domain per cluster. See cluster domains for more information.|
The Kubernetes integration provides a
KUBECONFIG with an auto-generated namespace
to deployment jobs. It defaults to using project-environment specific namespaces
of the form
<prefix> is of the form
<project_name>-<project_id>. For more information, see Deployment variables.
You can customize the deployment namespace in a few ways:
- You can choose between a namespace per environment or a namespace per project. A namespace per environment is the default and recommended setting, as it prevents the mixing of resources between production and non-production environments.
- When using a project-level cluster, you can additionally customize the namespace prefix.
When using namespace-per-environment, the deployment namespace is
<prefix>-<environment>, but otherwise just
- For non-managed clusters, the auto-generated namespace is set in the
KUBECONFIG, but the user is responsible for ensuring its existence. You can fully customize this value using
When you customize the namespace, existing environments remain linked to their current namespaces until you clear the cluster cache.
By default, anyone who can create a deployment job can access any CI/CD variable in
an environment's deployment job. This includes
KUBECONFIG, which gives access to
any secret available to the associated service account in your cluster.
To keep your production credentials safe, consider using
combined with one of the following:
- A GitLab-managed cluster and namespace per environment.
- An environment-scoped cluster per protected environment. The same cluster can be added multiple times with multiple restricted service accounts.
Web terminals for Kubernetes clusters
Introduced in GitLab 8.15.
The Kubernetes integration adds web terminal
support to your environments. This is based
exec functionality found in Docker and Kubernetes, so you get a new
shell session in your existing containers. To use this integration, you
should deploy to Kubernetes using the deployment variables above, ensuring any
deployments, replica sets, and pods are annotated with:
$CI_PROJECT_PATH_SLUG are the values of
the CI/CD variables.
You must be the project owner or have
maintainer permissions to use terminals.
Support is limited to the first container in the first pod of your environment.
Before the deployment jobs starts, GitLab creates the following specifically for the deployment job:
- A namespace.
- A service account.
However, sometimes GitLab cannot create them. In such instances, your job can fail with the message:
This job failed because the necessary resources were not successfully created.
To find the cause of this error when creating a namespace and service account, check the logs.
Reasons for failure include:
- The token you gave GitLab does not have
cluster-adminprivileges required by GitLab.
KUBE_TOKENdeployment variables. To be passed to your job, they must have a matching
environment:name. If your job has no
environment:nameset, the Kubernetes credentials are not passed to it.
NOTE: Project-level clusters upgraded from GitLab 12.0 or older may be configured in a way that causes this error. Ensure you clear the GitLab-managed cluster option if you want to manage namespaces and service accounts yourself.