En este paso, se explica cómo crear el espacio de nombres apigee de Kubernetes en el que operan los componentes de Apigee Hybrid.
Crea el espacio de nombres que se usará para los recursos híbridos de Apigee.
Este debe coincidir con el campo namespace en el archivo overrides.yaml. Si no está presente en overrides.yaml, el espacio de nombres predeterminado es apigee.
Verifica si el espacio de nombres ya existe:
kubectl get namespace APIGEE_NAMESPACE
Si el espacio de nombres existe, el resultado incluirá lo siguiente:
NAME STATUS AGE
apigee Active 1d
Si el espacio de nombres aún no existe, créalo:
kubectl create namespace APIGEE_NAMESPACE
Ahora que el híbrido tiene espacio para operar, el siguiente paso es crear las cuentas de servicio y las credenciales de Google Cloud necesarias para configurar los componentes del entorno de ejecución híbrido.
[[["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-05 (UTC)"],[[["\u003cp\u003eThis content details the creation of the \u003ccode\u003eapigee\u003c/code\u003e Kubernetes namespace, which is where Apigee hybrid components will be deployed and run.\u003c/p\u003e\n"],["\u003cp\u003eThe namespace specified in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file will be used, with \u003ccode\u003eapigee\u003c/code\u003e being the default if no other namespace is given.\u003c/p\u003e\n"],["\u003cp\u003eTo verify if the namespace exists, the command \u003ccode\u003ekubectl get namespace APIGEE_NAMESPACE\u003c/code\u003e is used.\u003c/p\u003e\n"],["\u003cp\u003eIf the \u003ccode\u003eapigee\u003c/code\u003e namespace does not exist, it can be created using \u003ccode\u003ekubectl create namespace APIGEE_NAMESPACE\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eAfter creating the namespace, the subsequent step is to set up the necessary Google Cloud service accounts and credentials for the hybrid runtime components.\u003c/p\u003e\n"]]],[],null,["# Step 3: Create the apigee namespace\n\n| You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nThis step explains how to create the `apigee` Kubernetes namespace in which the\nApigee hybrid components operate.\n\n\nCreate the namespace that will be used for the Apigee hybrid resources.\nThis should match the `namespace` field in the `overrides.yaml`\nfile. If this is not present in `overrides.yaml`, the\ndefault namespace is `apigee`.\n| **Note:** You can use any namespace. `apigee` is the default namespace. Be sure to replace `APIGEE_NAMESPACE` with the name of your namespace in the following commands.\n\n1. Check if the namespace already exists:\n\n ```\n kubectl get namespace APIGEE_NAMESPACE\n ```\n\n If the namespace exists, your output will include: \n\n ```text\n NAME STATUS AGE\n apigee Active 1d\n ```\n2. If the namespace does not already exist, create it:\n\n ```\n kubectl create namespace APIGEE_NAMESPACE\n ```\n\nNow that hybrid has a space to operate in, the next step is to create the Google Cloud\nservice accounts and credentials required to configure hybrid runtime components\n\nNext step\n---------\n\n\u003cbr /\u003e\n\n[1](/apigee/docs/hybrid/v1.14/install-create-cluster) [2](/apigee/docs/hybrid/v1.14/install-download-charts) [3](/apigee/docs/hybrid/v1.14/install-create-namespace) [(NEXT) Step 4: Set up service accounts](/apigee/docs/hybrid/v1.14/install-service-accounts) [5](/apigee/docs/hybrid/v1.14/install-create-tls-certificates) [6](/apigee/docs/hybrid/v1.14/install-create-overrides) [7](/apigee/docs/hybrid/v1.14/install-enable-control-plane-access) [8](/apigee/docs/hybrid/v1.14/install-cert-manager) [9](/apigee/docs/hybrid/v1.14/install-crds) [10](/apigee/docs/hybrid/v1.14/install-helm-charts) [11](/apigee/docs/hybrid/v1.14/install-workload-identity)\n\n\u003cbr /\u003e"]]
