# Spawn Multi-container Ai-Microservices

Workflow for deploying multiple container-based Ai-Microservices:

* Click on "Spawn Microservice" and select the "ISV Management Microservice"

  ![](/files/beX4tYACqGms6Bif3AS2)
* Select DataCentre

  ![](/files/cTXYtaRIXGo7MirL8NQn)

  **Note: If you have an enterprise setup, after selecting datacenter, please select where to deploy i.e. HUB or EDGE**
* Select your plan

  ![](/files/jGjABoUo2lRDPgvU9SKZ)
* Create your own [namespace](/info/1.3.2/more/admin-guide/namespaces.md) prior only and select that

  ![](/files/CfcHfLqyOoabGNbmqTgZ)
* Add environment variables as shown in the figure below

  ![](/files/JvkcOSpXdf176o3LQ1VJ)
* Enter any desired name of your microservice and click on "Spawn Microservice"

  ![](/files/IYArbQ7SbQjWiMxhF2Zw)

{% hint style="info" %}
After completing the previous steps, inform the Zeblok team about the namespace you created. They will provide you with the required access to that namespace.&#x20;
{% endhint %}

Once you receive confirmation via email from the Zeblok Team, please follow these steps:

1. Open the “ISV Management MicroService” that you spawned in a different browser tab
2. Log in using the credentials:
   * **Username: guest**
   * **Password: username**
3. Once logged in, please become the root user and perform the following commands:
   * Run `kubectl get pods -o wide`


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://computationaldocs.zeblok.com/info/1.3.2/procedure/microservice/spawn-multi-container-ai-microservices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
