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-06 UTC."],[[["This document provides instructions for creating the `apigee` Kubernetes namespace, which is essential for running Apigee hybrid components."],["The default namespace for Apigee hybrid is `apigee`, but any namespace can be used as long as it's consistently referenced."],["You can verify if the `apigee` namespace already exists by using the `kubectl get namespace apigee` command."],["If the namespace does not exist, you can create it using the command `kubectl create namespace apigee`."],["After 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."]]],[]]
