Build a Cloud Provider

Become an Nexqloud provider and make profit on your spare compute made available for tenant lease.

Our curated guide to building your decentralized provider follows these sequential steps.

• STEP 1 - Build the Kubernetes Cluster for your Provider

• STEP 2 - Build your Cloud Provider via Helm Charts

• STEP 3 - Complete a CheckUp of your New Provider

• STEP 4 - Enable GPU Resources on your Cloud Provider

• STEP 5 - Enable Persistent Storage on your Cloud Provider

• STEP 6 - Provider Maintenance

• STEP 7 - Provider Troubleshooting

• STEP 8 - What's Next (Provider Care and Maintenance)

OPTIONAL STEPS

NOTE - the following features are not requirements of an Nexqloud Provider but the enablement of such features may increase demand and tenant lease activity. Consider adding such functionality to your Nexqloud Provider either in initial build or at a later stage.

• TLS Certs for Nexqloud Providers

• IP Leases

• Persistent Storage

• Nexqloud Provider GPU Resource Enablement

VERIFICATIONS AND TROUBLESHOOTING

NOTE - utilize these guides post Nexqloud Provider build to ensure the provider is fully operational and during troubleshooting/maintenance needs.

• Nexqloud Provider Checkup

• Nexqloud Provider Maintenance/FAQ/Troubleshooting

Helm Chart Repository for Nexqloud Providers

The steps outlined above will guide the user through the creation of an Nexqloud Provider and necessary components. The table below clarifies required and optional Helm Charts in the Provider build process.

The Nexqloud Helm Chart repository can be accessed here.

Chart Name	Description
nexqloud-provider	Installs an Nexqloud provider (required)
nexqloud-hostname-operator	An operator to map Ingress objects to Nexqloud deployments (required)
nexqloud-node	Installs an Nexqloud RPC node (required)
nexqloud-inventory-operator	An operator required for persistent storage (optional)
nexqloud-ip-operator	An operator required for ip marketplace (optional)