Merge pull request #22 from IBM/2061fix

Fix broken links

CHANGELOG.md

@@ -2,6 +2,11 @@
 
 All notable changes to this project will be documented in this file.
 
+## v20.6.1 Changes
+
+### Changed
+
+* Updated URL format to match path prefix used by Gatsby build
 
 ## v20.6.0 Changes
 

src/pages/01-prereq/Docker-Kubernetes-Helm.mdx

@@ -23,7 +23,7 @@ Install Docker by following the instructions in [docker.com](https://docs.docker
 Kubernetes (which is also referred to as "K8s" and is described at a high-level on the [Kubernetes home page](https://kubernetes.io/)) is an open source system for automating deployment, scaling, and management of containerized applications.
 You will use the command-line tool, `kubectl`, extensively when you follow the steps that are described in this runbook. The `kubectl` download and installation steps are described on [kubernetes.io](https://kubernetes.io/docs/tasks/tools/install-kubectl/).
 
-Minikube is a variant of Kubernetes that runs a single-node cluster inside a virtual machine (VM) on your laptop. See [next page](../minikube) for Minikube configuration details for SPM.
+Minikube is a variant of Kubernetes that runs a single-node cluster inside a virtual machine (VM) on your laptop. See [next page](/01-prereq/minikube) for Minikube configuration details for SPM.
 
 <InlineNotification>
 

src/pages/01-prereq/crc_installation.mdx

@@ -89,7 +89,7 @@ This procedure will also create the ~/.crc directory if it does not already exis
 crc setup
 ```
 
-Now that the basic configuration is complete, we can edit the configuration further to change the memory limit and add the path to the pull secret file downloaded under `Installation of CRC` on the [crc installation page](../crc_installation).
+Now that the basic configuration is complete, we can edit the configuration further to change the memory limit and add the path to the pull secret file downloaded previously.
 We will also set the cpus to 6:
 
 ```shell

src/pages/01-prereq/prereq.mdx

@@ -6,9 +6,9 @@ description: Install prerequisite software
 IBM® Cúram Social Program Management (SPM) has been enhanced in version 7.0.10.0 to enable it to be deployed on cloud native hosting platforms.
 To build and run IBM Cúram Social Program Management (SPM) for Kubernetes, install the following software components:
 
-* [Base third-party software](../3rdparty-sw)
+* [Base third-party software](/01-prereq/3rdparty-sw)
 * [IBM Cúram Social Program Management (SPM) software](/02-deploy-spm/SPM-sw)
-* [Docker®, Kubernetes, and Helm](../Docker-Kubernetes-Helm)
-* [Minikube](../minikube) or [Code Ready Container](../crc_installation)
-* [ChartMuseum](../chartmuseum)
-* [GitHub repo](../git)
+* [Docker®, Kubernetes, and Helm](/01-prereq/Docker-Kubernetes-Helm)
+* [Minikube](/01-prereq/minikube) or [Code Ready Container](/01-prereq/crc_installation)
+* [ChartMuseum](/01-prereq/chartmuseum)
+* [GitHub repo](/01-prereq/git)

src/pages/02-deploy-spm/spm-build.mdx

@@ -5,7 +5,7 @@ description: Building the SPM application
 
 <InlineNotification>
 
-**Note:** Before proceeding with the following steps, ensure that the steps defined in [Create the SPM Database](../create_spm_db) are completed. This action should be only a one-off set-up.
+**Note:** Before proceeding with the following steps, ensure that the steps defined in [Create the SPM Database](/02-deploy-spm/create_spm_db) are completed. This action should be only a one-off set-up.
 
 </InlineNotification>
 

src/pages/04-deployment/hc_preparation.mdx

@@ -17,7 +17,7 @@ The [spm-kubernetes](https://github.com/IBM/spm-kubernetes) repository provides
 
 The charts use a templating mechanism to create the YAML file that is used by Kubernetes.
 For this reason, the main configuration values are stored for each chart in a `values.yaml` file in the main folder of the charts.
-The values can also be overwritten by the `spm:*` umbrella chart or by a provided override file during deployment as described in [Deploying Helm charts](../hc_deployment).
+The values can also be overwritten by the `spm:*` umbrella chart or by a provided override file during deployment as described in [Deploying Helm charts](/04-deployment/hc_deployment).
 
 YAML is a human-readable structured data format. It provides powerful configuration settings, without having to learn a more complex code type like CSS, JavaScript, or PHP.
 
@@ -61,7 +61,7 @@ The value can be obtained by running `./build.sh encrypt -Dpassword=<password>`
 `global.database.wlp_psw` is the WebSphere Liberty WebSphere `{xor}` encoding of the database password. The value can be obtained by using `$WLP_HOME/bin/securityUtility encode <password>`.
 
 While it is possible to update the values directly in the `spm` chart, it is advisable to maintain a separate YAML file with values specific to your environment.
-The YAML file will be used by the `helm install` command that is described in [Deploying Helm charts](../hc_deployment).
+The YAML file will be used by the `helm install` command that is described in [Deploying Helm charts](/04-deployment/hc_deployment).
 
 <InlineNotification>
 

src/pages/06-operations/updating_tools.mdx

@@ -36,4 +36,4 @@ As with any software, make sure to review the Helm [Release Notes](https://githu
 ## Middleware components
 
 Because of the ephemeral nature of containers, when the application middleware (for example, IBM® WebSphere® Liberty) needs to be updated, new application images must be built upon a new base image.
-The new images should then be promoted throughout the software development lifecycle using the methods outlined in the next section, [Updating SPM Deployment](../updating_curam).
+The new images should then be promoted throughout the software development lifecycle using the methods outlined in the next section, [Updating SPM Deployment](/06-operations/updating_curam).

src/pages/08-runtime/must_gather.mdx

@@ -308,7 +308,7 @@ See the `kubectl help logs` command for option details.
 
 Beyond basic stdout logging from a pod there may be additional logging or artifacts needed for investigating an issue.
 These logs and artifacts will be available with in the pod's Docker file system or; additionally, in the case of IKS cloud object storage, in the persistent storage location you specified as per the
-[runbook specific section](https://ibm.github.io/spm-kubernetes/05-supporting-infrastructure/COS).
+[runbook specific section](/07-supporting-infrastructure/COS).
 Further, the specific logs, artifacts, and their locations will vary depending on the software running within the pod.
 
 The following sections identify these various locations.