Step 3: Create the apigee namespace

This step explains how to create the apigee Kubernetes namespace in which the Apigee hybrid components operate.

Note: Starting with version 1.13, all Apigee hybrid components run in the same namespace. In versions 1.12 and earlier, the Apigee Controller component ran in a separate apigee-system namespace.

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.

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

Next step

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

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 2024-09-11 UTC.