Process to become a provider

1. Preparing the Environment

• Kubernetes (k8s)

  • Cluster The quantity of resources in the k8s cluster is arbitrary. You need to have the "admin.conf" file prepared, which supplies the token for accessing and controlling the cluster.

• Deployment Server

  • Recommended server configuration:

    • CPU: 2 cores

    • Memory: 4GB

    • Bandwidth: 5Mbps

    • Disk: 100GB

  • Please note that this is just the recommended configuration. Lower server configurations are also supported. The stability of the server is more crucial.

1. Connect your wallet to INIChain.

• We are currently at the Testnet stage https://testnet.inichain.com/console

• To become a provider, stake 50-100 INI to be qualified (The final amount will be announced after the Mainnet launch).

• Please fill in the form, so we can airdrop INI to your wallet.

1. Register Identity on the Blockchain

Click "Apply" in the upper right corner, select "Become a Provider" and fill in the application form.

Field Meanings:

• Country: Used to showcase the country where the provider's resources are located for users.

• Email: Email address for contacting the provider.

• Website: Provider's self-displayed homepage.

• Kube Version: Version of Kubernetes (k8s) being used.

• Platform: Indicates the platform (Linux or macOS) on which the deployed k8s is situated.

• URI: The URI for the providerService's listening service gateway access. This domain should point to the deployment server. Port 8443 is the default port for providerService.

• Region: Information about the region where the provider offers resources.

• CPU: information about CPU

1. Submit the application form

2. Writing Configuration Information for providerService

After registering as a provider, click on "Write Config" in the upper right corner of the provider page link, as shown in the image below:

Configuration Explanation:

• NodeUrl: This needs to be configured with the RPC node service of the blockchain. You can use the RPC node provided by the official chain, or you can set up your own node.

• CpuPrice: When making quotes in providerService, this represents the price per one-thousandth of a CPU per second. This parameter represents a precise amount. Since INI has 18 decimal places of precision, 1 represents a charge of 0.001 CPU per second, which is equivalent to 0.000000000000000001 INI.

• MemoryPrice: Similar to above, 1 represents a charge of 1 byte of memory per second, which is equivalent to 0.000000000000000001 INI. For 1GB of memory, the charge is 0.000000001073741824 INI per second.

• StoragePrice: Similar to above, 1 represents a charge of 1 byte of storage per second, which is equivalent to 0.000000000000000001 INI. For 1GB of storage, the charge is 0.000000001073741824 INI per second.

• DeploymentIngressDomain: This configuration represents the primary domain for user access to the deployed service. For example, if configured as ingress.mydomain.com, users might access instances created by the provider's service at addresses like 1u48m3ll0t8q99ri5ojaeabk1c.ingress.mydomain.com. Therefore, when configuring this domain, the provider needs to set up *.ingress.mydomain.com to point to the IP address of the ingress in the k8s cluster.

• SecretKey: This configuration is the plaintext private key of the provider. It can be exported using the MetaMask extension.

• ClusterPublicHostname: This configuration points to the domain of the providerService. An example configuration could be provider.mydomain.com.

• K8sConfigPath: This configuration represents the full path to the admin.conf file for accessing the k8s cluster. An example configuration could be ./admin.conf. Other configurations should be modified as needed once you're familiar with the program in detail.

The following content config the template

{
  "NodeURL":"http://192.168.1.123:30010",--You are advised to use the official or local http service ip address :port need -ethcompatible
  "NodeChainID": "172",
  "CPUPrice": "1000000000", --Order quote cpu a core of 1000 copies, quote precision bit value, chain accuracy of 18 bits
  "MemoryPrice": "10000000", -- quote precision bit value, chain accuracy of 18 bits
  "StoragePrice": "1000000", -- quote precision bit value, chain accuracy of 18 bits
  "SecretKey": "you private key", -- Please enter your private key
  "ProviderAddress": "0x624199661664b9EF607c02D934EA25701076C3B8",-- Please enter your address
  "OrderFactory": "0x495621f53EB82371dA50A256b5637421D3a79776",-- Please enter orderfactory address
  "ProviderContract": "0x725440598D4fE96523D7491FD198fd6D4f5884e5",-- Please enter providercontract address
  "ProviderFactoryContract": "0x000000000000000000000000000000000000C003",
  "ValidatorFactoryContract": "0x000000000000000000000000000000000000C002",
  "BidTimeOut": 600,
  "NameSpace": "ini-service",
  "K8sConfigPath": "./admin.conf", -- Enter the access configuration file path of the k8s cluster
  "Cert": "0xB3ce612Cf77D4e2F7CD6dea0651C90bD0295b2b3",-- Please enter cert address
  "GatewayListenAddress": "0.0.0.0:8443", -- This listening address is used by the provider to provide rpc for ordinary users to query the instance status and communicate with the instance
  "DeploymentIngressDomain":"ingress.daemon.com", -- Configure the domain name you intend for the user
  "DeploymentIngressExposeLBHosts":"false",
  "DeploymentIngressStaticHosts":"true",
  "DeploymentNetworkPoliciesEnabled":"true",
  "ClusterPublicHostname":"provider.daemon.com", -- Configure the domain name for which you provide services to users
  "OvercommitPercentCPU":"0",
  "OvercommitPercentMemory":"0",
  "OvercommitPercentStorage":"0",
  "DeploymentRuntimeClass":"",
  "DockerImagePullSecretsName":"",
  "HostNameServiceListenAddr": "0.0.0.0:28443",
  "HostPruneInterval": 600,
  "HostWebRefreshInterval": 5,
  "HostRetryDelay": 3

}

1. Obtain the providerService Code

See the download link here:https://media.inichain.com/bin/providerService

1. Configure Domain Names

Add DNS (type A) records for your public provider-related domains on your DNS hosting provider.

*.ingress.yourdomain.com

provider.yourdomain.com

• ingress.yourdomain.com should point to the entry nginx within your k8s cluster.

• Provider.yourdomain.com must point to the port monitored by the gatewaylistenaddress provided by the provider service.

Note: Do not use Cloudflare or any other TLS proxy solution to handle your provider DNS A records. Unlike multiple DNS A records for worker nodes, you might consider using CNAME DNS records for simplicity in management and higher availability.

Example using CNAME:

1. Install Ingress for the k8s Cluster

• Install Helm on a Kubernetes Master Node

wget https://get.helm.sh/helm-v3.9.4-linux-amd64.tar.gz

tar -zxvf helm-v3.9.4-linux-amd64.tar.gz

mv linux-amd64/helm /usr/local/bin/helm

• Kubernetes Configurations

kubectl create ns ini-service
kubectl label ns ini-service ini.net/name=ini-service ini.net=true

kubectl create ns ingress-nginx
kubectl label ns ingress-nginx app.kubernetes.io/name=ingress-nginx app.kubernetes.io/instance=ingress-nginx

kubectl create ns lease
kubectl label ns lease ini.net=true
kubectl apply -f ./src/ubicpkg/api/crd_v1.yaml

The location of the crd_v1.yaml file:
https://github.com/Project-InitVerse/ini-provider-service/blob/master/src/ubicpkg/api/crd_v1.yaml

• Copy ini-ingress-1.2.6.tgz file to the machine on which helm is installed

https://media.inichain.com/resources/ini-ingress-1.2.6.tgz

• Unzip the file.

tar xvfg ini-ingress-1.2.6.tgz

• Install the ingress-controller.

helm install ini-ingress ./ini-ingress -n ingress-nginx --set domain=ingress.youdomain.com

TIPS: To install Kubernetes on an uninstalled server, change the ingress port mode from ClusterIP to NodePort

1. Run providerService

nohup ./providerService  >> output.log 2>&1 &