[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"/en/kb/manual/creating-and-configuring-cluster-kubernetesKbData":3},{"page":4,"pages":115,"recommendedPages":116,"category":41,"categoryTree":41,"total":122,"currentOrder":145,"activeManualCategoryId":41,"tag":-1},{"route":5,"uuid":8,"title":9,"excerpt":10,"content":11,"view_count":12,"published_at":13,"modified_at":13,"like":14,"category":17,"hero_image":34,"seo_metadata":35,"schema_org_metadata":39,"open_graph_metadata":42,"sections":43,"tags":110,"breadcrumbs":111,"images":114},{"language":6,"path":7},"en","/kb/manual/creating-and-configuring-cluster-kubernetes","19bf67e4-040e-b8f7-d416-d1b12decef5d","Creating and Configuring a Kubernetes Cluster","A Kubernetes cluster (K8s cluster) is a group of servers (nodes) that are grouped together to run and manage containerized applications. For more information on how a cluster works, see the article “Kubernetes Basics”.","\u003Cp>A Kubernetes cluster (K8s cluster) is a group of servers (nodes) that are grouped together to run and manage containerized applications. For more information on how a cluster works, see the article “\u003Ca href=\"https://beget.com/en/kb/manual/what-is-kubernetes\">Kubernetes Basics\u003C/a>”.\u003C/p>\n\u003Cp>To create a cluster, go to the “\u003Ca href=\"https://cp.beget.com/cloud?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=kubernetes_sozdanie_klastera&amp;utm_content=cp_cloud\">Cloud\u003C/a>” section of the control panel, click “Create Service”, and select “Kubernetes Cluster”.\u003C/p>\n\u003Ch2 id=\"name-and-region\">Name and Region\u003C/h2>\n\u003Cp>Enter the cluster name and select the region. Currently, only one region is available: Russia, Saint Petersburg.\u003C/p>\n\u003Ch2 id=\"control-plane\">Control Plane\u003C/h2>\n\u003Cp>The control plane consists of Kubernetes components in the cloud infrastructure that are responsible for coordinating the cluster and are deployed on dedicated master nodes. You need to select the number of master nodes and the Kubernetes version.\u003C/p>\n\u003Ch3 id=\"number-of-master-nodes\">Number of master nodes\u003C/h3>\n\u003Cp>This parameter determines the cluster's fault tolerance:\u003C/p>\n\u003Cp>\u003Cstrong>1 master node – for development and testing.\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>Minimum cost\u003C/li>\n\u003Cli>If a master node fails, applications that are already running continue to operate normally, but the cluster’s internal functions become unavailable: you cannot create or modify resources, schedule new pods, or execute kubectl commands\u003C/li>\n\u003Cli>Any maintenance (updates, restarts) results in the temporary unavailability of cluster management\u003C/li>\n\u003C/ul>\n\u003Cp>\u003Cstrong>3 master nodes – for production environments.\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>If one master node fails, cluster management continues to operate without interruption\u003C/li>\n\u003Cli>Updates and maintenance are possible without loss of control\u003C/li>\n\u003Cli>The cluster state is replicated across nodes (etcd quorum – a majority of nodes is sufficient for decision-making)\u003C/li>\n\u003Cli>The cost is higher, but it ensures the fault tolerance of the control loop\u003C/li>\n\u003C/ul>\n\u003Cdiv class=\"wp-block-beget-alert alert-block alert-block-info\">\n\u003Cdiv class=\"alert-block-title\">\u003Cstrong>Please note!\u003C/strong>\u003C/div>\n\u003Cdiv class=\"alert-block-content\">If master nodes fail in any configuration, applications already running on worker nodes continue to operate. Only cluster management becomes unavailable: creating, modifying, and deleting resources, as well as scheduling new pods.\u003C/div>\n\u003C/div>\n\u003Cp>\u003Cstrong>How to choose:\u003C/strong> if uninterrupted cluster management is important to you (deploying, scaling, responding to incidents), choose 3 master nodes. For dev/test environments, where brief periods of management unavailability are acceptable, one is sufficient.\u003C/p>\n\u003Cdiv class=\"wp-block-beget-alert alert-block alert-block-info\">\n\u003Cdiv class=\"alert-block-title\">\u003Cstrong>Please note!\u003C/strong>\u003C/div>\n\u003Cdiv class=\"alert-block-content\">You can change the number of master nodes after creating the cluster by contacting technical support.\u003C/div>\n\u003C/div>\n\u003Ch3 id=\"kubernetes-version\">Kubernetes Version\u003C/h3>\n\u003Cp>Select a Kubernetes version for the cluster.\u003C/p>\n\u003Cul>\n\u003Cli>The latest stable version is selected by default\u003C/li>\n\u003Cli>The version determines the available APIs and component behavior\u003C/li>\n\u003Cli>Use the latest stable version unless you have specific compatibility requirements\u003C/li>\n\u003C/ul>\n\u003Cp>You can upgrade to a newer version after deploying the cluster. For more details, see the “\u003Ca href=\"https://beget.com/en/kb/manual/cluster-management-kubernetes\">Cluster Management\u003C/a>” article.\u003C/p>\n\u003Ch2 id=\"configuring-the-cluster-network\">Configuring the Cluster Network\u003C/h2>\n\u003Cp>Network settings determine how IP addresses are assigned to cluster components. These settings affect scalability, the number of pods, nodes, and services that can be in the cluster.\u003C/p>\n\u003Cdiv class=\"wp-block-beget-alert alert-block alert-block-info\">\n\u003Cdiv class=\"alert-block-title\">\u003Cstrong>Please note!\u003C/strong>\u003C/div>\n\u003Cdiv class=\"alert-block-content\">Network settings cannot be changed after the cluster is created. If changes are necessary, contact technical support.\u003C/div>\n\u003C/div>\n\u003Ch3 id=\"service-address-range\">Service Address Range\u003C/h3>\n\u003Cp>IP addresses for internal Kubernetes services (kube-dns, API server, and others).\u003C/p>\n\u003Cul>\n\u003Cli>Default starting address: \u003Ccode>10.96.0.0\u003C/code>\u003C/li>\n\u003Cli>Allowed networks: \u003Ccode>10.0.0.0/8\u003C/code>, \u003Ccode>172.16.0.0/12\u003C/code>, \u003Ccode>192.168.0.0/16\u003C/code>\u003C/li>\n\u003Cli>CIDR: from \u003Ccode>/16\u003C/code> to \u003Ccode>/24\u003C/code>\u003C/li>\n\u003C/ul>\n\u003Cp>All internal services in the cluster receive an address from this range.\u003C/p>\n\u003Ch3 id=\"pod-address-range-pod-cidr\">Pod Address Range (Pod CIDR)\u003C/h3>\n\u003Cp>IP addresses assigned to pods.\u003C/p>\n\u003Cul>\n\u003Cli>Default starting address: \u003Ccode>10.244.0.0\u003C/code>\u003C/li>\n\u003Cli>Allowed networks: \u003Ccode>10.0.0.0/8\u003C/code>, \u003Ccode>172.16.0.0/12\u003C/code>, \u003Ccode>192.168.0.0/16\u003C/code>\u003C/li>\n\u003Cli>CIDR: from \u003Ccode>/16\u003C/code> to \u003Ccode>/24\u003C/code>\u003C/li>\n\u003C/ul>\n\u003Cp>Each pod in the cluster receives a unique IP address from this range.\u003C/p>\n\u003Ch3 id=\"node-subnet-mask\">Node subnet mask\u003C/h3>\n\u003Cp>Determines how many pods can be hosted on a single node.\u003C/p>\n\u003Cul>\n\u003Cli>Value: from \u003Ccode>/22\u003C/code> to \u003Ccode>/28\u003C/code>\u003C/li>\n\u003C/ul>\n\u003Cp>Each worker node receives its own subrange of addresses from the Pod CIDR. The size of this subrange is determined by the node subnet mask.\u003C/p>\n\u003Ch3 id=\"how-the-parameters-are-related\">How the parameters are related\u003C/h3>\n\u003Cp>The pod range, node subnet mask, and maximum number of pods per node are interrelated parameters. The platform automatically calculates:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Maximum number of pods per node\u003C/strong> – based on the node subnet mask\u003C/li>\n\u003Cli>\u003Cstrong>Maximum number of nodes in the cluster\u003C/strong> – based on the pod range and node subnet mask\u003C/li>\n\u003C/ul>\n\u003Cp>Example with default parameters:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Pod range\u003C/strong> – \u003Ccode>10.244.0.0/16\u003C/code>\u003C/li>\n\u003Cli>\u003Cstrong>Node subnet mask \u003C/strong>– \u003Ccode>/24\u003C/code>\u003C/li>\n\u003Cli>\u003Cstrong>Maximum pods per node\u003C/strong> – 256\u003C/li>\n\u003Cli>\u003Cstrong>Maximum nodes in a cluster\u003C/strong> – 256\u003C/li>\n\u003C/ul>\n\u003Cp>\u003Cstrong>How to choose: \u003C/strong>The default values are suitable for most tasks. Increase the ranges if you plan to deploy a large cluster (hundreds of nodes) or a large number of pods per node. Keep in mind that these settings cannot be changed after creation. For more information on limitations when deploying a Kubernetes cluster, see the article “\u003Ca href=\"https://beget.com/en/kb/manual/limits-quotas-restrictions-kubernetes\">Limits, quotas, and constraints\u003C/a>”.\u003C/p>\n\u003Ch2 id=\"worker-groups\">Worker Groups\u003C/h2>\n\u003Cp>A worker group is a set of nodes with the same configuration on which your applications run. A cluster can contain multiple worker groups with different settings.\u003C/p>\n\u003Ch3 id=\"why-use-multiple-worker-groups\">Why Use Multiple Worker Groups\u003C/h3>\n\u003Cp>Different applications may have different resource requirements:\u003C/p>\n\u003Cul>\n\u003Cli>Web servers – many pods with low CPU and RAM usage\u003C/li>\n\u003Cli>ML tasks – few pods, but with large amounts of RAM or GPUs\u003C/li>\n\u003Cli>Background tasks – lower-cost nodes with no performance requirements\u003C/li>\n\u003C/ul>\n\u003Cp>You can create a separate worker group for each type of workload and select the appropriate configuration for it. You can route pods to the desired group using labels and selectors.\u003C/p>\n\u003Ch3 id=\"group-parameters\">Group parameters\u003C/h3>\n\u003Cp>\u003Cstrong>Group name\u003C/strong> – any name. Can be set manually or generated automatically.\u003C/p>\n\u003Cp>\u003Cstrong>Number of nodes\u003C/strong> – how many servers will be in the group. Minimum – 1. Maximum – 500.\u003C/p>\n\u003Cp>\u003Cstrong>Node configuration\u003C/strong> – resources for each server (CPU, RAM, disk). Two options are available:\u003C/p>\n\u003Cul>\n\u003Cli>Configurator for standard servers – flexible selection of parameters\u003C/li>\n\u003Cli>Pre-configured settings for high-frequency servers\u003C/li>\n\u003C/ul>\n\u003Cp>All nodes in a single group have the same configuration.\u003C/p>\n\u003Ch3 id=\"auto-healing\">Auto-healing\u003C/h3>\n\u003Cp>Auto-healing automatically checks the health of nodes in a worker group and restores them. If a node stays unhealthy for too long, the platform deletes it and creates a new one with the same configuration. This keeps the specified number of nodes in the group, so you don't have to recreate nodes manually.\u003C/p>\n\u003Cp>Auto-healing is configured separately for each worker group:\u003C/p>\n\u003Cul>\n\u003Cli>Auto-healing is disabled by default.\u003C/li>\n\u003Cli>You can enable it with the \u003Cstrong>Auto-healing\u003C/strong> toggle when creating a cluster or a worker group.\u003C/li>\n\u003Cli>You can enable or disable auto-healing at any time in the worker group settings. The change is applied without recreating nodes and without interrupting the group.\u003C/li>\n\u003C/ul>\n\u003Ch4 id=\"how-recovery-works\">How recovery works\u003C/h4>\n\u003Cp>\u003Cstrong>New nodes.\u003C/strong> Auto-healing starts working as soon as the group is created. If a new node fails to start within 6 minutes, the platform retries creating it. Attempts continue until the node reaches the Running status.\u003C/p>\n\u003Cp>\u003Cstrong>Running nodes:\u003C/strong>\u003C/p>\n\u003Col>\n\u003Cli>The node stops responding. Kubernetes marks it as NotReady and stops scheduling new pods on it.\u003C/li>\n\u003Cli>After 5 minutes, the pods from this node are moved to other nodes in the group.\u003C/li>\n\u003Cli>If the node remains unavailable for more than 15 minutes, the platform deletes it and creates a new one with the same configuration.\u003C/li>\n\u003Cli>The new node joins the cluster, and a node with a new name appears in the node list.\u003C/li>\n\u003C/ol>\n\u003Cp>The time thresholds are set by the platform and cannot be changed.\u003C/p>\n\u003Cp>\u003Cstrong>Without auto-healing\u003C/strong>, a faulty node remains in the cluster. You can restore it manually using the “Recreate node” button or by contacting \u003Ca href=\"https://cp.beget.com/support?utm_source=kb&amp;utm_campaign=k8s_documentation&amp;utm_content=cp_support\">technical support\u003C/a>.\u003C/p>\n\u003Ch4 id=\"limitations\">Limitations\u003C/h4>\n\u003Cul>\n\u003Cli>Auto-healing restores only worker nodes. Master nodes of the control plane are not covered.\u003C/li>\n\u003Cli>You cannot exclude an individual node from auto-healing. The feature can only be enabled or disabled for the entire worker group. If you need to troubleshoot a specific node, disable auto-healing for its group.\u003C/li>\n\u003C/ul>\n\u003Cdiv class=\"wp-block-beget-alert alert-block alert-block-info\">\n\u003Cdiv class=\"alert-block-title\">\u003Cstrong>Please note!\u003C/strong>\u003C/div>\n\u003Cdiv class=\"alert-block-content\">\u003Cstrong>Data on the node's disk \u003C/strong>is permanently deleted when the node is replaced\u003Cstrong>.\u003C/strong> Do not store data that needs to be preserved on node disks.\u003Cbr>\u003Cstrong>Single-node worker group.\u003C/strong> While the node is being replaced, applications in the group will be unavailable. If continuous application availability is important, use at least two nodes in the group.\u003Cbr>\u003Cstrong>Simultaneous failure of multiple nodes.\u003C/strong> Auto-healing is triggered only if a single node in the worker group is faulty. If two or more nodes fail, the platform does not recreate any of them to avoid stopping the entire group. In this case, recovery will be performed manually by our team.\u003Cbr>\u003Cstrong>Deleting a node via kubectl.\u003C/strong> If you delete a node with the \u003Ccode>kubectl delete node\u003C/code> command while auto-healing is enabled, the platform will consider the node faulty and recreate it. The data on the node's disk will be deleted. To reduce the number of nodes in a group, change it in the worker group settings in the control panel.\u003C/div>\n\u003C/div>\n\u003Ch3 id=\"labels\">Labels\u003C/h3>\n\u003Cp>Labels are key-value pairs assigned to nodes.&nbsp;\u003C/p>\n\u003Cp>Labels do not restrict pod deployment, but they allow you to:\u003C/p>\n\u003Cul>\n\u003Cli>Select nodes for pod placement using selectors (NodeSelector, affinity)\u003C/li>\n\u003Cli>Organize nodes by role, environment, or other criteria\u003C/li>\n\u003C/ul>\n\u003Cp>Format:\u003C/p>\n\u003Cdiv class=\"wp-block-beget-code code-block\">\n\u003Cpre data-options=\"{&quot;mode&quot;:&quot;&quot;}\">\u003Ccode>node-role.kubernetes.io/&lt;key&gt;=&lt;value&gt;\u003C/code>\u003C/pre>\n\u003C/div>\n\u003Cp>Example: You can label a group with the label \u003Ccode>workload=gpu\u003C/code> and specify in the pod manifest that it should only run on nodes with this label:\u003C/p>\n\u003Cdiv class=\"wp-block-beget-code code-block\">\n\u003Cpre data-options=\"{&quot;mode&quot;:&quot;&quot;}\">\u003Ccode>spec:\n  nodeSelector:\n    workload: gpu\u003C/code>\u003C/pre>\n\u003C/div>\n\u003Ch3 id=\"taints\">Taints\u003C/h3>\n\u003Cp>Taints are a mechanism that prevents pods from running on specific nodes if the pods do not have the corresponding Toleration.\u003C/p>\n\u003Cp>Format:\u003C/p>\n\u003Cdiv class=\"wp-block-beget-code code-block\">\n\u003Cpre data-options=\"{&quot;mode&quot;:&quot;&quot;}\">\u003Ccode>&lt;key&gt;=&lt;value&gt;:&lt;effect&gt;\u003C/code>\u003C/pre>\n\u003C/div>\n\u003Cp>Effects:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>NoSchedule \u003C/strong>– Pods without a Toleration will not be scheduled on this node\u003C/li>\n\u003Cli>\u003Cstrong>PreferNoSchedule \u003C/strong>– Kubernetes will avoid scheduling pods without a Toleration, but may schedule them if resources are scarce\u003C/li>\n\u003Cli>\u003Cstrong>NoExecute \u003C/strong>– Pods without a Toleration will be evicted from the node if they are already running\u003C/li>\n\u003C/ul>\n\u003Cp>Example: You can assign the taint \u003Ccode>dedicated=critical:NoSchedule\u003C/code> to a group of nodes so that only critical services run on them. To do this, specify the corresponding toleration in the pod manifest:\u003C/p>\n\u003Cdiv class=\"wp-block-beget-code code-block\">\n\u003Cpre data-options=\"{&quot;mode&quot;:&quot;&quot;}\">\u003Ccode>spec:\n  tolerations:\n    key: dedicated\n    value: critical\n    effect: NoSchedule\u003C/code>\u003C/pre>\n\u003C/div>\n\u003Ch3 id=\"authentication\">Authentication\u003C/h3>\n\u003Cp>SSH keys are used to connect directly to the worker group nodes via SSH. You can select one of the existing keys or add a new one.\u003C/p>\n\u003Cdiv class=\"wp-block-beget-alert alert-block alert-block-info\">\n\u003Cdiv class=\"alert-block-title\">\u003Cstrong>Please note!\u003C/strong>\u003C/div>\n\u003Cdiv class=\"alert-block-content\">Manually modifying system components on the nodes via SSH may disrupt the cluster’s operation. The consequences of such actions are the user’s responsibility.\u003C/div>\n\u003C/div>\n\u003Ch2 id=\"project\">Project\u003C/h2>\n\u003Cp>You can associate the cluster with a project for convenient resource management. An option to pin the cluster is also available in the main menu.\u003C/p>\n\u003Ch2 id=\"cost-and-creation\">Cost and Creation\u003C/h2>\n\u003Cp>Before installing and creating a Kubernetes cluster, the page displays the total cost, both daily and monthly. The cost is calculated based on master node and worker group resources.\u003C/p>\n\u003Cp>Click “Create Kubernetes Cluster” to start the creation process.\u003C/p>\n\u003Ch2 id=\"all-articles-in-this-section\">All articles in this section\u003C/h2>\n\u003Col>\n\u003Cli>\u003Ca href=\"https://beget.com/en/kb/manual/managed-kubernetes\">Kubernetes (K8s)\u003C/a> – An Overview of the Managed Kubernetes Service\u003C/li>\n\u003Cli>\u003Ca href=\"https://beget.com/en/kb/manual/what-is-kubernetes\">Kubernetes Basics\u003C/a> – Key Concepts: Cluster, Nodes, Pods, Services\u003C/li>\n\u003Cli>\u003Cstrong>Creating and Configuring a Cluster\u003C/strong> – You are here\u003C/li>\n\u003Cli>\u003Ca href=\"https://beget.com/en/kb/manual/kubectl\">Connecting to the Cluster and Working with kubectl\u003C/a> – kubeconfig, Connectivity, and Core Kubernetes Tools\u003C/li>\n\u003Cli>\u003Ca href=\"https://beget.com/en/kb/manual/cluster-management-kubernetes\">Cluster management\u003C/a> – adding nodes, changing configuration, updating, and deleting\u003C/li>\n\u003Cli>\u003Ca href=\"https://beget.com/en/kb/manual/network-and-load-balancer-kubernetes\">Networking and load balancers\u003C/a> – network model, external and internal load balancers\u003C/li>\n\u003Cli>\u003Ca href=\"https://beget.com/en/kb/manual/limits-quotas-restrictions-kubernetes\">Limits, quotas, and constraints\u003C/a> – platform constraints, what can and cannot be changed\u003C/li>\n\u003C/ol>\n\u003Cp>If you have any questions, please submit a ticket via the account dashboard (under “\u003Ca href=\"https://cp.beget.com/support?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=kubernetes_sozdanie_klastera&amp;utm_content=cp_support\">Help and Support\u003C/a>”). And if you’d like to discuss this article or our products, we’d love to see you in our Telegram \u003Ca href=\"https://t.me/beget_chat\">community\u003C/a>.\u003C/p>\n",57,"2026-11-11T14:50:31.000Z",{"count":15,"liked":16},5,false,{"route":18,"title":20,"tags":21,"breadcrumbs":27,"uuid":28,"parent_uuid":29,"default_page_path":26,"seo_metadata":30},{"language":6,"path":19},"/kb/manual","Control Panel User's Manual",[22],{"id":23,"title":24,"seo_metadata":25},"vps","VPS",{"title":26,"description":26,"header":26,"keywords":26},"",[],"5afe272b-ca8e-731e-0871-c5b169760081","80213437-0399-4b4f-2333-426bb5050534",{"title":31,"description":32,"header":31,"keywords":33},"Beget Hosting Panel Guide","Руководство по панели управления Beget. Инструкции по работе с аккаунтом, файловыми менеджерами, почтой, CMS и др.","hosting panel instructions, hosting beget",{"src":26,"text":26},{"title":36,"description":37,"keywords":38},"Kubernetes Cluster: Create and Configure","Read the documentation on using Managed Kubernetes in Beget Cloud ✔ How to deploy and configure a cluster in the service","Managed Kubernetes User Guide for Beget: User Guide and Documentation for Deployment and Configuration",{"faq":40,"how_to":41,"product":41},[],null,{},[44,48,51,55,58,61,64,67,70,73,76,79,82,85,89,92,95,98,101,104,107],{"level":45,"name":46,"anchor":47},1,"Name and Region","name-and-region",{"level":45,"name":49,"anchor":50},"Control Plane","control-plane",{"level":52,"name":53,"anchor":54},2,"Number of master nodes","number-of-master-nodes",{"level":52,"name":56,"anchor":57},"Kubernetes Version","kubernetes-version",{"level":45,"name":59,"anchor":60},"Configuring the Cluster Network","configuring-the-cluster-network",{"level":52,"name":62,"anchor":63},"Service Address Range","service-address-range",{"level":52,"name":65,"anchor":66},"Pod Address Range (Pod CIDR)","pod-address-range-pod-cidr",{"level":52,"name":68,"anchor":69},"Node subnet mask","node-subnet-mask",{"level":52,"name":71,"anchor":72},"How the parameters are related","how-the-parameters-are-related",{"level":45,"name":74,"anchor":75},"Worker Groups","worker-groups",{"level":52,"name":77,"anchor":78},"Why Use Multiple Worker Groups","why-use-multiple-worker-groups",{"level":52,"name":80,"anchor":81},"Group parameters","group-parameters",{"level":52,"name":83,"anchor":84},"Auto-healing","auto-healing",{"level":86,"name":87,"anchor":88},3,"How recovery works","how-recovery-works",{"level":86,"name":90,"anchor":91},"Limitations","limitations",{"level":52,"name":93,"anchor":94},"Labels","labels",{"level":52,"name":96,"anchor":97},"Taints","taints",{"level":52,"name":99,"anchor":100},"Authentication","authentication",{"level":45,"name":102,"anchor":103},"Project","project",{"level":45,"name":105,"anchor":106},"Cost and Creation","cost-and-creation",{"level":45,"name":108,"anchor":109},"All articles in this section","all-articles-in-this-section",[],[112],{"route":113,"title":20},{"language":6,"path":19},[],[],[117,127,136],{"route":118,"uuid":120,"title":121,"excerpt":26,"content":26,"view_count":122,"published_at":26,"modified_at":26,"like":41,"category":41,"hero_image":41,"seo_metadata":41,"schema_org_metadata":41,"open_graph_metadata":41,"sections":123,"tags":124,"breadcrumbs":125,"images":126},{"language":6,"path":119},"/kb/manual/cloud-server","c57ad9b8-843e-cd93-1fb6-21b8f64528e7","MySQL Cloud Servers in the Beget Cloud",0,[],[],[],[],{"route":128,"uuid":130,"title":131,"excerpt":26,"content":26,"view_count":122,"published_at":26,"modified_at":26,"like":41,"category":41,"hero_image":41,"seo_metadata":41,"schema_org_metadata":41,"open_graph_metadata":41,"sections":132,"tags":133,"breadcrumbs":134,"images":135},{"language":6,"path":129},"/kb/manual/vps-backup","f2b7f4db-f11f-f695-d9ee-7992420f320a","VPS backup in the Beget cloud",[],[],[],[],{"route":137,"uuid":139,"title":140,"excerpt":26,"content":26,"view_count":122,"published_at":26,"modified_at":26,"like":41,"category":41,"hero_image":41,"seo_metadata":41,"schema_org_metadata":41,"open_graph_metadata":41,"sections":141,"tags":142,"breadcrumbs":143,"images":144},{"language":6,"path":138},"/kb/manual/dns","c4261afe-ce3a-914d-df27-aa76c93446cf","DNS",[],[],[],[],"popularity-desc"]