From aa47e5832e7c365b8cd204c1370c73f3dc4a38e0 Mon Sep 17 00:00:00 2001 From: Kostis Trantzas <ktrantzas@ece.upatras.gr> Date: Thu, 8 Aug 2024 02:35:07 +0300 Subject: [PATCH] fix broken links --- .../HELM_Installation_aaS_Jenkins_Example.md | 4 ++-- doc/service_design/kubernetes/helm/design_helmaas.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/service_design/examples/helmInstallation_aaS_Example_Jenkins/HELM_Installation_aaS_Jenkins_Example.md b/doc/service_design/examples/helmInstallation_aaS_Example_Jenkins/HELM_Installation_aaS_Jenkins_Example.md index 2a865e1e..8623e562 100644 --- a/doc/service_design/examples/helmInstallation_aaS_Example_Jenkins/HELM_Installation_aaS_Jenkins_Example.md +++ b/doc/service_design/examples/helmInstallation_aaS_Example_Jenkins/HELM_Installation_aaS_Jenkins_Example.md @@ -2,7 +2,7 @@ ## Design the Jenkins (Resource-Facing) Service -Before reading this example please make sure that you went through the [Design Helm as a Service](../design_helmaas.md) +Before reading this example please make sure that you went through the [Design Helm as a Service](../../kubernetes/helm/design_helmaas.md) In this example, we will use the ```Kind: Application``` of ArgoCD and create a ResourceFacingServiceSpecification (RFSS) for Jenkins. Eventually, we will offer Jenkins as a Service. @@ -161,7 +161,7 @@ Select the secret resource, which will navigate you to the Resource Inventory pa  -Use a Base64 decoder to parse the credentials and use them to login in your Jenkins installation, through the exposed Jenkis Server UI. +Use a Base64 decoder to parse the credentials and use them to login in your Jenkins installation, through the exposed Jenkins Server UI. > Exposing Jenkins externally is a matter of cluster configuration and request (nodeport, load balancing, etc), thus is not a topic for this example diff --git a/doc/service_design/kubernetes/helm/design_helmaas.md b/doc/service_design/kubernetes/helm/design_helmaas.md index e4f3d75e..ba69891b 100644 --- a/doc/service_design/kubernetes/helm/design_helmaas.md +++ b/doc/service_design/kubernetes/helm/design_helmaas.md @@ -38,7 +38,7 @@ For installing HELM charts we will use ArgoCD a well known Kubernetes-native con > ArgoCD is a Kubernetes-native continuous deployment (CD) tool -> While just deploying Heml charts is just a scenario for ArgoCD , in future one can exploit it for many things +> While just deploying HELM charts is just a scenario for ArgoCD , in future one can exploit it for many things > Despite some other tools like FluxCD, it provides also a UI which is useful for management and troubleshooting @@ -64,4 +64,4 @@ see image: ## Probe further -See the [Example: Offer Jenkins as a Service via Openslice](../../examples/helmInstallation_aaS_Example_Jenkins/HELM_Installation_aaS_Jenkins_Example.md) +See the [Example: Offer Jenkins as a Service via OpenSlice](../../examples/helmInstallation_aaS_Example_Jenkins/HELM_Installation_aaS_Jenkins_Example.md) -- GitLab