EDAS microservices namespaces support the creation of Serverless Application Engine (SAE)–associated namespaces. By default, an SAE-associated namespace is linked to an EDAS microservices namespace and shares the same registry and configuration center. EDAS applications and SAE applications within the same virtual private cloud (VPC) can access each other. This association is visible in the EDAS console.
Prerequisites
Activate SAE.
Create an SAE-associated namespace
Log on to the EDAS console.
In the left navigation pane, choose .
On the right side of the microservices namespace list, click Create SAE-associated Namespace.
Enter a name and ID for the SAE-associated namespace, select a VPC, and then click OK.
Configuration item
Description
Region
The region where the microservices namespace resides. This cannot be changed.
SAE Namespace Name
Enter a name for the microservices namespace.
SAE Namespace ID
Prefix: Cannot be edited. The prefix is generated based on the selected region.
Suffix: You can enter only lowercase letters and digits.
Description
Enter a description for the microservices namespace.
Virtual Private Cloud (VPC)
Displays only the VPC IDs of clusters that contain EDAS applications in the EDAS microservices namespace.
Validation:
New SAE console
Log on to the SAE console.
In the left navigation pane, click Namespaces and view the list.
The namespace is created as expected.
Legacy SAE console
Log on to the SAE console.
In the left navigation pane, click Namespaces (Environments) and view the list.
The creation is successful.
Edit an SAE-associated namespace
New SAE console
Log on to the SAE console.
In the left navigation pane, click Namespaces.
Find the namespace that you want to edit and click Edit in the Actions column.
Change the namespace name and description, and then click OK.
Configuration item
Description
Region
The region where the microservices namespace resides. This cannot be changed.
Namespace Name
Enter the name of the microservices namespace that you want to change.
Namespace ID
The ID was set when you created the SAE-associated namespace. It cannot be changed.
Description
Enter the new description for the namespace.
Validation:
Log on to the EDAS console.
In the left navigation pane, choose .
Hover over the SAE-associated namespace in the microservices namespace list to view the changes.
Legacy SAE console
Log on to the SAE console.
In the left navigation pane, click Namespaces (Environments).
Find the namespace that you want to edit and click Edit in the Actions column.
Change the namespace name and description, and then click OK.
Configuration item
Description
Region
The region where the microservices namespace resides. This cannot be changed.
Namespace Name
Enter the new name for the microservices namespace.
Namespace ID
The ID was set when you created the SAE-associated namespace. It cannot be changed.
Description
Enter the new description for the namespace.
Validation:
Log on to the EDAS console.
In the left navigation pane, choose .
Hover over the SAE-associated namespace in the microservices namespace list to view the changes.
Delete an SAE-associated namespace
New SAE console
Log on to the SAE console.
In the left navigation pane, click Namespaces.
Find the namespace that you want to delete and click Delete in the Actions column.
In the message that appears, click OK. The namespace is deleted.
Validation:
Log on to the EDAS console.
In the left navigation pane, choose .
You can hover over the namespace associated with SAE in the microservices namespace list to confirm that it has been deleted.
Legacy SAE console
Log on to the SAE console.
In the left navigation pane, click Namespaces (Environments).
Click Delete to the right of the target namespace.
In the message that appears, click OK. The namespace is deleted.
Validation:
Log on to the EDAS console.
In the left navigation pane, choose .
In the microservices namespace list, hover over the namespace associated with SAE to view its deletion status.
FAQ
What is the difference between an SAE-associated namespace created in the EDAS console and a standard SAE namespace?
An SAE-associated namespace created in the EDAS console is connected to the corresponding EDAS microservices namespace. This association is visible in the EDAS console. Otherwise, it functions identically to a standard SAE namespace. You can edit and delete it in the SAE console.
You cannot directly delete an EDAS microservices namespace that has an SAE-associated namespace. You must first delete the corresponding namespace in the SAE console before deleting the microservices namespace in the EDAS console.
Why is the VPC list empty when I create an associated namespace?
When creating an SAE-associated namespace, only VPCs that contain EDAS applications are supported.