No ILB and Cosmos items' deployed

[gallegogti]

Hi,

In the last version 3.4.0, ILB is not being deployed and the Cosmos DB contains all tables mentioned on docs, but no item in any of them.
I've followed the documentation, get the object id from Azure CLI and tried options with "value" and "secret id" from the service application. Unsuccessful in both of them.

[JaydenLiang]

Hi,

In the last version 3.4.0, ILB is not being deployed and the Cosmos DB contains all tables mentioned on docs, but no item in any of them. I've followed the documentation, get the object id from Azure CLI and tried options with "value" and "secret id" from the service application. Unsuccessful in both of them.

We removed the deployment of the internal load balancer since 3.4.0. We leave deploying the ILB as an optional post-deployment integration for users. You can follow the Microsoft documentation to set up the ILB for your own specific use.

For the CosmosDB table and item issue, I assume that you are talking about the Settings table. You need to start the vmss in order to initiate the items in the Settings table.

[gallegogti]

Hi @JaydenLiang, thank you for your response and sorry for the delay to get it back.

Today I tried again and I got the same "errors" and with that, I'll be more specific.

ILB: Ok, got it.
Cosmos DB tables empty: even after I change the VMSS settings and 2 new VMs are up and running, I got no items in Cosmos tables.

I'm assuming the settings for Fortigates are not being loaded, because I can SSH to them so I could check the admin-sport is set to 443 and not for 8443 (as this deployment implies). So in a case of a disaster or problem with one of those vms, I wouldn't have it working, using VMSS.

I followed all the instructions, more than twice, but I couldn't find my mistake... Please if you could guide me... I'm attaching some screenshots.