Nesta etapa, explicaremos como criar o namespace apigee do Kubernetes em que
os componentes da Apigee híbrida operam.
Crie o namespace que será usado para os recursos da Apigee híbrida.
Ele precisa corresponder ao campo namespace no arquivo
overrides.yaml. Se não estiver presente em overrides.yaml, o
namespace padrão será apigee.
Verifique se o namespace já existe:
kubectl get namespace APIGEE_NAMESPACE
Se o namespace existir, a saída incluirá:
NAME STATUS AGE
apigee Active 1d
Se o namespace ainda não existir, crie-o:
kubectl create namespace APIGEE_NAMESPACE
Agora que o modelo híbrido tem um espaço para operar, a próxima etapa é criar as contas de serviço
e as credenciais do Google Cloud necessárias para configurar os componentes do ambiente de execução híbrido
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-18 UTC."],[[["\u003cp\u003eThis content explains the process of creating the \u003ccode\u003eapigee\u003c/code\u003e Kubernetes namespace, which is essential for housing all Apigee hybrid components in versions 1.13 and later.\u003c/p\u003e\n"],["\u003cp\u003eThe namespace specified should match the \u003ccode\u003enamespace\u003c/code\u003e field in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file, with \u003ccode\u003eapigee\u003c/code\u003e as the default if not explicitly defined.\u003c/p\u003e\n"],["\u003cp\u003eYou can verify the existence of the namespace using \u003ccode\u003ekubectl get namespace APIGEE_NAMESPACE\u003c/code\u003e before creating it, which is done via \u003ccode\u003ekubectl create namespace APIGEE_NAMESPACE\u003c/code\u003e if it does not already exist.\u003c/p\u003e\n"],["\u003cp\u003eAll further configurations will be made in the \u003ccode\u003eapigee\u003c/code\u003e namespace.\u003c/p\u003e\n"]]],[],null,["# Step 3: Create the apigee namespace\n\n| You are currently viewing version 1.13 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| **Note:** Starting with version 1.13, all Apigee hybrid components run in the same namespace. In versions 1.12 and earlier, the Apigee Controller component ran in a separate `apigee-system` namespace.\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.13/install-create-cluster) [2](/apigee/docs/hybrid/v1.13/install-download-charts) [3](/apigee/docs/hybrid/v1.13/install-create-namespace) [(NEXT) Step 4: Set up service accounts](/apigee/docs/hybrid/v1.13/install-service-accounts) [5](/apigee/docs/hybrid/v1.13/install-create-tls-certificates) [6](/apigee/docs/hybrid/v1.13/install-create-overrides) [7](/apigee/docs/hybrid/v1.13/install-enable-synchronizer-access) [8](/apigee/docs/hybrid/v1.13/install-cert-manager) [9](/apigee/docs/hybrid/v1.13/install-crds) [10](/apigee/docs/hybrid/v1.13/install-helm-charts) [11](/apigee/docs/hybrid/v1.13/install-workload-identity)\n\n\u003cbr /\u003e"]]
