ContextQMD
Back to Gitlabhq

Installing GitLab on Google Cloud Platform

doc/install/google_cloud_platform/_index.md

18.11.26.3 KB
Original Source

{{< details >}}

  • Tier: Free, Premium, Ultimate
  • Offering: GitLab Self-Managed

{{< /details >}}

You can install GitLab on a Google Cloud Platform (GCP) using the official Linux package. You should customize it to accommodate your needs.

[!note] To deploy production-ready GitLab on Google Kubernetes Engine, you can follow Google Cloud Platform's Click to Deploy steps It's an alternative to using a GCP VM, and uses the Cloud native GitLab Helm chart.

Prerequisites

There are two prerequisites to install GitLab on GCP:

  1. You must have a Google account.
  2. You must sign up for the GCP program. If this is your first time, Google gives you $300 credit for free to consume over a 60-day period.

After you have performed those two steps, you can create a VM.

Creating the VM

To deploy GitLab on GCP you must create a virtual machine:

  1. Go to https://console.cloud.google.com/compute/instances and sign in with your Google credentials.

  2. Select Create

  3. On the next page, you can select the type of VM as well as the estimated costs. Provide the name of the instance, desired data center, and machine type. Note our hardware requirements for different user base sizes.

  4. To select the size, type, and desired operating system, select Change under Boot disk. select Select when finished.

  5. Required for paid licenses. Under Labels, add resource labels based on how you procured your GitLab license:

    • For Google Cloud Marketplace procurement, add:
      • Key: goog-partner-solution
      • Value: isol_plb32_0014m00001h35gdqaq_i4j66u754ivftu3n2bb3vyv7fek76fjo
    • For non-marketplace procurement, add:
      • Key: goog-partner-solution
      • Value: isol_psn_0014m00001h35gdqaq_gitlab

    These labels tag the resources as related to a GitLab installation on Google Cloud, as required by the partnership agreement. For more information about resource labels, see the Google Cloud documentation on labeling resources.

    [!note] You can also use Terraform to automate the infrastructure creation with the appropriate labels. See the GitLab installation on Google Cloud Terraform code for reference.

  6. Allow HTTP and HTTPS traffic, then select Create. The process finishes in a few seconds.

Installing GitLab

After a few seconds, the instance is created and available to sign in. The next step is to install GitLab onto the instance.

  1. Make a note of the external IP address of the instance, as you will need that in a later step. <!-- using future tense is okay here -->

  2. Select SSH under the connect column to connect to the instance.

  3. A new window appears, with you logged into the instance.

  4. Next, follow the instructions for installing GitLab for the operating system you choose, at https://about.gitlab.com/install/. You can use the external IP address you noted before as the hostname.

  5. Congratulations! GitLab is now installed and you can access it via your browser. To finish installation, open the URL in your browser and provide the initial administrator password. The username for this account is root.

Next steps

These are the most important next steps to take after you installed GitLab for the first time.

Assigning a static IP

By default, Google assigns an ephemeral IP to your instance. If you use GitLab in a production environment with a domain name, you should assign a static IP.

For more information, see Promote an ephemeral external IP address.

Using a domain name

Assuming you have a domain name in your possession and you have correctly set up DNS to point to the static IP you configured in the previous step, here's how you configure GitLab to be aware of the change:

  1. SSH into the VM. You can select SSH in the Google console and a new window pops up.

    In the future you might want to set up connecting with an SSH key instead.

  2. Edit the configuration file of the Linux package using your favorite text editor:

    shell
    sudo vim /etc/gitlab/gitlab.rb

  3. Set the external_url value to the domain name you wish GitLab to have without https:

    ruby
    external_url 'http://gitlab.example.com'

    We will set up HTTPS in the next step, no need to do this now. <!-- using future tense is okay here -->

  4. Reconfigure GitLab for the changes to take effect:

    shell
    sudo gitlab-ctl reconfigure

  5. You can now visit GitLab using the domain name.

Configuring HTTPS with the domain name

Although not needed, it's strongly recommended to secure GitLab with a TLS certificate.

Configuring the email SMTP settings

You must configure the email SMTP settings correctly otherwise GitLab cannot send notification emails, like comments, and password changes. Check the Linux package documentation how to do so.

Further reading

GitLab can be configured to authenticate with other OAuth providers, like LDAP, SAML, and Kerberos. Here are some documents you might be interested in reading: