Applies to: 
Kyvos Enterprise 
Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
Kyvos Azure Marketplace Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)
...
Before you begin
In addition to the prerequisites, please ensure the following settings are enabled on your GCP project.
...
Creating resources using script
| Anchor |
|---|
| creatingscript |
|---|
| creatingscript |
|---|
|
Download the terraform.tarfile on your workstation.
On your workstation, install the gcloud command-line tool.
To execute Terraform on Google Cloud Platform's Cloud Shell, activate Cloud Shell.
Configure the gcloud command-line tool to use your project using the following command.
gcloud config set project [MY_PROJECT]
Here, replace [MY_PROJECT] with your project ID.
...
| Panel |
|---|
| panelIconId | atlassian-note |
|---|
| panelIcon | :note: |
|---|
| bgColor | #DEEBFF |
|---|
|
Note After successfully executing the configuration, Terraform will automatically generate a .tfstate file. To create a new file using the same configuration files, first delete the existing deployment configured by those files. To change the sourceImage or kmSourceImage, navigate to the source folder, open the variable.tf file, and update the default value as needed. Possible values in volume type fields: Change the value of the parameter kmCount to 0 in the kyvosparams.tfvars file to go with wizard-based deployment. Once created, you can validateif the resources meet the requirements for installing Kyvos on the Google cloud platform. Post-deployment, for a non-SSH based cluster, if you use an existing Dataproc cluster and a new bucket for automated deployment on GCP, you must execute the dataproc.sh script on the master node of Dataproc after modifying the values of DEPLOYMENT_BUCKET, WORK_DIR, COPY_LIB, and DATAPROC_VERSION to the name of the existing bucket. Then, sync the library and configuration files from the Kyvos Manager on the Dataproc page.
|
...
