Preparing OKE resources for the GitLab chart

For a fully functional GitLab instance, you need a few resources before deploying the GitLab chart to Oracle Container Engine for Kubernetes (OKE). Check how to prepare your Oracle Cloud Infrastructure tenancy before creating the OKE cluster.

Creating the OKE cluster


To provision the Kubernetes cluster manually, follow the OKE instructions. Check the list of compute shapes available for worker nodes supported by OKE.

A cluster with 4 OCPUs and 30GB of RAM is recommended.

External access to GitLab

By default, the GitLab chart deploys an Ingress Controller which creates an Oracle Cloud Infrastructure Public Load Balancer with 100Mbps shape. The Load Balancer service assigns a floating public IP address which doesn’t come from the host subnet.

To change the shape and other configurations (port, SSL, security lists, etc.) during the installation of the chart, you can use the following command line argument nginx-ingress.controller.service.annotations. For example, to specify a Load Balancer with a 400Mbps shape:

--set nginx-ingress.controller.service.annotations."service\.beta\.kubernetes\.io/oci-load-balancer-shape"="400Mbps"

Once deployed, you can check the annotations associated with the Ingress controller service:

$ kubectl get service gitlab-nginx-ingress-controller -o yaml

apiVersion: v1
kind: Service
    ... 400Mbps

Check the OKE Load Balancer documentation for more information.

Next steps

Once you have the cluster up and running, continue with the installation of the chart. Set the DNS domain name via the global.hosts.domain option, but omit the static IP setting via the global.hosts.externalIP option.

After completing the deployment, you can query the Load Balancer’s IP address to associate with the DNS record type:

kubectl get ingress/<RELEASE>-webservice-default -ojsonpath='{.status.loadBalancer.ingress[0].ip}'

<RELEASE> should be substituted with the release name used in helm install <RELEASE>.