From dd17f033919066f8752c10b50ab0758185583feb Mon Sep 17 00:00:00 2001
From: sknop <118932232+sknop-cgn@users.noreply.github.com>
Date: Mon, 28 Oct 2024 15:20:13 +0100
Subject: [PATCH 1/2] Update vpnsaas.md

url rollback

Signed-off-by: sknop <118932232+sknop-cgn@users.noreply.github.com>
---
 .../managed-kubernetes/documentation/information/vpnsaas.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/de/container/managed-kubernetes/documentation/information/vpnsaas.md b/content/de/container/managed-kubernetes/documentation/information/vpnsaas.md
index b8bf836c..d0fcc7ec 100644
--- a/content/de/container/managed-kubernetes/documentation/information/vpnsaas.md
+++ b/content/de/container/managed-kubernetes/documentation/information/vpnsaas.md
@@ -11,7 +11,7 @@ der PSKE zuzugreifen. Wir stellen verschiedene Optionen vor, damit Sie die bestm
 
 ## Site-to-Site-VPN (Hybrid Connector kurz HC)
 Diese Lösung ist gut geeignet, wenn ein VMware Cloud Endpoint, einen Database Service zur Verfügung stellt und ein PSKE Kubernetes-Cluster 
-über eine VPN-Verbindung sicher auf diesen Service zugreifen soll. Die Provisionierung wird im Artikel [{{< pagetitle "HC - Provisionierung" >}}]({{< ref "/container/managed-kubernetes/documentation/hybridconnector/hc-provisioning" >}}) näher beschrieben.
+über eine VPN-Verbindung sicher auf diesen Service zugreifen soll. Die Provisionierung wird im Artikel [HC - Provisionierung](https://docs.plusserver.com/de/container/managed-kubernetes/documentation/hybridconnector/hc-provisioning/) näher beschrieben.
 
 ## Remote-Access-VPN (Virtual Cloud Firewall kurz vCFW)
 Diese Lösung wird hauptsächlich verwendet, wenn Einzelpersonen auf Services zugreifen, die über einen PSKE Kubernetes-Cluster bereitgestellt und

From 5e19c94ce77c06bd2fe3b3b03428a856b25699d4 Mon Sep 17 00:00:00 2001
From: sknop <118932232+sknop-cgn@users.noreply.github.com>
Date: Mon, 28 Oct 2024 15:21:11 +0100
Subject: [PATCH 2/2] Update vpnsaas.md

url fix

Signed-off-by: sknop <118932232+sknop-cgn@users.noreply.github.com>
---
 .../managed-kubernetes/documentation/information/vpnsaas.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/container/managed-kubernetes/documentation/information/vpnsaas.md b/content/en/container/managed-kubernetes/documentation/information/vpnsaas.md
index 99feaacb..6fbf3092 100644
--- a/content/en/container/managed-kubernetes/documentation/information/vpnsaas.md
+++ b/content/en/container/managed-kubernetes/documentation/information/vpnsaas.md
@@ -11,7 +11,7 @@ We present different options to help you find the best possible solution to secu
 
 ## Site-to-Site-VPN (Hybrid Connector kurz HC)
 This solution is well suited if a VMware Cloud Endpoint provides a database service and a PSKE Kubernetes cluster is to access this service securely via a VPN connection. 
-Provisioning is described in more detail in article  [{{< pagetitle "HC - Provisioning">}}]({{< ref "/container/managed-kubernetes/documentation/hybridconnector/hc-provisioning" >}}).
+Provisioning is described in more detail in article [HC - Provisioning](https://docs.plusserver.com/en/container/managed-kubernetes/documentation/hybridconnector/hc-provisioning/).
 
 ## Remote-Access-VPN (Virtual Cloud Firewall kurz vCFW)
 This solution is mainly used when individuals access services that are to be provided via a Kubernetes PSKE cluster and securely consumed via a VPN connection.