Akash Provider Migration Guide - 0.14.X to 0.16.3
v0.14.x to v0.16.3
Akash version 0.16.3 will introduce changes in CRDs that need to be applied in order to continue operations.
All steps below MUST be executed in the same order as declared and applied to your environment. If any step fails STOP and reach out to the Akash team.

cd ~
vi manifest-purge.sh

#!/usr/bin/env bash
kubectl get mani -n lease -o 'custom-columns=name:{.metadata.name}' --no-headers | \
while read ns; do
# if ns exists, it's a fresh manifest.
if kubectl get ns "$ns" >/dev/null 2>&1; then
echo "FOUND: $ns"
# make sure it's a NotFound error before deleting.
nserr=$(kubectl get ns "$ns" 2>&1)
if [[ "$nserr" == *NotFound* ]]; then
echo "GONE: $ns"
kubectl delete mani "$ns" -n lease

chmod +x ~/manifest-purge.sh


If you are using 3rd-party RPC node ensure upgrade has been applied.
If you are using your own RPC node - as recommended for Providers - ensure the node has been upgraded.

The Akash Provider service is most likely controlled by systemd and if so can be stopped as shown below
systemctl stop akash-provider

Download and extract the v0.16.3 from under the Assets drop-down menu here https://github.com/ovrclk/akash/releases/tag/v0.16.3 for your OS & Architecture.
Replace the old akash binary with the new one.

[email protected]:/home/ubuntu# akash version

wget https://raw.githubusercontent.com/ovrclk/akash/mainnet/main/pkg/apis/akash.network/crd.yaml

akash provider migrate v0.14tov0.16 --crd ./crd.yaml

[email protected]:~# akash provider migrate v0.14tov0.16 --crd ./crd.yaml
using kube config file /root/.kube/config
checking manifests to backup
checking providers hosts to backup
total to backup
manifests: 1
provider hosts: 1
backup manifests
backup manifests DONE
backup provider hosts
backup provider hosts DONE
applying CRDs
customresourcedefinition.apiextensions.k8s.io "manifests.akash.network" deleted
customresourcedefinition.apiextensions.k8s.io "providerhosts.akash.network" deleted
customresourcedefinition.apiextensions.k8s.io/manifests.akash.network created
customresourcedefinition.apiextensions.k8s.io/providerhosts.akash.network created
applying CRDs DONE
applying manifests
manifest "mbamrdgl7ser2f253ubem42r074vsi6aj6c6a4bldfgq4" has been migrated successfully
applying manifests DONE
applying hosts
provider host "c5o7gdvuodea90sgpm7v3rt0d0.ingress.akashtesting.xyz" has been migrated successfully
applying hosts DONE

systemctl start akash-provider

cat /etc/systemd/system/akash-hostname-operator.service
Description=Akash Hostname Operator
ExecStart=akash provider hostname-operator

systemctl start akash-hostname-operator
systemctl enable akash-hostname-operator

  • Make a test deployment and ensure the DSEQ hits provider logs and that you can create deployment/lease and send manifest
journalctl -u akash-provider --since '5 min ago' -f

If you are using Helm Charts for installing the Akash Provider and wishing to upgrade to 0.16.3, then run the same commands you have previously used with adding --set image.tag="0.16.3" on the command line like in the example below.

If you are using a 3rd-party RPC node ensure upgrade has been applied.
If you are using your own RPC node - as recommended for Providers - ensure the node has been upgraded.

kubectl scale deploy -n akash-services akash-provider --replicas=0
Update Current CRDs
kubectl apply --server-side -f https://raw.githubusercontent.com/ovrclk/helm-charts/main/charts/akash-provider/templates/crds.yaml

helm repo add akash https://ovrclk.github.io/helm-charts
helm repo update

helm upgrade akash-node akash/akash-node -n akash-services ... --set image.tag="0.16.3"
helm upgrade akash-provider akash/provider -n akash-services ... --set image.tag="0.16.3"
helm upgrade hostname-operator akash/hostname-operator -n akash-services ... --set image.tag="0.16.3"

kubectl scale deploy -n akash-services akash-provider --replicas=1

Migrate command creates a directory to backup kubernetes objects. By default it is the current directory. It can be changed with --k8s-crd-migrate-path flag Directory content is preserved after success. Delete it IF and ONLY IF migration has been successful.
Copy link
On this page
Precursor to Upgrade - Orphan Manifest Purge
Create Script File
Populate Script File
Make Script Executable
Execute Script
Provider Service Running on Bare Metal/VM
STEP 1 - Upgrade RPC node to 0.16.3
STEP 2 - Stop provider service
STEP 3 - Upgrade Akash Version
STEP 4 - Ensure Akash Client Upgrade
STEP 5 - Download v0.16.3 Provider CRDs
STEP 6 - Install v0.16.3 CRDs
STEP 7 - Start provider service
STEP 8 - Create the Hostname Operator Service
STEP 9 - Start the Hostname Operator Service
STEP 10 - Check Status of Provider
Provider Service Running in Kubernetes via Helm Charts
STEP 1 - Upgrade RPC node to 0.16.3
STEP2 - Upgrade Provider
Additional Notes