Skip to main content

Google Cloud Marketplace Installation

Prerequisites​

To install the issuer node through the Google Cloud Marketplace, you will need:

  • A running Kubernetes cluster (in standard mode).
  • An EXTERNAL IP ADDRESS (Access Type = "external", Region = "Global" and Network Tier = "Premium" will be a good choice).
note

In the following examples, you will see a checkbox labeled "Issuer Network Main Net". If this checkbox is selected, the issuer node will be configured for the Polygon Main network, and in the Ethereum URL field, you should enter the RPC URL for that network. If you do not select this checkbox, the issuer node will be deployed on the Amoy network, and the Ethereum URL field should contain the RPC URL for the Polygon Amoy network.

Install the Application resource definition​

An Application resource is a collection of individual Kubernetes components, such as Services, Deployments, and so on, that you can manage as a group.

To set up your cluster to understand Application resources, run the following command:

kubectl apply -f "https://raw.githubusercontent.com/GoogleCloudPlatform/marketplace-k8s-app-tools/master/crd/app-crd.yaml"

Reverse Hash Service (RHS) Configuration.​

In the following examples of configuring the issuer node for deployment you will be able to see at the end of the form two fields related to the reverse hash service (credential revocation status). Here are some clarifications:

  • If you leave the "Mode of Reverse Hash Service" field blank, the issuer node will be deployed using "None" mode and you should not populate the "URL for RHS" field.
  • If you enter the value "None" in the "Mode of Reverse Hash Service" field then you must not complete the "URL for RHS" field.
  • If you enter the value "OffChain" in the "Mode of Reverse Hash Service" field the "URL for RHS" field must be completed with the URL of the RHS to use.
  • If you enter the value "OnChain" in the "Mode of Reverse Hash Service" field the "URL for RHS" field, you must not complete the "URL for RHS" field.

More about Revocation Status

Key Type for Issuer Identity field.​

Leave it blank for now, it will be useful in the next versions.

UI Authentication​

In the following examples you will see a field called "The password for UI". The value you enter in this field of the form will allow you to authenticate in the Issuer Node UI using the username user-ui and the password entered.

Important Note About the deployment of the issuer node.​

Once the form is completed and the issuer node is deployed, GCP and K8s will perform tasks (such as creating a certificate and a load balancer). These tasks take time (it can take 10 minutes or more), be patient.

Install Issuer Node without domain names​

If you don't own domain names, you can deploy the issuer node through the Google Cloud Marketplace and access the APIs and frontend through a domain name that Google Cloud will generate using the public IP that you provide.

You should pay attention to the The Name of the Reserved External IP field; this field should be filled in with the name of the external IP you have. Then, in the fields related to domain names, you can enter names following the pattern domain-name.XXX.nip.io, where XXX is the number of the IP associated with the name entered in the The Name of the Reserved External IP field. In this example, that IP number is 34.160.87.138.

After pressing "deploy," you should wait a few minutes, and the issuer node will be ready.

Install Issuer Node with domain names​

If you have domain names, the installation process is similar and very simple. You only have to enter the domain names in the corresponding fields and configure the DNS records to point to the external IP of the issuer node.

Here is an example:

After a few minutes, you will be able to enter the registered domains.

Here more information about Google Cloud DNS.