docs: url updates (#1563)

* docs: url updates

* ci: removed make versions from default runs

* docs: updated node repave text

* Apply suggestions from code review

Co-authored-by: Rita Watson <117382432+ritawatson@users.noreply.github.com>

---------

Co-authored-by: Rita Watson <117382432+ritawatson@users.noreply.github.com>

docs/docs-content/clusters/public-cloud/azure/aks.md

@@ -94,14 +94,15 @@ For Azure cloud account creation, we first need to create an Azure Active Direct
 <br />
 
 
-<video title="aks-cluster-creation" src="/videos/clusters/public-cloud/cluster-creation-videos/aks.mp4"></video>
+<video title="aks-cluster-creation" src="/videos/clusters/public-cloud/cloud-accounts/azure.mp4"></video>
 
 
 The following steps need to be performed to provision a new cluster:
 <br />
 
 
-1. If you already have a profile to use, go to the **Cluster** > **Add a New Cluster** > **Deploy New Cluster** and select an Azure cloud. If you do not have a profile to use, reference the [Creating a Cluster Profile](https://docs.spectrocloud.com/cluster-profiles/task-define-profile) page for steps on how to create one.
+1. If you already have a profile to use, go to **Cluster** > **Add a New Cluster** > **Deploy New Cluster** and select an Azure cloud. If you do not have a profile to use, review the [Creating a Cluster Profile](../../../cluster-profiles/task-define-profile.md) page for steps to create one.
+
 
 
 2. Fill the basic cluster profile information such as **Name**, **Description**, **Tags** and **Cloud Account**.

docs/docs-content/troubleshooting/nodes.md

@@ -24,7 +24,24 @@ Palette performs a rolling upgrade on nodes when it detects a change in the `kub
 * Changes in instance types
 * Certificate renewal
 
-Logs are provided in Palette for traceability. However, these logs may be lost when the pods are relaunched. To ensure that the cause and context is persisted across repaving, a field titled **upgrades** is available in the status section of [SpectroCluster object](https://docs.spectrocloud.com/api/v1/clusters/). This field is represented in the Palette UI so that you can understand why and when repaving happened.
+Logs are provided in Palette for traceability. However, these logs may be lost when the pods are relaunched. To ensure that the cause and context is persisted across repaving, refer to the `status.upgrades: []` field in the in the `SpectroCluster` object in the `/v1/dashboard/spectroclusters/:uid/overview` API.
+
+The following example shows the `status.upgrades` field for a cluster that had Kubernetes configuration changes that resulted in a node repave. The API payload is incomplete for brevity.
+
+```json hideClipboard
+"upgrades": [
+    {
+        "reason": [
+            "{v1beta1.KubeadmConfigSpec}.ClusterConfiguration.APIServer.ControlPlaneComponent.ExtraArgs[\"oidc-client-id\"] changed from <invalid reflect.Value> to xxxxxxxxxxx",
+            "{v1beta1.KubeadmConfigSpec}.ClusterConfiguration.APIServer.ControlPlaneComponent.ExtraArgs[\"oidc-groups-claim\"] changed from <invalid reflect.Value> to groups",
+            "{v1beta1.KubeadmConfigSpec}.ClusterConfiguration.APIServer.ControlPlaneComponent.ExtraArgs[\"oidc-issuer-url\"] changed from <invalid reflect.Value> to https://console.spectrocloud.com/v1/oidc/tenant/XXXXXXXXXXXX",
+            "{v1beta1.KubeadmConfigSpec}.ClusterConfiguration.APIServer.ControlPlaneComponent.ExtraArgs[\"oidc-username-claim\"] changed from <invalid reflect.Value> to email"
+        ],
+        "timestamp": "2023-09-18T19:49:33.000Z"
+    }
+]
+```
+
 
 For detailed information, review the cluster upgrades [page](../clusters/clusters.md).
 

netlify.toml

@@ -1,5 +1,5 @@
 [build]
   ignore = "./scripts/netlify.sh"
-  command = "make versions && npm run build"
+  command = "npm run build"