Step 3: Create the apigee namespace

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.

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.

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

1 2 3 (NEXT) Step 4: Set up service accounts 5 6 7 8 9 10 11 12

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-10-16 UTC.

Step 3: Create the apigee namespace Stay organized with collections Save and categorize content based on your preferences.

Step 3: Create the apigee namespace