GITBOOK-1265: Edit feature discovery upgrade instructions for custom …

…pricing

SUMMARY.md

@@ -120,12 +120,12 @@
       * [STEP 6 - Verify Current Provider Settings](providers/build-a-cloud-provider/akash-provider-checkup/step-6-verify-current-provider-settings.md)
       * [STEP 7 - Additional Verifications](providers/build-a-cloud-provider/akash-provider-checkup/step-6-additional-verifications.md)
       * [Contact Technical Support](providers/build-a-cloud-provider/akash-provider-checkup/contact-technical-support.md)
-    * [GPU Resource Enablement (Optional Step)](other-resources/experimental/build-a-cloud-provider/gpu-resource-enablement-optional-step/README.md)
-      * [GPU Provider Configuration](other-resources/experimental/build-a-cloud-provider/gpu-resource-enablement-optional-step/gpu-provider-configuration.md)
-      * [GPU Node Label](other-resources/experimental/build-a-cloud-provider/gpu-resource-enablement-optional-step/gpu-node-label.md)
-      * [Apply NVIDIA Runtime Engine](other-resources/experimental/build-a-cloud-provider/gpu-resource-enablement-optional-step/apply-nvidia-runtime-engine.md)
+    * [GPU Resource Enablement (Optional Step)](providers/build-a-cloud-provider/gpu-resource-enablement-optional-step/README.md)
+      * [GPU Provider Configuration](providers/build-a-cloud-provider/gpu-resource-enablement-optional-step/gpu-provider-configuration.md)
+      * [GPU Node Label](providers/build-a-cloud-provider/gpu-resource-enablement-optional-step/gpu-node-label.md)
+      * [Apply NVIDIA Runtime Engine](providers/build-a-cloud-provider/gpu-resource-enablement-optional-step/apply-nvidia-runtime-engine.md)
       * [Update Akash Provider](providers/build-a-cloud-provider/gpu-resource-enablement-optional-step/update-akash-provider.md)
-      * [GPU Test Deployments](other-resources/experimental/build-a-cloud-provider/gpu-resource-enablement-optional-step/gpu-test-deployments.md)
+      * [GPU Test Deployments](providers/build-a-cloud-provider/gpu-resource-enablement-optional-step/gpu-test-deployments.md)
     * [TLS Certs for Akash Provider (Optional Step)](providers/build-a-cloud-provider/tls-certs-for-akash-provider-optional-step/README.md)
       * [Install Let's Encrypt Cert Manager](providers/build-a-cloud-provider/tls-certs-for-akash-provider-optional-step/install-lets-encrypt-cert-manager.md)
       * [Configure the Issuer](providers/build-a-cloud-provider/tls-certs-for-akash-provider-optional-step/configure-the-issuer.md)
@@ -329,20 +329,20 @@
       * [Provider Upgrade](other-resources/archived-resources/mainnet5-upgrade-docs/provider-upgrade.md)
     * [Upgrades](other-resources/archived-resources/upgrades/README.md)
       * [Akash Mainnet5 Node Upgrade Guide](other-resources/archived-resources/upgrades/v0.20.0-upgrade-docs.md)
-    * [Provider Build With GPU](providers/build-a-cloud-provider/provider-build-with-gpu/README.md)
-      * [Prepare Kubernetes Hosts](providers/build-a-cloud-provider/provider-build-with-gpu/prepare-kubernetes-hosts.md)
-      * [Disable Search Domains](providers/build-a-cloud-provider/provider-build-with-gpu/disable-search-domains.md)
-      * [Install NVIDIA Drivers & Toolkit](providers/build-a-cloud-provider/provider-build-with-gpu/install-nvidia-drivers-and-toolkit.md)
-      * [NVIDIA Runtime Configuration](providers/build-a-cloud-provider/provider-build-with-gpu/nvidia-runtime-configuration.md)
-      * [Create Kubernetes Cluster](providers/build-a-cloud-provider/provider-build-with-gpu/create-kubernetes-cluster.md)
-      * [Confirm Kubernetes Cluster](providers/build-a-cloud-provider/provider-build-with-gpu/step-7-confirm-kubernetes-cluster.md)
-      * [Helm Installation on Kubernetes Node](providers/build-a-cloud-provider/provider-build-with-gpu/step-4-helm-installation-on-kubernetes-node.md)
-      * [Apply NVIDIA Runtime Engine](providers/build-a-cloud-provider/provider-build-with-gpu/apply-nvidia-runtime-engine.md)
-      * [Test GPUs](providers/build-a-cloud-provider/provider-build-with-gpu/test-gpus.md)
-      * [Akash Provider Install](providers/build-a-cloud-provider/provider-build-with-gpu/akash-provider-install.md)
-      * [Ingress Controller Install](providers/build-a-cloud-provider/provider-build-with-gpu/step-8-ingress-controller-install.md)
-      * [Domain Name Review](providers/build-a-cloud-provider/provider-build-with-gpu/step-5-domain-name-review.md)
-      * [GPU Test Deployments](providers/build-a-cloud-provider/provider-build-with-gpu/gpu-test-deployments.md)
+    * [Provider Build With GPU](other-resources/archived-resources/provider-build-with-gpu/README.md)
+      * [Prepare Kubernetes Hosts](other-resources/archived-resources/provider-build-with-gpu/prepare-kubernetes-hosts.md)
+      * [Disable Search Domains](other-resources/archived-resources/provider-build-with-gpu/disable-search-domains.md)
+      * [Install NVIDIA Drivers & Toolkit](other-resources/archived-resources/provider-build-with-gpu/install-nvidia-drivers-and-toolkit.md)
+      * [NVIDIA Runtime Configuration](other-resources/archived-resources/provider-build-with-gpu/nvidia-runtime-configuration.md)
+      * [Create Kubernetes Cluster](other-resources/archived-resources/provider-build-with-gpu/create-kubernetes-cluster.md)
+      * [Confirm Kubernetes Cluster](other-resources/archived-resources/provider-build-with-gpu/step-7-confirm-kubernetes-cluster.md)
+      * [Helm Installation on Kubernetes Node](other-resources/archived-resources/provider-build-with-gpu/step-4-helm-installation-on-kubernetes-node.md)
+      * [Apply NVIDIA Runtime Engine](other-resources/archived-resources/provider-build-with-gpu/apply-nvidia-runtime-engine.md)
+      * [Test GPUs](other-resources/archived-resources/provider-build-with-gpu/test-gpus.md)
+      * [Akash Provider Install](other-resources/archived-resources/provider-build-with-gpu/akash-provider-install.md)
+      * [Ingress Controller Install](other-resources/archived-resources/provider-build-with-gpu/step-8-ingress-controller-install.md)
+      * [Domain Name Review](other-resources/archived-resources/provider-build-with-gpu/step-5-domain-name-review.md)
+      * [GPU Test Deployments](other-resources/archived-resources/provider-build-with-gpu/gpu-test-deployments.md)
     * [Akash v0.24.0 Network Upgrade](other-resources/archived-resources/akash-v0.24.0-network-upgrade/README.md)
       * [Akash v0.24.0 Node Upgrade Guide](other-resources/archived-resources/akash-v0.24.0-network-upgrade/v0.24.0-upgrade-docs.md)
       * [Akash v0.26.1 Node Upgrade Guide](other-resources/archived-resources/akash-v0.24.0-network-upgrade/v0.26.1-upgrade-docs.md)

akash-nodes/akash-node-deployment-via-omnibus.md

@@ -24,12 +24,12 @@ If you have not used Cloudmos Deploy previously, please use [this guide](https:/
 * To install the Akash Node we will use a custom SDL file
 * Select the “Empty” option so that we can copy/paste the Akash Node SDL in the next step
 
-![](<../.gitbook/assets/manifestSelectInitial (1).png>)
+![](../.gitbook/assets/manifestSelectInitial.png)
 
 * Copy and paste the SDL from [this site](https://github.com/akash-network/cosmos-omnibus/blob/master/akash/deploy.yml) into the Cloudmos SDL editor window
 * **NOTE -** the SDL within GitHub currently has a storage > size value of 120Gi. Omnibus uses a compressed snapshot of the blockchain and when expanded 120GB of storage for the deployment will not be enough. At the time of this writing adjusting the storage size to 350GB will suffice and allow some growth. Please adjust the storage appropriately and as shown in the screenshot below.
 
-![](../.gitbook/assets/sdlWithStorageAdjustment.png)
+![](<../.gitbook/assets/sdlWithStorageAdjustment (1).png>)
 
 * Accept the initial deposit of 5 AKT into the deployment’s escrow account
 * The escrow can be refilled easily within Cloudmos Deploy at any time
@@ -38,21 +38,21 @@ If you have not used Cloudmos Deploy previously, please use [this guide](https:/
 
 * Approve the transaction fee to allow the deployment to continue
 
-![](../.gitbook/assets/transactionFeeDeployAccept.png)
+![](<../.gitbook/assets/transactionFeeDeployAccept (1).png>)
 
 * Select a provider from the bid list
 
 ![](<../.gitbook/assets/bidSelect (1).png>)
 
 * Accept the transaction fee to create a lease with the provider
 
-![](<../.gitbook/assets/bidTransactionFee (1).png>)
+![](../.gitbook/assets/bidTransactionFee.png)
 
 ### Cloudmos Deploy Complete
 
 * Once the deployment is complete the lease details are shown
 
-![](../.gitbook/assets/deploymentComplete.png)
+![](<../.gitbook/assets/deploymentComplete (2).png>)
 
 * After some time the Available/Ready Replicas fields will update to show the current node count. It may be necessary to refresh the screen for this count to update.
 
@@ -67,14 +67,14 @@ With the install of the Akash node complete, it must sync with the blockchain. O
 * While the blockchain snapshot is downloading, the following logs should be visible within Cloudmos
 * We can know that the snapshot download is not yet complete if we see this message in the logs
 
-![](../.gitbook/assets/snapshotDownloading.png)
+![](<../.gitbook/assets/snapshotDownloading (1).png>)
 
 ### Snapshot Download Completed
 
 * After the snapshot download completes the logs will begin showing blockchain sync activity
 * Example output shown should look something like this but with the current blocks on the chain
 
-![](../.gitbook/assets/snapshotDownloadComplete.png)
+![](<../.gitbook/assets/snapshotDownloadComplete (1).png>)
 
 ### Akash Node Verifications
 
@@ -84,7 +84,7 @@ With the install of the Akash node complete, it must sync with the blockchain. O
 
 * Begin by capturing the deployment’s public URI from Cloudmos
 
-![](../.gitbook/assets/nodeUIR.png)
+![](<../.gitbook/assets/nodeUIR (1).png>)
 
 #### Confirm Blockchain Sync
 
@@ -101,7 +101,7 @@ With the install of the Akash node complete, it must sync with the blockchain. O
 * Open [Mintscan](https://www.mintscan.io/akash), a popular blockchain explorer, to compare the captured “latest\_block\_height” value to the latest block displayed in the explorer
 * The block height from the Akash Node and Mintscan will not be exactly match but should be close to each other
 
-![](../.gitbook/assets/mintscanBlockHeight.png)
+![](<../.gitbook/assets/mintscanBlockHeight (1).png>)
 
 #### Confirm Peer Nodes
 

deploy/chia-on-akash.md

@@ -20,7 +20,7 @@ For the following providers who are participating in the sale, expect to see the
 
 ### Required SDL
 
-To make sure you get the sale price from the providers, please Copy and Paste the SDL into [Cloudmos](broken-reference) :
+To make sure you get the sale price from the providers, please Copy and Paste the SDL into [Cloudmos](broken-reference/) :
 
 [BladeBit Summer Sale SDL](chia-on-akash.md#bladebit-ram-plotting)
 
@@ -34,7 +34,7 @@ Please wait up to 60 seconds to see bids from all the providers.
 2. Install [Cloudmos Deploy](https://cloudmos.io/cloud-deploy) and import your AKT wallet address from Keplr.
 3. [Fund your wallet](https://github.com/akash-network/awesome-akash/tree/chia/chia#Quickest-way-to-get-more-AKT)
 
-For additional help we recommend you [follow our full deployment guide](broken-reference) in parallel with this guide.
+For additional help we recommend you [follow our full deployment guide](broken-reference/) in parallel with this guide.
 
 ## How does this work?
 
@@ -275,7 +275,7 @@ deployment:
 To access the Chia Plot Manager, click on the \`Uri\` link on the deployment detail page.\
 To download plots, click an invididual plot in the Chia Plot Manager and click on Download/Open.
 
-![Chia Plot Manager](<../.gitbook/assets/image (13).png>)
+![Chia Plot Manager](<../.gitbook/assets/image (7).png>)
 
 \*Once your download has finished - Delete the plot from the container - to make room for new plots! Plots will continue to be created as long as there is enough free space available in the container (Max 32Tb) and the deployment is fully funded.
 
@@ -334,7 +334,7 @@ Upload your plots to any SSH destination by modifying the `env:`
 
 ### Rclone
 
-Upload your plots to any [Rclone](https://rclone.org/) endpoint! You need to first create a connection to your endpoint on a standard client so that you have a valid configuration in `~/.config/rclone/rclone.conf` You need to modify this block and add  to the end of each line to make it valid for Akash. Below you can find examples of how the `env:` should look.
+Upload your plots to any [Rclone](https://rclone.org/) endpoint! You need to first create a connection to your endpoint on a standard client so that you have a valid configuration in `~/.config/rclone/rclone.conf` You need to modify this block and add to the end of each line to make it valid for Akash. Below you can find examples of how the `env:` should look.
 
 ### Rclone to Dropbox
 

deploy/kava-rpc-node-deployment/kava-rpc-node-deployment.md

@@ -48,7 +48,7 @@
 
 * Accept the Keplr prompt to approve small blockchain fee for lease creation with the selected cloud provider
 
-<figure><img src="../../.gitbook/assets/akashConsoleLeaseFees.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/akashConsoleLeaseFees (1).png" alt=""><figcaption></figcaption></figure>
 
 ## Kava RPC Node Deployment Complete
 

deploy/mine-raptoreum-on-akash-network.md

@@ -4,7 +4,7 @@ description: How to Mine Raptoreum (RTM) on Akash Network
 
 # Mine Raptoreum on Akash Network
 
-![](../.gitbook/assets/raptoreumAkashlytics.png)
+![](<../.gitbook/assets/raptoreumAkashlytics (1).png>)
 
 ## Why use Akash?
 
@@ -99,7 +99,7 @@ deployment:
 
 Akash is a marketplace of compute. Providers set their own prices for compute resources. We recommend you try different providers and check your logs after deployment to determine the hashrate.
 
-![](<../.gitbook/assets/chooseProvider (1).png>)
+![](../.gitbook/assets/chooseProvider.png)
 
 ## How to speed up mining?
 

guides/cloudmos-deploy/wordpress-deployment-example.md

@@ -20,7 +20,7 @@ In this section we will use Cloudmos Deploy to launch an example Minecraft deplo
 * The tool provides several sample templates launch of popular applications
 * Select the `Minecraft` template for our initial deployment
 
-<figure><img src="../../.gitbook/assets/cloudmosSelectTemplate (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/cloudmosSelectTemplate.png" alt=""><figcaption></figcaption></figure>
 
 #### **STEP 4 - Proceed with Deployment**
 

guides/deploy/minesweeper-deployment-example.md

@@ -90,4 +90,4 @@ Access the Deployment's URL via the exposed link.
 
 Example display of the Minesweeper web app within the Akash Deployment.
 
-<figure><img src="../../.gitbook/assets/akashConsoleAccess.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/akashConsoleAccess (1).png" alt=""><figcaption></figcaption></figure>

other-resources/archived-resources/provider-build-with-gpu/README.md

@@ -0,0 +1,18 @@
+# Provider Build With GPU
+
+Use this guide and follow the sequential steps to build your Testnet Akash Provider with GPU support.
+
+* [Prepare Kubernetes Hosts](prepare-kubernetes-hosts.md)
+* [Disable Search Domains](disable-search-domains.md)
+* [Install NVIDIA Drivers & Toolkit](install-nvidia-drivers-and-toolkit.md)
+* [NVIDIA Runtime Configuration](nvidia-runtime-configuration.md)
+* [Create Kubernetes Cluster](create-kubernetes-cluster.md)
+* [Confirm Kubernetes Cluster](step-7-confirm-kubernetes-cluster.md)
+* [Helm Installation on Kubernetes Node](step-4-helm-installation-on-kubernetes-node.md)
+* [Apply NVIDIA Runtime Engine](apply-nvidia-runtime-engine.md)
+* [Test GPUs](test-gpus.md)
+* [Akash Provider Install](akash-provider-install.md)
+* [Ingress Controller Install](step-8-ingress-controller-install.md)
+* [Domain Name Review](step-5-domain-name-review.md)
+* [GPU Test Deployments](gpu-test-deployments.md)
+