-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Provider Audit] provider.akash.colnetwork.com #711
Comments
hi @jars101 , First provider attributes:
This key-value pair:
Pertains to persistent storage which your provider doesn't have. Please remove it. The info section needs to be populated as well. Also, your provider is not responding to orders. Please fix those issues then we can continue. thanks, |
Thank you for the update. Please see comments below: a) Pertains to persistent storage which your provider doesn't have. Please remove it. b) The info section needs to be populated as well. c) Also, your provider is not responding to orders. #################################################### ######################################################### |
Unfortunately, I have tried like 20 times to get orders to work but im still unable to do so. Discord channel not being very helpful. I have read the majority of the docs at https://akash.network/docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/ and https://akashengineers.xyz/provider-build-scripts/ multiple times. |
I honestly dont want to give up also when i have bough like 100 AKT already tryhing to set this up. |
Of course not. |
Update: Provider name: provider.akash.colnetwork.com @andy108369 |
Hello, so I redeployed my cluster from scratch and added 2 gpu worker nodes. One with a t4 and one with a rtx 3050 (this one is not yet listed by you so I opened akash-network/provider-configs#37 ) . Please advice if all ok . This is the final production cluster deployment with 3 control plane nodes + multiple workers. |
Prerequisite Steps:
1. Make sure your provider has community provider attributes and your contact details (email, website):
Done
2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)
root@akash-1:/home/user# host aaa.ingress.akash.colnetwork.com
aaa.ingress.akash.colnetwork.com is an alias for akash.colnetwork.com.
akash.colnetwork.com has address 161.10.254.22
3. Please make sure your Akash provider doesn't block any Akash specific ports.
Confirmed
Leave contact information (optional)
The text was updated successfully, but these errors were encountered: