If you enable Auto DevOps without setting the base domain and deployment strategy, GitLab can’t deploy your application directly. Therefore, we recommend that you prepare them before enabling Auto DevOps.
Introduced in GitLab 11.0.
When using Auto DevOps to deploy your applications, choose the continuous deployment strategy that works best for your needs:
|Continuous deployment to production||Enables Auto Deploy with the default branch continuously deployed to production.||Continuous deployment to production.|
|Continuous deployment to production using timed incremental rollout||Sets the ||Continuously deploy to production with a 5 minutes delay between rollouts.|
|Automatic deployment to staging, manual deployment to production||Sets ||The default branch is continuously deployed to staging and continuously delivered to production.|
You can choose the deployment method when enabling Auto DevOps or later:
- In GitLab, go to your project’s Settings > CI/CD > Auto DevOps.
- Choose the deployment strategy.
- Select Save changes.
To define the base domain, either:
- In the project, group, or instance level: go to your cluster settings and add it there.
- In the project or group level: add it as an environment variable:
- In the instance level: go to the Admin Area, then Settings > CI/CD > Continuous Integration and Delivery and add it there.
The base domain variable
KUBE_INGRESS_BASE_DOMAIN follows the same order of precedence
as other environment variables.
If you don’t specify the base domain in your projects and groups, Auto DevOps uses the instance-wide Auto DevOps domain.
Auto DevOps requires a wildcard DNS
A record matching the base domains. For
a base domain of
example.com, you’d need a DNS entry like:
*.example.com 3600 A 10.0.2.2
In this case, the deployed applications are served from
is the IP address of your load balancer, generally NGINX (see requirements).
Setting up the DNS record is beyond the scope of this document; check with your
DNS provider for information.
After completing setup, all requests hit the load balancer, which routes requests to the Kubernetes pods running your application.