chore: fix broken URLs (#2631)

* chore: fix broken URLs

* chore: broken URL

Makefile

@@ -159,14 +159,17 @@ pdf-local: ## Generate PDF from local docs
 verify-url-links:
 	@echo "Checking for broken external URLs in markdown files..."
 	rm link_report.csv || echo "No report exists. Proceeding to scan step"
-	@npx linkinator "docs/**/*.md" --markdown --recurse --timeout 60000 --retry --retry-errors-count 3 \
+	@npx linkinator "docs/**/*.md" --markdown --recurse --timeout 60000 --retry --retry-errors-jitter --retry-errors-count 3 \
 		--skip "^https:\/\/docs\.spectrocloud\.com.*$$" \
 		--skip "^https:\/\/docs\.spectrocloud\.com\/.*\/supplemental\-packs$$" \
 		--skip "^http:\/\/docs\.spectrocloud\.com.*$$" \
 		--skip "^https:\/\/software-private\.spectrocloud\.com.*$$" \
 		--skip "^\/.*\.md$$" \
 		--skip "!\[.*\]\(.*\)$$" \
 		--skip "\.(jpg|jpeg|png|gif|webp)$$" \
+		--skip "https:\/\/linux\.die\.net\/man\/.*$$" \
+		--skip "https:\/\/mysql\.com\/.*\.*$$" \
+		--skip "https:\/\/dev\.mysql\.com\/doc/\.*$$" \
 		--format csv > temp_report.csv && sleep 2
 	@grep -E 'https?://' temp_report.csv > filtered_report.csv
 	@grep -E ',[[:space:]]*([4-9][0-9]{2}|[0-9]{4,}),' filtered_report.csv > link_report.csv && rm temp_report.csv filtered_report.csv
@@ -175,10 +178,16 @@ verify-url-links-ci: ## Check for broken URLs in production in a GitHub Actions
 	@echo "Checking for broken external URLs in CI environment..."
 	rm link_report.json || echo "No report exists. Proceeding to scan step"
 	@npx linkinator "docs/**/*.md" --markdown --recurse --timeout 60000 --retry --retry-errors-count 3 \
-		--skip '^https:\/\/docs\.spectrocloud\.com.*' \
-		--skip '^https:\/\/docs\.spectrocloud\.com\/.*\/supplemental\-packs' \
-		--skip '^http:\/\/docs\.spectrocloud\.com.*' \
-		--skip '^https:\/\/software-private\.spectrocloud\.com.*' \
+		--skip "^https:\/\/docs\.spectrocloud\.com.*$$" \
+		--skip "^https:\/\/docs\.spectrocloud\.com\/.*\/supplemental\-packs$$" \
+		--skip "^http:\/\/docs\.spectrocloud\.com.*$$" \
+		--skip "^https:\/\/software-private\.spectrocloud\.com.*$$" \
+		--skip "^\/.*\.md$$" \
+		--skip "!\[.*\]\(.*\)$$" \
+		--skip "\.(jpg|jpeg|png|gif|webp)$$" \
+		--skip "https:\/\/linux\.die\.net\/man\/.*$$" \
+		--skip "https:\/\/mysql\.com\/.*\.*$$" \
+		--skip "https:\/\/dev\.mysql\.com\/doc/\.*$$" \
 		--format json > temp_report.json
 	@# Use jq to filter out links that do not start with http or https and keep only broken links
 	@jq '[.links[] | select(.url | test("^https?://")) | select(.status >= 400)]' temp_report.json > filtered_report.json

docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos.md

@@ -75,8 +75,7 @@ To complete this basic guide, you will need the following items:
   - 8 GB memory
   - 50 GB storage
 
-- [Git](https://cli.github.com/manual/installation). You can ensure git installation by issuing the `git --version`
-  command.
+- [Git](https://git-scm.com/downloads). You can ensure git installation by issuing the `git --version` command.
 
 - [Docker Engine](https://docs.docker.com/engine/install/) version 18.09.x or later. You can use the `docker --version`
   command to view the existing Docker version. You should have root-level or `sudo` privileges on your Linux machine to
@@ -435,8 +434,7 @@ To complete this advanced guide, you will need the following items: <br />
   - 8 GB memory
   - 50 GB storage
 
-- [Git](https://cli.github.com/manual/installation). You can ensure git installation by issuing the `git --version`
-  command.
+- [Git](https://git-scm.com/downloads). You can ensure git installation by issuing the `git --version` command.
 
 - [Docker Engine](https://docs.docker.com/engine/install/) version 18.09.x or later. You can use the `docker --version`
   command to view the existing Docker version. You should have root-level or `sudo` privileges on your Linux machine to

docs/docs-content/clusters/edge/site-deployment/deploy-cluster.md

@@ -76,7 +76,7 @@ To complete this tutorial, you will need the following:
   - 8 GB memory
   - 50 GB storage
 
-- [Git](https://cli.github.com/manual/installation). Ensure git installation by issuing the `git --version` command.
+- [Git](https://git-scm.com/downloads). Ensure git installation by issuing the `git --version` command.
 
 - [Docker Engine](https://docs.docker.com/engine/install/) version 18.09.x or later. You can use the `docker --version`
   command to view the existing Docker version. You should have root-level or `sudo` privileges on your Linux machine to
@@ -487,7 +487,7 @@ is an explanation of the options and sub-command used below:
 - The
   `sh -c "source /edge/vmware/clone_vm_template/setenv.sh && bash /edge/vmware/clone_vm_template/delete-packer-cache.sh"`
   shell sub-command deletes any pre-existing **packer_cache**. A known
-  [issue]((https://github.com/hashicorp/packer-plugin-vsphere/issues/55) with the Packer vSphere plugin causes checksum
+  [issue](https://github.com/hashicorp/packer-plugin-vsphere/issues/55) with the Packer vSphere plugin causes checksum
   logic to ignore previous builds, and reuse previously created ISO found in the **packer_cache** folder. The delete
   script removes any existing packer cache to prevent re-using a previously created ISO.
 

docs/docs-content/clusters/public-cloud/gcp/required-permissions.md

@@ -13,7 +13,7 @@ Ensure the following Google Cloud Platform (GCP) API services are enabled in you
 
 - [Cloud Resource Manager API](https://cloud.google.com/resource-manager/reference/rest)
 - [Compute Engine API](https://cloud.google.com/compute/docs/reference/rest/v1)
-- [Kubernetes Engine API](https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1)
+- [Kubernetes Engine API](https://cloud.google.com/kubernetes-engine/docs/reference/rest)
 
 :::tip
 

docs/docs-content/devx/services/service-listings/mysql.md

@@ -10,10 +10,9 @@ logoUrl: "https://registry.dev.spectrocloud.com/v1/mysql-operator/blobs/sha256:2
 tags: ["devx", "app mode", "pde", "databases"]
 ---
 
-[MySQL](https://www.mysql.com/) is an open-source relational database management system commonly used in web
-applications and other software that requires a database. It is known for its reliability, ease of use, and flexibility.
-MySQL is covered under the GNU license and uses structured query language (SQL) to manage data with the following
-properties:
+[MySQL](https://mysql.com/) is an open-source relational database management system commonly used in web applications
+and other software that requires a database. It is known for its reliability, ease of use, and flexibility. MySQL is
+covered under the GNU license and uses structured query language (SQL) to manage data with the following properties:
 
 - Creates a database for storing and manipulating data and defining the relationship of each table.
 
@@ -120,17 +119,14 @@ kubectl get secret app-tarfful-mysql-2-user \
 #### Output
 
 ```shell hideClipboard
-,U31nQ@T2tN4uM
+****************
 ```
 
 ## Next Steps
 
 You can add MySQL to your application profile and start integrating MySQL with your applications. To learn more about
-integrating MySQL with your applications, check out the [MySQL](https://redis.io/docs/manual/) documentation from
-Oracle.
+integrating MySQL with your applications, check out the [MySQL](https://dev.mysql.com/doc/) documentation from Oracle.
 
 ## Resources
 
 - [MySQL Documentation](https://dev.mysql.com/doc/)
-
-- [MySQL Tutorial](https://dev.mysql.com/doc/refman/8.0/en/tutorial.html)

docs/docs-content/devx/services/service-listings/vault.md

@@ -23,7 +23,7 @@ Vault also tracks who has accessed which secrets and when, making it easier to m
 govern access to secrets, automate application delivery, and consume secrets programmatically.
 
 Vault is deployed behind the scenes through the use of the
-[Bank-Vaults Vault Operator Helm Chart](https://github.com/banzaicloud/bank-vaults/tree/main/charts/vault-operator).
+[Bank-Vaults Vault Operator Helm Chart](https://github.com/bank-vaults/bank-vaults).
 
 <br />
 
@@ -201,4 +201,4 @@ integrating Vault with your applications, check out the
 
 - [HashiCorp Vault Tutorial](https://developer.hashicorp.com/vault/tutorials)
 
-- [Bank-Vaults Vault Operator Helm Chart](https://github.com/banzaicloud/bank-vaults/tree/main/charts/vault-operator)
+- [Bank-Vaults Vault Operator Helm Chart](https://github.com/bank-vaults/vault-helm-chart)

docs/docs-content/integrations/citrix-ipam.md

@@ -46,6 +46,6 @@ Integration deploys the following components:
 
 ## References
 
-- [Citrix IPAM Controller](https://developer-docs.citrix.com/projects/citrix-k8s-ingress-controller/en/latest/crds/vip)
+- [Citrix IPAM Controller](https://docs.netscaler.com/en-us/netscaler-k8s-ingress-controller/configure/ipam-for-ingress.html)
 
-- [Citrix Ingress controller](https://developer-docs.citrix.com/projects/citrix-k8s-ingress-controller/en/latest/network/type_loadbalancer/#expose-services-of-type-loadbalancer-using-an-ip-address-from-the-citrix-ipam-controller)
+- [Citrix Ingress controller](https://docs.netscaler.com/en-us/netscaler-k8s-ingress-controller/#expose-services-of-type-loadbalancer-using-an-ip-address-from-the-citrix-ipam-controller)

docs/docs-content/integrations/cloudanix.md

@@ -128,4 +128,4 @@ data "spectrocloud_pack_simple" "cloudanix" {
 
 ## References
 
-- [Cloudanix Documentation](https://docs.cloudanix.com/introduction)
+- [Cloudanix Documentation](https://www.cloudanix.com/docs/introduction)

docs/docs-content/integrations/falco.md

@@ -39,4 +39,4 @@ use Falco to monitor the run-time security of your Kubernetes applications and i
 
 ## References
 
-- [Falco Helm Chart GitHub](https://github.com/falcosecurity/charts/tree/master/falco)
+- [Falco Helm Chart GitHub](https://github.com/falcosecurity/charts/tree/master/charts/falco)

docs/docs-content/integrations/longhorn.md

@@ -123,7 +123,7 @@ when learning how to use Longhorn.
 
 - [How to Create Volumes](https://longhorn.io/docs/1.4.4/volumes-and-nodes/create-volumes/).
 
-- [Access the Longhorn UI](https://longhorn.io/docs/1.4.4/deploy/accessing-the-ui/)
+- [Access the Longhorn UI](https://longhorn.io/docs/latest/deploy/accessing-the-ui/#accessing-the-longhorn-ui)
 
 - [Longhorn Networking](https://longhorn.io/docs/1.4.4/references/networking/)
 
@@ -175,7 +175,7 @@ when learning how to use Longhorn.
 
 - [How to Create Volumes](https://longhorn.io/docs/1.4.4/volumes-and-nodes/create-volumes/).
 
-- [Access the Longhorn UI](https://longhorn.io/docs/1.4.4/deploy/accessing-the-ui/)
+- [Access the Longhorn UI](https://longhorn.io/docs/latest/deploy/accessing-the-ui/#accessing-the-longhorn-ui)
 
 - [Longhorn Networking](https://longhorn.io/docs/1.4.4/references/networking/)
 

docs/docs-content/integrations/nutanix-csi.md

@@ -36,9 +36,8 @@ platform with Kubernetes by implementing a node controller function.
 
 ## Parameters
 
-The table below lists commonly used parameters you can configure when adding the Nutanix CSI pack. Review the
-[Nutanix CSI Pack](https://github.com/spectrocloud/pax/edit/master/stable/storage/nutanix-csi-2.6.6/README.md) GitHub
-page for a complete parameters list.
+The table below lists commonly used parameters you can configure when adding the Nutanix CSI pack. Review the Nutanix
+CSI Pack README for a complete list of parameters.
 
 | **Parameter**                                   | **Description**                                                                                                        | **Default**      |
 | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ---------------- |
@@ -102,4 +101,3 @@ data "spectrocloud_pack_simple" "nutanix-csi" {
 - [Nutanix Documentation](https://www.nutanixbible.com)
 - [Nutanix Cloud Controller Manager on GitHub](https://github.com/nutanix-cloud-native/cloud-provider-nutanix)
 - [Nutanix CSI Volume Driver Documentation](https://portal.nutanix.com/page/documents/details?targetId=CSI-Volume-Driver-v2_6:CSI-Volume-Driver-v2_6)
-- [Nutanix CSI Pack on GitHub](https://github.com/spectrocloud/pax/tree/master/stable/storage/nutanix-csi-2.6.6)

docs/docs-content/integrations/portworx.md

@@ -72,7 +72,7 @@ The default installation of Portworx will deploy the following components in the
 - [Lighthouse](https://portworx.com/blog/manage-portworx-clusters-using-lighthouse/)
 
 - [Stork](https://github.com/libopenstorage/stork) and
-  [Stork on Portworx](https://docs.portworx.com/portworx-install-with-kubernetes/storage-operations/stork/)
+  [Stork on Portworx](https://docs.portworx.com/portworx-enterprise/platform/openshift/ocp-gcp/operations/storage-operations/stork.html)
 
 - Storage class making use of portworx-volume provisioner.
 
@@ -525,8 +525,6 @@ manifests:
 
 - [Portworx Install with Kubernetes](https://docs.portworx.com/portworx-install-with-kubernetes/)
 
-- [Lighthouse](https://legacy-docs.portworx.com/enterprise/lighthouse-new.html)
-
 - [Installation Prerequisites](https://docs.portworx.com/install-portworx/prerequisites/)
 
-- [Install Portworx on AWS ASG using the DaemonSet](https://docs.portworx.com/install-portworx/cloud/aws/aws-asg/daemonset/)
+- [Install Portworx on AWS ASG](https://docs.portworx.com/portworx-enterprise/install-portworx/kubernetes/aws/aws-asg)

docs/docs-content/integrations/portworx_operator.md

@@ -531,7 +531,7 @@ vsphereSecret:
 
 To activate the Pure Flash Array integration, you will need to create a Kubernetes secret named `px-pure-secret` on your
 cluster containing your
-[Flash Array license JSON](https://docs.portworx.com/portworx-enterprise/cloud-references/auto-disk-provisioning/pure-flash-array.html#deploy-portworx).
+[Flash Array license JSON](https://docs.portworx.com/portworx-enterprise/install-portworx/kubernetes/install-flasharray.html#create-a-json-configuration-file).
 The secret must be created in the namespace that contains the `StorageCluster` resource. The namespace is `portworx` by
 default.
 
@@ -1138,7 +1138,7 @@ vsphereSecret:
 
 To activate the Pure Flash Array integration, you will need to create a Kubernetes secret named `px-pure-secret` on your
 cluster containing your
-[Flash Array license JSON](https://docs.portworx.com/portworx-enterprise/cloud-references/auto-disk-provisioning/pure-flash-array.html#deploy-portworx).
+[Flash Array license JSON](https://docs.portworx.com/portworx-enterprise/install-portworx/kubernetes/install-flasharray.html#create-a-json-configuration-file).
 The secret must be created in the namespace that contains the `StorageCluster` resource. The namespace is `kube-system`
 by default.
 
@@ -1727,7 +1727,7 @@ vsphereSecret:
 
 To activate the Pure Flash Array integration, you will need to create a Kubernetes secret named `px-pure-secret` on your
 cluster containing your
-[Flash Array license JSON](https://docs.portworx.com/portworx-enterprise/cloud-references/auto-disk-provisioning/pure-flash-array.html#deploy-portworx).
+[Flash Array license JSON](https://docs.portworx.com/portworx-enterprise/install-portworx/kubernetes/install-flasharray.html#create-a-json-configuration-file).
 The secret must be created in the namespace that contains the `StorageCluster` resource. The namespace is `kube-system`
 by default.
 
@@ -1910,4 +1910,4 @@ data "spectrocloud_pack_simple" "portworx-operator" {
 
 - [Portworx Central](https://docs.portworx.com/portworx-central-on-prem/install/px-central.html)
 
-- [Flash Array License JSON](https://docs.portworx.com/portworx-enterprise/cloud-references/auto-disk-provisioning/pure-flash-array.html#deploy-portworx)
+- [Flash Array License JSON](https://docs.portworx.com/portworx-enterprise/install-portworx/kubernetes/install-flasharray.html#create-a-json-configuration-file)

docs/docs-content/integrations/prometheus-operator.md

@@ -934,7 +934,7 @@ The Prometheus Operator pack installs the following dependencies:
 ## Parameters
 
 The Prometheus operator supports all the parameters exposed by the kube-prometheus-stack Helm Chart. Refer to the
-[kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stackn)
+[kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack)
 documentation for details.
 
 The Prometheus Operator pack has one parameter you must initialize `grafana.adminPassword`:
@@ -1083,7 +1083,7 @@ The Prometheus Operator pack installs the following dependencies:
 ## Parameters
 
 The Prometheus operator supports all the parameters exposed by the kube-prometheus-stack Helm Chart. Refer to the
-[kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stackn)
+[kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack)
 documentation for details.
 
 The Prometheus Operator pack has one parameter you must initialize `grafana.adminPassword`:

docs/docs-content/integrations/vault.md

@@ -88,7 +88,7 @@ unseal Vault. You can do so by following these steps:
    kubectl port-forward $APP_NAME 8200:8200 --namespace $VAULT_NAMESPACE
    ```
 
-8. Open your browser and access the [Vault UI](https://localhost:8200/ui). You will receive a warning due to using a
+8. Open your browser and access the Vault UI at `https://localhost:8200/ui`. You will receive a warning due to using a
    self-signed certificate, but you can ignore this warning. Follow the prompts on the UI to initialize your root token.
 
 :::tip

docs/docs-content/vertex/system-management/enable-non-fips-settings/use-non-fips-addon-packs.md

@@ -23,10 +23,10 @@ registries. To utilize the entire suite of packs we recommend adding both regist
 [Add a Registry](../add-registry.md) for guidance. Our support team will provide the required credentials to access the
 registries.
 
-| **Registry**                         | **Type** | **Endpoint URL**                                     | **FIPS** | **Base Path** |
-| ------------------------------------ | -------- | ---------------------------------------------------- | -------- | ------------- |
-| **OCI Pack Registry**                | AWS ECR  | https://415789037893.dkr.ecr.us-east-1.amazonaws.com | No       | production    |
-| **Spectro Cloud Community Registry** | AWS ECR  | https://415789037893.dkr.ecr.us-east-1.amazonaws.com | No       | community     |
+| **Registry**                         | **Type** | **Endpoint URL**                                       | **FIPS** | **Base Path** |
+| ------------------------------------ | -------- | ------------------------------------------------------ | -------- | ------------- |
+| **OCI Pack Registry**                | AWS ECR  | `https://415789037893.dkr.ecr.us-east-1.amazonaws.com` | No       | production    |
+| **Spectro Cloud Community Registry** | AWS ECR  | `https://415789037893.dkr.ecr.us-east-1.amazonaws.com` | No       | community     |
 
 :::info