1. Packages
  2. Vkcs Provider
vkcs 0.14.0 published on Tuesday, Dec 30, 2025 by vk-cs

Vkcs Provider

vkcs logo
vkcs 0.14.0 published on Tuesday, Dec 30, 2025 by vk-cs

    Generate Provider

    The Vkcs provider must be installed as a Local Package by following the instructions for Any Terraform Provider:

    pulumi package add terraform-provider vk-cs/vkcs
    

    Overview

    The VKCS provider is used to interact with VKCS services. The provider needs to be configured with the proper credentials before it can be used.

    Use the navigation to the left to read about the available resources.

    Example Usage

    import * as pulumi from "@pulumi/pulumi";
    import * as vkcs from "@pulumi/vkcs";
    
    // Create new compute instance
    const myinstance = new vkcs.ComputeInstance("myinstance", {});
    
    import pulumi
    import pulumi_vkcs as vkcs
    
    # Create new compute instance
    myinstance = vkcs.ComputeInstance("myinstance")
    
    using System.Collections.Generic;
    using System.Linq;
    using Pulumi;
    using Vkcs = Pulumi.Vkcs;
    
    return await Deployment.RunAsync(() =>
    {
        // Create new compute instance
        var myinstance = new Vkcs.ComputeInstance("myinstance");
    
    });
    
    package main
    
    import (
    	"github.com/pulumi/pulumi-pulumi-provider/sdks/go/vkcs/vkcs"
    	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
    )
    
    func main() {
    	pulumi.Run(func(ctx *pulumi.Context) error {
    		// Create new compute instance
    		_, err := vkcs.NewComputeInstance(ctx, "myinstance", nil)
    		if err != nil {
    			return err
    		}
    		return nil
    	})
    }
    
    resources:
      # Create new compute instance
      myinstance:
        type: vkcs:ComputeInstance
    
    package generated_program;
    
    import com.pulumi.Context;
    import com.pulumi.Pulumi;
    import com.pulumi.core.Output;
    import com.pulumi.vkcs.ComputeInstance;
    import java.util.List;
    import java.util.ArrayList;
    import java.util.Map;
    import java.io.File;
    import java.nio.file.Files;
    import java.nio.file.Paths;
    
    public class App {
        public static void main(String[] args) {
            Pulumi.run(App::stack);
        }
    
        public static void stack(Context ctx) {
            // Create new compute instance
            var myinstance = new ComputeInstance("myinstance");
    
        }
    }
    

    Authentication

    The VKCS provider supports username/password authentication. Preconfigured provider file with username and projectId can be downloaded from https://mcs.mail.ru/app/project portal. Go to Pulumi tab > click on the “Download VKCS provider file”.

    # Pulumi.yaml provider configuration file
    name: configuration-example
    runtime:
    config:
        vkcs:password:
            value: PASSWORD
        vkcs:projectId:
            value: PROJECT_ID
        vkcs:username:
            value: USERNAME
    

    Configuration Reference

    • accessToken optional sensitive string → A temporary token to use for authentication. You alternatively can use OS_AUTH_TOKEN environment variable. If both are specified, this attribute takes precedence.
      Note: The token will not be renewed and will eventually expire, usually after 1 hour. If access is needed for longer than a token’s lifetime, use credentials-based authentication.

    • authUrl optional string → The Identity authentication URL.

    • cloudContainersApiVersion optional string → Cloud Containers API version to use.
      Note: Only for custom VKCS deployments.

    • endpointOverrides optional → Custom endpoints for corresponding APIs. If not specified, endpoints provided by the catalog will be used.

      • backup optional string → Backup API custom endpoint.

      • blockStorage optional string → Block Storage API custom endpoint.

      • cdn optional string → CDN API custom endpoint.

      • compute optional string → Compute API custom endpoint.

      • containerInfra optional string → Cloud Containers API custom endpoint.

      • containerInfraAddons optional string → Cloud Containers Addons API custom endpoint.

      • dataPlatform optional string → Data Platform API custom endpoint.

      • database optional string → Database API custom endpoint.

      • iamServiceUsers optional string → IAM Service Users API custom endpoint.

      • ics optional string → ICS API custom endpoint.

      • image optional string → Image API custom endpoint.

      • keyManager optional string → Key Manager API custom endpoint.

      • loadBalancer optional string → Load Balancer API custom endpoint.

      • mlPlatform optional string → ML Platform API custom endpoint.

      • networking optional string → Networking API custom endpoint.

      • publicDns optional string → Public DNS API custom endpoint.

      • sharedFilesystem optional string → Shared Filesystem API custom endpoint.

      • templater optional string → Templater API custom endpoint.

    • password optional sensitive string → Password to login with.

    • projectId optional string → The ID of Project to login with.

    • region optional string → A region to use.

    • skipClientAuth optional boolean → Skip authentication on client initialization. Only applicablie if accessToken is provided.
      Note: If set to true, the endpoint catalog will not be used for discovery and all required endpoints must be provided via endpointOverrides.

    • userDomainId optional string → The id of the domain where the user resides.

    • userDomainName optional string → The name of the domain where the user resides.

    • username optional string → User name to login with.

    Working with VKCS Cloud Storage

    VKCS provider does not support working with cloud storage. To do this, we recommend an AWS provider, you can learn how to use it by following this documentation.

    vkcs logo
    vkcs 0.14.0 published on Tuesday, Dec 30, 2025 by vk-cs
      Meet Neo: Your AI Platform Teammate