Step 3: Create the apigee namespace

Version 1.14 (latest)

   Supported versions:

• v1.14 (latest)                        
• v1.13                         
• v1.12                         
• v1.11                         
• List of supported versions

   Unsupported versions:

• v1.10                                      
• v1.9                                         
• v1.8                                         
• v1.7                                         
• v1.6                                         
• v1.5                                         
• v1.4                                         
• v1.3                                         
• v1.2                                         
• v1.1                                         

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.

Note: You can use any namespace. apigee is the default namespace. Be sure to replace APIGEE_NAMESPACE with the name of your namespace in the following commands.

1. 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

2. 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

Next step

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