From 250c1b8d6a1a2da19303b241c90ece2822c66278 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Thu, 25 Apr 2024 10:57:05 +0200
Subject: [PATCH 01/18] init lychee checks

---
 .github/workflows/links.yml | 36 ++++++++++++++++++++++++++++++++++++
 lychee.toml                 | 12 ++++++++++++
 2 files changed, 48 insertions(+)
 create mode 100644 .github/workflows/links.yml
 create mode 100644 lychee.toml

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
new file mode 100644
index 00000000000..fc5ad663f6a
--- /dev/null
+++ b/.github/workflows/links.yml
@@ -0,0 +1,36 @@
+---
+# desc: lint sanity check
+name: Links (Fail Fast)
+
+on:
+  push:
+  pull_request:
+  workflow_dispatch:
+
+
+jobs:
+    lint:
+        name: pre-commit
+        runs-on: ubuntu-latest
+        steps:
+            - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4
+            - name: Restore lychee cache
+              uses: actions/cache@v3
+              with:
+                path: .lycheecache
+                key: cache-lychee-${{ github.sha }}
+                restore-keys: cache-lychee-
+                    
+            - name: Link Checker
+              uses: lycheeverse/lychee-action@v1.9.0
+              with:
+                fail: true
+                args: --base . --cache --max-cache-age 1d . --verbose --no-progress 'docs/**/*.md' 'versioned_docs/**/*.md'
+
+            # - name: Create Issue From File
+            #   if: env.lychee_exit_code != 0
+            #   uses: peter-evans/create-issue-from-file@v4
+            #   with:
+            #     title: Link Checker Report
+            #     content-filepath: ./lychee/out.md
+            #     labels: report, automated issue
\ No newline at end of file
diff --git a/lychee.toml b/lychee.toml
new file mode 100644
index 00000000000..53532a9952a
--- /dev/null
+++ b/lychee.toml
@@ -0,0 +1,12 @@
+# Cache the results of Lychee if ran locally in order to minimise the chance of rate limiting
+cache = true
+# Ignore all private link (such as localhost) to avoid errors
+exclude_all_private = true
+# HTTP status code: 429 (Too Many Requests) will also be treated as a valid link if Lychee gets rate limited
+accept = [200, 429]
+# retry
+max_retries = 6
+# Explicitly exclude some URLs
+exclude = [
+  "^file:",
+]
\ No newline at end of file

From c2a48b60218b2e81cee463eac992e2841971e60e Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Thu, 25 Apr 2024 11:00:26 +0200
Subject: [PATCH 02/18] add config

---
 .github/workflows/links.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index fc5ad663f6a..3e7f743c6a8 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -25,7 +25,7 @@ jobs:
               uses: lycheeverse/lychee-action@v1.9.0
               with:
                 fail: true
-                args: --base . --cache --max-cache-age 1d . --verbose --no-progress 'docs/**/*.md' 'versioned_docs/**/*.md'
+                args: -c ./lychee.toml --base . --cache --max-cache-age 1d . --verbose --no-progress 'docs/**/*.md' 'versioned_docs/**/*.md'
 
             # - name: Create Issue From File
             #   if: env.lychee_exit_code != 0

From 36000888fd6a22826fcc1acca06319758e7bfb99 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Thu, 25 Apr 2024 12:15:10 +0200
Subject: [PATCH 03/18] fix config

---
 lychee.toml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lychee.toml b/lychee.toml
index 53532a9952a..237eb479e59 100644
--- a/lychee.toml
+++ b/lychee.toml
@@ -3,7 +3,7 @@ cache = true
 # Ignore all private link (such as localhost) to avoid errors
 exclude_all_private = true
 # HTTP status code: 429 (Too Many Requests) will also be treated as a valid link if Lychee gets rate limited
-accept = [200, 429]
+accept = ["200", "429"]
 # retry
 max_retries = 6
 # Explicitly exclude some URLs

From 859d0c4b27efff70f9a4c35a23695e039c0305ca Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Thu, 25 Apr 2024 12:20:42 +0200
Subject: [PATCH 04/18] lower parallel

---
 .github/workflows/links.yml | 3 +--
 lychee.toml                 | 2 ++
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index 3e7f743c6a8..a1c4d81b9c9 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -4,13 +4,12 @@ name: Links (Fail Fast)
 
 on:
   push:
-  pull_request:
   workflow_dispatch:
 
 
 jobs:
     lint:
-        name: pre-commit
+        name: links-check
         runs-on: ubuntu-latest
         steps:
             - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4
diff --git a/lychee.toml b/lychee.toml
index 237eb479e59..1473f654088 100644
--- a/lychee.toml
+++ b/lychee.toml
@@ -6,6 +6,8 @@ exclude_all_private = true
 accept = ["200", "429"]
 # retry
 max_retries = 6
+retry_wait_time = 10
+max_concurrency = 10
 # Explicitly exclude some URLs
 exclude = [
   "^file:",

From 83cb26cd977a60bd2c2b0624cdf2a70d53e2f333 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Thu, 25 Apr 2024 13:19:01 +0200
Subject: [PATCH 05/18] add gh token

---
 .github/workflows/links.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index a1c4d81b9c9..a9c2e21f4d0 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -25,6 +25,7 @@ jobs:
               with:
                 fail: true
                 args: -c ./lychee.toml --base . --cache --max-cache-age 1d . --verbose --no-progress 'docs/**/*.md' 'versioned_docs/**/*.md'
+                token: "${{ secrets.GITHUB_TOKEN }}"
 
             # - name: Create Issue From File
             #   if: env.lychee_exit_code != 0

From 86b3cb4f805f12b3864ddecc093963e2019f7dd5 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Thu, 25 Apr 2024 13:49:35 +0200
Subject: [PATCH 06/18] lower concurrency

---
 lychee.toml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lychee.toml b/lychee.toml
index 1473f654088..30861f54478 100644
--- a/lychee.toml
+++ b/lychee.toml
@@ -7,7 +7,7 @@ accept = ["200", "429"]
 # retry
 max_retries = 6
 retry_wait_time = 10
-max_concurrency = 10
+max_concurrency = 3
 # Explicitly exclude some URLs
 exclude = [
   "^file:",

From 99c7cc8169c509af9bb142765ed65b327fc6d81f Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Thu, 25 Apr 2024 13:59:34 +0200
Subject: [PATCH 07/18] fix 403 temporarly

---
 lychee.toml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lychee.toml b/lychee.toml
index 30861f54478..31e25cf0bd5 100644
--- a/lychee.toml
+++ b/lychee.toml
@@ -3,7 +3,7 @@ cache = true
 # Ignore all private link (such as localhost) to avoid errors
 exclude_all_private = true
 # HTTP status code: 429 (Too Many Requests) will also be treated as a valid link if Lychee gets rate limited
-accept = ["200", "429"]
+accept = ["200", "403"]
 # retry
 max_retries = 6
 retry_wait_time = 10

From 00a13bdd888300e434917050c76c38e26d4b4a22 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Thu, 25 Apr 2024 21:12:52 +0200
Subject: [PATCH 08/18] add schedule and report

---
 .github/workflows/links.yml | 26 +++++++++++++++-----------
 1 file changed, 15 insertions(+), 11 deletions(-)

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index a9c2e21f4d0..b8812e10f56 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -1,11 +1,10 @@
----
-# desc: lint sanity check
 name: Links (Fail Fast)
 
 on:
   push:
   workflow_dispatch:
-
+  schedule:
+    - cron: "0 3 * * *"
 
 jobs:
     lint:
@@ -13,11 +12,16 @@ jobs:
         runs-on: ubuntu-latest
         steps:
             - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4
+            
+            - name: Get Current Timestamp
+              id: timestamp
+              run: echo "TIMESTAMP=$(date +%s)" >> "$GITHUB_ENV"
+            
             - name: Restore lychee cache
               uses: actions/cache@v3
               with:
                 path: .lycheecache
-                key: cache-lychee-${{ github.sha }}
+                key: "cache-lychee-${{ env.TIMESTAMP }}"
                 restore-keys: cache-lychee-
                     
             - name: Link Checker
@@ -27,10 +31,10 @@ jobs:
                 args: -c ./lychee.toml --base . --cache --max-cache-age 1d . --verbose --no-progress 'docs/**/*.md' 'versioned_docs/**/*.md'
                 token: "${{ secrets.GITHUB_TOKEN }}"
 
-            # - name: Create Issue From File
-            #   if: env.lychee_exit_code != 0
-            #   uses: peter-evans/create-issue-from-file@v4
-            #   with:
-            #     title: Link Checker Report
-            #     content-filepath: ./lychee/out.md
-            #     labels: report, automated issue
\ No newline at end of file
+            - name: Create Issue From File
+              if: ${{ github.event_name == 'schedule' && env.lychee_exit_code != 0 }}
+              uses: peter-evans/create-issue-from-file@v4
+              with:
+                title: Link Checker Report
+                content-filepath: ./lychee/out.md
+                labels: report, automated issue
\ No newline at end of file

From 2f0847dabe0ceed3b54aa2e5f95693186de21132 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Thu, 25 Apr 2024 21:26:00 +0200
Subject: [PATCH 09/18] apply prettier

---
 .github/workflows/links.yml | 60 ++++++++++++++++++-------------------
 1 file changed, 30 insertions(+), 30 deletions(-)

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index b8812e10f56..87e80648e0b 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -7,34 +7,34 @@ on:
     - cron: "0 3 * * *"
 
 jobs:
-    lint:
-        name: links-check
-        runs-on: ubuntu-latest
-        steps:
-            - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4
-            
-            - name: Get Current Timestamp
-              id: timestamp
-              run: echo "TIMESTAMP=$(date +%s)" >> "$GITHUB_ENV"
-            
-            - name: Restore lychee cache
-              uses: actions/cache@v3
-              with:
-                path: .lycheecache
-                key: "cache-lychee-${{ env.TIMESTAMP }}"
-                restore-keys: cache-lychee-
-                    
-            - name: Link Checker
-              uses: lycheeverse/lychee-action@v1.9.0
-              with:
-                fail: true
-                args: -c ./lychee.toml --base . --cache --max-cache-age 1d . --verbose --no-progress 'docs/**/*.md' 'versioned_docs/**/*.md'
-                token: "${{ secrets.GITHUB_TOKEN }}"
+  lint:
+    name: links-check
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4
 
-            - name: Create Issue From File
-              if: ${{ github.event_name == 'schedule' && env.lychee_exit_code != 0 }}
-              uses: peter-evans/create-issue-from-file@v4
-              with:
-                title: Link Checker Report
-                content-filepath: ./lychee/out.md
-                labels: report, automated issue
\ No newline at end of file
+      - name: Get Current Timestamp
+        id: timestamp
+        run: echo "TIMESTAMP=$(date +%s)" >> "$GITHUB_ENV"
+
+      - name: Restore lychee cache
+        uses: actions/cache@v3
+        with:
+          path: .lycheecache
+          key: "cache-lychee-${{ env.TIMESTAMP }}"
+          restore-keys: cache-lychee-
+
+      - name: Link Checker
+        uses: lycheeverse/lychee-action@v1.9.0
+        with:
+          fail: true
+          args: -c ./lychee.toml --base . --cache --max-cache-age 1d . --verbose --no-progress 'docs/**/*.md' 'versioned_docs/**/*.md'
+          token: "${{ secrets.GITHUB_TOKEN }}"
+
+      - name: Create Issue From File
+        if: ${{ github.event_name == 'schedule' && env.lychee_exit_code != 0 }}
+        uses: peter-evans/create-issue-from-file@v4
+        with:
+          title: Link Checker Report
+          content-filepath: ./lychee/out.md
+          labels: report, automated issue

From 9b664a9a73a8cd085debc0e7f58b8f0e1c8c1584 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Fri, 26 Apr 2024 09:52:04 +0200
Subject: [PATCH 10/18] use dedicated config for external links

---
 .github/workflows/links.yml               | 2 +-
 lychee.toml => lychee-external-links.toml | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename lychee.toml => lychee-external-links.toml (100%)

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index 87e80648e0b..ed326e320b4 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -28,7 +28,7 @@ jobs:
         uses: lycheeverse/lychee-action@v1.9.0
         with:
           fail: true
-          args: -c ./lychee.toml --base . --cache --max-cache-age 1d . --verbose --no-progress 'docs/**/*.md' 'versioned_docs/**/*.md'
+          args: -c ./lychee-external-links.toml --base . --cache --max-cache-age 1d . --verbose --no-progress 'docs/**/*.md' 'versioned_docs/**/*.md'
           token: "${{ secrets.GITHUB_TOKEN }}"
 
       - name: Create Issue From File
diff --git a/lychee.toml b/lychee-external-links.toml
similarity index 100%
rename from lychee.toml
rename to lychee-external-links.toml

From e2bc1dfe256f986ee32b519e1733267dbb38b5a0 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Fri, 26 Apr 2024 10:30:07 +0200
Subject: [PATCH 11/18] fix part of broken links

---
 .../best-practices/development/service-integration-patterns.md | 2 +-
 docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md     | 2 +-
 docs/self-managed/setup/deploy/openshift/redhat-openshift.md   | 2 +-
 lychee-external-links.toml                                     | 3 +++
 versioned_docs/version-1.3/.lycheeignore                       | 0
 .../best-practices/development/service-integration-patterns.md | 2 +-
 .../helm-kubernetes/platforms/redhat-openshift.md              | 2 +-
 .../best-practices/development/service-integration-patterns.md | 2 +-
 .../helm-kubernetes/platforms/redhat-openshift.md              | 2 +-
 .../best-practices/development/service-integration-patterns.md | 2 +-
 .../helm-kubernetes/platforms/redhat-openshift.md              | 2 +-
 .../best-practices/development/service-integration-patterns.md | 2 +-
 .../helm-kubernetes/platforms/amazon-eks/eksctl.md             | 2 +-
 .../helm-kubernetes/platforms/redhat-openshift.md              | 2 +-
 .../best-practices/development/service-integration-patterns.md | 2 +-
 .../self-managed/setup/deploy/amazon/amazon-eks/eksctl.md      | 2 +-
 .../self-managed/setup/deploy/openshift/redhat-openshift.md    | 2 +-
 17 files changed, 18 insertions(+), 15 deletions(-)
 create mode 100644 versioned_docs/version-1.3/.lycheeignore

diff --git a/docs/components/best-practices/development/service-integration-patterns.md b/docs/components/best-practices/development/service-integration-patterns.md
index e367ad8978d..5c5e68ce69e 100644
--- a/docs/components/best-practices/development/service-integration-patterns.md
+++ b/docs/components/best-practices/development/service-integration-patterns.md
@@ -23,7 +23,7 @@ The following table gives a summary of the three options:
 | **Technical communication style** | Synchronous                  | Asynchronous                  | Asynchronous                    |
 | **Example**                       | HTTP                         | AMQP, JMS                     | AMQP, Apache Kafka              |
 
-You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://medium.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
+You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://blog.bernd-ruecker.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
 
 ## Integrating services with BPMN tasks
 
diff --git a/docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md b/docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md
index cfc5a2f7ce6..8cad92a25a7 100644
--- a/docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md
+++ b/docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md
@@ -14,7 +14,7 @@ This guide provides a user-friendly approach for setting up and managing Amazon
 
 - An [AWS account](https://docs.aws.amazon.com/accounts/latest/reference/accounts-welcome.html) is required to create resources within AWS.
 - [AWS CLI (2.11+)](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html), a CLI tool for creating AWS resources.
-- [eksctl (0.163+)](https://eksctl.io/setup/), a CLI tool for creating and managing Amazon EKS clusters.
+- [eksctl (0.163+)](https://eksctl.io/getting-started/), a CLI tool for creating and managing Amazon EKS clusters.
 - [kubectl (1.28+)](https://kubernetes.io/docs/tasks/tools/#kubectl), a CLI tool to interact with the cluster.
 
 ## Considerations
diff --git a/docs/self-managed/setup/deploy/openshift/redhat-openshift.md b/docs/self-managed/setup/deploy/openshift/redhat-openshift.md
index 49f2f0e3f65..3c17328ddd2 100644
--- a/docs/self-managed/setup/deploy/openshift/redhat-openshift.md
+++ b/docs/self-managed/setup/deploy/openshift/redhat-openshift.md
@@ -205,7 +205,7 @@ You also need to use a custom values file, where instead of using `null` as a va
 Copy these values to your values file or save them as a separate file, e.g. `openshift.yaml`:
 
 :::note
-These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/openshift/values-patch.yaml).
+These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/charts/camunda-platform/openshift/values.yaml).
 :::
 
 ```yaml
diff --git a/lychee-external-links.toml b/lychee-external-links.toml
index 31e25cf0bd5..85cefc6d15a 100644
--- a/lychee-external-links.toml
+++ b/lychee-external-links.toml
@@ -11,4 +11,7 @@ max_concurrency = 3
 # Explicitly exclude some URLs
 exclude = [
   "^file:",
+  "^http(s)?:\/\/optimize\.myorg",
+  "^http(s)?://identity:8084",
+  "^http(s)?://keycloak:8080",
 ]
\ No newline at end of file
diff --git a/versioned_docs/version-1.3/.lycheeignore b/versioned_docs/version-1.3/.lycheeignore
new file mode 100644
index 00000000000..e69de29bb2d
diff --git a/versioned_docs/version-8.1/components/best-practices/development/service-integration-patterns.md b/versioned_docs/version-8.1/components/best-practices/development/service-integration-patterns.md
index 066efc0c013..bded871f4b5 100644
--- a/versioned_docs/version-8.1/components/best-practices/development/service-integration-patterns.md
+++ b/versioned_docs/version-8.1/components/best-practices/development/service-integration-patterns.md
@@ -23,7 +23,7 @@ The following table gives a summary of the three options:
 | **Technical communication style** | Synchronous                  | Asynchronous                  | Asynchronous                    |
 | **Example**                       | HTTP                         | AMQP, JMS                     | AMQP, Apache Kafka              |
 
-You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://medium.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
+You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://blog.bernd-ruecker.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
 
 ## Integrating services with BPMN tasks
 
diff --git a/versioned_docs/version-8.1/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md b/versioned_docs/version-8.1/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
index 57fd1bdfb88..c2d1e9e57b3 100644
--- a/versioned_docs/version-8.1/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
+++ b/versioned_docs/version-8.1/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
@@ -205,7 +205,7 @@ You also need to use a custom values file, where instead of using `null` as a va
 Copy these values to your values file or save them as a separate file, e.g. `openshift.yaml`:
 
 :::note
-These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/openshift/values-patch.yaml).
+These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/charts/camunda-platform/openshift/values.yaml).
 :::
 
 ```yaml
diff --git a/versioned_docs/version-8.2/components/best-practices/development/service-integration-patterns.md b/versioned_docs/version-8.2/components/best-practices/development/service-integration-patterns.md
index 066efc0c013..bded871f4b5 100644
--- a/versioned_docs/version-8.2/components/best-practices/development/service-integration-patterns.md
+++ b/versioned_docs/version-8.2/components/best-practices/development/service-integration-patterns.md
@@ -23,7 +23,7 @@ The following table gives a summary of the three options:
 | **Technical communication style** | Synchronous                  | Asynchronous                  | Asynchronous                    |
 | **Example**                       | HTTP                         | AMQP, JMS                     | AMQP, Apache Kafka              |
 
-You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://medium.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
+You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://blog.bernd-ruecker.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
 
 ## Integrating services with BPMN tasks
 
diff --git a/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md b/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
index df87504ce9e..b9822517fbd 100644
--- a/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
+++ b/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
@@ -208,7 +208,7 @@ You also need to use a custom values file, where instead of using `null` as a va
 Copy these values to your values file or save them as a separate file, e.g. `openshift.yaml`:
 
 :::note
-These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/openshift/values-patch.yaml).
+These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/charts/camunda-platform/openshift/values.yaml).
 :::
 
 ```yaml
diff --git a/versioned_docs/version-8.3/components/best-practices/development/service-integration-patterns.md b/versioned_docs/version-8.3/components/best-practices/development/service-integration-patterns.md
index e367ad8978d..5c5e68ce69e 100644
--- a/versioned_docs/version-8.3/components/best-practices/development/service-integration-patterns.md
+++ b/versioned_docs/version-8.3/components/best-practices/development/service-integration-patterns.md
@@ -23,7 +23,7 @@ The following table gives a summary of the three options:
 | **Technical communication style** | Synchronous                  | Asynchronous                  | Asynchronous                    |
 | **Example**                       | HTTP                         | AMQP, JMS                     | AMQP, Apache Kafka              |
 
-You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://medium.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
+You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://blog.bernd-ruecker.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
 
 ## Integrating services with BPMN tasks
 
diff --git a/versioned_docs/version-8.3/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md b/versioned_docs/version-8.3/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
index b6d84169834..10555313a07 100644
--- a/versioned_docs/version-8.3/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
+++ b/versioned_docs/version-8.3/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
@@ -207,7 +207,7 @@ You also need to use a custom values file, where instead of using `null` as a va
 Copy these values to your values file or save them as a separate file, e.g. `openshift.yaml`:
 
 :::note
-These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/openshift/values-patch.yaml).
+These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/charts/camunda-platform/openshift/values.yaml).
 :::
 
 ```yaml
diff --git a/versioned_docs/version-8.4/components/best-practices/development/service-integration-patterns.md b/versioned_docs/version-8.4/components/best-practices/development/service-integration-patterns.md
index e367ad8978d..5c5e68ce69e 100644
--- a/versioned_docs/version-8.4/components/best-practices/development/service-integration-patterns.md
+++ b/versioned_docs/version-8.4/components/best-practices/development/service-integration-patterns.md
@@ -23,7 +23,7 @@ The following table gives a summary of the three options:
 | **Technical communication style** | Synchronous                  | Asynchronous                  | Asynchronous                    |
 | **Example**                       | HTTP                         | AMQP, JMS                     | AMQP, Apache Kafka              |
 
-You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://medium.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
+You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://blog.bernd-ruecker.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
 
 ## Integrating services with BPMN tasks
 
diff --git a/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eksctl.md b/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eksctl.md
index cfc5a2f7ce6..8cad92a25a7 100644
--- a/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eksctl.md
+++ b/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eksctl.md
@@ -14,7 +14,7 @@ This guide provides a user-friendly approach for setting up and managing Amazon
 
 - An [AWS account](https://docs.aws.amazon.com/accounts/latest/reference/accounts-welcome.html) is required to create resources within AWS.
 - [AWS CLI (2.11+)](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html), a CLI tool for creating AWS resources.
-- [eksctl (0.163+)](https://eksctl.io/setup/), a CLI tool for creating and managing Amazon EKS clusters.
+- [eksctl (0.163+)](https://eksctl.io/getting-started/), a CLI tool for creating and managing Amazon EKS clusters.
 - [kubectl (1.28+)](https://kubernetes.io/docs/tasks/tools/#kubectl), a CLI tool to interact with the cluster.
 
 ## Considerations
diff --git a/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md b/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
index b6d84169834..10555313a07 100644
--- a/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
+++ b/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
@@ -207,7 +207,7 @@ You also need to use a custom values file, where instead of using `null` as a va
 Copy these values to your values file or save them as a separate file, e.g. `openshift.yaml`:
 
 :::note
-These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/openshift/values-patch.yaml).
+These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/charts/camunda-platform/openshift/values.yaml).
 :::
 
 ```yaml
diff --git a/versioned_docs/version-8.5/components/best-practices/development/service-integration-patterns.md b/versioned_docs/version-8.5/components/best-practices/development/service-integration-patterns.md
index e367ad8978d..5c5e68ce69e 100644
--- a/versioned_docs/version-8.5/components/best-practices/development/service-integration-patterns.md
+++ b/versioned_docs/version-8.5/components/best-practices/development/service-integration-patterns.md
@@ -23,7 +23,7 @@ The following table gives a summary of the three options:
 | **Technical communication style** | Synchronous                  | Asynchronous                  | Asynchronous                    |
 | **Example**                       | HTTP                         | AMQP, JMS                     | AMQP, Apache Kafka              |
 
-You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://medium.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
+You can dive more into communication styles in the webinar [Communication Between Loosely Coupled Microservices](https://page.camunda.com/wb-communication-between-microservices) ([slides](https://www.slideshare.net/BerndRuecker/webinar-communication-between-loosely-coupled-microservices), [recording](https://page.camunda.com/wb-communication-between-microservices) and [FAQ](https://blog.bernd-ruecker.com/communication-between-loosely-coupled-microservices-webinar-faq-a02708b3c8b5)).
 
 ## Integrating services with BPMN tasks
 
diff --git a/versioned_docs/version-8.5/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md b/versioned_docs/version-8.5/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md
index cfc5a2f7ce6..8cad92a25a7 100644
--- a/versioned_docs/version-8.5/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md
+++ b/versioned_docs/version-8.5/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md
@@ -14,7 +14,7 @@ This guide provides a user-friendly approach for setting up and managing Amazon
 
 - An [AWS account](https://docs.aws.amazon.com/accounts/latest/reference/accounts-welcome.html) is required to create resources within AWS.
 - [AWS CLI (2.11+)](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html), a CLI tool for creating AWS resources.
-- [eksctl (0.163+)](https://eksctl.io/setup/), a CLI tool for creating and managing Amazon EKS clusters.
+- [eksctl (0.163+)](https://eksctl.io/getting-started/), a CLI tool for creating and managing Amazon EKS clusters.
 - [kubectl (1.28+)](https://kubernetes.io/docs/tasks/tools/#kubectl), a CLI tool to interact with the cluster.
 
 ## Considerations
diff --git a/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md b/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md
index 49f2f0e3f65..3c17328ddd2 100644
--- a/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md
+++ b/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md
@@ -205,7 +205,7 @@ You also need to use a custom values file, where instead of using `null` as a va
 Copy these values to your values file or save them as a separate file, e.g. `openshift.yaml`:
 
 :::note
-These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/openshift/values-patch.yaml).
+These values are also available in the [Camunda Helm chart repository](https://github.com/camunda/camunda-platform-helm/blob/main/charts/camunda-platform/openshift/values.yaml).
 :::
 
 ```yaml

From 822700440038aac4d46f68579d96ae0c436a8f4b Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Fri, 26 Apr 2024 10:33:58 +0200
Subject: [PATCH 12/18] fix config

---
 lychee-external-links.toml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lychee-external-links.toml b/lychee-external-links.toml
index 85cefc6d15a..b3bbde58126 100644
--- a/lychee-external-links.toml
+++ b/lychee-external-links.toml
@@ -11,7 +11,7 @@ max_concurrency = 3
 # Explicitly exclude some URLs
 exclude = [
   "^file:",
-  "^http(s)?:\/\/optimize\.myorg",
+  "^http(s)?://optimize.myorg",
   "^http(s)?://identity:8084",
   "^http(s)?://keycloak:8080",
 ]
\ No newline at end of file

From 130f8235f6ab767ec647e29417826d4fc34c0a79 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Fri, 26 Apr 2024 11:59:43 +0200
Subject: [PATCH 13/18] exclude version-1.3

---
 lychee-external-links.toml               | 4 ++++
 versioned_docs/version-1.3/.lycheeignore | 0
 2 files changed, 4 insertions(+)
 delete mode 100644 versioned_docs/version-1.3/.lycheeignore

diff --git a/lychee-external-links.toml b/lychee-external-links.toml
index b3bbde58126..eba73b7ad17 100644
--- a/lychee-external-links.toml
+++ b/lychee-external-links.toml
@@ -9,9 +9,13 @@ max_retries = 6
 retry_wait_time = 10
 max_concurrency = 3
 # Explicitly exclude some URLs
+exclude_path = [
+  "versioned_docs/version-1.3",
+]
 exclude = [
   "^file:",
   "^http(s)?://optimize.myorg",
   "^http(s)?://identity:8084",
   "^http(s)?://keycloak:8080",
+  "^http(s)?://camunda-platform-keycloak",
 ]
\ No newline at end of file
diff --git a/versioned_docs/version-1.3/.lycheeignore b/versioned_docs/version-1.3/.lycheeignore
deleted file mode 100644
index e69de29bb2d..00000000000

From a3e05e496dc4d43b364b2c9732b20bed729c0b49 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Fri, 26 Apr 2024 12:00:08 +0200
Subject: [PATCH 14/18] fix some links

---
 docs/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md    | 2 +-
 docs/self-managed/setup/deploy/openshift/redhat-openshift.md    | 2 +-
 .../helm-kubernetes/platforms/redhat-openshift.md               | 2 +-
 .../helm-kubernetes/platforms/redhat-openshift.md               | 2 +-
 .../helm-kubernetes/platforms/redhat-openshift.md               | 2 +-
 .../helm-kubernetes/platforms/amazon-eks/eks-helm.md            | 2 +-
 .../helm-kubernetes/platforms/redhat-openshift.md               | 2 +-
 .../self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md     | 2 +-
 .../self-managed/setup/deploy/openshift/redhat-openshift.md     | 2 +-
 9 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/docs/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md b/docs/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md
index ef6985b0b19..c0fcfd96fc3 100644
--- a/docs/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md
+++ b/docs/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md
@@ -121,7 +121,7 @@ helm upgrade --install \
 
 [Cert-manager](https://cert-manager.io/) is an open-source Kubernetes add-on that automates the management and issuance of TLS certificates. It integrates with various certificate authorities (CAs) and provides a straightforward way to obtain, renew, and manage SSL/TLS certificates for your Kubernetes applications.
 
-To simplify the installation process, it is [recommended](https://cert-manager.io/docs/setup/helm/#crd-installation-advice) to install the cert-manager `CustomResourceDefinition` resources before installing the chart. This separate step allows for easy uninstallation and reinstallation of cert-manager without deleting any custom resources that have been installed.
+To simplify the installation process, it is [recommended](https://cert-manager.io/docs/installation/helm/#3-install-customresourcedefinitions) to install the cert-manager `CustomResourceDefinition` resources before installing the chart. This separate step allows for easy uninstallation and reinstallation of cert-manager without deleting any custom resources that have been installed.
 
 ```shell
 kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v$CERT_MANAGER_HELM_CHART_VERSION/cert-manager.crds.yaml
diff --git a/docs/self-managed/setup/deploy/openshift/redhat-openshift.md b/docs/self-managed/setup/deploy/openshift/redhat-openshift.md
index 3c17328ddd2..13281a55513 100644
--- a/docs/self-managed/setup/deploy/openshift/redhat-openshift.md
+++ b/docs/self-managed/setup/deploy/openshift/redhat-openshift.md
@@ -169,7 +169,7 @@ helm install camunda camunda/camunda-platform --skip-crds -f values.yaml -f open
 
 #### Helm 3.2.0 and greater
 
-If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/openshift#using-a-post-renderer).
+If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/charts/camunda-platform/openshift#post-renderer-setup).
 
 :::warning
 If using a post-renderer, you **must** use the post-renderer whenever you are updating your release, not only during the initial installation. If you do not, the default values will be used again, which will prevent some services from starting.
diff --git a/versioned_docs/version-8.1/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md b/versioned_docs/version-8.1/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
index c2d1e9e57b3..6f392b7a04d 100644
--- a/versioned_docs/version-8.1/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
+++ b/versioned_docs/version-8.1/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
@@ -169,7 +169,7 @@ helm install camunda camunda/camunda-platform--skip-crds -f values.yaml -f opens
 
 #### Helm 3.2.0 and greater
 
-If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/openshift#using-a-post-renderer).
+If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/charts/camunda-platform/openshift#post-renderer-setup).
 
 :::warning
 If using a post-renderer, you **must** use the post-renderer whenever you are updating your release, not only during the initial installation. If you do not, the default values will be used again, which will prevent some services from starting.
diff --git a/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md b/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
index b9822517fbd..2f842d7794c 100644
--- a/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
+++ b/versioned_docs/version-8.2/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
@@ -172,7 +172,7 @@ helm install camunda camunda/camunda-platform--skip-crds -f values.yaml -f opens
 
 #### Helm 3.2.0 and greater
 
-If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/openshift#using-a-post-renderer).
+If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/charts/camunda-platform/openshift#post-renderer-setup).
 
 :::warning
 If using a post-renderer, you **must** use the post-renderer whenever you are updating your release, not only during the initial installation. If you do not, the default values will be used again, which will prevent some services from starting.
diff --git a/versioned_docs/version-8.3/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md b/versioned_docs/version-8.3/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
index 10555313a07..f047c917d25 100644
--- a/versioned_docs/version-8.3/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
+++ b/versioned_docs/version-8.3/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
@@ -171,7 +171,7 @@ helm install camunda camunda/camunda-platform --skip-crds -f values.yaml -f open
 
 #### Helm 3.2.0 and greater
 
-If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/openshift#using-a-post-renderer).
+If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/charts/camunda-platform/openshift#post-renderer-setup).
 
 :::warning
 If using a post-renderer, you **must** use the post-renderer whenever you are updating your release, not only during the initial installation. If you do not, the default values will be used again, which will prevent some services from starting.
diff --git a/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eks-helm.md b/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eks-helm.md
index 52f0f83213d..ef07488d43e 100644
--- a/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eks-helm.md
+++ b/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eks-helm.md
@@ -121,7 +121,7 @@ helm upgrade --install \
 
 [Cert-manager](https://cert-manager.io/) is an open-source Kubernetes add-on that automates the management and issuance of TLS certificates. It integrates with various certificate authorities (CAs) and provides a straightforward way to obtain, renew, and manage SSL/TLS certificates for your Kubernetes applications.
 
-To simplify the installation process, it is [recommended](https://cert-manager.io/docs/setup/helm/#crd-installation-advice) to install the cert-manager `CustomResourceDefinition` resources before installing the chart. This separate step allows for easy uninstallation and reinstallation of cert-manager without deleting any custom resources that have been installed.
+To simplify the installation process, it is [recommended](https://cert-manager.io/docs/installation/helm/#3-install-customresourcedefinitions) to install the cert-manager `CustomResourceDefinition` resources before installing the chart. This separate step allows for easy uninstallation and reinstallation of cert-manager without deleting any custom resources that have been installed.
 
 ```shell
 kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v$CERT_MANAGER_HELM_CHART_VERSION/cert-manager.crds.yaml
diff --git a/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md b/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
index 10555313a07..f047c917d25 100644
--- a/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
+++ b/versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/redhat-openshift.md
@@ -171,7 +171,7 @@ helm install camunda camunda/camunda-platform --skip-crds -f values.yaml -f open
 
 #### Helm 3.2.0 and greater
 
-If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/openshift#using-a-post-renderer).
+If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/charts/camunda-platform/openshift#post-renderer-setup).
 
 :::warning
 If using a post-renderer, you **must** use the post-renderer whenever you are updating your release, not only during the initial installation. If you do not, the default values will be used again, which will prevent some services from starting.
diff --git a/versioned_docs/version-8.5/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md b/versioned_docs/version-8.5/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md
index ef6985b0b19..c0fcfd96fc3 100644
--- a/versioned_docs/version-8.5/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md
+++ b/versioned_docs/version-8.5/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md
@@ -121,7 +121,7 @@ helm upgrade --install \
 
 [Cert-manager](https://cert-manager.io/) is an open-source Kubernetes add-on that automates the management and issuance of TLS certificates. It integrates with various certificate authorities (CAs) and provides a straightforward way to obtain, renew, and manage SSL/TLS certificates for your Kubernetes applications.
 
-To simplify the installation process, it is [recommended](https://cert-manager.io/docs/setup/helm/#crd-installation-advice) to install the cert-manager `CustomResourceDefinition` resources before installing the chart. This separate step allows for easy uninstallation and reinstallation of cert-manager without deleting any custom resources that have been installed.
+To simplify the installation process, it is [recommended](https://cert-manager.io/docs/installation/helm/#3-install-customresourcedefinitions) to install the cert-manager `CustomResourceDefinition` resources before installing the chart. This separate step allows for easy uninstallation and reinstallation of cert-manager without deleting any custom resources that have been installed.
 
 ```shell
 kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v$CERT_MANAGER_HELM_CHART_VERSION/cert-manager.crds.yaml
diff --git a/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md b/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md
index 3c17328ddd2..13281a55513 100644
--- a/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md
+++ b/versioned_docs/version-8.5/self-managed/setup/deploy/openshift/redhat-openshift.md
@@ -169,7 +169,7 @@ helm install camunda camunda/camunda-platform --skip-crds -f values.yaml -f open
 
 #### Helm 3.2.0 and greater
 
-If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/openshift#using-a-post-renderer).
+If you must deploy using Helm 3.2.0 or greater, you have two options. One is to use a SCCs which defines the `RunAsUser` strategy to be at least `RunAsAny`. If that's not possible, then you need to make use of [a post-renderer](https://helm.sh/docs/topics/advanced/#post-rendering). This workaround is also described in detail in the [Helm chart repository](https://github.com/camunda/camunda-platform-helm/tree/main/charts/camunda-platform/openshift#post-renderer-setup).
 
 :::warning
 If using a post-renderer, you **must** use the post-renderer whenever you are updating your release, not only during the initial installation. If you do not, the default values will be used again, which will prevent some services from starting.

From 6b0879d3bd20cd689fbac91b6f78a8c0ef53fdfa Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Fri, 26 Apr 2024 12:32:27 +0200
Subject: [PATCH 15/18] remove unsupported versions from the check

---
 lychee-external-links.toml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/lychee-external-links.toml b/lychee-external-links.toml
index eba73b7ad17..303a0d3ae26 100644
--- a/lychee-external-links.toml
+++ b/lychee-external-links.toml
@@ -8,10 +8,14 @@ accept = ["200", "403"]
 max_retries = 6
 retry_wait_time = 10
 max_concurrency = 3
-# Explicitly exclude some URLs
+
+# Exclude all unsupported versioned_docs
 exclude_path = [
   "versioned_docs/version-1.3",
+  "versioned_docs/version-8.1",
 ]
+
+# Explicitly exclude some URLs
 exclude = [
   "^file:",
   "^http(s)?://optimize.myorg",

From 31c85e20a78851d253c8ae496d7625a279d610e7 Mon Sep 17 00:00:00 2001
From: Leo J <153937047+leiicamundi@users.noreply.github.com>
Date: Mon, 29 Apr 2024 09:03:52 +0200
Subject: [PATCH 16/18] Update .github/workflows/links.yml

Co-authored-by: Steven Hicks <steven.j.hicks@gmail.com>
---
 .github/workflows/links.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index ed326e320b4..458ebba8e9a 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -1,4 +1,4 @@
-name: Links (Fail Fast)
+name: Check external links
 
 on:
   push:

From 4b26de313c3c50db42acd145dae0e0b6735cd875 Mon Sep 17 00:00:00 2001
From: Leo J <153937047+leiicamundi@users.noreply.github.com>
Date: Mon, 29 Apr 2024 09:04:02 +0200
Subject: [PATCH 17/18] Update .github/workflows/links.yml

Co-authored-by: Steven Hicks <steven.j.hicks@gmail.com>
---
 .github/workflows/links.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index 458ebba8e9a..1748edd2cdb 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -4,7 +4,7 @@ on:
   push:
   workflow_dispatch:
   schedule:
-    - cron: "0 3 * * *"
+    - cron: "0 3 1 * *"
 
 jobs:
   lint:

From 137cc60c4288e6dc58acfb9ee4ac8c45b0b00d06 Mon Sep 17 00:00:00 2001
From: leiicamundi <153937047+leiicamundi@users.noreply.github.com>
Date: Mon, 29 Apr 2024 12:12:36 +0200
Subject: [PATCH 18/18] remove on push links checks

We want to review the broken links on a weekly basis and adress broken
links in batchs.
Also, the gha does not support checking only the links modified by the
push commit, it is something that we could implement later.
---
 .github/workflows/links.yml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index 1748edd2cdb..ffe86651365 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -1,7 +1,6 @@
 name: Check external links
 
 on:
-  push:
   workflow_dispatch:
   schedule:
     - cron: "0 3 1 * *"