From 2686b33acdf0896963b745f8f5527d8e135ac2b5 Mon Sep 17 00:00:00 2001 From: Simon Cornet Date: Tue, 10 Jun 2025 16:39:26 +0200 Subject: [PATCH] feat: try to use admonitions --- docs/gitlab/runner-config-ocp.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/gitlab/runner-config-ocp.md b/docs/gitlab/runner-config-ocp.md index 7d19c01..c60d716 100644 --- a/docs/gitlab/runner-config-ocp.md +++ b/docs/gitlab/runner-config-ocp.md @@ -3,7 +3,7 @@ A quick and dirty guide for making the Gitlab Runner work on OCP. This is probably not what you want for you prodcution environment... -## Step 1 Setup namespace and RBAC +## Step 1 | Setup namespace and RBAC ```shell oc new-project gitlab-runner @@ -40,27 +40,28 @@ roleRef: EOF ``` -## Step 2 Create secrets +## Step 2 | Create secrets -[!warning] REPLACE YOUR TOKEN! +!!! note + REPLACE YOUR TOKEN! ```shell -# 2. Create secret (REPLACE TOKEN!) oc create secret generic gitlab-runner-secret \ --from-literal=runner-registration-token=YOUR_REGISTRATION_TOKEN \ -n gitlab-runner ``` -## 3. Apply SCCs +## Step 3 | Apply SCCs ```shell oc adm policy add-scc-to-user anyuid -z gitlab-runner -n gitlab-runner oc adm policy add-scc-to-user privileged -z gitlab-runner -n gitlab-runner ``` -## 4. Deploy runner (REPLACE TOKEN IN YAML!) +## Step 4 | Deploy runner -[!warning] REPLACE YOUR TOKEN! +!!! note + REPLACE YOUR TOKEN! ```shell oc apply -f - <