diff options
Diffstat (limited to 'doc/install/azure/index.md')
| -rw-r--r-- | doc/install/azure/index.md | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/doc/install/azure/index.md b/doc/install/azure/index.md index 9dc30ab2476..15906bc056f 100644 --- a/doc/install/azure/index.md +++ b/doc/install/azure/index.md @@ -1,16 +1,16 @@ --- stage: Enablement group: Distribution -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments description: 'Learn how to spin up a pre-configured GitLab VM on Microsoft Azure.' type: howto --- # Install GitLab on Microsoft Azure -CAUTION: **Deprecated:** -The GitLab image in the Azure Marketplace is deprecated. You can track GitLab's -efforts to [post a new image](https://gitlab.com/gitlab-com/alliances/microsoft/gitlab-tracker/-/issues/2). +WARNING: +This guide is deprecated and pending an update. For the time being, use the GitLab +[image in the Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/gitlabinc1586447921813.gitlabee?tab=Overview). Azure is Microsoft's business cloud and GitLab is a pre-configured offering on the Azure Marketplace. Hopefully, you aren't surprised to hear that Microsoft @@ -74,7 +74,7 @@ The first items we need to configure are the basic settings of the underlying vi 1. Enter a `User name` - e.g. `gitlab-admin` 1. Select an `Authentication type`, either **SSH public key** or **Password**: - NOTE: **Note:** + NOTE: If you're unsure which authentication type to use, select **Password** 1. If you chose **SSH public key** - enter your `SSH public key` into the field provided @@ -86,7 +86,7 @@ The first items we need to configure are the basic settings of the underlying vi 1. Choose the appropriate `Subscription` tier for your Azure account 1. Choose an existing `Resource Group` or create a new one - e.g. **"GitLab-CE-Azure"** - NOTE **Note:** + NOTE: A "Resource group" is a way to group related resources together for easier administration. We chose "GitLab-CE-Azure", but your resource group can have the same name as your VM. @@ -103,7 +103,7 @@ Check the settings you have entered, and then click **"OK"** when you're ready t Next, you need to choose the size of your VM - selecting features such as the number of CPU cores, the amount of RAM, the size of storage (and its speed), etc. -NOTE: **Note:** +NOTE: In common with other cloud vendors, Azure operates a resource/usage pricing model, i.e. the more resources your VM consumes the more it will cost you to run, so make your selection carefully. You'll see that Azure provides an _estimated_ monthly cost beneath each VM Size to help @@ -115,7 +115,7 @@ ahead and select this one, but please choose the size which best meets your own  -NOTE: **Note:** +NOTE: Be aware that while your VM is active (known as "allocated"), it will incur "compute charges" which, ultimately, you will be billed for. So, even if you're using the free trial credits, you'll likely want to learn @@ -142,7 +142,7 @@ new VM. You'll be billed only for the VM itself (e.g. "Standard DS1 v2") because  -NOTE: **Note:** +NOTE: At this stage, you can review and modify the any of the settings you have made during all previous steps, just click on any of the four steps to re-open them. @@ -185,7 +185,7 @@ _(the full domain name of your own VM will be different, of course)_. Click **"Save"** for the changes to take effect. -NOTE **Note:** +NOTE: If you want to use your own domain name, you will need to add a DNS `A` record at your domain registrar which points to the public IP address of your Azure VM. If you do this, you'll need to make sure your VM is configured to use a _static_ public IP address (i.e. not a _dynamic_ one) @@ -202,7 +202,7 @@ Ports are opened by adding _security rules_ to the **"Network security group"** has been assigned to. If you followed the process above, then Azure will have automatically created an NSG named `GitLab-CE-nsg` and assigned the `GitLab-CE` VM to it. -NOTE: **Note:** +NOTE: If you gave your VM a different name then the NSG automatically created by Azure will also have a different name - the name you have your VM, with `-nsg` appended to it. @@ -334,7 +334,7 @@ Under the **"Components"** section, we can see that our VM is currently running GitLab. This is the version of GitLab which was contained in the Azure Marketplace **"GitLab Community Edition"** offering we used to build the VM when we wrote this tutorial. -NOTE **Note:** +NOTE: The version of GitLab in your own VM instance may well be different, but the update process will still be the same. |