NOTE - do NOT use these instructions until they have been migrated out of experimental and the Akash core team has communicated it is safe to execute.
The following provides an overview of the steps necessary to upgrade your Akash provider to version 0.5.0
and to enable Feature Discovery:
- Download Helm Chart and Use Feature Discovery Branch
- Akash Hostname Operator Upgrade
- Akash Provider Upgrade
- Akash IP Operator Upgrade (If Applicable)
- Akash Inventory Operator Install/Upgrade
- Update Ingress Controller
- Verifications
- Testing
NOTE - complete the steps in this guide in the order presented
Download Helm Chart and Use Feature Discovery Branch
Clone Akash Helm Chart Repository
Checkout Feature Discovery Branch of Helm Chart Repo
Expected Output
Akash Hostname Operator Upgrade
Akash Provider Upgrade
NOTE - these instructions assume your Akash Provider settings are stored in
/root/provider/provider.yaml
. If this is not the cause - dump current provider settings prior to initiating this process via the following command and ensure thehelm install
command points to the location of this file.
helm -n akash-services get values akash-provider > provider.yaml
NOTE - provider GPU attributes must now adhere to the naming conventions in this JSON file. Your attributes may need to be updated to follow these standards. If your provider attributes do not adhere to the naming conventions in this JSON file it may not bid when specific models are included in the SDL.
NOTE - if your provider uses a custom price script - ensure to add pointer to that script in the
helm install
command such as the following. Note that this syntax assumes the pricing script resides in the/root/provider
directory.
--set bidpricescript="$(cat /root/provider/price_script_generic.sh | openssl base64 -A)"
Akash IP Operator Upgrade (If Applicable)
NOTE - the IP Operator is only necessary if your Akash Provider provides IP Leases
Akash Inventory Operator Install/Upgrade
NOTE - the Inventory Operator is now required on ALL Akash Providers. Previously this operator was only required when the Provider hosted persistent storage. But the operator is now mandated on all providers.
NOTE - if your provider hosts persistent storage, ensure that the CEPH cluster is in a healthy state prior to upgrading the Akash Inventory Operator
STEP 1
NOTE - if you do not have a prior installation of the inventory operator the uninstall command will produce an error. Disregard the error and proceed to next step.
STEP 2
NOTE - this step is only necessary for providers hosting persistent storage
Within the values.yaml
file ensure that the inventoryConfig
section is updated with your persistent storage type - I.e. beta1
, beta2
, or beta3
.
STEP 3
Update Ingress Controller
NOTE - this step must be completed by all providers to expose the Feature Discovery gRPC port
NOTE - ensure to open port
8444
on your firewall if necessary as well
The Ingress Controller rules have been updated to include Feature Discovery destinations and mainly port 8444
. Update your ingress controller to ensure they are current via the instructions in this doc section.
Verifications
- Verify the status of the Akash Provider and Akash Operators following the upgrade
Example/Expected Output
Note - pay particular attention to the presence of the
operator-inventory-hardware-discovery
. One such pod should be spawned for each Kubernetes worker node.
Testing
Test your Akash Provider’s Feature Discovery functionality via the use of gRPC CuRL and examples provided below. If you do not have gRPC CuRL installed - follow the instructions in this guide to install via brew.
Template
- Replace
<PROVIDER-IP-ADDRESS>
with actual