Skip to main content
Version: Cloud

OHVcloud resources

We advice to run Deeploy on the following managed OVHcloud services:

  • Managed Kubernetes: Manged Kubernetes to run the deeploy software and AI/ML deployments
  • Managed PostgreSQL Managed PostgreSQL database to store application and AI/ML deployment data
  • Object storage: Object storage to store repository and model files and artifacts
  • Key management system: Key management and encryption to story sensitive data encrypted in the database

For production workloads, we advise to manage the cloud resources in code. OVH provides providers to manage you infrastructure as code. See the Terraform documentation for Terraform/OpenTofu providers.

Managed Kubernetes​

We suggest using a managed Kubernetes cluster (Stateless).

To set up Managed Kubernetes for your Deeploy installation, follow the steps outlined in this guide. Keep in mind the following specific considerations:

  • For normal usage, Deeploy requires approximately 3 medium nodes; minimal requirements: 3 (v)CPU and 6 GB RAM.
  • Kubernetes version: we advise to use only standard supported versions to prevent extra costs.
  • Enable cluster autoscaling. This prevents running into resource limits, but take into account this also results in dynamic costs.

GPU support​

For GPU support we recommend attaching an autoscaling node group with your preferred GPU node type that can scale to 0 to your cluster. To make sure no other pods will be scheduled on GPU nodes you can add the following taint to your node pool:

taints:
- key: nvidia.com/gpu
  value: present
  effect: NoSchedule

When specifying a GPU node for a Deeploy deployment, automatically the nvidia.com/gpu label will be applied. To make sure you can select the nodes that are scaled to 0 in Deeploy, add a list of node types to the values.yaml file when you install the Deeploy Helm chart.

Read more about our NVIDIA integration here

Managed PostgreSQL​

To set up a Managed PostgreSQL database for your Deeploy installation, follow the steps outlined in this guide. Take into account the following considerations:

  • Align the network configuration of the database with the managed Kubernetes cluster. Read more about private networking here. This will allow for data transfers over the internal network.
  • Implement best practices for backing up and restoring data at any point in time, as described in this article.
  • Create a separate user with admin rights only on the required databases (deeploy and deeploy-kratos). Save the user credentials to use in the Helm values.yaml file that you use in the Deeploy Helm installation.

Database configuration​

Make sure that the Postgres database server has the following two databases:

  1. deeploy
  2. deeploy_kratos
info
  • A single user should have administrative rights on both databases.
  • The databases should have at least one (public) database schema.

Object storage​

To set up a object storage, use this guide. Keep in mind the following considerations:

  • Deeploy follows OVHcloud to use the AWS S3 client to communicate with the OVHcloud object storage. So use the AWS object storage values for you OVHcloud object storage.
  • Configure the following minimal s3 policy using this guide:
{.
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
         "s3:ListBucket",
         "s3:GetBucketLocation",
         "s3:ListBucketMultipartUploads",
         "s3:ListBucketVersions",
       ],
      "Resource": [
         "arn:aws:s3:::<YOUR-BUCKET-NAME>"
       ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "s3:*Object*",
        "s3:ListMultipartUploadParts",
        "s3:AbortMultipartUpload",
      ],
      "Resource": [
         "arn:aws:s3:::<YOUR-BUCKET-NAME>/*"
      ]
    }
  ]
}

Key management system​

To set up a Key management, use this guide, keep in mind the following considerations:

  • This feature is still and beta and not publicly released, contact us to get access to it

Resource health​

We suggest setting up Service Logs for monitoring and alerting related to resource health. If you suspect an issue with your OVHcloud Resources, check out the status dashboard.

Estimation of costs​

Next to the Deeploy license costs, OVHcloud will bill you for the cloud resources. Check the expected costs here.

Next steps​