This is a step-by-step guide to deploying a project hosted on GitLab.com to Google Cloud, using Auto Deploy.
This is a step-by-step guide to deploying a project hosted on GitLab.com to Google Cloud, using Auto Deploy.
...
@@ -47,11 +43,7 @@ You need to copy-paste the ca.crt and token into your project on GitLab.com in t
...
@@ -47,11 +43,7 @@ You need to copy-paste the ca.crt and token into your project on GitLab.com in t
For API URL, you should use the `Endpoint` IP from your cluster page on Google Cloud Platform.
For API URL, you should use the `Endpoint` IP from your cluster page on Google Cloud Platform.
<<<<<<< HEAD
## Expose application to the world
=======
## Expose the application to the internet
## Expose the application to the internet
>>>>>>> upstream/master
In order to be able to visit your application, you need to install an NGINX ingress controller and point your domain name to its external IP address.
In order to be able to visit your application, you need to install an NGINX ingress controller and point your domain name to its external IP address.
...
@@ -75,11 +67,7 @@ Find out the external IP address of the `ruby-app-nginx-ingress-controller` by r
...
@@ -75,11 +67,7 @@ Find out the external IP address of the `ruby-app-nginx-ingress-controller` by r
kubectl get svc ruby-app-nginx-ingress-controller -ojsonpath='{.status.loadBalancer.ingress[0].ip}'
kubectl get svc ruby-app-nginx-ingress-controller -ojsonpath='{.status.loadBalancer.ingress[0].ip}'
```
```
<<<<<<< HEAD
Use this IP address to configure your DNS. This part heavily depends on your preferences and domain provider. But in case you are not sure, just create an A record with a wildcard host like `*.<your-domain>`.
=======
Use this IP address to configure your DNS. This part heavily depends on your preferences and domain provider. But in case you are not sure, just create an A record with a wildcard host like `*.<your-domain>` pointing to the external IP address you found above.
Use this IP address to configure your DNS. This part heavily depends on your preferences and domain provider. But in case you are not sure, just create an A record with a wildcard host like `*.<your-domain>` pointing to the external IP address you found above.
>>>>>>> upstream/master
Use `nslookup minimal-ruby-app-staging.<yourdomain>` to confirm that domain is assigned to the cluster IP.
Use `nslookup minimal-ruby-app-staging.<yourdomain>` to confirm that domain is assigned to the cluster IP.
...
@@ -89,13 +77,6 @@ Visit the home page of your GitLab.com project and press "Set up Auto Deploy" bu
...
@@ -89,13 +77,6 @@ Visit the home page of your GitLab.com project and press "Set up Auto Deploy" bu
<<<<<<< HEAD
You will be redirected to the New file page where you can apply one of the Auto Deploy templates. Select "Kubernetes" to apply the template, then in the file, replace "domain.example.com" with your domain name and any other adjustments you feel comfortable with.
Change the target branch to `master`, and submit your changes. This should create a new pipeline with several jobs. If you made only the domain name change, the pipeline will have 3 jobs: `build`, `staging` and `production`. The `build` job will create a docker image with your new change and push it to the GitLab Container Registry. The `staging` job will deploy this image on your cluster. Once the deploy job succeeds you should be able to see your application by visiting the Kubernetes dashboard. Select the namespace of your project, which will look like `ruby-autodeploy-23`, but with a unique ID for your project, and your app will be listed as “staging” under the Deployment tab.
=======
You will be redirected to the "New file" page where you can apply one of the Auto Deploy templates. Select "Kubernetes" to apply the template, then in the file, replace `domain.example.com` with your domain name and make any other adjustments you need.
You will be redirected to the "New file" page where you can apply one of the Auto Deploy templates. Select "Kubernetes" to apply the template, then in the file, replace `domain.example.com` with your domain name and make any other adjustments you need.
[ee-28]:https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/28"Merge Request for adding issues template"
[ee-7478ece]:https://gitlab.com/gitlab-org/gitlab-ee/commit/7478ece8b48e80782b5465b96c79f85cc91d391b"Commit that introduced merge requests templates"
[products]: https://about.gitlab.com/products/
=======
## Description template example
## Description template example
We make use of Description Templates for Issues and Merge Requests within the GitLab Community Edition project. Please refer to the [`.gitlab` folder][gitlab-ce-templates] for some examples.
We make use of Description Templates for Issues and Merge Requests within the GitLab Community Edition project. Please refer to the [`.gitlab` folder][gitlab-ce-templates] for some examples.
