Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Managed Service for Kubernetes
  • Comparing with other Yandex Cloud services
  • Getting started
    • All guides
    • Connecting to a node over SSH
    • Connecting to a node via OS Login
    • Updating Kubernetes
    • Configuring autoscaling
    • Activating a Kubernetes Terraform provider
    • Installing applications from Yandex Cloud Marketplace using Terraform
    • Working with private Docker image registries
      • Connecting to the terminal of a running container
      • Managing pod allocation to nodes
      • Managing workloads
      • Managing storages
      • Managing Service and Ingress resources
      • Managing ConfigMap and Secret resources
      • Managing Kubernetes service accounts
      • Managing namespaces
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes

In this article:

  • Creating a storage resource
  • Editing a storage resource
  • Setting or removing the default storage class
  • Deleting a storage resource
  1. Step-by-step guides
  2. Working with Kubernetes objects from the management console
  3. Managing storages

Managing storages

Written by
Yandex Cloud
Updated at May 5, 2026
  • Creating a storage resource
  • Editing a storage resource
  • Setting or removing the default storage class
  • Deleting a storage resource

Kubernetes storages provide a common file system to pod containers enabling them to store and exchange data. The management console allows you to manage your Kubernetes storage without using kubectl.

Creating a storage resourceCreating a storage resource

You can create storage resources in the management console in the same way as when using the kubectl apply -f <manifest_file.yaml> -n <namespace_name> command.

Management console
  1. In the management console, navigate to the folder dashboard and select Managed Service for Kubernetes.
  2. Click the cluster name and select Storage in the left-hand panel.
  3. In the top-right corner, click Create and select the resource type.
  4. In the drop-down list, select the Namespace to create the resource in.
  5. Fill out the manifest file according to the Kubernetes guide: Persistent Volume Claim, Persistent Volume, storage class.
  6. Click Create.

Editing a storage resourceEditing a storage resource

In the management console, you can edit storage resource manifests in a visual editor. This approach is equivalent to running the kubectl apply -f <manifest_file.yaml> command and allows you to update the resource configuration without re-creating it.

The list of editable fields depends on the object type and is available in this Kubernetes guide.

Management console
  1. In the management console, navigate to the folder dashboard and select Managed Service for Kubernetes.
  2. Click the cluster name and select Storage in the left-hand panel.
  3. Select the tab with the resource type you want to edit.
  4. In the row of the resource, click and select Edit.
  5. Edit the manifest file on the right side of the screen. Your changes will be highlighted with color.
  6. In the top-right corner, click Save.

If the manifest is correct, the changes will be applied. If the updated manifest contains an error or edits uneditable fields, an error message will appear. Click More information for details.

Setting or removing the default storage classSetting or removing the default storage class

The default storage class is used when creating a Persistent Volume Claim, if spec.storageClassName is not specified in its manifest. You can designate multiple storage classes as default classes at the same time. In which case the last created storage class is used when creating a Persistent Volume Claim.

This approach is equivalent to running the kubectl patch storageclass <storage_class_name> -p '{"metadata":{"annotations":{"storageclass.kubernetes.io/is-default-class":"<true-or-false>"}}}' command.

To set or remove the default storage class:

Management console
  1. In the management console, navigate to the folder dashboard and select Managed Service for Kubernetes.
  2. Click the cluster name and select Storage in the left-hand panel.
  3. Select the Storage classes tab.
  4. In the storage class row, click and select Use as default or Don't use as default.
  5. Confirm the action.

Deleting a storage resourceDeleting a storage resource

Deleting a storage resource is equivalent to running the kubectl delete -f <manifest_file.yaml> command.

To delete a storage resource:

Management console
  1. In the management console, navigate to the folder dashboard and select Managed Service for Kubernetes.
  2. Click the cluster name and select Storage in the left-hand panel.
  3. Select the tab containing the resource type you want to delete.
  4. In the row of the resource, click and select Delete.
  5. Confirm the action.

Was the article helpful?

Previous
Managing workloads
Next
Managing Service and Ingress resources
© 2026 Direct Cursus Technology L.L.C.