diff --git a/docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos.md b/docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos.md index 821cd45d5f..9e7b830352 100644 --- a/docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos.md +++ b/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 diff --git a/docs/docs-content/clusters/public-cloud/gcp/required-permissions.md b/docs/docs-content/clusters/public-cloud/gcp/required-permissions.md index 4bdc24c3be..e18b68dc0e 100644 --- a/docs/docs-content/clusters/public-cloud/gcp/required-permissions.md +++ b/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 diff --git a/docs/docs-content/devx/services/service-listings/vault.md b/docs/docs-content/devx/services/service-listings/vault.md index e7427c4c32..28c62861b6 100644 --- a/docs/docs-content/devx/services/service-listings/vault.md +++ b/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).
diff --git a/docs/docs-content/integrations/citrix-ipam.md b/docs/docs-content/integrations/citrix-ipam.md index 27302359d9..fe2fdc0d4c 100644 --- a/docs/docs-content/integrations/citrix-ipam.md +++ b/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) diff --git a/docs/docs-content/integrations/cloudanix.md b/docs/docs-content/integrations/cloudanix.md index 70b91c9b3a..2d175d66ec 100644 --- a/docs/docs-content/integrations/cloudanix.md +++ b/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) diff --git a/docs/docs-content/integrations/falco.md b/docs/docs-content/integrations/falco.md index 49e59820ac..15787d9a98 100644 --- a/docs/docs-content/integrations/falco.md +++ b/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) diff --git a/docs/docs-content/integrations/longhorn.md b/docs/docs-content/integrations/longhorn.md index 375ef98efb..b6b3fe8e74 100644 --- a/docs/docs-content/integrations/longhorn.md +++ b/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/) diff --git a/docs/docs-content/integrations/nutanix-csi.md b/docs/docs-content/integrations/nutanix-csi.md index 3cf11d1492..f69b71549b 100644 --- a/docs/docs-content/integrations/nutanix-csi.md +++ b/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) diff --git a/docs/docs-content/integrations/portworx.md b/docs/docs-content/integrations/portworx.md index b21e0fa264..1a8881baef 100644 --- a/docs/docs-content/integrations/portworx.md +++ b/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) diff --git a/docs/docs-content/integrations/portworx_operator.md b/docs/docs-content/integrations/portworx_operator.md index 9252088742..13cfa78eca 100644 --- a/docs/docs-content/integrations/portworx_operator.md +++ b/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) diff --git a/docs/docs-content/integrations/prometheus-operator.md b/docs/docs-content/integrations/prometheus-operator.md index bc638000fc..e691ade455 100644 --- a/docs/docs-content/integrations/prometheus-operator.md +++ b/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`: diff --git a/docs/docs-content/integrations/vault.md b/docs/docs-content/integrations/vault.md index 2ba38f1384..2bad5981a8 100644 --- a/docs/docs-content/integrations/vault.md +++ b/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