Sign inTry Free

Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

Projects

On this page

Projects are used to organize clusters and databases for a specific workload or set of workloads in SingleStore Helios. Projects allow organizations with multiple workloads to conveniently group and manage resources for an application, team, or deployment environment.

Projects and clusters are organized in the following hierarchy:

Organization
└── Project
    ├── Clusters
    └── Databases

Clusters are assigned to a project when they are created and cannot be moved between projects.

Projects and Editions

Edition is set at the project level. An organization can have multiple projects, where each project has a single edition. Multiple projects can have the same edition. Refer to SingleStore Helios Editions for information on supported editions.

All clusters and databases in a project have access to the features available in the selected edition. For example, databases in a project configured with Enterprise Edition have Point in Time Recovery (PITR) available, but databases in a project configured with Standard Edition only support restoring from daily continuous backups.

Use projects to separate resources with different lifecycle, operational, security, governance, or edition requirements. For example:

Environment

Recommended Edition

Purpose

Production

Standard or Enterprise

Production application workloads

Staging

Standard

Pre-production validation and testing

Development

Standard

Application development and integration testing

Sandbox

Shared

Prototypes and lightweight experimentation

To illustrate:

Organization
│
├── app-prod-project (Enterprise/Standard Edition)
│   ├── Production cluster
│   └── Production database
│
├── app-staging-project (Standard Edition)
│   ├── Staging cluster
│   └── Staging database
│
├── app-dev-project (Standard Edition)
│   ├── Development cluster
│   └── Development database
│
└── app-sandbox-project (Shared Edition)
    ├── Development cluster
    └── Development database

Create or Manage Projects

To create a new project or manage existing projects:

  1. Log in to the Cloud Portal.

  2. Select Clusters in the left navigation pane, and then select Manage Projects.

  3. On the Manage Projects dialog:

    Create a Project

    1. Select Create Project. 

    2. In the Name field, enter a name for the project. Use consistent names that identify the application and environment.

    3. From the Edition list, select an edition.

    4. In the Actions column, select the save icon to create the project.

    Manage an Existing Project

    Only the name of an existing project can be updated; its edition cannot be changed.

    A project cannot be deleted while it has active clusters. 

    To update a project, select the three dots in the Actions column of the project, and select one of the following options:

    • Rename: Rename the project.

    • Delete: Delete the project.

To view the clusters in a project, on the Clusters page, select a project from the project filter.

Related Topic

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In