Questo passaggio spiega come creare lo spazio dei nomi apigee Kubernetes in cui opera la maggior parte dei componenti di Apigee hybrid.
Crea lo spazio dei nomi che verrà utilizzato per la maggior parte delle risorse ibride Apigee.
Deve corrispondere al campo namespace del
file overrides.yaml. Se non è presente in overrides.yaml, il
namespaces predefinito è apigee.
Verifica se lo spazio dei nomi esiste già:
kubectl get namespace apigee
Se lo spazio dei nomi esiste, l'output include:
NAME STATUS AGE
apigee Active 1d
Se lo spazio dei nomi non esiste già, creane uno:
kubectl create namespace apigee
Ora che l'ambiente ibrido ha uno spazio in cui operare, il passaggio successivo consiste nel creare gli account di servizio e le credenziali Google Cloud necessari per configurare i componenti di runtime ibridi.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-05 UTC."],[[["\u003cp\u003eThis document provides instructions for creating the \u003ccode\u003eapigee\u003c/code\u003e Kubernetes namespace, which is essential for running Apigee hybrid components.\u003c/p\u003e\n"],["\u003cp\u003eThe default namespace for Apigee hybrid is \u003ccode\u003eapigee\u003c/code\u003e, but any namespace can be used as long as it's consistently referenced.\u003c/p\u003e\n"],["\u003cp\u003eYou can verify if the \u003ccode\u003eapigee\u003c/code\u003e namespace already exists by using the \u003ccode\u003ekubectl get namespace apigee\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eIf the namespace does not exist, you can create it using the command \u003ccode\u003ekubectl create namespace apigee\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eAfter the namespace is set up, the next step in the process is creating 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.11 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. 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 most\nApigee hybrid components operate.\n\n\nCreate the namespace that will be used for most 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. If you use a different namespace, be sure to replace `apigee` 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\n ```\n\n If the namespace exists, your output includes: \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\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[1](/apigee/docs/hybrid/v1.11/helm-install-create-cluster) [2](/apigee/docs/hybrid/v1.11/helm-install-download-charts) [3](/apigee/docs/hybrid/v1.11/helm-install-create-namespace) [(NEXT) Step 4: Set up service accounts](/apigee/docs/hybrid/v1.11/helm-install-service-accounts) [5](/apigee/docs/hybrid/v1.11/helm-install-create-tls-certificates) [6](/apigee/docs/hybrid/v1.11/helm-install-create-overrides) [7](/apigee/docs/hybrid/v1.11/helm-install-enable-synchronizer-access) [8](/apigee/docs/hybrid/v1.11/helm-install-cert-manager) [9](/apigee/docs/hybrid/v1.11/helm-install-crds) [10](/apigee/docs/hybrid/v1.11/helm-install-check-cluster) [11](/apigee/docs/hybrid/v1.11/helm-install-helm-charts) [12](/apigee/docs/hybrid/v1.11/helm-install-workload-identity)\n\n\u003cbr /\u003e"]]
