Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Ajusta la escala de tus cargas de trabajo con estado según los requisitos cambiantes de las cargas de trabajo de contenedores.
Antes de comenzar
Para ejecutar comandos en un clúster de Kubernetes, asegúrate de tener los siguientes recursos:
Ubica el nombre del clúster de Kubernetes o pregúntale al administrador de la plataforma cuál es el nombre del clúster.
Accede y genera el archivo kubeconfig para el clúster de Kubernetes si no tienes uno.
Usa la ruta de acceso de kubeconfig del clúster de Kubernetes para reemplazar KUBERNETES_CLUSTER_KUBECONFIG en estas instrucciones.
Para obtener los permisos necesarios para escalar cargas de trabajo con estado, pídele al administrador de IAM de tu organización que te otorgue el rol de administrador de espacios de nombres (namespace-admin) en el espacio de nombres de tu proyecto.
Cómo escalar un recurso StatefulSet
Aprovecha la funcionalidad de escalamiento de Kubernetes para escalar de forma adecuada la cantidad de Pods que se ejecutan en tu recurso StatefulSet.
Ajusta manualmente la escala de los Pods de un recurso StatefulSet
Para ajustar manualmente la escala de tu recurso StatefulSet, ejecuta el siguiente comando:
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis document guides users on how to scale stateful workloads within a Kubernetes cluster to meet evolving container requirements.\u003c/p\u003e\n"],["\u003cp\u003eBefore scaling, you need to locate your Kubernetes cluster name, sign in to generate the kubeconfig file, and obtain the Namespace Admin role.\u003c/p\u003e\n"],["\u003cp\u003eYou can manually scale a \u003ccode\u003eStatefulSet\u003c/code\u003e resource by running the \u003ccode\u003ekubectl scale statefulset\u003c/code\u003e command, specifying the cluster's kubeconfig, namespace, \u003ccode\u003eStatefulSet\u003c/code\u003e name, and desired number of replicas.\u003c/p\u003e\n"],["\u003cp\u003eAlternatively, scale the pods by making an in-place update to the \u003ccode\u003eStatefulSet\u003c/code\u003e manifest file using the \u003ccode\u003ekubectl patch statefulsets\u003c/code\u003e command, indicating the kubeconfig, namespace, \u003ccode\u003eStatefulSet\u003c/code\u003e name, and new replica count.\u003c/p\u003e\n"]]],[],null,["# Scale stateful workloads\n\nScale your stateful workloads to your evolving container workload requirements.\n\nBefore you begin\n----------------\n\nTo run commands against a\n[Kubernetes cluster](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/clusters#cluster-architecture),\nmake sure you have the following resources:\n\n1. Locate the Kubernetes cluster name, or ask your Platform Administrator what\n the cluster name is.\n\n2. [Sign in and generate](/distributed-cloud/hosted/docs/latest/gdch/application/ao-user/iam/sign-in#zonal-cluster-kubeconfig)\n the kubeconfig file for the Kubernetes cluster if you don't have one.\n\n3. Use the kubeconfig path of the Kubernetes cluster to replace\n \u003cvar translate=\"no\"\u003eKUBERNETES_CLUSTER_KUBECONFIG\u003c/var\u003e in these instructions.\n\nTo get the required permissions to scale stateful workloads, ask your\nOrganization IAM Admin to grant you the Namespace Admin role (`namespace-admin`)\nin your project namespace.\n\nScale a `StatefulSet` resource\n------------------------------\n\nLeverage the scaling functionality of Kubernetes to appropriately scale the\namount of pods running in your `StatefulSet` resource.\n\n### Manually scale the pods of a `StatefulSet` resource\n\nTo manually scale your `StatefulSet` resource, run: \n\n kubectl --kubeconfig \u003cvar translate=\"no\"\u003eKUBERNETES__CLUSTER_KUBECONFIG\u003c/var\u003e -n \u003cvar translate=\"no\"\u003eNAMESPACE\u003c/var\u003e \\\n scale statefulset \u003cvar translate=\"no\"\u003eSTATEFULSET_NAME\u003c/var\u003e \\\n --replicas \u003cvar translate=\"no\"\u003eNUMBER_OF_REPLICAS\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eKUBERNETES_CLUSTER_KUBECONFIG\u003c/var\u003e: the kubeconfig file for\n the cluster.\n\n- \u003cvar translate=\"no\"\u003eNAMESPACE\u003c/var\u003e: the project namespace.\n\n- \u003cvar translate=\"no\"\u003eSTATEFULSET_NAME\u003c/var\u003e: the name of the `StatefulSet`\n object in which to scale.\n\n- \u003cvar translate=\"no\"\u003eNUMBER_OF_REPLICAS\u003c/var\u003e: the desired number of replicated\n `Pod` objects in the `StatefulSet` object.\n\n### Scale the pods by making an in-place update\n\nTo scale the pods of a `StatefulSet` resource directly in the manifest file,\nrun: \n\n kubectl --kubeconfig \u003cvar translate=\"no\"\u003eKUBERNETES__CLUSTER_KUBECONFIG\u003c/var\u003e -n \u003cvar translate=\"no\"\u003eNAMESPACE\u003c/var\u003e \\\n patch statefulsets \u003cvar translate=\"no\"\u003eSTATEFULSET_NAME\u003c/var\u003e \\\n -p '{\"spec\":{\"replicas\":\u003cvar translate=\"no\"\u003eNUMBER_OF_REPLICAS\u003c/var\u003e}}'\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eKUBERNETES__CLUSTER_KUBECONFIG\u003c/var\u003e: the kubeconfig file for\n the cluster.\n\n- \u003cvar translate=\"no\"\u003eNAMESPACE\u003c/var\u003e: the project namespace.\n\n- \u003cvar translate=\"no\"\u003eSTATEFULSET_NAME\u003c/var\u003e: the name of the `StatefulSet`\n object in which to scale.\n\n- \u003cvar translate=\"no\"\u003eNUMBER_OF_REPLICAS\u003c/var\u003e: the desired number of replicated\n `Pod` objects in the `StatefulSet` object."]]