Commit 4a37ff32 authored by GitLab Bot's avatar GitLab Bot

Automatic merge of gitlab-org/gitlab-ce master

parents 396e3fe7 07e079e8
...@@ -44,12 +44,10 @@ user 0m0.025s ...@@ -44,12 +44,10 @@ user 0m0.025s
sys 0m0.091s sys 0m0.091s
``` ```
From experience with multiple customers, the following are ranges that indicate From experience with multiple customers, this task should take under 10
whether your filesystem performance is satisfactory or less than ideal: seconds to indicate good filesystem performance.
| Rating | Benchmark result | NOTE: **Note:**
|:----------|:------------------------| This test is naive and only evaluates write performance. It's possible to
| Best | Less than 10 seconds | receive good results on this test but still have poor performance due to read
| OK | 10-18 seconds | speed and various other factors.
| Poor | 18-25 seconds | \ No newline at end of file
| Very poor | Greater than 25 seconds |
...@@ -49,7 +49,7 @@ A few details from the EKS cluster will be required to connect it to GitLab: ...@@ -49,7 +49,7 @@ A few details from the EKS cluster will be required to connect it to GitLab:
- Get the certificate with: - Get the certificate with:
```sh ```sh
kubectl get secret <secret name> -o jsonpath="{['data']['ca\.crt']}" | base64 -D kubectl get secret <secret name> -o jsonpath="{['data']['ca\.crt']}" | base64 --decode
``` ```
1. **Create admin token**: A `cluster-admin` token is required to install and 1. **Create admin token**: A `cluster-admin` token is required to install and
......
...@@ -158,8 +158,8 @@ To determine the: ...@@ -158,8 +158,8 @@ To determine the:
- API URL, run `kubectl cluster-info | grep 'Kubernetes master' | awk '/http/ {print $NF}'`. - API URL, run `kubectl cluster-info | grep 'Kubernetes master' | awk '/http/ {print $NF}'`.
- Token: - Token:
1. List the secrets by running: `kubectl get secrets`. Note the name of the secret you need the token for. 1. List the secrets by running: `kubectl get secrets`. Note the name of the secret you need the token for.
1. Get the token for the appropriate secret by running: `kubectl get secret <SECRET_NAME> -o jsonpath="{['data']['token']}" | base64 -D`. 1. Get the token for the appropriate secret by running: `kubectl get secret <SECRET_NAME> -o jsonpath="{['data']['token']}" | base64 --decode`.
- CA certificate, run `kubectl get secret <secret name> -o jsonpath="{['data']['ca\.crt']}" | base64 -D`. - CA certificate, run `kubectl get secret <secret name> -o jsonpath="{['data']['ca\.crt']}" | base64 --decode`.
## Security implications ## Security implications
......
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