diff --git a/docs/components/best-practices/development/service-integration-patterns.md b/docs/components/best-practices/development/service-integration-patterns.md
index e367ad8978..5c5e68ce69 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 cfc5a2f7ce..8cad92a25a 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 49f2f0e3f6..3c17328ddd 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 31e25cf0bd..85cefc6d15 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 0000000000..e69de29bb2
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 066efc0c01..bded871f4b 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 57fd1bdfb8..c2d1e9e57b 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 066efc0c01..bded871f4b 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 df87504ce9..b9822517fb 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 e367ad8978..5c5e68ce69 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 b6d8416983..10555313a0 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 e367ad8978..5c5e68ce69 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 cfc5a2f7ce..8cad92a25a 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 b6d8416983..10555313a0 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 e367ad8978..5c5e68ce69 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 cfc5a2f7ce..8cad92a25a 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 49f2f0e3f6..3c17328ddd 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