This step explains how to create the apigee Kubernetes namespace in which most
Apigee hybrid components operate.
Create the namespace that will be used for most Apigee hybrid resources.
This should match the namespace field in the overrides.yaml
file. If this is not present in overrides.yaml, the
default namespace is apigee.
Check if the namespace already exists:
kubectl get namespace apigee
If the namespace exists, your output includes:
NAME STATUS AGE
apigee Active 1d
If the namespace does not already exist, create it:
kubectl create namespace apigee
Now that hybrid has a space to operate in, the next step is to create the Google Cloud
service accounts and credentials required to configure hybrid runtime components
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eapigee\u003c/code\u003e namespace is where most Apigee hybrid components will operate, and it's the default unless specified otherwise in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file.\u003c/p\u003e\n"],["\u003cp\u003eYou can verify if the \u003ccode\u003eapigee\u003c/code\u003e namespace already exists by using the command \u003ccode\u003ekubectl get namespace apigee\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eIf the \u003ccode\u003eapigee\u003c/code\u003e namespace does not exist, it can be created using the command \u003ccode\u003ekubectl create namespace apigee\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eIf a different namespace is used other than \u003ccode\u003eapigee\u003c/code\u003e, remember to replace the name \u003ccode\u003eapigee\u003c/code\u003e with the namespace's name in all commands.\u003c/p\u003e\n"]]],[],null,["# Step 3: Create the apigee namespace\n\n| You are currently viewing version 1.12 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\nNext step\n---------\n\n\u003cbr /\u003e\n\n[1](/apigee/docs/hybrid/v1.12/install-create-cluster) [2](/apigee/docs/hybrid/v1.12/install-download-charts) [3](/apigee/docs/hybrid/v1.12/install-create-namespace) [(NEXT) Step 4: Set up service accounts](/apigee/docs/hybrid/v1.12/install-service-accounts) [5](/apigee/docs/hybrid/v1.12/install-create-tls-certificates) [6](/apigee/docs/hybrid/v1.12/install-create-overrides) [7](/apigee/docs/hybrid/v1.12/install-enable-synchronizer-access) [8](/apigee/docs/hybrid/v1.12/install-cert-manager) [9](/apigee/docs/hybrid/v1.12/install-crds) [10](/apigee/docs/hybrid/v1.12/install-check-cluster) [11](/apigee/docs/hybrid/v1.12/install-helm-charts) [12](/apigee/docs/hybrid/v1.12/install-workload-identity)\n\n\u003cbr /\u003e"]]