Cells are complete, independent instances of entire application in Ambassador Cloud. With Cells, your applications are not limited to the standard Development, Staging, and Production lifecycle. Cells give you the freedom to configure the lifecycle what works best for your application.
Ambassador Cloud associates Kubernetes clusters with Cells.
When you first generate an API key for a cluster, and you added that key to your cluster, the cluster will start reporting the services, we will create as many Cells as namespaces you have in your Cluster, the cell names will be the same as the namespaces, If you do not like the names, do not worry you will be able to rename it.
In the Cells Page click in the + New button.
The Cell box is shown on the screen in "rename" state, you should type the Cell name that you prefer and click in Rename.
The new Cell is automatically favorited and is not connected to anything else.
Select the Rename Cell option.
The Cell box is sown on the screen with a field to name the Cell. Enter a name for the Cell and click Rename.
Locate the Cell you want to delete and click in the menu (to delete a Cell is a prerequisite to not have any
cluster:namespaceadded to it, if that's not the case you will need to remove all the
cluster:namespacefrom the Cell).
Select the Delete Cell option.
Create a new Cell or locate the Cell you wish to use.
Now, from the list, select the
cluster:namespacewhere is running your application.
cluster:namespace can be associated to a single Cell, if you associate a
cluster:namespace that is already associated to other Cell, it will be removed from the previous Cell.
Select the Cell where you want to add an existing
It will show a list of the
cluster:namespacesthat are already reported, select and click on the
cluster:namespacethat you want in this Cell.
Locate the Cell that contains the
cluster:namespacethat you want to remove.
Click on the icon from the
cluster:namespacethat you want to remove and then select the destination Cell.
A service moves through many environments during its lifecycle. Typical examples are development, staging, and production, but there are often many more than just these three. For example, different developers or teams may have their own development environment, but share staging and production. Or perhaps there are multiple production environments in different regions. You can model these scenarios by defining cells for each environment and then connecting them in a parent-child relationship to represent how the service flows through development, testing, and production in your particular case.
Locate the Cells you want to connect to define the new relationship.
Select the Cell's connector from the Cell that you identify as start point and draw the line to the Cell that is your end point.
If everything went well, you should be able to see a connection line between the Cells in the graphical view.
You can create as many relationships as you need, from one to one, one to many, or many to many.