Vectice Docs
API Reference (Latest)Vectice WebsiteStart Free Trial
Latest
Latest
  • 🏠Introduction
    • Vectice overview
      • Autolog
      • Next-Gen Autolog [BETA]
      • AskAI
      • Vectice for financial services
  • 🏁Quickstart
    • Getting started
    • Quickstart project
    • Tutorial project
    • FAQ
  • ▶️Demo Center
    • Feature videos
  • 📊Manage AI/ML projects
    • Organize workspaces
      • Create a workspace
      • Workspace Dashboard
    • Organize projects
      • Create a project
      • Project templates best practices
    • Invite colleagues
    • Define phase requirements
    • Collaborate with your team
  • 🚀Log and Manage Assets with Vectice API
    • API cheatsheets
      • Vectice Python API cheatsheet
      • Vectice R API cheatsheet
    • Connect to API
    • Log assets to Vectice
      • Autolog your assets
      • Log datasets
      • Log models
      • Log attachments and notes
      • Log code
      • Log a custom data source
      • Log assets using Vectice IDs
      • Log dataset structure and statistics
      • Log custom metadata in a table format
      • Log MLFLow runs
    • Retrieve assets from app
    • Manage your assets
    • Manage your iteration
    • Preserve your code and asset lineage
  • 🤝Create Model documentation and reports
    • Create model documentation with Vectice Reports
    • Streamline documentation with Macros
    • Auto-document Models and Datasets with AskAI Prompts
    • Document phase outcomes
  • 🗂️Admin Guides
    • Organization management
    • Workspace management
    • Teams management
    • User management
      • User roles and permissions
      • Update a user role in your organization
      • Activate and deactivate users
      • Reset a user's password
    • Manage report templates
  • 🔗Integrations
    • Integrations Overview
    • Integrate Vectice with your data platform
  • 💻IT & Security
    • IT & Security Overview
    • Secure Evaluation Environment Overview
    • Deployment
      • SaaS offering (Multi-Tenant SaaS)
      • Kubernetes self-hosted offering
        • General Architecture & Infrastructure
        • Kubernetes on GCP
          • Appendices
        • Kubernetes on AWS
          • Appendices
        • Kubernetes on Azure
          • Appendices
        • GCP Marketplace deployment
        • On premise
        • Configuration
      • Bring Your Own LLM Guide
    • Data privacy
    • User management
    • SSO management
      • Generic SAML integration
      • Okta SSO integration
    • Security
      • Data storage security
      • Network Security
        • HTTPS communication
        • Reverse proxy
        • CORS/CSRF
        • VPC segregation
      • Sessions
      • Secrets and certificates
      • Audit logs
      • SOC2
      • Security updates
      • Best practices
      • Business continuity
    • Monitoring
      • Installation guide
      • Customizing the deployments
    • Maintenance & upgrades
    • Integrating Vectice Securely
  • ⭐Glossary
    • Concepts
      • Workspaces
      • Projects
        • Setup a project
      • Phases
      • Iterations
        • Iterative development
      • Datasets
        • Dataset resources
        • Dataset properties
        • Dataset lineage and versions
      • Models
      • Reports
  • 🎯Release notes
    • Release notes
  • ↗️References
    • Vectice Python API Reference
    • Vectice R API Cheatsheet
    • Notebooks and code samples
    • Vectice website
Powered by GitBook
On this page
  • Appendix 1: Creating the Cloud SQL instance and the two databases
  • Appendix 2: Create Bucket and Service account
  • Bucket creation
  • IAM role creation
  • Appendix 3: Creating the Kubernetes cluster
  • Cluster creation
  • Appendix 4: Disaster recovery plan
  • Backup strategy
  • Recovery mechanism

Was this helpful?

  1. IT & Security
  2. Deployment
  3. Kubernetes self-hosted offering
  4. Kubernetes on GCP

Appendices

PreviousKubernetes on GCPNextKubernetes on AWS

Last updated 1 year ago

Was this helpful?

Appendix 1: Creating the Cloud SQL instance and the two databases

Find here the instructions for creating the Cloud SQL Instance with PostgreSQL 13.X and the two databases necessary: keycloak and vectice

Type Cloud SQL in the search bar and reach the first page. Go to the SQL menu, and press CREATE INSTANCE

We’ll then input the instance name, the master user, and password.

Then, create the two databases, vectice and keycloak, from the menu “Databases,” CREATE DATABASE, create Vectice, and then redo the operation for keycloak.

Appendix 2: Create Bucket and Service account

Find the instructions for creating the role, the service account, and the GCS Bucket.

The role will be attached to the service account to obtain permission to read/write the GCS Bucket. The Bucket is used for storing asset metadata from Models, Datasets, Notes, and Graphs.

Bucket creation

  1. Type Cloud Storage in the search bar and view the first page.

  2. Go to Cloud Storage, Buckets menu, and Press CREATE.

  3. Fill in the settings as in the screenshot below.

IAM role creation

  1. Type IAM in the search enginer.

  2. Create an IAM role with the following permissions:

In this example, it will be named “bucket-storage”.

Service account creation

Assign the IAM role previously created to the service account.

Appendix 3: Creating the Kubernetes cluster

Cluster creation

Type Kubernetes Engine in the search bar and reach the first page. Then click on the CREATE button.

Follow the steps in the console, like in the screenshots below.

Once you select the create button, the cluster creation will take about 30 minutes to build the Cluster, Control Plan, NodePool, and Nodes.

Appendix 4: Disaster recovery plan

Backup strategy

As there is no persistent data on the Kubernetes Cluster, no backup of the Cluster is necessary. At the minimum, we recommend a daily Backup of the GCS Bucket and the Cloud SQL instance.

Recovery mechanism

Learn more about our and .

The default Cloud SQL instance backup strategy is a daily backup of the whole instance. Backups can also be customized. More information can be found in this . For the Bucket, we recommend making a copy of the Bucket content and placing it in another Bucket, in a folder named with a timestamp to create at each backup.

Depending on the nature of the disaster, recovery solutions might change. In case of an infrastructure issue, please refer to the section; to recreate the defaulting infrastructure elements. The restoration of Bucket content consists of copying the content of the time-stamped folder described in the Backup strategy section to the application GCS Bucket on which the helm vectice configuration aims at. The restoration of the Cloud SQL instance consists of restoring the database backup following the . If the issue requires the creation of a new Kubernetes Cluster, for example, in a new region, please refer to the section: to redeploy the software. Make sure to fill in the values according to your new environment deployment.

💻
GCP documentation
data storage
backup policies
GCP documentation
Provisioning the infrastructure
Application deployment