Skip to content
Snippets Groups Projects
Commit 8ae96e19 authored by Jason Plum's avatar Jason Plum
Browse files

Merge branch 'fix-typos' into 'master'

Fix a few typos

See merge request !27
parents 8b93b85a cd1fa2a1
No related branches found
No related tags found
1 merge request!27Fix a few typos
Loading
Loading
@@ -58,11 +58,11 @@ Login to [GCP console](https://console.cloud.google.com) and navigate to Compute
 
You can name this cluster how you see fit, and place it in any *Zone* that you wish. It is suggested that the cluster be made up of at least 3 nodes, and that the *Machine type* include at least 2 vCPU for performance reasons.
 
As you make this cluster, take note of the *Zone* that it is created it, as we will need this for the create of the Static IP inthe next step.
As you make this cluster, take note of the *Zone* that it is created it, as we will need this for the create of the Static IP in the next step.
 
## Reserve a Static IP in GCP
 
Navigate to Compute > [Networking](https://console.cloud.google.com/networking) via the navigation menu, or follow the link directly. Here, we will reserve the Static IP address that the deployed GitLab instance will use for Ingress control. This step is very important because of the requirement for the Domain Name Service to be able to consitently resolve, and allow Let's Encrypt integration across all services.
Navigate to Compute > [Networking](https://console.cloud.google.com/networking) via the navigation menu, or follow the link directly. Here, we will reserve the Static IP address that the deployed GitLab instance will use for Ingress control. This step is very important because of the requirement for the Domain Name Service to be able to consistently resolve, and allow Let's Encrypt integration across all services.
 
Once on the Networking page of GCP, navigate to `External IP addresses`, and use the `+ Reserve Static Address` button. You may supply any name you wish here, as this is not a host name but a descriptor. For this, be sure to the the *Region* to that which includes the *Zone* used when creating the GKE cluster. If you selected `us-central1-b`, your *Region* would be `us-central1`. Once the necessary fields are complete, click `Reserve`.
 
Loading
Loading
@@ -97,7 +97,7 @@ This command will generate YAML file with your GitLab cluster configuration. For
 
## Connect to cluster via `gcloud`
 
To apply the configuration to Kubernetes cluster you first need to configure your kubectl cmdline tool to connect to proper cluster.
To apply the configuration to Kubernetes cluster you first need to configure your kubectl command line tool to connect to proper cluster.
 
Go to following GKE page [Cluster List](https://console.cloud.google.com/kubernetes/list), find your cluster. Click *Connect* button that is just besides your cluster name. From window that will pop up copy the gcloud command that will be shown and execute in your terminal.
This command will configure your local kubernetes command line client.
Loading
Loading
@@ -110,7 +110,7 @@ gcloud container clusters get-credentials <cluster-name> \
 
## Deploy via `kubectl`
 
Once you have everthing configured you can deploy the GitLab to your Kubernetes cluster by invoking following command:
Once you have everything configured you can deploy the GitLab to your Kubernetes cluster by invoking following command:
 
```shell
kubectl apply -f <generated-configuration-filename>
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment