This step explains how to create the apigee Kubernetes namespace in which the
Apigee hybrid components operate.
Create the namespace that will be used for the 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_NAMESPACE
If the namespace exists, your output will include:
NAME STATUS AGE
apigee Active 1d
If the namespace does not already exist, create it:
kubectl create namespace APIGEE_NAMESPACE
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-03-10 UTC."],[[["This content details the creation of the `apigee` Kubernetes namespace, which is where Apigee hybrid components will be deployed and run."],["The namespace specified in the `overrides.yaml` file will be used, with `apigee` being the default if no other namespace is given."],["To verify if the namespace exists, the command `kubectl get namespace APIGEE_NAMESPACE` is used."],["If the `apigee` namespace does not exist, it can be created using `kubectl create namespace APIGEE_NAMESPACE`."],["After creating the namespace, the subsequent step is to set up the necessary Google Cloud service accounts and credentials for the hybrid runtime components."]]],[]]
