Deploy an Akash Provider with kubeadm, containerd, gvisor (docker-less!)

This write-up follows you through the necessary configuration & setup steps required for you to run the Akash Provider on your own Linux distro. (I used x86_64 Ubuntu Focal).
The steps to register and activate Akash Provider are also included.

Continue reading here:

My organization is interested in becoming an Akash cloud provider. I would like to use a RancherOS for the underlying operating system, as not only is it really the ideal platform for Kubernetes for many reasons, but being so lightweight I think it will be the best OS to get the most out of the cloud resources we provide.
Am I correct that this how-to should work for setting up the Akash cloud provider infrastructure?

Hello, thank you for the guide.

I have almost finished the configuration in a single master/worker node. But I have a problem with the network being able to connect with my node. I registered the provider in the blockchain in “europe” And got a public domain registering my node in a localhost exposer in, I have tried to open my port in the firewall. But Akash still can’t connect with my port. I have also listed the cluster external nodes, and I see that they are very different listening ports. As you can see in the image.

Sorry if this is very ignorant but what is the workaround here? Should I try to change the cluster ports, do any port forwarding, allow my node to receive HTTPS connections… I would appreciate any help so thank you a lot in advance.

Cluster ports:

Hi @danielrgc97 !
8443/tcp port is the akash provider run service that is listening at, so there is no need to configure anything in the Kubernetes for it :wink:

  1. check akash-provider.service it is running
  2. if it is running, then you should be able to access it over 8443/tcp (self-signed certs are expected there)

you can also query it using curl -k command.

Right now your port is locked, most likely firewall is blocking it or the akash-provider.service is not running:

$ curl -k ""
curl: (7) Failed to connect to port 8443: Connection refused

Thank you a lot for your help. Unfortunately, I couldn’t connect.
I have checked and the service is running but I can’t see the port 8443 listening in my node (maybe I am using the wrong command).
But apart from that, I think the main problem is with tunnelto, which is only exposing the http ports, so it won’t respond to port 8443 anyway. :sob:

But thank you anyway for your help, and great post!