Yandex Cloud
Поиск
Связаться с намиПодключиться
  • Истории успеха
  • Документация
  • Блог
  • Все сервисы
  • Статус работы сервисов
    • Доступны в регионе
    • Инфраструктура и сеть
    • Платформа данных
    • Контейнеры
    • Инструменты разработчика
    • Бессерверные вычисления
    • Безопасность
    • Мониторинг и управление ресурсами
    • ИИ для бизнеса
    • Бизнес-инструменты
  • Все решения
    • По отраслям
    • По типу задач
    • Экономика платформы
    • Безопасность
    • Техническая поддержка
    • Каталог партнёров
    • Обучение и сертификация
    • Облако для стартапов
    • Облако для крупного бизнеса
    • Центр технологий для общества
    • Партнёрская программа
    • Поддержка IT-бизнеса
    • Облако для фрилансеров
    • Обучение и сертификация
    • Блог
    • Документация
    • Мероприятия и вебинары
    • Контакты, чаты и сообщества
    • Идеи
    • Тарифы Yandex Cloud
    • Промоакции и free tier
    • Правила тарификации
  • Истории успеха
  • Документация
  • Блог
Проект Яндекса
© 2025 ТОО «Облачные Сервисы Казахстан»
Terraform в Yandex Cloud
  • Начало работы
  • Библиотека решений
    • Обзор
    • История изменений (англ.)
          • compute_disk
          • compute_disk_iam_binding
          • compute_disk_placement_group
          • compute_disk_placement_group_iam_binding
          • compute_filesystem
          • compute_filesystem_iam_binding
          • compute_gpu_cluster
          • compute_gpu_cluster_iam_binding
          • compute_image
          • compute_image_iam_binding
          • compute_instance
          • compute_instance_group
          • compute_instance_iam_binding
          • compute_placement_group
          • compute_placement_group_iam_binding
          • compute_snapshot
          • compute_snapshot_iam_binding
          • compute_snapshot_schedule
          • compute_snapshot_schedule_iam_binding

В этой статье:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  • Import
  1. Справочник Terraform
  2. Ресурсы (англ.)
  3. Compute Cloud
  4. Resources
  5. compute_gpu_cluster

yandex_compute_gpu_cluster (Resource)

Статья создана
Yandex Cloud
Обновлена 2 октября 2025 г.
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for timeouts
  • Import

A GPU cluster. For details about the concept, see documentation.

Example usageExample usage

//
// Create a new GPU Cluster.
//
resource "yandex_compute_gpu_cluster" "default" {
  name              = "gpu-cluster-name"
  interconnect_type = "INFINIBAND"
  zone              = "ru-central1-a"

  labels = {
    environment = "test"
  }
}

SchemaSchema

OptionalOptional

  • description (String) Description of the GPU cluster.
  • folder_id (String) ID of the folder that the GPU cluster belongs to.
  • gpu_cluster_id (String) ID of the GPU cluster to return.

To get a GPU cluster ID, make a [GpuClusterService.List] request.

  • id (String) ID of the GPU cluster to return.

To get a GPU cluster ID, make a [GpuClusterService.List] request.

  • interconnect_type (String) Type of interconnect used for this GPU cluster.
  • labels (Map of String) GPU cluster labels as key:value pairs.
  • name (String) Name of the GPU cluster.

The name is unique within the folder.

  • timeouts (Block, Optional) (see below for nested schema)
  • zone (String) ID of the availability zone where the GPU cluster resides.

Read-OnlyRead-Only

  • created_at (String) Creation timestamp.
  • status (String) Status of the GPU cluster.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • read (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
  • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

ImportImport

The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console or YC CLI.

# terraform import yandex_compute_gpu_cluster.<resource Name> <resource Id>
terraform import yandex_compute_gpu_cluster.my_gpu_cluster fv4h4**********u4dpa

Была ли статья полезна?

Предыдущая
compute_filesystem_iam_binding
Следующая
compute_gpu_cluster_iam_binding
Проект Яндекса
© 2025 ТОО «Облачные Сервисы Казахстан»