[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"/en/kb/manual/cluster-management-kubernetesKbData":3},{"page":4,"pages":128,"recommendedPages":129,"category":41,"categoryTree":41,"total":135,"currentOrder":158,"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":123,"breadcrumbs":124,"images":127},{"language":6,"path":7},"en","/kb/manual/cluster-management-kubernetes","741dc849-a7fe-f150-c578-c8542b32aa84","Managed Kubernetes Cluster Management","This article describes common operations for managing a Kubernetes cluster: adding and modifying worker groups, updating the Kubernetes version, and deleting the cluster. For each operation, it explains what will happen and how to verify the result.","\u003Cp>This article describes common operations for managing a Kubernetes cluster: adding and modifying worker groups, updating the Kubernetes version, and deleting the cluster. For each operation, it explains what will happen and how to verify the result.\u003C/p>\n\u003Cp>If you haven’t created a cluster yet, start with the article “\u003Ca href=\"https://beget.com/en/kb/manual/creating-and-configuring-cluster-kubernetes\">Creating and Configuring a Cluster\u003C/a>”. To connect to the cluster and work with kubectl (the command-line tool for managing Kubernetes), see “\u003Ca href=\"https://beget.com/en/kb/manual/kubectl\">Connecting to the Cluster and Working with kubectl\u003C/a>”.\u003C/p>\n\u003Ch2 id=\"cluster-dashboard\">Cluster Dashboard\u003C/h2>\n\u003Cp>When you navigate to the created K8s cluster, the dashboard will open, a page providing an overview of the cluster’s status.&nbsp;\u003C/p>\n\u003Cp>The following are available here:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Statistics \u003C/strong>– CPU load and RAM usage graphs for master nodes and worker groups\u003C/li>\n\u003Cli>\u003Cstrong>Information \u003C/strong>– Kubernetes version and a “Connect” button for quick access to the kubeconfig. For more details, see the “\u003Ca href=\"https://beget.com/en/kb/manual/kubectl\">Connecting to the Cluster\u003C/a>” section\u003C/li>\n\u003Cli>\u003Cstrong>Worker groups and nodes\u003C/strong> – number of nodes and their statuses\u003C/li>\n\u003Cli>\u003Cstrong>Settings \u003C/strong>– number of master nodes, Kubernetes version, network parameters\u003C/li>\n\u003Cli>\u003Cstrong>Add-ons\u003C/strong> – installed and available add-ons\u003C/li>\n\u003C/ul>\n\u003Ch2 id=\"statistics\">Statistics\u003C/h2>\n\u003Cp>The “Statistics” section contains two tabs:\u003C/p>\n\u003Cp>\u003Cstrong>Groups and nodes:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>Worker group load – select a group using the selector\u003C/li>\n\u003Cli>Load by individual nodes – broken down by worker groups\u003C/li>\n\u003Cli>Number of pods in different statuses – broken down by namespace\u003C/li>\n\u003Cli>Number of container restarts – broken down by namespace\u003C/li>\n\u003C/ul>\n\u003Cp>\u003Cstrong>ControlPlane:\u003C/strong>\u003C/p>\n\u003Cul>\n\u003Cli>CPU load on the master node\u003C/li>\n\u003Cli>RAM usage\u003C/li>\n\u003Cli>Disk utilization\u003C/li>\n\u003C/ul>\n\u003Ch2 id=\"adding-a-worker-group\">Adding a Worker Group\u003C/h2>\n\u003Cp>A new worker group is needed when current resources are insufficient or when a different node configuration is required for a new type of workload.\u003C/p>\n\u003Ch3 id=\"via-the-control-panel\">Via the Control Panel\u003C/h3>\n\u003Col>\n\u003Cli>Go to the cluster dashboard → “Worker Groups and Nodes” tab\u003C/li>\n\u003Cli>Click “Create New Group”\u003C/li>\n\u003Cli>Set the group parameters: name, number of nodes, configuration, labels, and limits\u003C/li>\n\u003Cli>Confirm creation\u003C/li>\n\u003C/ol>\n\u003Ch3 id=\"what-happens\">What happens\u003C/h3>\n\u003Cul>\n\u003Cli>Creation time – approximately 1–2 minutes per node. All nodes in the group are created simultaneously\u003C/li>\n\u003Cli>Pod scheduling – new pods will be automatically placed on the new nodes according to taints/tolerations policies\u003C/li>\n\u003Cli>Existing pods – remain on their current nodes and are not moved\u003C/li>\n\u003Cli>Impact on the cluster – adding a group does not affect the operation of existing nodes and pods\u003C/li>\n\u003C/ul>\n\u003Cp>After the group is created, new nodes will appear in the cluster. You can verify this with the command:\u003C/p>\n\u003Cdiv class=\"wp-block-beget-code code-block\">\n\u003Cpre data-options=\"{&quot;mode&quot;:&quot;&quot;}\">\u003Ccode>kubectl get nodes\u003C/code>\u003C/pre>\n\u003C/div>\n\u003Cp>The new nodes must transition to \u003Ccode>Ready\u003C/code> status.\u003C/p>\n\u003Ch2 id=\"changing-a-worker-group-configuration\">Changing a Worker Group Configuration\u003C/h2>\n\u003Cp>You can modify the settings of an existing worker group: the number of nodes, labels, and taints.\u003C/p>\n\u003Ch3 id=\"via-the-control-panel-2\">Via the Control Panel\u003C/h3>\n\u003Col>\n\u003Cli>Go to the cluster dashboard → “Worker Groups and Nodes” tab\u003C/li>\n\u003Cli>Click the edit icon (pencil) next to the desired group\u003C/li>\n\u003Cli>Change the settings\u003C/li>\n\u003Cli>Save the changes\u003C/li>\n\u003C/ol>\n\u003Ch3 id=\"changing-the-number-of-nodes\">Changing the number of nodes\u003C/h3>\n\u003Cp>\u003Cstrong>Increasing \u003C/strong>– new nodes with the same configuration are added to the group. Existing pods continue to run without interruption.\u003C/p>\n\u003Cp>\u003Cstrong>Decreasing \u003C/strong>– pods are drained before nodes are removed. Pods are correctly migrated to other available nodes.\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\">If PodDisruptionBudget (PDB) is used in the cluster, ensure that the allowed number of unavailable pods (maxUnavailable) is greater than 1. Otherwise, the eviction process will not complete, and the node will not be deleted.\u003C/div>\n\u003C/div>\n\u003Ch3 id=\"changing-node-configurations-cpu-ram-disk\">Changing node configurations (CPU, RAM, disk)\u003C/h3>\n\u003Cp>Node configuration supports in-place updates for the entire worker group:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>CPU and RAM\u003C/strong> – can be increased or decreased\u003C/li>\n\u003Cli>\u003Cstrong>Disk \u003C/strong>– can only be increased\u003C/li>\n\u003C/ul>\n\u003Cp>When the configuration is changed, pods are evicted from the node to apply the new settings. To avoid application downtime:\u003C/p>\n\u003Cul>\n\u003Cli>Use more than one replica for each application\u003C/li>\n\u003Cli>Configure Pod Anti-Affinity so that replicas of the same application are not placed on the same node\u003C/li>\n\u003C/ul>\n\u003Ch3 id=\"verifying-the-result\">Verifying the result\u003C/h3>\n\u003Cdiv class=\"wp-block-beget-code code-block\">\n\u003Cpre data-options=\"{&quot;mode&quot;:&quot;&quot;}\">\u003Ccode># Check the number and status of nodes\nkubectl get nodes\n\n# Check node labels\nkubectl get nodes --show-labels\n\n# Check node taints\nkubectl describe node &lt;node-name&gt; | grep Taints\u003C/code>\u003C/pre>\n\u003C/div>\n\u003Ch2 id=\"updating-the-kubernetes-version\">Updating the Kubernetes version\u003C/h2>\n\u003Cp>Updates are only possible to a newer version.\u003C/p>\n\u003Ch3 id=\"via-the-control-panel-3\">Via the control panel\u003C/h3>\n\u003Col>\n\u003Cli>Go to the cluster dashboard → “Settings” tab\u003C/li>\n\u003Cli>In the “Kubernetes Version” space, select the target version\u003C/li>\n\u003Cli>Confirm the update\u003C/li>\n\u003C/ol>\n\u003Cp>Update process:\u003C/p>\n\u003Col>\n\u003Cli>Master nodes are recreated, the version changes from the current one to the target version\u003C/li>\n\u003Cli>After the control plane is successfully updated, the worker groups begin to update\u003C/li>\n\u003Cli>Worker groups are updated sequentially, one group at a time\u003C/li>\n\u003Cli>Within each group, nodes are updated one by one to minimize the impact on running applications\u003C/li>\n\u003C/ol>\n\u003Ch3 id=\"release-channel\">Release channel\u003C/h3>\n\u003Cp>A release channel is an update strategy that determines which Kubernetes version your cluster will be automatically upgraded to.\u003C/p>\n\u003Cp>Three channels are available:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Stable\u003C/strong> — upgrades to a version that is no more than two minor versions behind the latest available one. The most battle-tested option, with a lower risk of issues after an upgrade\u003C/li>\n\u003Cli>\u003Cstrong>Balanced\u003C/strong> — upgrades to a version that is no more than one minor version behind. Newer than Stable, but with less risk than Latest\u003C/li>\n\u003Cli>\u003Cstrong>Latest\u003C/strong> — upgrades to the most recent available Kubernetes version. New features arrive sooner, but the version is less proven\u003C/li>\n\u003C/ul>\n\u003Cdiv class=\"wp-block-beget-alert alert-block alert-block-info\">\n\u003Cdiv class=\"alert-block-title\">Note!\u003C/div>\n\u003Cdiv class=\"alert-block-content\">Changing the release channel changes the list of Kubernetes versions available for selection.\u003C/div>\n\u003C/div>\n\u003Ch4 id=\"what-a-version-number-consists-of\">What a version number consists of\u003C/h4>\n\u003Cp>A Kubernetes version number has three parts — for example, \u003Ccode>1.34.5\u003C/code>:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>1\u003C/strong> — major version. Changes with fundamental changes to the product\u003C/li>\n\u003Cli>\u003Cstrong>34\u003C/strong> — minor version. These releases add new features, promote existing options to stable (GA), or mark them as deprecated\u003C/li>\n\u003Cli>\u003Cstrong>5\u003C/strong> — patch version. Fixes critical bugs and vulnerabilities without changing how things work\u003C/li>\n\u003C/ul>\n\u003Cp>The release channel determines which minor version the cluster will be upgraded to. In addition, the cluster may be updated when new patch versions and internal platform versions are released — such updates do not change how things work.\u003C/p>\n\u003Cdiv class=\"wp-block-beget-alert alert-block alert-block-info\">\n\u003Cdiv class=\"alert-block-title\">Note!\u003C/div>\n\u003Cdiv class=\"alert-block-content\">Upgrading the Kubernetes minor version may affect your services — new releases change API behavior and remove deprecated options.\u003C/div>\n\u003C/div>\n\u003Ch4 id=\"how-to-change-the-release-channel\">How to change the release channel\u003C/h4>\n\u003Col>\n\u003Cli>Go to the cluster dashboard → the \u003Cstrong>Settings\u003C/strong> card\u003C/li>\n\u003Cli>In the \u003Cstrong>Release channel\u003C/strong> field, select the option you need\u003C/li>\n\u003Cli>Save the changes\u003C/li>\n\u003C/ol>\n\u003Ch4 id=\"rules-and-limitations\">Rules and limitations\u003C/h4>\n\u003Cul>\n\u003Cli>The \u003Cstrong>Balanced\u003C/strong> channel is used by default — it provides the optimal version: recent enough, yet already proven\u003C/li>\n\u003Cli>The selected channel applies to subsequent updates — the current cluster version does not change when you switch channels\u003C/li>\n\u003Cli>Updates are performed according to the configured maintenance window\u003C/li>\n\u003Cli>The cluster is upgraded by no more than one minor version at a time\u003C/li>\n\u003C/ul>\n\u003Ch3 id=\"tech-window\">Maintenance window\u003C/h3>\n\u003Cp>The maintenance window determines when the platform may apply automatic cluster updates: Kubernetes patch versions, internal platform versions, and minor version upgrades within the selected release channel.\u003C/p>\n\u003Ch4 id=\"system-update-period\">System update period\u003C/h4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Any time\u003C/strong> — updates are applied as soon as they become available\u003C/li>\n\u003Cli>\u003Cstrong>Scheduled\u003C/strong> — updates are performed only within the window you specify. When \u003Cstrong>Scheduled\u003C/strong> is selected, you configure:\n\u003Cul>\n\u003Cli>\u003Cstrong>Day of week\u003C/strong> — one or more days on which updates are allowed. The \u003Cstrong>Any day\u003C/strong> checkbox allows updates on any day of the week\u003C/li>\n\u003Cli>\u003Cstrong>Time window\u003C/strong> — the start time and time zone. The window duration is fixed at 3 hours\u003C/li>\n\u003C/ul>\n\u003C/li>\n\u003C/ul>\n\u003Cdiv class=\"wp-block-beget-alert alert-block alert-block-info\">\n\u003Cdiv class=\"alert-block-title\">Note!\u003C/div>\n\u003Cdiv class=\"alert-block-content\">If the maintenance is not completed within 3 hours and cannot be safely postponed, it will be finished regardless — outside the window.\u003C/div>\n\u003C/div>\n\u003Ch4 id=\"how-to-change-the-maintenance-window\">How to change the maintenance window\u003C/h4>\n\u003Col>\n\u003Cli>Go to the cluster dashboard → the \u003Cstrong>Settings\u003C/strong> card\u003C/li>\n\u003Cli>In the \u003Cstrong>System update period\u003C/strong> field, select \u003Cstrong>Any time\u003C/strong> or \u003Cstrong>Scheduled\u003C/strong>\u003C/li>\n\u003Cli>For \u003Cstrong>Scheduled\u003C/strong>, specify the days of the week, start time, and time zone\u003C/li>\n\u003Cli>Save the changes\u003C/li>\n\u003C/ol>\n\u003Ch4 id=\"recommendations\">Recommendations\u003C/h4>\n\u003Cul>\n\u003Cli>Choose the hours when your services are under the lowest load: during an update, nodes are recreated one by one and pods are evicted to other nodes\u003C/li>\n\u003Cli>Keep more than one replica of your application and configure Pod Anti-Affinity so that updates go through without downtime\u003C/li>\n\u003Cli>A window that is too narrow (for example, one day a week) delays the installation of security fixes — keep this in mind when configuring it\u003C/li>\n\u003C/ul>\n\u003Cp>Пара заметок: «Актуальный» перевёл как \u003Cstrong>Latest\u003C/strong> (в GKE аналог — Rapid, но Latest понятнее), «В заданное время» — \u003Cstrong>Scheduled\u003C/strong>. Если в интерфейсе уже есть английские названия полей, подгони под них.\u003C/p>\n\u003Ch3 id=\"checking-the-version\">Checking the Version\u003C/h3>\n\u003Cdiv class=\"wp-block-beget-code code-block\">\n\u003Cpre data-options=\"{&quot;mode&quot;:&quot;&quot;}\">\u003Ccode># API server version\nkubectl version\n\n# Kubelet version on nodes\nkubectl get nodes\u003C/code>\u003C/pre>\n\u003C/div>\n\u003Cp>The \u003Ccode>VERSION\u003C/code> column displays the kubelet version on each node. If the update is still in progress, different nodes may have different versions.\u003C/p>\n\u003Ch2 id=\"add-ons\">Add-ons\u003C/h2>\n\u003Cp>Add-ons are additional components that simplify the administration of Kubernetes clusters by adding monitoring, certificate management, network plugins, and other capabilities.\u003C/p>\n\u003Ch3 id=\"managing-add-ons\">Managing Add-ons\u003C/h3>\n\u003Col>\n\u003Cli>Go to the cluster dashboard → “Add-ons” tab\u003C/li>\n\u003Cli>The page displays a list of available add-ons with descriptions and statuses\u003C/li>\n\u003Cli>To install, click “Install” on the add-on card\u003C/li>\n\u003Cli>To view details or remove an add-on, click on the add-on card\u003C/li>\n\u003C/ol>\n\u003Cp>Each add-on card includes:\u003C/p>\n\u003Cul>\n\u003Cli>Description and purpose\u003C/li>\n\u003Cli>Components (which components are installed)\u003C/li>\n\u003Cli>Links to documentation\u003C/li>\n\u003C/ul>\n\u003Cp>If you would like to suggest a new add-on, please contact technical support.\u003C/p>\n\u003Ch2 id=\"deleting-a-cluster\">Deleting a Cluster\u003C/h2>\n\u003Ch3 id=\"via-the-control-panel-4\">Via the Control Panel\u003C/h3>\n\u003Col>\n\u003Cli>Go to the cluster dashboard → “Settings” tab\u003C/li>\n\u003Cli>At the bottom of the page, click “Delete Kubernetes Cluster”\u003C/li>\n\u003Cli>Confirm the deletion\u003C/li>\n\u003C/ol>\n\u003Ch3 id=\"what-happens-2\">What Happens\u003C/h3>\n\u003Cp>When you delete a cluster, the following are deleted:\u003C/p>\n\u003Cul>\n\u003Cli>All load balancers created via LoadBalancer-type services\u003C/li>\n\u003Cli>All worker group virtual machines\u003C/li>\n\u003Cli>Control plane nodes (master nodes)\u003C/li>\n\u003C/ul>\n\u003Cp>Deletion occurs immediately.\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\">Deleting a cluster is an irreversible operation. Make sure all important data is saved before deleting the cluster.\u003C/div>\n\u003C/div>\n\u003Cp>All articles in this section\u003C/p>\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>\u003Ca href=\"https://beget.com/en/kb/manual/creating-and-configuring-cluster-kubernetes\">Creating and Configuring a Cluster\u003C/a> – Master Node Configuration, Networking, and Worker Groups\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>\u003Cstrong>Cluster management\u003C/strong> – You are here\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_upravlenie_klasterom&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",54,"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},"Managing Kubernetes cluster","Guide to Managing a Managed Kubernetes Cluster on Beget Cloud ✔ User Guide","User Manual for Beget's Managed Kubernetes Service: A Guide and Documentation for Working with Kubernetes Clusters",{"faq":40,"how_to":41,"product":41},[],null,{},[44,48,51,54,58,61,64,66,69,72,75,78,81,84,88,91,94,97,100,103,106,109,112,115,118,120],{"level":45,"name":46,"anchor":47},1,"Cluster Dashboard","cluster-dashboard",{"level":45,"name":49,"anchor":50},"Statistics","statistics",{"level":45,"name":52,"anchor":53},"Adding a Worker Group","adding-a-worker-group",{"level":55,"name":56,"anchor":57},2,"Via the Control Panel","via-the-control-panel",{"level":55,"name":59,"anchor":60},"What happens","what-happens",{"level":45,"name":62,"anchor":63},"Changing a Worker Group Configuration","changing-a-worker-group-configuration",{"level":55,"name":56,"anchor":65},"via-the-control-panel-2",{"level":55,"name":67,"anchor":68},"Changing the number of nodes","changing-the-number-of-nodes",{"level":55,"name":70,"anchor":71},"Changing node configurations (CPU, RAM, disk)","changing-node-configurations-cpu-ram-disk",{"level":55,"name":73,"anchor":74},"Verifying the result","verifying-the-result",{"level":45,"name":76,"anchor":77},"Updating the Kubernetes version","updating-the-kubernetes-version",{"level":55,"name":79,"anchor":80},"Via the control panel","via-the-control-panel-3",{"level":55,"name":82,"anchor":83},"Release channel","release-channel",{"level":85,"name":86,"anchor":87},3,"What a version number consists of","what-a-version-number-consists-of",{"level":85,"name":89,"anchor":90},"How to change the release channel","how-to-change-the-release-channel",{"level":85,"name":92,"anchor":93},"Rules and limitations","rules-and-limitations",{"level":55,"name":95,"anchor":96},"Maintenance window","tech-window",{"level":85,"name":98,"anchor":99},"System update period","system-update-period",{"level":85,"name":101,"anchor":102},"How to change the maintenance window","how-to-change-the-maintenance-window",{"level":85,"name":104,"anchor":105},"Recommendations","recommendations",{"level":55,"name":107,"anchor":108},"Checking the Version","checking-the-version",{"level":45,"name":110,"anchor":111},"Add-ons","add-ons",{"level":55,"name":113,"anchor":114},"Managing Add-ons","managing-add-ons",{"level":45,"name":116,"anchor":117},"Deleting a Cluster","deleting-a-cluster",{"level":55,"name":56,"anchor":119},"via-the-control-panel-4",{"level":55,"name":121,"anchor":122},"What Happens","what-happens-2",[],[125],{"route":126,"title":20},{"language":6,"path":19},[],[],[130,140,149],{"route":131,"uuid":133,"title":134,"excerpt":26,"content":26,"view_count":135,"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":136,"tags":137,"breadcrumbs":138,"images":139},{"language":6,"path":132},"/kb/manual/what-is-kubernetes","4df6686a-8edd-8055-e4e9-70607c90f4ed","What is Kubernetes (K8s)? Key terms: cluster, container, services",0,[],[],[],[],{"route":141,"uuid":143,"title":144,"excerpt":26,"content":26,"view_count":135,"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":145,"tags":146,"breadcrumbs":147,"images":148},{"language":6,"path":142},"/kb/manual/services","6a9cdcac-9f9f-17d4-9799-c257a08937f0","Services",[],[],[],[],{"route":150,"uuid":152,"title":153,"excerpt":26,"content":26,"view_count":135,"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":154,"tags":155,"breadcrumbs":156,"images":157},{"language":6,"path":151},"/kb/manual/ftp","b97c3b6e-0c0d-4d0b-dff2-1de38d0b2a61","FTP",[],[],[],[],"popularity-desc"]