Applies to: Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
Kyvos Azure Marketplace Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)
In the automated deployment method, you must use the scripts to create all the resources and services required for installing and deploying the Kyvos cluster in your GCP environment.
To create resources, see the Creating Kyvos Resources for GCP using Script section for more details.
Important
Download the GCP Installation Files folder and keep the requisite files handy.
After creating resources using scripts, the configuration of the Kyvos GCP cluster on Kyvos Manager is no longer needed. Once the resources have been created successfully, you must log in to Kyvos Manager. Upon logging in, the deployment of the Kyvos cluster will start automatically. You can verify the 'Cluster Deploy' on the Operations page of the Kyvos Manager.
Important
Before proceeding with the installation and deployment, please ensure that you have all the prerequisites.
GCP automated deployment supports the Kyvos cluster deployment in the following cases:
When all the resources are created in the same deployment
When an existing Dataproc or external Dataproc cluster is used in the same deployment
Tip
To proceed with wizard-based deployment, change the value of the parameter kmCount to 0 in the kyvos-template.yaml file (provided in the Installation Files folder).
To deploy the Kyvos cluster with password-based authentication and custom hostnames, you must use the wizard-based deployment, as these features are not supported in the automated deployment.
Post-deployment, for a non-SSH based cluster, if you use an existing Dataproc cluster and a new bucket, you must execute the dataproc.sh script (provided in the Installation Files folder) 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 in the Common Configuration section.