docs(gitlabrunner): add GitLab registration details ext-fix-gitlabrunner (scaleway#3960)

* fix(gitlabrunner): add details for GitLab Runner registration

* Apply suggestions from code review

Co-authored-by: nerda-codes <[email protected]>

* Update tutorials/easydeploy-gitlab-runner/index.mdx

Co-authored-by: ldecarvalho-doc <[email protected]>

* Update tutorials/easydeploy-gitlab-runner/index.mdx

Co-authored-by: ldecarvalho-doc <[email protected]>

---------

Co-authored-by: Benedikt Rollik <[email protected]>
Co-authored-by: nerda-codes <[email protected]>
Co-authored-by: ldecarvalho-doc <[email protected]>

Author: 4 people

tutorials/easydeploy-gitlab-runner/index.mdx

@@ -36,11 +36,24 @@ This setup enables you to optimize resource utilization, reduce overhead, and en
         If you cannot find GitLab Runner on the first page, use the search bar or navigate through the library using the arrow buttons.
     </Message>
 7. Optionally, customize the default configuration for GitLab Runner using [Helm Charts](/tutorials/kubernetes-package-management-helm/). If you do not need any customized configuration you can skip this step.
-8. Enter a name (e.g. `gitlab-runner`) and a Kubernetes namespace for your application. If no name is entered, GitLab Runner will be installed in the default namespace of the cluster.
-9. Click **Deploy Application** to deploy GitLab Runner on your Kubernetes cluster.
-10. Verify that the GitLab Runner is successfully installed and running:
+8. **Provide the following GitLab details:**
+    - **GitLab URL (`gitlabUrl`)**: Go to your GitLab project, click **Settings > CI/CD > Runners**, and copy the GitLab Instance URL.
+    - **Registration Token (`runnerToken`)**: Under the **Specific Runners** section in **Settings > CI/CD > Runners**, copy the registration token for your project. These are necessary to allow GitLab Runner to register correctly with your GitLab project.
+    ```yaml
+    gitlabUrl: https://your-gitlab.com
+    runnerToken: "your-token"
+    rbac:
+      create: true
+    ```
+
+    <Message type="note">
+        The information above is required to register your GitLab Runner with your GitLab project.
+    </Message>
+9. Enter a name (e.g. `gitlab-runner`) and a Kubernetes namespace for your application. If you do not specify a name, GitLab Runner will be installed in the default namespace of the cluster.
+10. Click **Deploy Application** to deploy GitLab Runner on your Kubernetes cluster.
+11. Use the following command to verify that the GitLab Runner is installed and running:
     ```bash
-    kubectl get pods -n default # replace "default" with the name of the Kubernetes namespace in which you have installed your GitLab Runner.
+    kubectl get pods -n <namespace> # replace "<namespace>" with the name of the Kubernetes namespace in which you have installed your GitLab Runner.
     ```
     You should see a pod with a name similar to `gitlab-runner-xxxxxx-xxxxx` in the `Running` state.
 
@@ -120,12 +133,12 @@ Navigate to **CI/CD** > **Pipelines** in your GitLab project to view the status
 <Message type="tip">
   If the pipeline fails, you can check the logs of the GitLab Runner pod for more information:
    ```bash
-   kubectl logs -n default <gitlab-runner-pod-name>
+   kubectl logs -n <namespace> <gitlab-runner-pod-name>
    ```
 </Message>
 
 # Conclusion
 
 You have successfully set up a GitLab Runner hosted on Kubernetes and configured your GitLab CI/CD pipeline to use it. This setup allows you to leverage the scalability and flexibility of Kubernetes for your CI/CD workflows.
 
-For more detailed information on configuring your GitLab Runner, refer to the [official GitLab documentation](https://docs.gitlab.com/runner/install/kubernetes.html#configuring-gitlab-runner-using-the-helm-chart).
+For more detailed information on configuring your GitLab Runner, refer to the [official GitLab documentation](https://docs.gitlab.com/runner/install/kubernetes.html#configuring-gitlab-runner-using-the-helm-chart).