Commit bbed1b09 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'fix-formatting-eks-docs' into 'master'

Fix EKS formatting

See merge request gitlab-org/gitlab-ce!22781
parents 0df7adef 970ce8d5
...@@ -13,11 +13,13 @@ date: 2018-06-05 ...@@ -13,11 +13,13 @@ date: 2018-06-05
In this tutorial, we will show how easy it is to integrate an [Amazon EKS](https://aws.amazon.com/eks/) cluster with GitLab, and begin deploying applications. In this tutorial, we will show how easy it is to integrate an [Amazon EKS](https://aws.amazon.com/eks/) cluster with GitLab, and begin deploying applications.
For an end-to-end walkthrough we will: For an end-to-end walkthrough we will:
1. Start with a new project based on the sample Ruby on Rails template 1. Start with a new project based on the sample Ruby on Rails template
1. Integrate an EKS cluster 1. Integrate an EKS cluster
1. Utilize [Auto DevOps](../../../../topics/autodevops/) to build, test, and deploy our application 1. Utilize [Auto DevOps](../../../../topics/autodevops/) to build, test, and deploy our application
You will need: You will need:
1. An account on GitLab, like [GitLab.com](https://gitlab.com) 1. An account on GitLab, like [GitLab.com](https://gitlab.com)
1. An Amazon EKS cluster 1. An Amazon EKS cluster
1. `kubectl` [installed and configured for access to the EKS cluster](https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html#get-started-kubectl) 1. `kubectl` [installed and configured for access to the EKS cluster](https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html#get-started-kubectl)
...@@ -49,11 +51,12 @@ A few details from the EKS cluster will be required to connect it to GitLab. ...@@ -49,11 +51,12 @@ A few details from the EKS cluster will be required to connect it to GitLab.
1. The API server endpoint is also required, so GitLab can connect to the cluster. This is displayed on the AWS EKS console, when viewing the EKS cluster details. 1. The API server endpoint is also required, so GitLab can connect to the cluster. This is displayed on the AWS EKS console, when viewing the EKS cluster details.
You now have all the information needed to connect the EKS cluster: You now have all the information needed to connect the EKS cluster:
* Kubernetes cluster name: Provide a name for the cluster to identify it within GitLab. * Kubernetes cluster name: Provide a name for the cluster to identify it within GitLab.
* Environment scope: Leave this as `*` for now, since we are only connecting a single cluster. * Environment scope: Leave this as `*` for now, since we are only connecting a single cluster.
* API URL: Paste in the API server endpoint retrieved above. * API URL: Paste in the API server endpoint retrieved above.
* CA Certificate: Paste the certificate data from the earlier step, as-is. * CA Certificate: Paste the certificate data from the earlier step, as-is.
* Paste the token value. Note on some versions of Kubernetes a trailing `%` is output, do not include it. * Paste the token value.
* Project namespace: This can be left blank to accept the default namespace, based on the project name. * Project namespace: This can be left blank to accept the default namespace, based on the project name.
![Add Cluster](img/add_cluster.png) ![Add Cluster](img/add_cluster.png)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment